Re: [Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Phillip Susi]

costales writes:

> Would this hack fix the issue? (Add/Remove xhost +si:localuser:root to the 
> launcher)
> I don't know if this could means something dangerous in Wayland.

I'm not sure if it will fix things run as root via pkexec but it will if
you manually run gui programs as root.  There's no risk involved since
root can already do anything anyhow, including debug the X server and
force it to let them connect.

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in HPLIP:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  Invalid
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  Fix Released
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-

[Touch-packages] [Bug 1609900] Re: Unplugging and re-plugging keyboard forgets xmodmap

[Phillip Susi]

** Summary changed:

- After QEMU execution with keyboard passthrough, key mappings are lost
+ Unplugging and re-plugging keyboard forgets xmodmap

** Package changed: qemu (Ubuntu) => xorg (Ubuntu)

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

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

Title:
  Unplugging and re-plugging keyboard forgets xmodmap

Status in xorg package in Ubuntu:
  New

Bug description:
  [I'm not sure against which package I can report this, so I've
  preliminary done it against `qemu`]

  Since I have a non-standard keyboard (a Kinesis, without Super key), I 
remapped a key on my system (XUbuntu 16.04).
  This is accomplished via:

  ~$ cat ~/.Xmodmap
  keycode 108 = Super_L

  This works fine, but after any qemu execution, with passthrough of my
  USB keyboard, the mapping is lost - more precisely, the system it
  starts behaving like the key is not mapped.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu 1:2.5+dfsg-5ubuntu10.2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Aug  4 19:11:24 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-11 (24 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0  1261 2  0.0 [kvm-irqfd-clean]
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=7f35da3f-4f3a-40e1-8af0-3f02cfbf9884 ro
  SourcePackage: qemu
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Phillip Susi]

Also what does getconf PAGESIZE say under the broken kernel?

-- 
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 1788321] Re: swapon failed: invalid argument

[Phillip Susi]

This doesn't happen on amd64.  Do you also have to re-run mkswap when
switching back to the older, working kernel, or does simply using the
other kernel let you run swapon on the same file that doesn't work with
the newer kernel?


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

** Changed in: util-linux (Ubuntu)
   Status: Confirmed => Invalid

-- 
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 1789166] Re: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Phillip Susi]

You have a broken third party startup script installed named "nifi".
You will need to remove it.


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

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

Title:
  package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.6
  ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Mon Aug 27 12:21:46 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-05-15 (103 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1456579] Re: ubuntu-bug segfaults, Kubuntu 15.04 (100% reproducible - multiple machines)

[Phillip Susi]

15.04 reached end of life years ago.  Are you still seeing this on a
currently supported release?


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

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

Title:
  ubuntu-bug segfaults, Kubuntu 15.04 (100% reproducible - multiple
  machines)

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  On multiple machines ubuntu-bug segfaults if I choose the following
  options

   'other problem' -> 'other display-related problem'

  It immediately 100% of the time segfaults

  i.e

  [325594.232720] apport-kde[14031]: segfault at 38 ip 7f38386f10c3
  sp 7ffdf8a0ae80 error 4 in
  libQt5Core.so.5.4.1[7f383866b000+533000]

  However if I choose

  'other problem' -> 'I don't know'  it does create  bug report.

  Another user in IRC confirmed it was happening to them also.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue May 19 12:06:40 2015
  InstallationDate: Installed on 2015-04-28 (21 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 575542] Re: resize2fs does not respect flex_bg

[Phillip Susi]

You haven't happened to fix this in the last 8 years have you Ted? ;)

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

Title:
  resize2fs does not respect flex_bg

Status in e2fsprogs package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: e2fsprogs

  When running resize2fs to perform an online extend of an ext4
  filesystem, it does not respect the flex_bg feature.  Instead, it lays
  out the added block groups with their normal non flex_bg positions.

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

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

[Touch-packages] [Bug 1679220] Re: Installer pulls packages from other releases in the pool

[Phillip Susi]

I'm not sure there is any legitimate case for booting $RELEASE1 and
trying to have the installer install $RELEASE2.  And even if there were,
you can't do that now anyhow.  It should be as simple as having apt-
cdrom check lsb_release, and only look in that pool directory instead of
searching them all.

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

Title:
  Installer pulls packages from other releases in the pool

Status in apt package in Ubuntu:
  Triaged

Bug description:
  Frequently people reuse a USB stick to install another release, and
  the install fails because apt tries to pull packages from the wrong
  release.  Apt should only be looking in the pool for the current
  release rather than everything it can find.

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

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

[Touch-packages] [Bug 1787824] Re: "rfkill: input handler disabled" boot time 11 seconds.

[Phillip Susi]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

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

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

Title:
  "rfkill: input handler disabled" boot time 11 seconds.

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  My computer is slowly opening, I looked at the output of dmesg and at 11th I 
get this post.
  What i need to do? thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rfkill 2.31.1-0.4ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 19 19:44:21 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libsmartcols1 2.31.1-0.4ubuntu3.1
  InstallationDate: Installed on 2018-08-18 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1787799] Re: package bsdutils 1:2.31.1-0.4ubuntu3 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed')

[Phillip Susi]

Please attach /var/log/apt/term.log


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

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

Title:
  package bsdutils 1:2.31.1-0.4ubuntu3 failed to install/upgrade:
  package bsdutils is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  Attempted to install idle3 when this error occured

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bsdutils 1:2.31.1-0.4ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 18 20:45:10 2018
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package bsdutils is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package bsdutils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-07-21 (28 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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.1
  SourcePackage: util-linux
  Title: package bsdutils 1:2.31.1-0.4ubuntu3 failed to install/upgrade: 
package bsdutils is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 779130] Re: debconf refuses to die

[Phillip Susi]

Wow... 7 years and no response.

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

Title:
  debconf refuses to die

Status in debconf package in Ubuntu:
  New

Bug description:
  Binary package hint: debconf

  Sometimes I go to install mdadm on the livecd and forget to add --no-
  install-recommends so it tries to pull in postfix.  The debconf for
  postfix comes up and I realize my mistake and want to abort, but
  debconf ignores ctrl-c as well as ctrl-z, and even closing the
  terminal window does not kill it, so it holds the apt lock open and
  needs manually killed.

  Trying to reproduce the behavior with dpkg-reconfigure it still
  ignores ctrl-c and ctrl-z, but does die when closing the terminal
  window.

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

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

[Touch-packages] [Bug 1784218] Re: package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 128

[Phillip Susi]

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

** This bug has been marked a duplicate of bug 1780913
   package grub-efi-amd64 2.02-2ubuntu8.1 failed to install/upgrade: installed 
grub-efi-amd64 package post-installation script subprocess returned error exit 
status 128

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

Title:
  package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade:
  installed grub-efi-amd64 package post-installation script subprocess
  returned error exit status 128

Status in debconf package in Ubuntu:
  New
Status in grub2 package in Ubuntu:
  New

Bug description:
  I was booting into Ubuntu, using the default option in grub, and was
  able to enter my password in the login screen, but the displays
  started flickering a lot, and there were a lot of repeated text
  messages (it switched into text mode).  I finally did a hard reset and
  tried booting into ubuntu - generic which seemed to work.  There was a
  prompt from apt to update, so I did, and then I got this error
  message.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: grub-efi-amd64 2.02-2ubuntu8.2
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Jul 29 06:00:14 2018
  ErrorMessage: installed grub-efi-amd64 package post-installation script 
subprocess returned error exit status 128
  InstallationDate: Installed on 2017-11-11 (259 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=a68c1ee5-ce8a-4eed-b95f-7625f3118746 ro quiet splash vt.handoff=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.3
  SourcePackage: grub2
  Title: package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: 
installed grub-efi-amd64 package post-installation script subprocess returned 
error exit status 128
  UpgradeStatus: Upgraded to bionic on 2018-06-23 (35 days ago)

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

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

[Touch-packages] [Bug 1786629] Re: package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1

[Phillip Susi]

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

** This bug has been marked a duplicate of bug 1780913
   package grub-efi-amd64 2.02-2ubuntu8.1 failed to install/upgrade: installed 
grub-efi-amd64 package post-installation script subprocess returned error exit 
status 128

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

Title:
  package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade:
  installed grub-efi-amd64 package post-installation script subprocess
  returned error exit status 1

Status in debconf package in Ubuntu:
  New

Bug description:
  while upgrading to Ubantu 18.04 version pc hanged and it did not orked
  even after leaving for hours

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: grub-efi-amd64 2.02-2ubuntu8.2
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sat Aug 11 22:33:39 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: installed grub-efi-amd64 package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-04-30 (103 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic.efi.signed 
root=UUID=51e2afee-e9ee-4527-adf4-853e7c5827d5 ro acpi_rev_override quiet 
splash vt.handoff=7
  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.3
  SourcePackage: grub2
  Title: package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: 
installed grub-efi-amd64 package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (0 days ago)

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

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

[Touch-packages] [Bug 1788030] [NEW] Only 800x600 resolution available after install

[Phillip Susi]

Public bug reported:

Boot 18.04 iso inside a qemu vm using stdvga display.  A usable
resolution works fine in live cd, but after installing to the hard disk
and rebooting, only 800x600 is available.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 20 16:10:44 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Device [1234:] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc Device [1af4:1100]
InstallationDate: Installed on 2018-08-20 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
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: Xen HVM domU
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=dd1777df-63a5-474f-94a7-2240033e0a9b ro quiet splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/16/2018
dmi.bios.vendor: Xen
dmi.bios.version: 4.9.2
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias: 
dmi:bvnXen:bvr4.9.2:bd04/16/2018:svnXen:pnHVMdomU:pvr4.9.2:cvnXen:ct1:cvr:
dmi.product.name: HVM domU
dmi.product.version: 4.9.2
dmi.sys.vendor: Xen
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic resolution ubuntu

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

Title:
  Only 800x600 resolution available after install

Status in xorg package in Ubuntu:
  New

Bug description:
  Boot 18.04 iso inside a qemu vm using stdvga display.  A usable
  resolution works fine in live cd, but after installing to the hard
  disk and rebooting, only 800x600 is available.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 20 16:10:44 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Device [1234:] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc Device [1af4:1100]
  InstallationDate: Installed on 2018-08-20 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=dd1777df-63a5-474f-94a7-2240033e0a9b ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2018
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.9.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.9.2:bd04/16/2018:svnXen:pnHVMdomU:pvr4.9.2:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.9.2
  dmi.sys.vendor: Xen
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.l

[Touch-packages] [Bug 1776622] Re: snapd on cosmic never finishes installing/updating. Can't install any other updates.

[Phillip Susi]

Since ctrl-c doesn't seem to work to interrupt the upgrade, I had to
ctrl-z and I checked pstree.  It seems that the init script runs
systemctl, which runs systemd-tty-ask-password-agent, and that hangs,
never presenting a prompt.  I tried to kill that and it became a zombie,
never being reaped by systemctl.


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

Title:
  snapd on cosmic never finishes installing/updating. Can't install any
  other updates.

Status in snapd:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't
  install any other updates.

  The first time I gave up waiting and killed it. Then...

  $ sudo apt full-upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  $ sudo dpkg --configure -a
  Setting up snapd (2.33+18.10ubuntu3) ...
  snapd.snap-repair.service is a disabled or a static unit, not starting it.

  << never ends >>

  All the while the snap and snapd process use about 0.3% CPU (which is
  more than usual).

  WORKAROUND:

  sudo killall apt dpkg
  sudo dpkg -r snapd gnome-software-plugin-snap
  sudo apt update
  sudo apt full-upgrade

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: snapd 2.33+18.10ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Wed Jun 13 16:49:20 2018
  InstallationDate: Installed on 2018-05-26 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Phillip Susi]

On 8/15/2018 11:46 AM, bodhi.zazen wrote:
> Phillip: I don't know why they even allow you to speak on this thread.
> Please stop spreading misinformation .

Go stand in front of a mirror.  That is the person spreading
misinformation.

> Your gdm3 / XAUTHORITY "bug" has been closed as obsolete, it does not
> work the way you envision.
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=789867

No, it hasn't... it has been migrated to the new bug tracker.

> Yes it was migrated, but there is no acknowledgement in the new location
> that your gdm3 / XAUTHORITY "bug" is going to get addressed in the new
> location and, as with your other "bugs", will be closed .
> 
> The other "bug" you claimed earlier was closed as "not a bug"
> 
> https://bugs.freedesktop.org/show_bug.cgi?id=91071

That isn't mine, and it was closed because it was filed against
Xwayland, which is not where the bug is.  Xwayland is doing what it was
told to do by gdm3.

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  Invalid
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  Fix Released
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to

[Touch-packages] [Bug 1786629] Re: package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1

[Phillip Susi]

It looks like grub tried to ask a question and debconf ran the gtk
frontend and somehow dropped you to a subshell, which you typed exit
from, then the gtk frontend errored out, causing the grub script to
return the error.


** Package changed: grub2 (Ubuntu) => debconf (Ubuntu)

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

Title:
  package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade:
  installed grub-efi-amd64 package post-installation script subprocess
  returned error exit status 1

Status in debconf package in Ubuntu:
  New

Bug description:
  while upgrading to Ubantu 18.04 version pc hanged and it did not orked
  even after leaving for hours

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: grub-efi-amd64 2.02-2ubuntu8.2
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sat Aug 11 22:33:39 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: installed grub-efi-amd64 package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-04-30 (103 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic.efi.signed 
root=UUID=51e2afee-e9ee-4527-adf4-853e7c5827d5 ro acpi_rev_override quiet 
splash vt.handoff=7
  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.3
  SourcePackage: grub2
  Title: package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: 
installed grub-efi-amd64 package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-08-11 (0 days ago)

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

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

[Touch-packages] [Bug 1786465] Re: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Phillip Susi]

You have a broken third party init script named ".depend.boot" and
".depend.start" that you will need to remove.


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

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

Title:
  package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  I dont know, it was a automatic update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.6
  ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Thu Aug  9 11:57:45 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-02-26 (164 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Phillip Susi]

On 8/6/2018 12:57 PM, PeterPall wrote:
> This isn't a bug but a major feature of wayland: If you have root rights
> you no more get access to the graphical user interface which makes it
> harder for a gui application to spy on another application's keyboard
> input. The backdraw of this is that every application that needs root
> rights for its work has to be re-written to have 2 parts:

No Peter, this is incorrect.  Wayland is just fine with programs running
as root.  The bug is in gdm3 which is supposed to generate an Xorg
configuration that sets up XAUTHORITY.  Instead when it configures the
Xwayland X11 compatibility server, it configures it to check UID instead
of using XAUTHORITY.  The result is that X11 apps running as root fail
to work, but native Wayland/GTK3 applications run as root work just fine.

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  Invalid
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  Fix Released
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: ca

[Touch-packages] [Bug 1783757] Re: shrinking previous file systems makes them corrupted

[Phillip Susi]

** Package changed: ubiquity (Ubuntu) => e2fsprogs (Ubuntu)

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

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

Title:
  shrinking previous file systems makes them corrupted

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Booted in UEFI mode, running test example 'Install (auto-resize) in
  Kubuntu Desktop amd64 in Bionic Daily' the previous file system was
  shrunk in order to create space for the current one. But it was
  corrupted and must be fixed.

  Workaround: sudo e2fsck -f /dev/sda2

  The same thing happened when booted  in UEFI mode, running test
  example 'Install (manual partitioning) in Kubuntu Desktop amd64 in
  Bionic Daily'

  Workaround: sudo e2fsck -f /dev/sda3

  (This current operating system's file system was fixed and made
  bootable again.)

  ---
  tester@tester-SATELLITE-PRO-C850-19W:~$ sudo parted -ls
  [sudo] password for tester: 
  Model: ATA KINGSTON SUV400S (scsi)
  Disk /dev/sda: 120GB
  Sector size (logical/physical): 512B/4096B
  Partition Table: gpt
  Disk Flags: 

  Number  Start   End SizeFile system  Name  Flags
   1  2098kB  317MB   315MB   fat32  boot, esp
   2  317MB   20,3GB  20,0GB  ext4
   3  20,3GB  45,9GB  25,6GB  ext4
   4  45,9GB  107GB   61,4GB  ext4

  
  tester@tester-SATELLITE-PRO-C850-19W:~$ sudo lsblk -fm
  NAME   FSTYPE LABEL UUID MOUNTPOINT   SIZE 
OWNER GROUP MODE
  sda 111,8G 
root  disk  brw-rw
  ├─sda1 vfat 6106-B035/boot/efi300M 
root  disk  brw-rw
  ├─sda2 ext4 d6df56de-4490-4508-beb4-8259dda193c4 18,6G 
root  disk  brw-rw
  ├─sda3 ext4 e375e0d6-e162-4136-af21-377a635761a8 /   23,9G 
root  disk  brw-rw
  └─sda4 ext4 646734a2-45bf-4000-815e-31bbafcdfd29 57,2G 
root  disk  brw-rw
  sr0  1024M 
root  cdrom brw-rw
  tester@tester-SATELLITE-PRO-C850-19W:~$ ubuntu-bug ubiquity
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Jul 26 14:01:38 2018
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
boot=casper maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2018-07-26 (0 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1784597] Re: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Phillip Susi]

You have a broken third party init script named "smfpd" installed.  You
will need to remove it.


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

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

Title:
  package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Quando faço a atualização, a tela de vídeo fica toda escura e
  listrada... tenho que fazer o reboot direto no botão do gabinete, pois
  não consigo ver nada do que está acontecendo na tela.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.6
  ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-45-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  Date: Tue Jul 31 06:40:49 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-03-19 (134 days ago)
  InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1784218] Re: package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 128

[Phillip Susi]

Looks like some more debconf breakage:

Use of uninitialized value $reply in scalar chomp at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66,  line 10.
Use of uninitialized value $reply in concatenation (.) or string at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67,  line 10.
Use of uninitialized value $reply in split at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68,  line 10.
Use of uninitialized value in string eq at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 202,  line 10.
Use of uninitialized value $reply in scalar chomp at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66,  line 10.
Use of uninitialized value $reply in concatenation (.) or string at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67,  line 10.
Use of uninitialized value $reply in split at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68,  line 10.
Use of uninitialized value $ret in string eq at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 212,  line 10.
Use of uninitialized value $_[1] in join or string at 
/usr/share/perl5/Debconf/DbDriver/Stack.pm line 111,  line 10.


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

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

Title:
  package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade:
  installed grub-efi-amd64 package post-installation script subprocess
  returned error exit status 128

Status in debconf package in Ubuntu:
  New
Status in grub2 package in Ubuntu:
  New

Bug description:
  I was booting into Ubuntu, using the default option in grub, and was
  able to enter my password in the login screen, but the displays
  started flickering a lot, and there were a lot of repeated text
  messages (it switched into text mode).  I finally did a hard reset and
  tried booting into ubuntu - generic which seemed to work.  There was a
  prompt from apt to update, so I did, and then I got this error
  message.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: grub-efi-amd64 2.02-2ubuntu8.2
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Jul 29 06:00:14 2018
  ErrorMessage: installed grub-efi-amd64 package post-installation script 
subprocess returned error exit status 128
  InstallationDate: Installed on 2017-11-11 (259 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=a68c1ee5-ce8a-4eed-b95f-7625f3118746 ro quiet splash vt.handoff=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.3
  SourcePackage: grub2
  Title: package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: 
installed grub-efi-amd64 package post-installation script subprocess returned 
error exit status 128
  UpgradeStatus: Upgraded to bionic on 2018-06-23 (35 days ago)

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

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

[Touch-packages] [Bug 1780913] Re: package grub-efi-amd64 2.02-2ubuntu8.1 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 128

[Phillip Susi]

This looks like breakage in debconf:

Use of uninitialized value $reply in scalar chomp at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66,  line 10.
Use of uninitialized value $reply in concatenation (.) or string at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67,  line 10.
Use of uninitialized value $reply in split at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68,  line 10.
Use of uninitialized value in string eq at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 202,  line 10.
Use of uninitialized value $reply in scalar chomp at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66,  line 10.
Use of uninitialized value $reply in concatenation (.) or string at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67,  line 10.
Use of uninitialized value $reply in split at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68,  line 10.
Use of uninitialized value $ret in string eq at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 212,  line 10.
Use of uninitialized value $_[1] in join or string at 
/usr/share/perl5/Debconf/DbDriver/Stack.pm line 111,  line 10.


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

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

Title:
  package grub-efi-amd64 2.02-2ubuntu8.1 failed to install/upgrade:
  installed grub-efi-amd64 package post-installation script subprocess
  returned error exit status 128

Status in debconf package in Ubuntu:
  New
Status in grub2 package in Ubuntu:
  Confirmed

Bug description:
  Maybe I discontinued the actual installation of grub.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: grub-efi-amd64 2.02-2ubuntu8.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jul 10 15:13:27 2018
  ErrorMessage: installed grub-efi-amd64 package post-installation script 
subprocess returned error exit status 128
  InstallationDate: Installed on 2017-05-27 (408 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=91216df1-ea26-4117-af3a-2ba8790880fc ro quiet splash nouveau.runpm=0 
vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.2
  SourcePackage: grub2
  Title: package grub-efi-amd64 2.02-2ubuntu8.1 failed to install/upgrade: 
installed grub-efi-amd64 package post-installation script subprocess returned 
error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1781608] Re: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Phillip Susi]

You have a broken third party init script installed named "discagent".
You will need to remove it.


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

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

Title:
  package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Was part of a group of packages that apt-get upgrade pulled down.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.4
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri Jul 13 10:21:56 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-06-26 (17 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.10ubuntu1
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.pam.d.runuser: 2018-07-12T17:51:21.962750

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

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

[Touch-packages] [Bug 1782262] Re: systemd's default critical battery policy is to hybrid suspend

[Phillip Susi]

Oh, and there is no way to change this behavior in the GUI despite it
being there in previous releases; gnome seems to continue to remove
useful features and dumb down the gui to uselessness.

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

Title:
  systemd's default critical battery policy is to hybrid suspend

Status in systemd package in Ubuntu:
  New

Bug description:
  Despite the fact that hibernation is not officially supported, and
  does not work out of the box ( and still does not seem to work even
  after I manually added the resume= kernel parameter ), the default
  policy of systemd on a critical battery level is to perform a hybrid
  suspend, wasting time and power writing ram to disk that will never be
  resumed.

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

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

[Touch-packages] [Bug 1782262] [NEW] systemd's default critical battery policy is to hybrid suspend

[Phillip Susi]

Public bug reported:

Despite the fact that hibernation is not officially supported, and does
not work out of the box ( and still does not seem to work even after I
manually added the resume= kernel parameter ), the default policy of
systemd on a critical battery level is to perform a hybrid suspend,
wasting time and power writing ram to disk that will never be resumed.

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

Title:
  systemd's default critical battery policy is to hybrid suspend

Status in systemd package in Ubuntu:
  New

Bug description:
  Despite the fact that hibernation is not officially supported, and
  does not work out of the box ( and still does not seem to work even
  after I manually added the resume= kernel parameter ), the default
  policy of systemd on a critical battery level is to perform a hybrid
  suspend, wasting time and power writing ram to disk that will never be
  resumed.

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

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

[Touch-packages] [Bug 1752876] Re: sfdisk: allow disabling boot flag on MBR partition table

[Phillip Susi]

Say, how does moving to sfdisk help?  It still has to be run as root.
You might consider using partman, which is the libparted wrapper program
that allows debian-installer to make libparted calls from bash scripts.
It takes commands and gives replies via a pair of named pipes.

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

Title:
  sfdisk: allow disabling boot flag on MBR partition table

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  I would like to propose the following patch for Ubuntu 18.04 LTS

  
  
https://github.com/karelzak/util-linux/commit/8175ed3d74adacc895657ded7546cb3c5deeabad


  [Impact]

   * This patch allows to use sfdisk to remove boot flag from all MBR 
partitions.
  At the moment you can only "move" boot flag to other partitions.

  
   * Derivatives of Ubuntu that use Calamares might be impacted by this. At the 
moment
  KDE Partition Manager and KPMcore (which is used by Calamares installer) are 
working on migrating to Polkit, so that they won't need to run GUI as root. One 
of the steps was moving from libparted backend to sfdisk backend for 
partitioning operations, so kpmcore will require 2.32 or 2.31.1 with this patch 
to have full functionality.

  
  [Test Case]

  Assuming that your want to deactivate boot flag on /dev/sdb which has
  MBR partition table:

  sudo sfdisk --activate /dev/sdb -

  Without this patch you should see an error message.

  With the patch it will print:


 
  The bootable flag on partition 1 is disabled now. 





  The partition table has been altered. 


  Calling ioctl() to re-read partition table.   


  Syncing disks.


  [Regression Potential]
  .
   * Should be extremely low. The change only adds a couple of lines in one file
  which parses arguments of "sfdisk --activate". Nothing would change unless you
  run sfdisk --activate

   * This patch does not change any libraries in util-linux, no need to
  worry about API/ABI stability.

   * GPT users are not affected at all.

  
  [Other Info]
   * This patch is part of util-linux 2.32.

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

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

[Touch-packages] [Bug 1779129] Re: package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] failed to install/upgrade: package libfdisk1:amd64 is not ready for conf

[Phillip Susi]

** Package changed: util-linux (Ubuntu) => apt (Ubuntu)

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

Title:
  package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-
  gnu/libfdisk.so.1.1.0] failed to install/upgrade: package
  libfdisk1:amd64 is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in apt package in Ubuntu:
  New

Bug description:
  i was installing latex-maker and as it ended i got that error.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: 
lib/x86_64-linux-gnu/libfdisk.so.1.1.0]
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu Jun 28 07:03:23 2018
  DpkgTerminalLog:
   dpkg: error processing package libfdisk1:amd64 (--configure):
package libfdisk1:amd64 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package libfdisk1:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-06-18 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: util-linux
  Title: package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: 
lib/x86_64-linux-gnu/libfdisk.so.1.1.0] failed to install/upgrade: package 
libfdisk1:amd64 is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1773334] Re: Ubuntu 18.04 mounted network shares not appearing under devices in file manager

[Phillip Susi]

I have patched glib to fix this.  Could you try the version in my PPA
and verify that it works?

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

Title:
  Ubuntu 18.04 mounted network shares not appearing under devices in
  file manager

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Apologies if this is not the correct package to file this
  bug/regression against.

  On my 18.04 desktop installs (Gnome shell and Ubuntu Mate) when
  mounting network shares (SMB and NFS) they no longer appear under
  Devices in file manager (Nautilus or Caja), the mounts do succeed and
  are accessible at their mount points.

  In 16.04 and 17.10 these mounts appeared under Devices (Screenshot of
  mounted network shares on Ubuntu Mate 17.10 attached)

  I am using the following code to mount NFS shares

  `sudo mount.nfs 192.168.2.123:/mnt/freenas-data1/photobackup
  /media/philroche/photobackup`

  and for SMB shares

  `sudo mount.cifs //192.168.2.123/photobackup
  /media/philroche/photobackup`

  Is this a bug/regression, or perhaps it is an intentional change?

  I did ask this on IRC in #ubuntu and askubuntu.com but no reply.

  Expected behaviour:

  I expected the mounted network shares to appear under Devices in File
  manager

  Actual behaviour:

  Mounting network shares does succeed as expected but does not appear
  under Devices in File manager as it did in previous releases.

  Requested details:

  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  udisks2:
Installed: 2.7.6-3
Candidate: 2.7.6-3
Version table:
   *** 2.7.6-3 500
  500 http://ie.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1773334] Re: Ubuntu 18.04 mounted network shares not appearing under devices in file manager

[Phillip Susi]

Reported upstream: https://gitlab.gnome.org/GNOME/glib/issues/1424


** Package changed: udisks2 (Ubuntu) => glib2.0 (Ubuntu)

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Ubuntu 18.04 mounted network shares not appearing under devices in
  file manager

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Apologies if this is not the correct package to file this
  bug/regression against.

  On my 18.04 desktop installs (Gnome shell and Ubuntu Mate) when
  mounting network shares (SMB and NFS) they no longer appear under
  Devices in file manager (Nautilus or Caja), the mounts do succeed and
  are accessible at their mount points.

  In 16.04 and 17.10 these mounts appeared under Devices (Screenshot of
  mounted network shares on Ubuntu Mate 17.10 attached)

  I am using the following code to mount NFS shares

  `sudo mount.nfs 192.168.2.123:/mnt/freenas-data1/photobackup
  /media/philroche/photobackup`

  and for SMB shares

  `sudo mount.cifs //192.168.2.123/photobackup
  /media/philroche/photobackup`

  Is this a bug/regression, or perhaps it is an intentional change?

  I did ask this on IRC in #ubuntu and askubuntu.com but no reply.

  Expected behaviour:

  I expected the mounted network shares to appear under Devices in File
  manager

  Actual behaviour:

  Mounting network shares does succeed as expected but does not appear
  under Devices in File manager as it did in previous releases.

  Requested details:

  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  udisks2:
Installed: 2.7.6-3
Candidate: 2.7.6-3
Version table:
   *** 2.7.6-3 500
  500 http://ie.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1773691] Re: software-properties-gtk --massive-debug does not output any information when switching graphics drivers

[Phillip Susi]

** Package changed: gparted (Ubuntu) => software-properties (Ubuntu)

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

Title:
  software-properties-gtk --massive-debug does not output any
  information when switching graphics drivers

Status in software-properties package in Ubuntu:
  New

Bug description:
  Running the command 'sudo software-properties-gtk --massive-debug' and
  switching from nouveau to nvidia graphics drivers or vice-versa does
  not output any information about the process. It should log what is
  being done exactly.

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

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

[Touch-packages] [Bug 1773583] Re: errno 5

[Phillip Susi]

I don't see any errors about being able to read the disk, or that ubiquity even 
crashed.  What I do see is your log spammed full of lines like this:
May 26 20:55:51 ubuntu systemd-udevd[16997]: Process 'hid2hci --method=dell 
--devpath=/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0' failed 
with exit code 1.
May 26 20:55:51 ubuntu upowerd[1500]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0

Which appear to be a problem with a program in the bluez package.


** Package changed: ubiquity (Ubuntu) => bluez (Ubuntu)

** Summary changed:

- errno 5
+ hid2hci spamming log with error messages

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

Title:
  hid2hci spamming log with error messages

Status in bluez package in Ubuntu:
  New

Bug description:
  unable to read disk

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.14
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 02:25:39 2018
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   LANGUAGE=en_IN
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1773438] Re: packagekitd is locking /var/lib/dpkg/lock

[Phillip Susi]

That is normal; it is manipulating the dpkg database.


** Package changed: gparted (Ubuntu) => packagekit (Ubuntu)

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

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

Title:
  packagekitd is locking /var/lib/dpkg/lock

Status in packagekit package in Ubuntu:
  Invalid

Bug description:
  root@ubuntu:~# apt dist-upgrade
  E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily 
unavailable)
  E: Unable to lock the administration directory (/var/lib/dpkg/), is another 
process using it?

  root@ubuntu:~# fuser /var/lib/dpkg/lock 
  /var/lib/dpkg/lock:   2738

  root@ubuntu:~# ps aux
  USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  root  2738 12.4  0.5 491528 90328 ?Ssl  21:02   0:19 
/usr/lib/packagekit/packagekitd

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

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

[Touch-packages] [Bug 1771216] Re: Disabling one of multiple wlan chipsets

[Phillip Susi]

** Package changed: util-linux (Ubuntu) => network-manager (Ubuntu)

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

Title:
  Disabling one of multiple wlan chipsets

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have attached multiple WLANs to my computer. One is build-in (pci) and one 
is connected via usb.
  The Ubuntu Gnome GUI shows 2 WLANs and for both a different signal strength. 
  When however I disable one of the WLANs via the "Turn Off" option, it is 
expected that only this WLAN is deactivated, however both WLANs get disabled at 
the same time. When enabling one of them afterwards, both get enabled again. 
  There does not seem to be a way to disable one of them alone. 

  lspci
  00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge
  00:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI 
bridge (int gfx)
  00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI 
bridge (PCIE port 0)
  00:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI 
bridge (PCIE port 3)
  00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI 
bridge (PCIE port 4)
  00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]
  00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB 
OHCI1 Controller
  00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB 
OHCI1 Controller
  00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller 
(rev 3a)
  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
  00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
LPC host controller
  00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI 
Bridge
  00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 11h Processor 
HyperTransport Configuration (rev 40)
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 11h Processor 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 11h Processor 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 11h Processor 
Miscellaneous Control
  00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 11h Processor 
Link Control
  01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RS780M [Mobility Radeon HD 3200]
  02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8042 PCI-E Fast 
Ethernet Controller (rev 10)
  06:00.0 Network controller: Broadcom Limited BCM4322 802.11a/b/g/n Wireless 
LAN Controller (rev 01)

  lsusb
  Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 002: ID 04f2:b083 Chicony Electronics Co., Ltd CKF7063 Webcam 
(HP)
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 006 Device 002: ID 03f0:171d Hewlett-Packard Bluetooth 2.0 Interface 
[Broadcom BCM2045]
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 005: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 046d:c019 Logitech, Inc. Optical Tilt Wheel Mouse
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rfkill 2.31.1-0.4ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 14 23:15:51 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libsmartcols1 2.31.1-0.4ubuntu3
  InstallationDate: Installed on 2016-12-24 (506 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (2 days ago)

To manage notifications about this bug g

[Touch-packages] [Bug 1769343] Re: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Phillip Susi]

You have a broken third party init script named "noip" installed.  You
will have to remove it.


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

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

Title:
  package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  i dont'know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.4
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sat May  5 15:43:53 2018
  DpkgHistoryLog:
   Start-Date: 2018-05-05  15:43:49
   Commandline: apt-get install xrdp
   Requested-By: sv2hrt (1000)
   Install: vnc4server:i386 (4.1.1+xorg4.3.0-37.3ubuntu2, automatic), 
xbase-clients:i386 (1:7.7+13ubuntu3, automatic), xrdp:i386 (0.6.1-2)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-10-03 (945 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1768941] Re: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime

[Phillip Susi]

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

** This bug has been marked a duplicate of bug 1768933
   package uuid-runtime 2.20.1-5.1ubuntu20.9 failed to install/upgrade: 
pre-dependency problem - not installing uuid-runtime

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

Title:
  package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre-
  dependency problem - not installing uuid-runtime

Status in util-linux package in Ubuntu:
  New

Bug description:
  Encountered error message about this after upgrading from 14.04.05 to
  18

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: uuid-runtime 2.27.1-6ubuntu3.4
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu May  3 17:57:04 2018
  ErrorMessage: pre-dependency problem - not installing uuid-runtime
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: util-linux
  Title: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: 
pre-dependency problem - not installing uuid-runtime
  UpgradeStatus: Upgraded to xenial on 2018-05-03 (0 days ago)

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

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

[Touch-packages] [Bug 1768943] Re: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime

[Phillip Susi]

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

** This bug is no longer a duplicate of bug 1768941
   package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: 
pre-dependency problem - not installing uuid-runtime
** This bug has been marked a duplicate of bug 1768933
   package uuid-runtime 2.20.1-5.1ubuntu20.9 failed to install/upgrade: 
pre-dependency problem - not installing uuid-runtime

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

Title:
  package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre-
  dependency problem - not installing uuid-runtime

Status in util-linux package in Ubuntu:
  New

Bug description:
  Encountered error message about this after upgrading from 14.04.05 to
  16

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: uuid-runtime 2.27.1-6ubuntu3.4
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu May  3 17:57:04 2018
  ErrorMessage: pre-dependency problem - not installing uuid-runtime
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: util-linux
  Title: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: 
pre-dependency problem - not installing uuid-runtime
  UpgradeStatus: Upgraded to xenial on 2018-05-03 (0 days ago)

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

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

[Touch-packages] [Bug 1768933] Re: package uuid-runtime 2.20.1-5.1ubuntu20.9 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime

[Phillip Susi]

It looks like you upgraded from trusty to xenial then to bionic.  Were
there errors during the upgrade to xenial?  It does not appear to have
completed correctly since you still have the Trusty version of libuuid1
installed.


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

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

Title:
  package uuid-runtime 2.20.1-5.1ubuntu20.9 failed to install/upgrade:
  pre-dependency problem - not installing uuid-runtime

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  Encountered error message about this after upgrading from 14.04.05 to
  18

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: uuid-runtime 2.20.1-5.1ubuntu20.9
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu May  3 17:57:04 2018
  ErrorMessage: pre-dependency problem - not installing uuid-runtime
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: util-linux
  Title: package uuid-runtime 2.20.1-5.1ubuntu20.9 failed to install/upgrade: 
pre-dependency problem - not installing uuid-runtime
  UpgradeStatus: Upgraded to xenial on 2018-05-03 (0 days ago)

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

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

[Touch-packages] [Bug 1767774] Re: package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Phillip Susi]

You have a broken third party init script named "tomcat7" that you will
need to remove.


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

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

Title:
  package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  this bug appearde in ubuntu3.5 unlike others which seems to be 3.1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.5
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Sun Apr 29 12:04:16 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-04-06 (22 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1767982] Re: package libmount1:i386 2.31.1-0.4ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura

[Phillip Susi]

Does this actually have anything to do with util-linux?  What makes dpkg
give this error message?


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

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

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

Title:
  package libmount1:i386 2.31.1-0.4ubuntu3 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  Since my last update, i'm getting this error every time when i want to
  install something.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libmount1:i386 2.31.1-0.4ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Apr 30 11:29:35 2018
  DpkgTerminalLog:
   dpkg: error processing package libmount1:i386 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-11-17 (163 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: util-linux
  Title: package libmount1:i386 2.31.1-0.4ubuntu3 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1767331] Re: package uuid-runtime 2.31.1-0.4ubuntu3 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.

[Phillip Susi]

** Package changed: util-linux (Ubuntu) => glib2.0 (Ubuntu)

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

Title:
  package uuid-runtime 2.31.1-0.4ubuntu3 failed to install/upgrade: O
  pacote está num mau estado de inconsistência; deve  reinstala-lo antes
  de tentar configura-lo.

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  i dont know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: uuid-runtime 2.31.1-0.4ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Fri Apr 27 07:46:33 2018
  ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  InstallationDate: Installed on 2018-03-15 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180314)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Arquivo ou diretório inexistente: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: util-linux
  Title: package uuid-runtime 2.31.1-0.4ubuntu3 failed to install/upgrade: O 
pacote está num mau estado de inconsistência; deve  reinstala-lo antes de 
tentar configura-lo.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1763473] Re: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Phillip Susi]

You have a broken third party init script installed named runlcactivator
that you will need to remove.


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

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

Title:
  package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  COMMAND GIVEN WAS: sudo apt-get -y dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.4
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Apr 12 23:46:46 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-12-11 (122 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.24
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1762813] Re: package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Phillip Susi]

You have broken third party init scripts installed named
.depend.{boot,start,stop} that you will need to remove.


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

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

Title:
  package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Regular software upgrade fails

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.5
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Tue Apr 10 20:02:57 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-10-17 (906 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (619 days ago)

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

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

[Touch-packages] [Bug 1762355] Re: package util-linux 2.30.1-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Phillip Susi]

Please run ls -l /usr/bin/nodejs and show the output.


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

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

Title:
  package util-linux 2.30.1-0ubuntu4.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  For a few weeks, I periodically receive this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: util-linux 2.30.1-0ubuntu4.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  AptOrdering:
   util-linux:amd64: Configure
   libvorbisidec1:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Apr  9 10:38:12 2018
  DpkgHistoryLog:
   Start-Date: 2018-04-09  10:38:12
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: libvorbisidec1:amd64 (1.0.2+svn18153-1, 
1.0.2+svn18153-1+deb9u1build0.17.10.1)
  DpkgTerminalLog:
   Setting up util-linux (2.30.1-0ubuntu4.1) ...
   update-alternatives: error: cannot stat file '/usr/bin/nodejs': Too many 
levels of symbolic links
   dpkg: error processing package util-linux (--configure):
subprocess installed post-installation script returned error exit status 2
  DuplicateSignature:
   package:util-linux:2.30.1-0ubuntu4.1
   Setting up util-linux (2.30.1-0ubuntu4.1) ...
   update-alternatives: error: cannot stat file '/usr/bin/nodejs': Too many 
levels of symbolic links
   dpkg: error processing package util-linux (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2017-03-08 (396 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: util-linux
  Title: package util-linux 2.30.1-0ubuntu4.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: Upgraded to artful on 2017-10-22 (168 days ago)

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

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

[Touch-packages] [Bug 1760283] Re: package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Phillip Susi]

You have a broken custom init script named "start_my_apps" that will
need to be removed.


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

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

Title:
  package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  unable to install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.5
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Mar 31 15:45:14 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-09-17 (560 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.20
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1757138] Re: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Phillip Susi]

You have a broken third party init script installed named "notes-enable-
ptrace" that you will need to remove.


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

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

Title:
  package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  got it from automatic failure report

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.4
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Feb 22 14:47:35 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-05-19 (670 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1752515] Re: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: podproces zainstalowany skrypt post-installation zwrócił kod błędu 1

[Phillip Susi]

You have a broken third party init script installed named "smfpd".  You
will need to remove it.


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

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

Title:
  package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade:
  podproces zainstalowany skrypt post-installation zwrócił kod błędu 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  I can't install it

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.4
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Mar  1 08:59:56 2018
  ErrorMessage: podproces zainstalowany skrypt post-installation zwrócił kod 
błędu 1
  InstallationDate: Installed on 2017-11-24 (96 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: 
podproces zainstalowany skrypt post-installation zwrócił kod błędu 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1749662] Re: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[Phillip Susi]

You have a broken init script installed named lwsmd.  You will need to
remove it.


** Changed in: util-linux (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  apt upgrade
  Leyendo lista de paquetes... Hecho
  Creando árbol de dependencias   
  Leyendo la información de estado... Hecho
  Calculando la actualización... Hecho
  Se actualizarán los siguientes paquetes:
libblkid1 libfdisk1 libmount1 libsmartcols1 libunity-control-center1 
libuuid1 libuuid1:i386 mount unity-control-center unity-control-center-faces 
util-linux uuid-runtime
  12 actualizados, 0 nuevos se instalarán, 0 para eliminar y 0 no actualizados.
  1 no instalados del todo o eliminados.
  Se necesita descargar 2.546 kB de archivos.
  Se utilizarán 8.192 B de espacio de disco adicional después de esta operación.
  ¿Desea continuar? [S/n] s
  Des:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 util-linux 
amd64 2.27.1-6ubuntu3.4 [849 kB]
  Des:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 mount amd64 
2.27.1-6ubuntu3.4 [121 kB]
  Des:3 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 uuid-runtime 
amd64 2.27.1-6ubuntu3.4 [26,1 kB]
  Des:4 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 libuuid1 i386 
2.27.1-6ubuntu3.4 [16,3 kB]
  Des:5 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libuuid1 
amd64 2.27.1-6ubuntu3.4 [15,2 kB]
  Des:6 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libblkid1 
amd64 2.27.1-6ubuntu3.4 [107 kB]
  Des:7 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libfdisk1 
amd64 2.27.1-6ubuntu3.4 [139 kB]
  Des:8 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libmount1 
amd64 2.27.1-6ubuntu3.4 [114 kB]
  Des:9 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libsmartcols1 amd64 2.27.1-6ubuntu3.4 [62,8 kB]
  Des:10 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libunity-control-center1 amd64 15.04.0+16.04.20171130-0ubuntu1 [81,1 kB]
  Des:11 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
unity-control-center amd64 15.04.0+16.04.20171130-0ubuntu1 [835 kB]
  Des:12 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
unity-control-center-faces all 15.04.0+16.04.20171130-0ubuntu1 [180 kB]
  Descargados 2.546 kB en 2s (957 kB/s)
  (Leyendo la base de datos ... 287355 ficheros o directorios instalados 
actualmente.)
  Preparando para desempaquetar .../util-linux_2.27.1-6ubuntu3.4_amd64.deb ...
  Desempaquetando util-linux (2.27.1-6ubuntu3.4) sobre (2.27.1-6ubuntu3.3) ...
  Procesando disparadores para ureadahead (0.100.0-19) ...
  Procesando disparadores para man-db (2.7.5-1) ...
  Procesando disparadores para mime-support (3.59ubuntu1) ...
  Configurando util-linux (2.27.1-6ubuntu3.4) ...
  insserv: Script lwsmd is broken: incomplete LSB comment.
  insserv: missing `Provides:' entry: please add.
  insserv: missing `Required-Start:' entry: please add even if empty.
  insserv: missing `Required-Stop:'  entry: please add even if empty.
  insserv: missing `Default-Start:'  entry: please add even if empty.
  insserv: missing `Default-Stop:'   entry: please add even if empty.
  insserv: warning: script 'K01GlassFish_aytohuelva' missing LSB tags and 
overrides
  insserv: warning: script 'K01postgresql-9.4' missing LSB tags and overrides
  insserv: Script likewise is broken: incomplete LSB comment.
  insserv: missing `Provides:' entry: please add.
  insserv: missing `Required-Start:' entry: please add even if empty.
  insserv: missing `Required-Stop:'  entry: please add even if empty.
  insserv: missing `Default-Start:'  entry: please add even if empty.
  insserv: missing `Default-Stop:'   entry: please add even if empty.
  insserv: Script lwsmd is broken: incomplete LSB comment.
  insserv: missing `Provides:' entry: please add.
  insserv: missing `Required-Start:' entry: please add even if empty.
  insserv: missing `Required-Stop:'  entry: please add even if empty.
  insserv: missing `Default-Start:'  entry: please add even if empty.
  insserv: missing `Default-Stop:'   entry: please add even if empty.
  insserv: Script likewise is broken: incomplete LSB comment.
  insserv: missing `Provides:' entry: please add.
  insserv: missing `Required-Start:' entry: please add even if empty.
  insserv: missing `Required-Stop:'  entry: please add even if empty.
  insserv: missing `Default-Start:'  entry: please add even if empty.
  insserv: missing `Default-Stop:'   entry: please add even if empty.
  insserv: Script likewise is broken: incomplete LSB comment.
  insserv: missing 

[Touch-packages] [Bug 1751303] Re: util-linux 2.27.1-6ubuntu3.4 subprocess installed post-installation script returned error exit status 139

[Phillip Susi]

Please run the memtest option from the boot menu for at least 15 minutes
and let us know if it finds problems.


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

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

Title:
  util-linux 2.27.1-6ubuntu3.4  subprocess installed post-installation
  script returned error exit status 139

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04


  
  Need to get 0 B/38.0 MB of archives.
  After this operation, 247 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Segmentation fault (core dumped)
  Setting up util-linux (2.27.1-6ubuntu3.4) ...
  Segmentation fault (core dumped)
  dpkg: error processing package util-linux (--configure):
   subprocess installed post-installation script returned error exit status 139
  Errors were encountered while processing:
   util-linux
  E: Sub-process /usr/bin/dpkg returned an error code (1)


  from syslog:

  Feb 23 09:17:51 faxor kernel: [ 1707.779093] dpkg-preconfigu[3359]: segfault 
at 126cfc8 ip 004bec94 sp 7ffcc3f59e00 error 6 in 
perl[40+1cf000]
  Feb 23 09:17:51 faxor kernel: [ 1707.946664] update-rc.d[3368]: segfault at 
1b4 ip 004bea0a sp 7ffc091a9b40 error 4 in perl[40+1cf000]
  Feb 23 09:17:51 faxor kernel: [ 1708.068377] update-rc.d[3370]: segfault at 
1b4 ip 004bea0a sp 7ffce3c40040 error 4 in perl[40+1cf000]

  apt-cache policy util-linux

  util-linux:
Installed: 2.27.1-6ubuntu3.4
Candidate: 2.27.1-6ubuntu3.4
Version table:
   *** 2.27.1-6ubuntu3.4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.27.1-6ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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

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

[Touch-packages] [Bug 19749] Re: SATA HDD not recognized during Breezy Colony 4 install or Dapper Flight 3 or Edgy Eft or Feisty Fawn

[Phillip Susi]

** Changed in: linux-source-2.6.15 (Ubuntu)
 Assignee: Anuradha ishan (123ishan) => Ben Collins (ben-collins)

** Changed in: linux (Ubuntu)
 Assignee: Anuradha ishan (123ishan) => (unassigned)

** Changed in: initramfs-tools (Ubuntu)
 Assignee: Anuradha ishan (123ishan) => (unassigned)

** Changed in: linux-source-2.6.20 (Ubuntu)
 Assignee: Anuradha ishan (123ishan) => (unassigned)

** Changed in: ubiquity (Ubuntu)
 Assignee: Anuradha ishan (123ishan) => (unassigned)

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

Title:
  SATA HDD not recognized during Breezy Colony 4 install or Dapper
  Flight 3 or Edgy Eft or Feisty Fawn

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-source-2.6.15 package in Ubuntu:
  Won't Fix
Status in linux-source-2.6.20 package in Ubuntu:
  Won't Fix
Status in ubiquity package in Ubuntu:
  Fix Released

Bug description:
  Machine is a Canonical supplied Toshiba Portege S100 - S113TD. Intel Pentium M
  Processor 740 [1.73Ghz, 2MB L2 cache, 533Mhz FSB]. Mobile Intel 915PM Express
  Chipset. Intel PRO/Wireless 2200BG WiFi. 512MB PC4200 DDR2 RAM. 60GB, 5400RPM
  Serial-ATA HDD. 

  Jeff Waugh pretty much told me that Hoary wouldn't run on this machine, so I
  went straight to Breezy Colony 2. I'm able to boot the CD, choose my location
  and language, and the installer stops because it's unable to detect a HDD. 
I've
  tried passing all the various ACPI options during boot with no success. The
  machine also supports Intel's software RAID, which I've tried disabling via
  Toshiba's own sparse BIOS settings with no success.

  I was able to mount a USB thumbdrive while in the installer and save some
  diagnostic stuff and the logs in /var/log. They can be found at the URL I
  provided. Additionally, ArminRonacher has added some notes to my Laptop 
Testing
  Team page confirming what I've also found - that nobody has been able to 
install
  Linux on this machine yet. That page can be found here:

  https://wiki.ubuntu.com/LaptopTestingTeam/ToshibaPortegeS100

  I can get to a console while in the installer if there are additional
  diagnostics that would be helpful. Just let me know.

  breezy log files: http://www.volvoguy.net/ubuntu/laptop-breezy/
  dapper log files: http://www.volvoguy.net/ubuntu/laptop-dapper/

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

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

[Touch-packages] [Bug 1747871] Re: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Phillip Susi]

You have a broken third party init script named "jasperserver" that you
will need to remove.


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

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

Title:
  package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  I can't proceed with the update.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Feb  7 16:45:49 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-01-26 (12 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.19
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1747119] Re: package util-linux 2.27.1-6ubuntu3.2 [modified: usr/bin/mesg usr/share/man/man1/mesg.1.gz] failed to install/upgrade: trying to overwrite '/usr/share/man/man1/mesg.1

[Phillip Susi]

It sounds like this orville-write package is broken and should probably
be deleted.


** Package changed: util-linux (Ubuntu) => orville-write (Ubuntu)

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

Title:
  package util-linux 2.27.1-6ubuntu3.2 [modified: usr/bin/mesg
  usr/share/man/man1/mesg.1.gz] failed to install/upgrade: trying to
  overwrite '/usr/share/man/man1/mesg.1.gz', which is also in package
  orville-write 2.55-3

Status in orville-write package in Ubuntu:
  New

Bug description:
  I expected updrade all packages (apt-get update; apt-get upgrade)
  Instead happened E: Sub-process /usr/bin/dpkg returned an error code (1)

  when unpack util-linux_2.27.1-6ununtu3.3_i386.deb
  rewrite mesg.1.gz that already exist in orville-write 2.55-3
  dpkg-deb: error

  Summary in the end apt-get install upgrade

  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Ubuntu 16.04.3 LTS
  Release 16.04

  apt-cache policy orville-write 2.55-3
  2.55-3 500
  500 http://mirror.yandex.ru/ubuntu xenial/universe i386 Packages
  100 /var/lib/dpkg/status

  
  apt-cache policy util-linux
  At the moment - 2.27.1-6ubuntu3.2
  Need - 2.27.1-6ubuntu3.3

  2.27.1-6ubuntu3.3
   500 http://mirror.yandex.ru/ubuntu xenial-updates/main i386 Packages
  2.27.1-6ubuntu3.2
   100 /var/lib/dpkg/status
  2.27.1-6ubuntu3 500
   500 http://mirror.yandex.ru/ubuntu xenial /main i386 Packages

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.2 [modified: usr/bin/mesg 
usr/share/man/man1/mesg.1.gz]
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sat Feb  3 10:39:39 2018
  DpkgTerminalLog:
   Preparing to unpack .../util-linux_2.27.1-6ubuntu3.3_i386.deb ...
   Unpacking util-linux (2.27.1-6ubuntu3.3) over (2.27.1-6ubuntu3.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/util-linux_2.27.1-6ubuntu3.3_i386.deb (--unpack):
trying to overwrite '/usr/share/man/man1/mesg.1.gz', which is also in 
package orville-write 2.55-3
  DuplicateSignature:
   package:util-linux:2.27.1-6ubuntu3.2 [modified: usr/bin/mesg 
usr/share/man/man1/mesg.1.gz]
   Unpacking util-linux (2.27.1-6ubuntu3.3) over (2.27.1-6ubuntu3.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/util-linux_2.27.1-6ubuntu3.3_i386.deb (--unpack):
trying to overwrite '/usr/share/man/man1/mesg.1.gz', which is also in 
package orville-write 2.55-3
  ErrorMessage: trying to overwrite '/usr/share/man/man1/mesg.1.gz', which is 
also in package orville-write 2.55-3
  InstallationDate: Installed on 2017-01-25 (373 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.19
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.2 [modified: usr/bin/mesg 
usr/share/man/man1/mesg.1.gz] failed to install/upgrade: trying to overwrite 
'/usr/share/man/man1/mesg.1.gz', which is also in package orville-write 2.55-3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1745089] Re: fsck freezing console

[Phillip Susi]

You asked e2fsck to run badblocks ( -c ), which takes a very, very long
time.


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

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

Title:
  fsck freezing console

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  1. After some operations, the program does not respond and does not allow you 
to exit back to the console. 
  2. Expected that the program or report the current state, or let go of it. 
  3. Started 
  root@ubuntu:~# fsck.ext4 -fyc /dev/sdb1
  After some time, the program froze the console.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: util-linux 2.30.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 24 05:13:39 2018
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1744372] Re: gparted does not start - Unit -.mount does not exist, proceeding anyway.

[Phillip Susi]

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

** This bug has been marked a duplicate of bug 1652282
   Xwayland not using XAUTHORITY, prevents root applications from connecting

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

Title:
  gparted does not start - Unit -.mount does not exist, proceeding
  anyway.

Status in gparted package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid

Bug description:
  1. fresh ubuntu 18.04 daily: lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2. install gparted with Software:
  gparted:
    Installiert:   0.30.0-3ubuntu1
    Installationskandidat: 0.30.0-3ubuntu1
    Versionstabelle:
   *** 0.30.0-3ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. launch with icon - enter password - nothing.
  4.launch in terminal:
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:8328): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  How to Fix: run xhost +local: before gparted! # this only bypass the
  wayland restriction; meaning a security violation (not a fix !!! )

  thomas@ubuntu-1804:~$ xhost +local:
  non-network local connections being added to access control list
  thomas@ubuntu-1804:~$ gparted
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  Gtk-Message: Failed to load module "canberra-gtk-module"
  ==
  libparted : 3.2
  ==
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gparted 0.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 19:45:14 2018
  InstallationDate: Installed on 2018-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gparted
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1739889] Re: Compiler warning about possiable overflow in devname.c

[Phillip Susi]

** Tags added: patch

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

Title:
  Compiler warning about possiable overflow in devname.c

Status in util-linux package in Ubuntu:
  New

Bug description:
  I just compiled mount and got the following warning:

  libblkid/src/devname.c:166:29: warning: ‘%s’ directive writing up to 255 
bytes into a region of size 245 [-Wformat-overflow=]
 sprintf(path, "/sys/block/%s/slaves", de->d_name);
   ^~
  In file included from /usr/include/stdio.h:862:0,
   from libblkid/src/devname.c:16:
  /usr/include/x86_64-linux-gnu/bits/stdio2.h:33:10: note: 
‘__builtin___sprintf_chk’ output between 19 and 274 bytes into a destination of 
size 256
 return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
^~
 __bos (__s), __fmt, __va_arg_pack ());
 ~ 

  Code preceding this does a length check to prevent overflow. However,
  the warning was still alarming. The attached patch switches sprintf to
  snprintf and ups the buffer size to 300. This will silence the
  compiler and support longer device names. There didn't appear to be
  any technical reason for the 256 byte limit. If there is we just get a
  different less alarming truncation warning. This also means we don't
  need the hard coded length check.

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

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

[Touch-packages] [Bug 1735932] Re: package util-linux 2.30.2-0.1ubuntu1 failed to install/upgrade: installed util-linux package post-installation script subprocess returned error exit status 1

[Phillip Susi]

You have a third party boot script named "tpeap" installed, and this
script is broken ( it has no LSB headers ).  You will need to remove or
repair it.


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

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

Title:
  package util-linux 2.30.2-0.1ubuntu1 failed to install/upgrade:
  installed util-linux package post-installation script subprocess
  returned error exit status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Ran  sudo do-release-upgrade -d.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.30.2-0.1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Sat Dec  2 17:48:12 2017
  ErrorMessage: installed util-linux package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-08-08 (481 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.2.24
  SourcePackage: util-linux
  Title: package util-linux 2.30.2-0.1ubuntu1 failed to install/upgrade: 
installed util-linux package post-installation script subprocess returned error 
exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-12-02 (0 days ago)

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

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

[Touch-packages] [Bug 1735784] Re: package uuid-runtime 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

[Phillip Susi]

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

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

Title:
  package uuid-runtime 2.27.1-6ubuntu3.3 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  it always shows a massage that is : "Package operation failed - this
  installation or removal of a software package failed"

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: uuid-runtime 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Fri Dec  1 21:14:54 2017
  DpkgHistoryLog:
   Start-Date: 2017-12-01  21:13:48
   Commandline: aptdaemon role='role-commit-packages' sender=':1.94'
   Upgrade: thunderbird-gnome-support:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2, 
1:52.5.0+build1-0ubuntu0.16.04.1), dpkg:amd64 (1.18.4ubuntu1.2, 
1.18.4ubuntu1.3), thunderbird-locale-en-us:amd64 
(1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1), 
firefox-locale-en:amd64 (57.0+build4-0ubuntu0.16.04.6, 
57.0.1+build2-0ubuntu0.16.04.1), thunderbird:amd64 
(1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1), 
firefox:amd64 (57.0+build4-0ubuntu0.16.04.6, 57.0.1+build2-0ubuntu0.16.04.1), 
libdpkg-perl:amd64 (1.18.4ubuntu1.2, 1.18.4ubuntu1.3), 
thunderbird-locale-en:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2, 
1:52.5.0+build1-0ubuntu0.16.04.1), dpkg-dev:amd64 (1.18.4ubuntu1.2, 
1.18.4ubuntu1.3)
  DuplicateSignature:
   package:uuid-runtime:2.27.1-6ubuntu3.3
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package uuid-runtime (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-08-26 (96 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: util-linux
  Title: package uuid-runtime 2.27.1-6ubuntu3.3 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Phillip Susi]

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

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: No upgrade log present (prob

Re: [Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Phillip Susi]

On 12/7/2017 8:15 PM, bodhi.zazen wrote:
> Wayland , upstream, does not and will not support running graphical
> applications, as root, from the terminal using sudo , period, end of story.
> There are other mechanisms to grant graphical applications root access, but
> again the application itself is not going to run as root.

Yes, it does, as you can easily test by suing to root and running gedit.

> And if you take your fat head out of your ass and look upstream you will
> see every bug files against wayland regarding the problem of running
> graphical applications with sudo has been closed as either not a bug or
> wont fix.

https://bugs.freedesktop.org/show_bug.cgi?id=91071 is not.

Neither is https://bugzilla.gnome.org/show_bug.cgi?id=789867

And there it is noted that wayland does not explicitly allow or deny
root applications.

> On the forums, we would ban him for a period of time, 1-3 months
> depending on his behavior. Often we would start with a week or a month,
> but on his return he would start right back up with his violations, and
> we would extend the ban. Eventually he would cool down and we would
> restore his  privileges.

Well now you're just lieing.  You banned me permanently one time because
I dared to point out that you incorrectly closed another user's thread
for breaking the rules when he did no such thing.

> reference 32 is here https://lwn.net/Articles/517375/

This talks about weston not having to be run as root; not disallowing
client applications running as root.

> The blog is here http://mupuf.org/blog/2014/02/19/wayland-compositors-
> why-and-how-to-handle/

This talks about having weston be able to isolate different clients from
interfering with one another.  Nowhere does it talk about refusing
clients with uid=0.

> Please could both of you take a deep breath and stop the personal
> attacks and aggressive language?

I haven't made any personal attacks.  What I have done is point out that
this misconception that disallowing root applications is not true; that
gdm fails to perform its job as described by its man page.  This
therefore is, ipso facto, a bug, whether or not you agree with the
terrible user facing consequences it has.

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in Settings editor for LightDM GTK+ Greeter:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Won't Fix
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4

[Touch-packages] [Bug 1734376] Re: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Phillip Susi]

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

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

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

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  I couldn't install the lastest update

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Fri Nov 24 11:10:53 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-06-08 (899 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to zesty on 2017-06-11 (166 days ago)

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

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

[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Phillip Susi]

Excuse my language Bodhi, but bull shit.  You actually can run wayland
apps as root just fine.  It is only X11 apps running under wayland that
no longer run as root, and the reason is simply that gdm3 fails to
configure Xwayland with a proper Xauthority policy, the way its man page
says it should.  It isn't doing what its documentation says it should,
so it's a bug.

Some idiots who think they are the end all know it alls are simply
seizing on the opportunity to push their agenda that GUI applications
should not be run as root.


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

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in Back In Time:
  Fix Released
Status in Boot-Info:
  Fix Committed
Status in Boot-Repair:
  Fix Committed
Status in GNOME Terminal:
  New
Status in OS-Uninstaller:
  Fix Committed
Status in Y PPA Manager:
  New
Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  New
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  *
  Main upstream discussion & fixes example to deal with wayland:
  https://bugzilla.gnome.org/show_bug.cgi?id=776437
  *

  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-

[Touch-packages] [Bug 1732069] Re: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Phillip Susi]

You have a broken third party startup script named "runlcactivator"
installed.  You will need to remove it.


** Changed in: util-linux (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  I can't update the any software in my laptop

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Mon Nov 13 10:47:12 2017
  DpkgHistoryLog:
   Start-Date: 2017-11-13  10:47:10
   Commandline: apt-get -f install
   Requested-By: mahima (1000)
   Upgrade: libtcmalloc-minimal4:amd64 (2.4-0ubuntu5, 2.4-0ubuntu5.16.04.1)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-22 (448 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1731794] Re: package grub-common 2.02~beta2-36ubuntu3.12 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Phillip Susi]

Looks like a systemd problem:

Failed to execute operation: Connection timed out
Failed to retrieve unit: Connection timed out
Failed to stop grub-common.service: Connection timed out


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

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

Title:
  package grub-common 2.02~beta2-36ubuntu3.12 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  My ubuntu system locks up regularly. Bugs I've reported about this get
  closed for inattention, after being ignored, and queries about how to
  do basic debugging get the same treatment, so I just power cycle
  whenever it happens again.

  This time the lock up happened while the GUI upgrade-everything-to-
  latest tool was running.

  When I power cycled the box to recover, the system was unusable -
  flashing "system problem detected" popups, none staying stable long
  enough to respond.

  ssh + "sudo apt-get update" + "sudo apt-get upgrade" pointed me to
  "sudo dpkg --configure -a"

  That command reported numerous errors - I don't know which of them are
  "normal" for this system, but hidden by the GUI, and which are new.

  But it got the system semi-usable from the GUI, so now I'm clicking on
  "yes, report it" for the many pop-ups, of which this is one.

  FWIW, grub2-common is one of the ones "dpkg --reconfigure -a"
  complained about.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: grub-common 2.02~beta2-36ubuntu3.12
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Nov 12 10:59:44 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2012-04-26 (2026 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=96551326-e461-4071-ab9c-0e81ad7015d7 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: grub2
  Title: package grub-common 2.02~beta2-36ubuntu3.12 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-03-31 (226 days ago)

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

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

[Touch-packages] [Bug 1704202] Re: package bsdutils 1:2.27.1-6ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Phillip Susi]

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

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

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

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  I was trying to install as normal the suggested installations, but the
  software installation couldn't run / had a problem.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bsdutils 1:2.27.1-6ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jul 13 22:23:14 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-02 (71 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: util-linux
  Title: package bsdutils 1:2.27.1-6ubuntu3 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1724013] Re: mount does not correctly process x-* options

[Phillip Susi]

mount.cifs is not part of util-linux, and it also is not supposed to
ignore unknown options.  This is only a feature of util-linux mount
since it is generic, and not expected to understand every possible
option supported by every possible filesystem.

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

Title:
  mount does not correctly process x-* options

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  According to the mount(8) man page:

  All options prefixed with "x-" are interpreted as comments or as
  userspace application-specific options.  These options are not stored
  in  the  mtab  file,  nor  sent  to  the mount.type helpers nor to the
  mount(2) system call.  The suggested format is x-appname.option (e.g.
  x-systemd.automount).

  However, adding any such option to cifs entry, such as "x-test.opt"
  (other than x-systemd.automount) results in:

  mount error(22): Invalid argument
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  No options starting with "x-" should be passed to mount.cifs, so the
  mount should succeed.

  Running Ubuntu 16.04.3 LTS
  mount package installed is 2.27.1-6ubuntu3.3

  This error always happens when such an option is specified. Here is an 
example fstab line that causes this failure:
  //192.168.1.3/Public/mnt/mybookcifs   
noauto,x-test.opt,rw,users,noperm,guest,soft,cache=none,sec=none  0  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mount 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 16 12:29:40 2017
  InstallationDate: Installed on 2016-04-22 (542 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/tcsh
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1728228] Re: package grub-common 2.02~beta2-36ubuntu3.12 failed to install/upgrade: sub-processo novo script pre-removal retornou estado de saída de erro 1

[Phillip Susi]

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

Title:
  package grub-common 2.02~beta2-36ubuntu3.12 failed to install/upgrade:
  sub-processo novo script pre-removal retornou estado de saída de erro
  1

Status in grub2 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  weiller@weiller-MS-7641:~$ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  weiller@weiller-MS-7641:~$ apt-cache policy grub2
  grub2:
Instalado: (nenhum)
Candidato: 2.02~beta2-36ubuntu3.14
Tabela de versão:
   2.02~beta2-36ubuntu3.14 500
  500 http://br.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
   2.02~beta2-36ubuntu3 500
  500 http://br.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  Update successful

  Package is Broken.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: grub-common 2.02~beta2-36ubuntu3.12
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Oct 28 09:02:23 2017
  ErrorMessage: sub-processo novo script pre-removal retornou estado de saída 
de erro 1
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=cd8acb14-5370-479a-b58b-4f7c352e5c06 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.2.24
  SourcePackage: grub2
  Title: package grub-common 2.02~beta2-36ubuntu3.12 failed to install/upgrade: 
sub-processo novo script pre-removal retornou estado de saída de erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1011007] Re: blkid identifies ext4 rootfs as silicon_medley_raid_member, breaks boot

[Phillip Susi]

Is anyone still having this issue and able to help troubleshoot it?


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

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

Title:
  blkid identifies ext4 rootfs as silicon_medley_raid_member, breaks
  boot

Status in util-linux package in Ubuntu:
  Incomplete
Status in Fedora:
  Invalid

Bug description:
  Ubuntu does not boot
  /disk/by-uuid not found
  blkid reports  silicon_medley_raid_member
  tryed this
  https://bugzilla.redhat.com/show_bug.cgi?id=730502

  tips: find out what's on the disk at the specified location

  ubuntu@ubuntu:/media$ sudo env BLKID_DEBUG=0x blkid -p /dev/sda1libblkid: 
debug mask set to 0x.
  ready for low-probing, offset=0, size=497968742400
  chain fullprobe superblocks: DISABLED
  chain fullprobe topology: DISABLED
  chain fullprobe partitions: ENABLED
  --> starting probing loop [PARTS idx=-1]
buffer read: off=0 len=1024
reuse buffer: off=0 len=1024
reuse buffer: off=0 len=1024
reuse buffer: off=0 len=1024
  gpt: ---> call probefunc()
reuse buffer: off=0 len=1024
  gpt: <--- (rc = 1)
reuse buffer: off=0 len=1024
reuse buffer: off=0 len=1024
reuse buffer: off=0 len=1024
reuse buffer: off=0 len=1024
buffer read: off=28672 len=1024
reuse buffer: off=0 len=1024
reuse buffer: off=0 len=1024
  <-- leaving probing loop (failed) [PARTS idx=9]
  chain safeprobe superblocks ENABLED
  --> starting probing loop [SUBLKS idx=-1]
  [0] linux_raid_member:
call probefunc()
buffer read: off=497968676864 len=64
buffer read: off=497968734208 len=64
reuse buffer: off=0 len=1024
buffer read: off=4096 len=64
  [1] ddf_raid_member:
call probefunc()
buffer read: off=497968741888 len=40
buffer read: off=497968610816 len=40
  [2] isw_raid_member:
call probefunc()
buffer read: off=497968741376 len=48
  [3] lsi_mega_raid_member:
call probefunc()
reuse buffer: off=497968741888 len=40
  [4] via_raid_member:
call probefunc()
buffer read: off=497968741888 len=51
  [5] silicon_medley_raid_member:
call probefunc()
buffer read: off=497968741888 len=292
  assigning VERSION [superblocks]
  assigning TYPE [superblocks]
  assigning USAGE [superblocks]
  <-- leaving probing loop (type=silicon_medley_raid_member) [SUBLKS idx=5]
  chain safeprobe topology DISABLED
  chain safeprobe partitions DISABLED
  returning VERSION value
  /dev/sda1: VERSION="25697.25960" returning TYPE value
  TYPE="silicon_medley_raid_member" returning USAGE value
  USAGE="raid" 
  reseting probing buffers
  buffers summary: 42949675671 bytes by 617802423873589236 read() call(s)

  ubuntu@ubuntu:/media$ sudo dd if=/dev/sda1 bs=1 skip=497968741887 count=200 | 
od -tx1z   
  000 13 03 bf 1b 67 42 9a 00 00 00 00 2f 75 73 72 2f  >gB./usr/<
  020 73 72 63 2f 6c 69 6e 75 78 2d 68 65 61 64 65 72  >src/linux-header<
  040 73 2d 32 2e 36 2e 33 38 2d 38 2d 67 65 6e 65 72  >s-2.6.38-8-gener<
  060 69 63 2f 69 6e 63 6c 75 64 65 2f 63 6f 6e 66 69  >ic/include/confi<
  100 67 2f 63 79 63 6c 61 64 65 73 00 00 73 79 6e 63  >g/cyclades..sync<
  120 2e 68 00 02 00 00 00 00 4e 13 03 bf 1b 67 42 9a  >.h..NgB.<
  140 00 00 00 00 2f 75 73 72 2f 73 72 63 2f 6c 69 6e  >/usr/src/lin<
  160 75 78 2d 68 65 61 64 65 72 73 2d 32 2e 36 2e 33  >ux-headers-2.6.3<
  200 38 2d 38 2d 67 65 6e 65 72 69 63 2f 69 6e 63 6c  >8-8-generic/incl<
  220 75 64 65 2f 63 6f 6e 66 69 67 2f 63 79 63 6c 6f  >ude/config/cyclo<
  240 6d 78 00 00 78 32 35 2e 68 00 02 00 00 00 00 4e  >mx..x25.h..N<
  260 13 03 bf 1b 67 42 9a 00 00 00 00 2f 75 73 72 2f  >gB./usr/<
  300 73 72 63 2f 6c 69 6e 75  >src/linu<
  310

  in my case it was a file linux-headers-2.6.38-8-generic.list
  so i simply overwriten it
  ubuntu@ubuntu:/media$ sudo dd if=/dev/zero bs=1 count=292 seek=497968741888 
of=/dev/sda1
  292+0 records in
  292+0 records out
  292 bytes (292 B) copied, 0.000560058 s, 521 kB/s

  ubuntu@ubuntu:/media$ sudo dd if=/dev/sda1 bs=1 skip=497968741887 count=200 | 
od -tx1z   
  000 13 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ><
  020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ><
  *
  300 00 00 00 00 00 00 00 00  ><
  310
  200+0 records in
  200+0 records out
  200 bytes (200 B) copied, 0.00189193 s, 106 kB/s

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: udisks 1.0.1-1ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18
  Uname: Linux 2.6.32-33-generic i686
  Architecture: i386
  Date: Sat Jun  9 21:35:05 2012
  LiveMediaBuild: 

[Touch-packages] [Bug 1021975] Re: gzip --rsyncable not rsyncable

[Phillip Susi]

That version has been merged into Ubuntu so it is fixed here now as
well.


** Changed in: gzip (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  gzip --rsyncable not rsyncable

Status in gzip package in Ubuntu:
  Fix Released
Status in gzip package in Debian:
  Fix Released

Bug description:
  i use gzip --rsyncable to compress postgresql 9 db dumps for rsyncing
  from an east-coast colo to a west-coast colo.  the dumps are always
  changing in small ways so this compression speeds up the rsync by
  quite a bit.  both the following tests are with a large text dump file
  on both sides, the local is newer than the remote.

  a gzip 1.3.12 (with
  
http://archive.ubuntu.com/ubuntu/pool/main/g/gzip/gzip_1.3.12-9ubuntu1.diff.gz)
  session ends with the usual infodump like this:

  rj@fudge:~$ rsync -Pvazl latest-linux-pg9.gz rj@cake:
  Password:
  sending incremental file list
  latest-linux-pg9.gz
1857354904 100%2.77MB/s0:10:39 (xfer#1, to-check=0/1)

  sent 310747861 bytes  received 301381 bytes  456418.55 bytes/sec
  total size is 1857354904  speedup is 5.97

  but with the ubuntu server LTS gzip 1.4 i'm getting little or no
  speedup:

  rj@fudge:~$ rsync -Pvazl latest-linux-pg9.gz rj@cake: 
  Password:
  sending incremental file list
  latest-linux-pg9.gz
1802447002 100%  634.16kB/s0:46:15 (xfer#1, to-check=0/1)

  sent 1739614120 bytes  received 297265 bytes  617318.21 bytes/sec
  total size is 1802447002  speedup is 1.04

  i haven't taken a look at the code or data to suggest the difference,
  but the result is noticeable.  basically, not super-critical because i
  can build previous versions with previous-version patches, but i
  figured i should report it.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gzip 1.4-1ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Fri Jul  6 21:21:29 2012
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gzip
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1724013] Re: mount does not correctly process x-* options

[Phillip Susi]

I don't think that is a bug in mount.cifs then.  The util-linux mount
treats x-* options as comments or application specific options.
mount.cifs is the specific application, and it expects to be able to
recognize all mount options.


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

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

Title:
  mount does not correctly process x-* options

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  According to the mount(8) man page:

  All options prefixed with "x-" are interpreted as comments or as
  userspace application-specific options.  These options are not stored
  in  the  mtab  file,  nor  sent  to  the mount.type helpers nor to the
  mount(2) system call.  The suggested format is x-appname.option (e.g.
  x-systemd.automount).

  However, adding any such option to cifs entry, such as "x-test.opt"
  (other than x-systemd.automount) results in:

  mount error(22): Invalid argument
  Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

  No options starting with "x-" should be passed to mount.cifs, so the
  mount should succeed.

  Running Ubuntu 16.04.3 LTS
  mount package installed is 2.27.1-6ubuntu3.3

  This error always happens when such an option is specified. Here is an 
example fstab line that causes this failure:
  //192.168.1.3/Public/mnt/mybookcifs   
noauto,x-test.opt,rw,users,noperm,guest,soft,cache=none,sec=none  0  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mount 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 16 12:29:40 2017
  InstallationDate: Installed on 2016-04-22 (542 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/tcsh
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720541] Re: flock does not lock dpkg lock file properly

[Phillip Susi]

lockfile from the procmail package will do it.


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

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

Title:
  flock does not lock dpkg lock file properly

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Test:
  sudo flock /var/lib/dpkg/lock -c \
  'echo 1; apt-get -o Debug::NoLocking=true check; echo 2; apt-get check'

  Expected behavior:
  apt-get fails in stage 2.

  
  Workaround (needs moreutils package, which is not installed by default):

  sudo lckdo /var/lib/dpkg/lock /bin/sh -c \
  'echo 1; apt-get -o Debug::NoLocking=true check; echo 2; apt-get check'

  
  Similarly, flock does not recognize lock set by e.g. apt-get.

  man lckdo:
  "Now that util-linux contains a similar command named flock, lckdo is 
deprecated, and will be removed from some  future version of moreutils."

  So developer can not rely on lckdo.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: util-linux 2.20.1-5.1ubuntu20.9
  ProcVersionSignature: Ubuntu 4.4.0-96.119~14.04.1-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 30 16:30:50 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (1105 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.cron.weekly.fstrim: 2014-09-21T13:07:51.420447

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

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

[Touch-packages] [Bug 1313169] Re: Ubuntu Trusty Tahr cannot boot on RAID5 array

[Phillip Susi]

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

** This bug has been marked a duplicate of bug 1683105
   Installation of DMRaid should automatically add necessary modules to 
/etc/initramfs-tools/modules

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

Title:
  Ubuntu Trusty Tahr cannot boot on RAID5 array

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Raid array is three identical Western Digital Green series 500GB hard
  drives on an NVIDIA controller set to RAID5 for a total of 1TiB
  (931.52GB) storage.

  Installation was done using the Ubuntu LiveCD.

  Partitions on the filesystem was created beforehand using gparted. The
  partition table is set up to be GPT with a 8MB bios_grub partition, a
  256MB fat32 EFIBoot partition (not used for this setup, board does not
  support EFI and is expected to boot from the bios_grub legacy
  partition), a 4GB swap, 80GB root partition, and the rest for /home.
  Then  the installer is invoked and the partitions are set up. GRUB is
  told to install to the root of the RAID array in /dev/mapper . The
  installation went flawlessly.

  Upon reboot, GRUB loads as expected, and loads the kernel and initrd
  as expected. However, the kernel gives up on waiting for the root
  partition and drops to initramfs busybox. "dmesg|grep device" shows
  the following errors:

  device-mapper: table: 252:0: raid: unknown target type
  device-mapper: ioctl: error adding target to table

  Trying to invoke dmraid -a y results in the following error:
  ERROR: device-mapper target type "raid" is not in the kernel
  RAID set "nvidia_babddecf" was not activated.

  nvidia_babddecf is the assigned volume name by the controller.

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

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

[Touch-packages] [Bug 1727753] [NEW] Installer crash reports failing to attach partman log

[Phillip Susi]

Public bug reported:

Recent install crash reports have all listed a hook error and fail to
attach the partman log file needed to help debug why the install failed.

I think this is a grave bug that will require a respin of the 17.10
release ASAP.

** Affects: apport (Ubuntu)
 Importance: Critical
 Status: New

** Affects: ubiquity (Ubuntu)
 Importance: Critical
 Status: New

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

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

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

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

Title:
  Installer crash reports failing to attach partman log

Status in apport package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New

Bug description:
  Recent install crash reports have all listed a hook error and fail to
  attach the partman log file needed to help debug why the install
  failed.

  I think this is a grave bug that will require a respin of the 17.10
  release ASAP.

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

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

[Touch-packages] [Bug 1720541] Re: flock does not lock dpkg lock file properly

[Phillip Susi]

No; what you want to do and what flock is intended to do are different
things.  You're complaining that you can't use a hammer to screw in a
screw.  You're using the wrong tool for the job.


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

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

Title:
  flock does not lock dpkg lock file properly

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Test:
  sudo flock /var/lib/dpkg/lock -c \
  'echo 1; apt-get -o Debug::NoLocking=true check; echo 2; apt-get check'

  Expected behavior:
  apt-get fails in stage 2.

  
  Workaround (needs moreutils package, which is not installed by default):

  sudo lckdo /var/lib/dpkg/lock /bin/sh -c \
  'echo 1; apt-get -o Debug::NoLocking=true check; echo 2; apt-get check'

  
  Similarly, flock does not recognize lock set by e.g. apt-get.

  man lckdo:
  "Now that util-linux contains a similar command named flock, lckdo is 
deprecated, and will be removed from some  future version of moreutils."

  So developer can not rely on lckdo.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: util-linux 2.20.1-5.1ubuntu20.9
  ProcVersionSignature: Ubuntu 4.4.0-96.119~14.04.1-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 30 16:30:50 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (1105 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.cron.weekly.fstrim: 2014-09-21T13:07:51.420447

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

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

[Touch-packages] [Bug 1721176] Re: util-linux blkid -o export is not working in 16.04

[Phillip Susi]

The version of blkid in 16.04 is 2.27.0 and is from 02-Nov-2015, and it
supports this option.  You are either running an older release than
16.04, or have an old locally built version.


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

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

Title:
   util-linux blkid -o export is not working in 16.04

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  patrikx3@workstation:~$ blkid -o export
  Invalid output format export. Choose from value,
device, list, or full

  I says export is not an available export (which is expected by update-
  grub) although the program is long ago is updated with this format.

  blkid --versions is 12-Feb-2003.

  When will be updated?
  I cannot update grub because of it.

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

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

[Touch-packages] [Bug 1720541] Re: flock does not lock dpkg lock file properly

[Phillip Susi]

dpkg does not use flock(); it uses the lock file /var/lib/dpkg/lock.


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

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

Title:
  flock does not lock dpkg lock file properly

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Test:
  sudo flock /var/lib/dpkg/lock -c \
  'echo 1; apt-get -o Debug::NoLocking=true check; echo 2; apt-get check'

  Expected behavior:
  apt-get fails in stage 2.

  
  Workaround (needs moreutils package, which is not installed by default):

  sudo lckdo /var/lib/dpkg/lock /bin/sh -c \
  'echo 1; apt-get -o Debug::NoLocking=true check; echo 2; apt-get check'

  
  Similarly, flock does not recognize lock set by e.g. apt-get.

  man lckdo:
  "Now that util-linux contains a similar command named flock, lckdo is 
deprecated, and will be removed from some  future version of moreutils."

  So developer can not rely on lckdo.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: util-linux 2.20.1-5.1ubuntu20.9
  ProcVersionSignature: Ubuntu 4.4.0-96.119~14.04.1-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 30 16:30:50 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (1105 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.cron.weekly.fstrim: 2014-09-21T13:07:51.420447

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

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

[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Phillip Susi]

The wayland package just needs to change its absurd default security
policy back to the one that X has used.


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

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  New
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  New

Bug description:
  Posting here what gnome says about porting to wayland, and their
  tests:

  GNOME Applications under Wayland
  GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a 
GTK+ application under Wayland simply by:

  GDK_BACKEND=wayland gnome-calculator
  Applications that use Clutter or clutter-gtk also need the Clutter Wayland 
backend enabled:

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

  https://wiki.gnome.org/Initiatives/Wayland/Applications

  ==> so hope the settings are well set at compile time; maybe a
  rebuilt to get sure all apps are ok.

  
  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 20

[Touch-packages] [Bug 1698967] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed')

[Phillip Susi]

** Tags removed: hardware-error
** Tags added: bot-stop-nagging

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

Title:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package
  bsdutils is not ready for configuration  cannot configure (current
  status 'half-installed')

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

Bug description:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package
  bsdutils is not ready for configuration  cannot configure (current
  status 'half-installed')

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   bsdutils:amd64: Configure
   axel:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jun 18 17:43:58 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package bsdutils is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package bsdutils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-15 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package 
bsdutils is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1716082] Re: package libblkid1:amd64 2.28.2-1ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur

[Phillip Susi]

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

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

Title:
  package libblkid1:amd64 2.28.2-1ubuntu1.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  i m not able to update or install any application

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libblkid1:amd64 2.28.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.7
  AptOrdering:
   libblkid1:amd64: Configure
   libglib2.0-0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Sep  4 22:56:24 2017
  DuplicateSignature:
   package:libblkid1:amd64:2.28.2-1ubuntu1.2
   Unpacking unity-control-center (15.04.0+16.10.20170214-0ubuntu1) over 
(15.04.0+16.10.20161003.1-0ubuntu2) ...
Log started: 2017-09-04  22:56:24
   dpkg: error processing package libblkid1:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-09-02 (6 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: util-linux
  Title: package libblkid1:amd64 2.28.2-1ubuntu1.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1715069] Re: package util-linux 2.29-1ubuntu2 failed to install/upgrade: il pacchetto util-linux non è pronto per la configurazione impossibile configurarlo (stato corrente "hal

[Phillip Susi]

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

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

Title:
  package util-linux 2.29-1ubuntu2 failed to install/upgrade: il
  pacchetto util-linux non è pronto per la configurazione  impossibile
  configurarlo (stato corrente "half-installed")

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  i'don't know

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Tue Sep  5 08:20:29 2017
  DpkgTerminalLog:
   dpkg: errore nell'elaborare il pacchetto util-linux (--configure):
il pacchetto util-linux non è pronto per la configurazione
impossibile configurarlo (stato corrente "half-installed")
  ErrorMessage: il pacchetto util-linux non è pronto per la configurazione  
impossibile configurarlo (stato corrente "half-installed")
  InstallationDate: Installed on 2017-03-21 (167 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: il 
pacchetto util-linux non è pronto per la configurazione  impossibile 
configurarlo (stato corrente "half-installed")
  UpgradeStatus: Upgraded to zesty on 2017-05-22 (105 days ago)

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

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

[Touch-packages] [Bug 1714997] Re: package util-linux 2.29-1ubuntu2 failed to install/upgrade: il pacchetto util-linux non è pronto per la configurazione impossibile configurarlo (stato corrente "hal

[Phillip Susi]

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

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

Title:
  package util-linux 2.29-1ubuntu2 failed to install/upgrade: il
  pacchetto util-linux non è pronto per la configurazione  impossibile
  configurarlo (stato corrente "half-installed")

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Mon Sep  4 18:38:10 2017
  DpkgTerminalLog:
   dpkg: errore nell'elaborare il pacchetto util-linux (--configure):
il pacchetto util-linux non è pronto per la configurazione
impossibile configurarlo (stato corrente "half-installed")
  ErrorMessage: il pacchetto util-linux non è pronto per la configurazione  
impossibile configurarlo (stato corrente "half-installed")
  InstallationDate: Installed on 2016-11-04 (304 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: il 
pacchetto util-linux non è pronto per la configurazione  impossibile 
configurarlo (stato corrente "half-installed")
  UpgradeStatus: Upgraded to zesty on 2017-04-23 (134 days ago)

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

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

[Touch-packages] [Bug 1698967] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed')

[Phillip Susi]

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

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

Title:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package
  bsdutils is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package
  bsdutils is not ready for configuration  cannot configure (current
  status 'half-installed')

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   bsdutils:amd64: Configure
   axel:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jun 18 17:43:58 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package bsdutils is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package bsdutils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-15 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package 
bsdutils is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1714705] Re: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Phillip Susi]

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

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

Title:
  package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  
  jefff@jefff-System-Product-Name:~$ sudo apt-get -f install util-linux
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  util-linux is already the newest version (2.27.1-6ubuntu3.3).
  You might want to run 'apt-get -f install' to correct these:
  The following packages have unmet dependencies:
   grub-pc : Depends: grub-common (= 2.02~beta2-36ubuntu3.12) but 
2.02~beta2-36ubuntu3.11 is to be installed
 Depends: grub2-common (= 2.02~beta2-36ubuntu3.12) but 
2.02~beta2-36ubuntu3.11 is to be installed
 Depends: grub-pc-bin (= 2.02~beta2-36ubuntu3.12) but 
2.02~beta2-36ubuntu3.11 is to be installed
  E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify 
a solution).

  jefff@jefff-System-Product-Name:~$ sudo apt-get -f install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-4.8.0-36 linux-headers-4.8.0-36-generic 
linux-headers-4.8.0-53 linux-headers-4.8.0-53-generic 
linux-image-4.8.0-36-generic linux-image-4.8.0-53-generic 
linux-image-extra-4.8.0-36-generic
linux-image-extra-4.8.0-53-generic
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
grub-common grub-pc grub-pc-bin grub2-common
  Suggested packages:
multiboot-doc grub-emu xorriso desktop-base
  The following packages will be upgraded:
grub-common grub-pc grub-pc-bin grub2-common
  4 upgraded, 0 newly installed, 0 to remove and 221 not upgraded.
  2 not fully installed or removed.
  Need to get 4,337 kB of archives.
  After this operation, 5,120 B of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  Get:1 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 util-linux 
i386 2.27.1-6ubuntu3.3 [875 kB]
  Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 grub-pc 
i386 2.02~beta2-36ubuntu3.12 [197 kB]
  Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 
grub-pc-bin i386 2.02~beta2-36ubuntu3.12 [915 kB]
  Get:4 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 
grub2-common i386 2.02~beta2-36ubuntu3.12 [545 kB]
  Get:5 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 
grub-common i386 2.02~beta2-36ubuntu3.12 [1,806 kB]
  Fetched 4,337 kB in 0s (6,404 kB/s)
  Preconfiguring packages ...
  dpkg: error processing package util-linux (--configure):
   package is in a very bad inconsistent state; you should
   reinstall it before attempting configuration
  Errors were encountered while processing:
   util-linux
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  jefff@jefff-System-Product-Name:~$ 

  jefff@jefff-System-Product-Name:~$ sudo apt-get -f install grub-common
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  You might want to run 'apt-get -f install' to correct these:
  The following packages have unmet dependencies:
   grub-pc : Depends: grub2-common (= 2.02~beta2-36ubuntu3.12) but 
2.02~beta2-36ubuntu3.11 is to be installed
 Depends: grub-pc-bin (= 2.02~beta2-36ubuntu3.12) but 
2.02~beta2-36ubuntu3.11 is to be installed
   grub-pc-bin : Depends: grub-common (= 2.02~beta2-36ubuntu3.11) but 
2.02~beta2-36ubuntu3.12 is to be installed
   grub2-common : Depends: grub-common (= 2.02~beta2-36ubuntu3.11) but 
2.02~beta2-36ubuntu3.12 is to be installed
  E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify 
a solution).
  jefff@jefff-System-Product-Name:~$ 

  jefff@jefff-System-Product-Name:~$ sudo apt-get -f install grub2-common
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  You might want to run 'apt-get -f install' to correct these:
  The following packages have unmet dependencies:
   grub-pc : Depends: grub-common (= 2.02~beta2-36ubuntu3.12) but 
2.02~beta2-36ubuntu3.11 is to be installed
 Depends: grub-pc-bin (= 2.02~beta2-36ubuntu3.12) but 
2.02~beta2-36ubuntu3.11 is to be installed
   grub2-common : Depends: grub-common (= 2.02~beta2-36ubuntu3.12) but 
2.02~beta2-36ubuntu3.11 is to be installed
  E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify 
a solution).

  jefff@jefff-System-Produ

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

[Phillip Susi]

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

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

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

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  not working

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

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

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

[Touch-packages] [Bug 1713175] Re: Obsolete backup ext2/3/4 superblocks can confuse e2fsck on an encrypted LUKS partition

[Phillip Susi]

I have to disagree; the only tool that uses the backup superblock is
e2fsck, and if you accidentally run wipefs on the volume, you should be
able to recover it with e2fsck.

If you don't want to attempt to recover a filesystem there, then don't
run e2fsck.


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

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

Title:
  Obsolete backup ext2/3/4 superblocks can confuse e2fsck on an
  encrypted LUKS partition

Status in cryptsetup package in Ubuntu:
  Confirmed
Status in e2fsprogs package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  fsck.ext4 runs on a LUKS partition and starts to correct inode
  entries, rendering the partition corrupted and useless. It seems like
  it should defensively check where it is an isLuks partition using
  "cryptsetup isLuks /dev/sda1" before continuing to modify it.

  I hope such a defensive check can be added.

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

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

[Touch-packages] [Bug 1713186] Re: package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Phillip Susi]

You have broken third party init scripts installed ( "K01.depend.boot"
for example ).  You will need to fix or remove them.


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

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

Title:
  package util-linux 2.29-1ubuntu2.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Aug 25 21:35:55 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-06-29 (423 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: util-linux
  Title: package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-08-26 (0 days ago)

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

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

[Touch-packages] [Bug 1712113] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgcannot updaterade: package bsdutils is not ready for configuration cannot configure (current status 'half-insta

[Phillip Susi]

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

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

Title:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgcannot
  updaterade: package bsdutils is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  tried to install unetbootin = failed. Cannot update core packages via
  software updater

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Mon Aug 21 17:10:30 2017
  DpkgHistoryLog:
   Start-Date: 2017-08-21  17:10:30
   Commandline: aptdaemon role='role-install-packages' sender=':1.76'
   Install: extlinux:amd64 (3:6.03+dfsg-14.1, automatic), unetbootin:amd64 
(608-1), gksu:amd64 (2.0.2-9ubuntu1, automatic), unetbootin-translations:amd64 
(608-1, automatic)
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package bsdutils is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package bsdutils is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-03-08 (165 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package 
bsdutils is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (126 days ago)

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

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

[Touch-packages] [Bug 1679220] Re: Installer pulls packages from other releases in the pool

[Phillip Susi]

To install the system in the first place of course.

Normally the installer iso contains a /pool directory with a single
release directory, but if someone later uses the usb creator to extract
another iso for another release, they end up with a /pool directory with
two different release directories under it, and apt searches both
releases for packages to install causing all sorts of problems.

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

Title:
  Installer pulls packages from other releases in the pool

Status in apt package in Ubuntu:
  New

Bug description:
  Frequently people reuse a USB stick to install another release, and
  the install fails because apt tries to pull packages from the wrong
  release.  Apt should only be looking in the pool for the current
  release rather than everything it can find.

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

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

[Touch-packages] [Bug 1711048] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet bsdutils n'est pas prêt pour la configuration configuration impossible (état actuel « half-ins

[Phillip Susi]

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

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

Title:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet
  bsdutils n'est pas prêt pour la configuration  configuration
  impossible (état actuel « half-installed »)

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  ce bug est signalé au démarrage

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering:
   bsdutils:amd64: Configure
   libgd3:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Aug 16 08:04:58 2017
  DpkgTerminalLog:
   dpkg: erreur de traitement du paquet bsdutils (--configure) :
le paquet bsdutils n'est pas prêt pour la configuration
configuration impossible (état actuel « half-installed »)
  ErrorMessage: le paquet bsdutils n'est pas prêt pour la configuration  
configuration impossible (état actuel « half-installed »)
  InstallationDate: Installed on 2017-03-19 (149 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet 
bsdutils n'est pas prêt pour la configuration  configuration impossible (état 
actuel « half-installed »)
  UpgradeStatus: Upgraded to zesty on 2017-05-03 (104 days ago)

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

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

[Touch-packages] [Bug 1710694] Re: package util-linux 2.29-1ubuntu2 failed to install/upgrade: Paket util-linux ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »h

[Phillip Susi]

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

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

Title:
  package util-linux 2.29-1ubuntu2 failed to install/upgrade: Paket
  util-linux ist nicht bereit zur Konfiguration  kann nicht konfiguriert
  werden (momentaner Status »half-installed«)

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  package util-linux 2.29-1ubuntu2 failed to install/upgrade: Paket
  util-linux ist nicht bereit zur Konfiguration  kann nicht konfiguriert
  werden (momentaner Status »half-installed«)

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sat Aug 12 13:41:53 2017
  DpkgTerminalLog:
   dpkg: Fehler beim Bearbeiten des Paketes util-linux (--configure):
Paket util-linux ist nicht bereit zur Konfiguration
kann nicht konfiguriert werden (momentaner Status »half-installed«)
  ErrorMessage: Paket util-linux ist nicht bereit zur Konfiguration  kann nicht 
konfiguriert werden (momentaner Status »half-installed«)
  InstallationDate: Installed on 2017-05-13 (93 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: Paket 
util-linux ist nicht bereit zur Konfiguration  kann nicht konfiguriert werden 
(momentaner Status »half-installed«)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1710066] Re: software update problem. Installation error reported frequently

[Phillip Susi]

You have several third party init scripts installed that are broken,
including "K01.depend.boot".  You will need to remove them.


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

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

Title:
  software update problem.  Installation error reported frequently

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Routine software updates always finish with a failure to instal one
  (or possibly more) updated software package downloads.

  Also, my particular Acer Aspire E 15 Start almost never shuts down and
  has to be manually switched off after disk reading and writing
  activity has stopped.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Fri Aug 11 06:32:42 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-10-17 (663 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (376 days ago)

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

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

[Touch-packages] [Bug 1707645] Re: system with high numbered uids has huge sparse /var/log/lastlog

[Phillip Susi]

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

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

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

Title:
  system with high numbered uids has huge sparse /var/log/lastlog

Status in pam package in Ubuntu:
  New
Status in shadow package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  I was investigating the use of a single high UID user (ie, 20)
  and discovered that /var/log/lastlog grew to an enormously large
  sparse file:

  $ ls -lh /var/log/lastlog 
  -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog

  The file is actually quite small though:
  $ ls -lh --size /var/log/lastlog 
  56K -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog

  On a standalone system, this is possibly not a problem since it is
  highly unlikely that a system will have 2 billion users, but this is
  confirmed to wreak havoc on rsync backups.

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

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

[Touch-packages] [Bug 1708888] Re: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Phillip Susi]

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

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

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

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  installation of calibre and other applications failed.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Fri Aug  4 19:28:57 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-06-08 (58 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1708438] Re: package util-linux 2.29-1ubuntu2 failed to install/upgrade: pacote util-linux não está pronto para configuração não posso configurar (estado atual 'half-installed')

[Phillip Susi]

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

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

Title:
  package util-linux 2.29-1ubuntu2 failed to install/upgrade: pacote
  util-linux não está pronto para configuração  não posso configurar
  (estado atual 'half-installed')

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  Not install

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Jul 26 06:27:22 2017
  DpkgTerminalLog:
   dpkg: erro ao processar o pacote util-linux (--configure):
pacote util-linux não está pronto para configuração
não posso configurar (estado atual 'half-installed')
  ErrorMessage: pacote util-linux não está pronto para configuração  não posso 
configurar (estado atual 'half-installed')
  InstallationDate: Installed on 2017-06-06 (57 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: pacote 
util-linux não está pronto para configuração  não posso configurar (estado 
atual 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1708602] Re: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor

[Phillip Susi]

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

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

Title:
  package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: Paket
  ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es
  nochmal installieren, bevor Sie die Konfiguration versuchen.

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed Aug  2 20:08:22 2017
  DpkgTerminalLog:
   dpkg: Fehler beim Bearbeiten des Paketes bsdutils (--configure):
Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es
nochmal installieren, bevor Sie die Konfiguration versuchen.
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  InstallationDate: Installed on 2017-04-15 (110 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: Paket 
ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es  nochmal 
installieren, bevor Sie die Konfiguration versuchen.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Phillip Susi]

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


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

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

Title:
  bsdutils conflict

Status in util-linux package in Ubuntu:
  Incomplete

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

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

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

[Touch-packages] [Bug 1705565] Re: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

[Phillip Susi]

You have a broken third party init script named "runmbbservice"
installed.  You will need to remove it or add appropriate LSB tags to
it.


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

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

Title:
  package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  1) release:
  Ubuntu 16.04.2 LTS Release 16.04
  2) Version of Package:
  util-linux:
Installiert:   2.27.1-6ubuntu3.3
Installationskandidat: 2.27.1-6ubuntu3.3
Versionstabelle:
   *** 2.27.1-6ubuntu3.3 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.27.1-6ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  3) I want to perform apt-get upgrade
  4) apt-get upgrade ends with:
  insserv: Starting runmbbservice depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: There is a loop between service runmbbservice and dns-clean if 
started
  insserv:  loop involving service dns-clean at depth 1
  insserv: Starting runmbbservice depends on plymouth and therefore on system 
facility `$all' which can not be true!
  insserv: exiting now without changing boot order!
  update-rc.d: error: insserv rejected the script header
  dpkg: Fehler beim Bearbeiten des Paketes util-linux (--configure):
   Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 
zurück
  Fehler traten auf beim Bearbeiten von:
   util-linux
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.3
  Uname: Linux 4.7.1-040701-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Jul 20 18:32:18 2017
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1704898] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Phillip Susi]

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

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

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

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  Not installing Wine

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

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

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

[Touch-packages] [Bug 1704825] Re: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: el paquete bsdutils no está listo para configurarse no se puede configurar (estado actual `half-instal

[Phillip Susi]

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

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

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

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

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

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

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

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

[Touch-packages] [Bug 1704541] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: o pacote bsdutils não está pronto para configuração não pode configurar (status actual `half-installed')

[Phillip Susi]

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

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

Title:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: o pacote
  bsdutils não está pronto para configuração  não pode configurar
  (status actual `half-installed')

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  Poped up when using Mozilla Thunderbird on my gmail Account.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  Date: Sat Jul 15 09:58:53 2017
  DpkgTerminalLog:
   dpkg: erro ao processar o pacote bsdutils (--configure):
o pacote bsdutils não está pronto para configuração
não pode configurar (status actual `half-installed')
  ErrorMessage: o pacote bsdutils não está pronto para configuração  não pode 
configurar (status actual `half-installed')
  InstallationDate: Installed on 2017-01-04 (191 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: o pacote 
bsdutils não está pronto para configuração  não pode configurar (status actual 
`half-installed')
  UpgradeStatus: Upgraded to zesty on 2017-05-17 (58 days ago)

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

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

[Touch-packages] [Bug 1703772] Re: package util-linux 2.29-1ubuntu2 [modified: bin/dmesg bin/lsblk bin/more bin/mountpoint bin/tailf bin/wdctl sbin/agetty sbin/blkdiscard sbin/blkid sbin/blockdev sbin

[Phillip Susi]

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

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

Title:
  package util-linux 2.29-1ubuntu2 [modified: bin/dmesg bin/lsblk
  bin/more bin/mountpoint bin/tailf bin/wdctl sbin/agetty
  sbin/blkdiscard sbin/blkid sbin/blockdev sbin/cfdisk sbin/chcpu
  sbin/ctrlaltdel sbin/fdisk sbin/findfs sbin/fsck sbin/fsck.cramfs
  sbin/fsck.minix sbin/fsfreeze sbin/fstrim sbin/hwclock sbin/isosize
  sbin/mkfs sbin/mkfs.bfs sbin/mkfs.cramfs sbin/mkfs.minix sbin/mkswap
  sbin/pivot_root sbin/raw sbin/runuser sbin/sfdisk sbin/sulogin
  sbin/swaplabel sbin/switch_root sbin/wipefs sbin/zramctl
  usr/bin/addpart usr/bin/chrt usr/bin/delpart usr/bin/fallocate
  usr/bin/flock usr/bin/getopt usr/bin/ionice usr/bin/ipcmk
  usr/bin/ipcrm usr/bin/ipcs usr/bin/last usr/bin/line usr/bin/lscpu
  usr/bin/lsipc usr/bin/lslocks usr/bin/lslogins usr/bin/lsns
  usr/bin/mcookie usr/bin/mesg usr/bin/namei usr/bin/nsenter
  usr/bin/partx usr/bin/pg usr/bin/prlimit usr/bin/rename.ul
  usr/bin/resizepart usr/bin/rev usr/bin/setarch usr/bin/setsid
  usr/bin/setterm usr/bin/taskset usr/bin/unshare usr/bin/utmpdump
  usr/bin/whereis usr/sbin/fdformat usr/sbin/ldattach
  usr/sbin/readprofile usr/sbin/rtcwake usr/sbin/tunelp] failed to
  install/upgrade: package util-linux is not ready for configuration
  cannot configure (current status 'half-installed')

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  Trying to install apcupsd I had this error

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   util-linux:amd64: Configure
   apcupsd-doc:amd64: Install
   libusb-0.1-4:amd64: Install
   apcupsd:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Jul 12 09:09:09 2017
  DpkgTerminalLog:
   dpkg: error processing package util-linux (--configure):
package util-linux is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package util-linux is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-04-24 (78 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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