[Touch-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

[Frank Heimes]

** Changed in: ubuntu-power-systems
   Status: New => Triaged

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

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

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+subscriptions

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

[Touch-packages] [Bug 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-themes (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  gedit edit window  is transparent when using Ambiance and Radiance
  themes

Status in gedit package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Expired

Bug description:
  In a freshly booted and fully updated Ubuntu 16.10 the edit window of
  gedit is transparent using the *Classic* colour scheme. Other colour
  schemes seem to work as intended.

  The text of loaded files shows against the desktop wallpaper but when
  no files are loaded gedit displays its edit window or pane as it
  should do.

  To clarify this bug is only apparent when a file is loaded.

  I don't know when this started as I don't normally used gedit to edit
  files. I haven't found any other application affected by this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gedit 3.20.2-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep  6 21:01:35 2016
  InstallationDate: Installed on 2016-03-11 (179 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c

[Karl Schindler]

old and still not fixed:
(SWT:7981): GLib-CRITICAL **: Source ID 383 was not found when attempting to 
remove it

Ubuntu 16.10 kernel 4.11.8-041108-generic

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

Title:
  GLib-CRITICAL **: Source ID was not found when attempting to remove it
  - warning when leaving Network menu of g-c-c

Status in AndroidSDK:
  New
Status in Banshee:
  New
Status in gnome-control-center:
  Incomplete
Status in GParted:
  Unknown
Status in notification-daemon:
  New
Status in anjuta package in Ubuntu:
  Confirmed
Status in consolekit package in Ubuntu:
  Confirmed
Status in f-spot package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in putty package in Ubuntu:
  Confirmed

Bug description:
  Steps to recreate:
  1. Open gnome-control-center in terminal.
  2. Go to Network.
  3. Go back to All preferences.
  4. Notice that in terminal there is a warning:

  $ gnome-control-center

  (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not
  found when attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu49
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 26 21:03:52 2013
  InstallationDate: Installed on 2013-10-15 (71 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131015)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago)

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

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

[Touch-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair

[aidanjt]

I'm having the same problem with PCI ID 1102:0012 & sub ID 1102:0010.
It's a SB Z OEM (no fancy shroud).

** Attachment added: "alsainfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1166529/+attachment/4926854/+files/alsainfo.txt

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

Title:
  Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken
  Beyond All Repair

Status in ALSA driver:
  Unknown
Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Debian:
  New

Bug description:
  [WORKAROUND] Run the following command:

  echo "options snd-hda-intel position_fix=1" | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.: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: To be filled by O.E.M.

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

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

[Touch-packages] [Bug 1599874] Re: no rear sound creative sound blaster Z ssid: 1102:0023

[aidanjt]

I'm having the same problem with PCI ID 1102:0012 & sub ID 1102:0010.
It's a SB Z OEM (no fancy shroud).

** Attachment added: "alsainfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1599874/+attachment/4926853/+files/alsainfo.txt

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

Title:
   no rear sound creative sound blaster Z ssid: 1102:0023

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  it's long standing bug we can't use Z series cards properly on linux 
  only front panel work 
  rest of ports are not working

  I extracted latest firmware from windows driver but no luck 
  here are extra details from windows and freebsd drivers both are works fine

  freebsd pin configs;
  hdaa0: Patched pins configuration:
  hdaa0: nid   0xas seq device   conn  jackloccolor   misc
  hdaa0: 11 410140f0 15 0  Line-out  None  1/8 Rear   Green   0 DISA
  hdaa0: 12 014520f0 15 0  SPDIF-out Jack  Optical Rear   Grey0
  hdaa0: 13 010170f0 15 0  Line-out  Jack  1/8 Rear   Yellow  0
  hdaa0: 14 01c510f0 15 0  SPDIF-in  Jack  Optical Rear   Black   0
  hdaa0: 15 412000f0 15 0  HeadphonesNone  Unknown Rear   Unknown 0 DISA
  hdaa0: 16 022140f0 15 0  HeadphonesJack  1/8 Front  Green   0
  hdaa0: 17 418120f0 15 0  Line-in   None  1/8 Rear   Grey0 DISA
  hdaa0: 18 01a190f0 15 0  Mic   Jack  1/8 Rear   Pink0
  hdaa0: 19 50d000f0 15 0  Digital-inNone  Unknown Internal   Unknown 0 DISA
  hdaa0: 24 50f0 15 0  Line-out  None  Unknown Internal   Unknown 0 DISA

  pin configs from windows driver
  NID: 11
  Node: 0x0b
  Pin: 0x410140f0
  Verb 00B71CF0 00B71D40 00B71E01 00B71F41 

  NID: 12
  Node: 0x0c
  Pin: 0x014520f0
  Verb 00C71CF0 00C71D20 00C71E45 00C71F01 

  NID: 13
  Node: 0x0d
  Pin: 0x010171f0
  Verb 00D71CF0 00D71D71 00D71E01 00D71F01 

  NID: 14
  Node: 0x0e
  Pin: 0x01c510f0
  Verb 00E71CF0 00E71D10 00E71EC5 00E71F01 

  NID: 15
  Node: 0x0f
  Pin: 0x412000f0
  Verb 00F71CF0 00F71D00 00F71E20 00F71F41 

  NID: 16
  Node: 0x10
  Pin: 0x022140f0
  Verb 01071CF0 01071D40 01071E21 01071F02 

  NID: 17
  Node: 0x11
  Pin: 0x418120f0
  Verb 01171CF0 01171D20 01171E81 01171F41 

  NID: 18
  Node:0x12
  Pin:0x01a190f0
  Verb 01271CF0 01271D90 01271EA1 01271F01 

  NID: 19
  Node:0x13
  Pin:0x50d000f0
  Verb 01371CF0 01371D00 01371ED0 01371F50 

  NID: 24
  Node:0x18
  Pin:0x50f0
  Verb 01871CF0 01871D00 01871E00 01871F50

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  olci   1701 F pulseaudio
   /dev/snd/controlC0:  olci   1701 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul  7 16:48:52 2016
  InstallationDate: Installed on 2016-06-25 (11 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 7 (MS-7916)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.12:bd02/16/2016:svnMSI:pnMS-7916:pvr1.0:rvnMSI:rnZ97GAMING7(MS-7916):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7916
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1708563] [NEW] apport fails to inform when not sending report

[John Pye]

Public bug reported:

For quite some time now, I have experienced apport popup windows
reporting certain crashes. When I click to submit a report, the popup
window disappears and nothing further happens.

In the past, when closing the popup window, I used to see a new
Launchpad bug report where I could enter further details about what was
happening, or check that the bug had already been reported by others.

However that feature seems to have been disabled or become broken some
time ago.

If apport is going to silently ignore my request to report my bug, or is
reporting it somehow without feedback me, then either of these is poor
design, since there has been no feedback to me as the user about what is
happening.

Can I suggest that apport be changed to inform the user of whether or
not the crash report will be uploaded, and whether or not the user will
be redirected to give extra details? Then, if the firefox window fails
to popup, I can report a separate bug about that if needed.

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

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

Title:
  apport fails to inform when not sending report

Status in apport package in Ubuntu:
  New

Bug description:
  For quite some time now, I have experienced apport popup windows
  reporting certain crashes. When I click to submit a report, the popup
  window disappears and nothing further happens.

  In the past, when closing the popup window, I used to see a new
  Launchpad bug report where I could enter further details about what
  was happening, or check that the bug had already been reported by
  others.

  However that feature seems to have been disabled or become broken some
  time ago.

  If apport is going to silently ignore my request to report my bug, or
  is reporting it somehow without feedback me, then either of these is
  poor design, since there has been no feedback to me as the user about
  what is happening.

  Can I suggest that apport be changed to inform the user of whether or
  not the crash report will be uploaded, and whether or not the user
  will be redirected to give extra details? Then, if the firefox window
  fails to popup, I can report a separate bug about that if needed.

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

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

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

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: patch

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

[Steve Langasek]

The referenced upstream bug report shows that upstream agrees this is a
regression in systemd behavior which they are planning to correct, which
is reasonable.

However, I think this is also a bug in the kdump-tools package.
'default.target' is a meta-target, which no package can know whether
it's appropriate to start its service under without knowing what
default.target is set to.  In particular, kdump-tools also declares
'Wants=network-online.target'.  If default.target (either on the kernel
commandline or on the filesystem) is pointed to some sort of local-only
rescue target, having network-online pulled into this target via kdump-
tools could break the boot.

I think kdump-tools in Debian and Ubuntu should instead be integrating
with multi-user.target.

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

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

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

** Changed in: makedumpfile (Ubuntu)
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

** Changed in: systemd (Ubuntu)
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => 
Canonical Foundations Team (canonical-foundations)

** Changed in: ubuntu-power-systems
 Assignee: Canonical Foundations Team (canonical-foundations) => 
(unassigned)

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  New
Status in makedumpfile package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

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

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+subscriptions

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

[Touch-packages] [Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: patch

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

Title:
  Removing a linux-image-extra package fails, if /boot is about full

Status in initramfs-tools:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  System calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space
  in /boot temporarily. But there is no space left, if /boot is full.

  Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u".

  The fix could be to create the new initrg.img file in different partition 
before replacing the old one by it in update-initramfs. So the update-initramfs 
script should be fixed. But there may not be such a partition..
  Anyway the likely case when space runs out is when there is a separate /boot 
partition.

  Alternatively the init scripts should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 
  That may be worse way, as then initrd.img file is missing for longer period 
of time and system integrity may suffer in case of e.g. power cut.

  Related question: http://askubuntu.com/q/898499/21005
  The output of 'dpkg --purge' presented there shows that corresponding 
linux-image package may get successfully removed while the linux-image-extra is 
left broken. If the linux-image-extra package will be removed later, the 
post-installation script will create an initrd.img file for a non-installed 
kernel! Same would happen, if removing would be done by apt-get purge.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1708556] [NEW] Restart from within GUI gets stuck sometimes

[jerriy]

Public bug reported:

And this happens some of the time, not all the time.

It seemingly gets stuck at random points of the process too (sometimes
it gets stuck while shutting down - other times it gets stuck after boot
begins.

This is a new phenomenon that I never experienced before I reinstalled a
fresh one from by live disk yesterday.

Note (a matter may or may not be related): I disabled the graphics
during boot and noticed that that there are "ERROR" lines when it
loading (even when the restart is succesful).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
Uname: Linux 4.4.0-89-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Aug  4 01:42:12 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.4.0-31-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.4.0-89-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6620G] 
[1002:9641] (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] BeaverCreek [Radeon HD 6620G] [1025:059b]
 Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] 
[1002:6760] (rev ff) (prog-if ff)
InstallationDate: Installed on 2017-08-03 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Packard Bell EasyNote LS11SB
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=526db693-db5f-4daf-b737-feeb9317ed96 ro nopat vesafb.invalid=1 
plymouth:debug drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/02/2011
dmi.bios.vendor: Packard Bell
dmi.bios.version: V2.00
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SJV70-SB
dmi.board.vendor: Packard Bell
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Packard Bell
dmi.chassis.version: V2.00
dmi.modalias: 
dmi:bvnPackardBell:bvrV2.00:bd11/02/2011:svnPackardBell:pnEasyNoteLS11SB:pvrV2.00:rvnPackardBell:rnSJV70-SB:rvrBaseBoardVersion:cvnPackardBell:ct10:cvrV2.00:
dmi.product.name: EasyNote LS11SB
dmi.product.version: V2.00
dmi.sys.vendor: Packard Bell
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Aug  4 03:03:54 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.3
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  Restart from within GUI gets stuck sometimes

Status in xorg package in Ubuntu:
  New

Bug description:
  And this happens some of the time, not all the time.

  It seemingly gets stuck at random points of the process too (sometimes
  it gets stuck while shutting down - other times it gets stuck after
  boot begins.

  This is a new phenomenon that I never experienced before I reinstalled
  a fresh one from by live disk yesterday.

  Note (a matter may or may not be related): I disabled the graphics
  during boot and noticed that that there are "ERROR" lines when it
  loading (even when the restart is succesful).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Aug  4 

[Touch-packages] [Bug 1708511] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren

[Seth Arnold]

This may be a duplicate of bug 1692981. Thanks.

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade:
  Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie
  sollten es  nochmal installieren, bevor Sie die Konfiguration
  versuchen.

Status in openssl package in Ubuntu:
  New

Bug description:
  in screen there is the information for a conflict

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  Uname: Linux 4.4.0-70-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Aug  3 21:10:17 2017
  DpkgHistoryLog:
   Start-Date: 2017-08-03  21:10:10
   Commandline: apt-get install -f
   Requested-By: carsten (1000)
   Upgrade: grub-common:amd64 (2.02~beta2-36ubuntu3.11, 
2.02~beta2-36ubuntu3.12), grub2-common:amd64 (2.02~beta2-36ubuntu3.11, 
2.02~beta2-36ubuntu3.12), grub-pc:amd64 (2.02~beta2-36ubuntu3.11, 
2.02~beta2-36ubuntu3.12), grub-pc-bin:amd64 (2.02~beta2-36ubuntu3.11, 
2.02~beta2-36ubuntu3.12)
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  InstallationDate: Installed on 2017-02-11 (173 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 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/openssl/+bug/1708511/+subscriptions

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

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space

[Jarno Suni]

I think the patch presented at 
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/comments/8
might give more helpful error message, since it avoids filling /boot as long as 
possible, thus the system is unlikely to run out of space while running 
mkinitramfs, but finds out, if the system lacks free space, and if it does, it 
tells the URL of the documentation page concerning removing old kernels.

P.S. The URL could be https://help.ubuntu.com/community/LowDiskOnBoot
alternatively. (Luke W Faraone uses that in his merge proposal, and it
redirects to the same document currently.)

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space

Status in initramfs-tools:
  Confirmed
Status in Software Updater:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

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

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

[Touch-packages] [Bug 1708437] Re: package firebird3.0-server 3.0.1.32609.ds4-13 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

[Seth Arnold]

I added apport because of the python2 -> python3 regression; is there a
better way to point out these python3 bugs?

Thanks

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

Title:
  package firebird3.0-server 3.0.1.32609.ds4-13 failed to
  install/upgrade: подпроцесс установлен сценарий post-installation
  возвратил код ошибки 1

Status in apport package in Ubuntu:
  New
Status in firebird3.0 package in Ubuntu:
  New

Bug description:
  don't install this package:(

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: firebird3.0-server 3.0.1.32609.ds4-13
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic i686
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering:
   libib-util:i386: Install
   firebird3.0-server-core:i386: Install
   firebird3.0-server:i386: Install
   NULL: ConfigurePending
  Architecture: i386
  Date: Thu Aug  3 14:26:15 2017
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2017-07-24 (9 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: firebird3.0
  Title: package firebird3.0-server 3.0.1.32609.ds4-13 failed to 
install/upgrade: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1708437] Re: package firebird3.0-server 3.0.1.32609.ds4-13 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

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

Title:
  package firebird3.0-server 3.0.1.32609.ds4-13 failed to
  install/upgrade: подпроцесс установлен сценарий post-installation
  возвратил код ошибки 1

Status in apport package in Ubuntu:
  New
Status in firebird3.0 package in Ubuntu:
  New

Bug description:
  don't install this package:(

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: firebird3.0-server 3.0.1.32609.ds4-13
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic i686
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering:
   libib-util:i386: Install
   firebird3.0-server-core:i386: Install
   firebird3.0-server:i386: Install
   NULL: ConfigurePending
  Architecture: i386
  Date: Thu Aug  3 14:26:15 2017
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2017-07-24 (9 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: firebird3.0
  Title: package firebird3.0-server 3.0.1.32609.ds4-13 failed to 
install/upgrade: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full

[Jarno Suni]

Patch against current https://git.launchpad.net/~usd-import-
team/ubuntu/+source/initramfs-tools/tree/update-initramfs

** Attachment added: "patch concerning generate_initramfs function in 
update_initramfs"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+attachment/4926765/+files/1

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

Title:
  Removing a linux-image-extra package fails, if /boot is about full

Status in initramfs-tools:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  System calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space
  in /boot temporarily. But there is no space left, if /boot is full.

  Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u".

  The fix could be to create the new initrg.img file in different partition 
before replacing the old one by it in update-initramfs. So the update-initramfs 
script should be fixed. But there may not be such a partition..
  Anyway the likely case when space runs out is when there is a separate /boot 
partition.

  Alternatively the init scripts should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 
  That may be worse way, as then initrd.img file is missing for longer period 
of time and system integrity may suffer in case of e.g. power cut.

  Related question: http://askubuntu.com/q/898499/21005
  The output of 'dpkg --purge' presented there shows that corresponding 
linux-image package may get successfully removed while the linux-image-extra is 
left broken. If the linux-image-extra package will be removed later, the 
post-installation script will create an initrd.img file for a non-installed 
kernel! Same would happen, if removing would be done by apt-get purge.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Jarno Suni]

According to commant #8
patch against current 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/initramfs-tools/tree/update-initramfs
Removes all leftover initramfs files, even after dkms is uninstalled.

** Attachment added: "patch against update-imitramfs"
   
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+attachment/4926764/+files/2

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1708520] [NEW] no hdmi signal

[ryan vaughan]

Public bug reported:

i cant connect my laptop to my tv through an hdmi it says no signal

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
Uname: Linux 4.4.0-87-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Aug  3 15:38:45 2017
DistUpgraded: 2017-07-29 00:23:28,354 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Carrizo [103c:80b0]
InstallationDate: Installed on 2017-07-14 (20 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
MachineType: HP HP Pavilion Notebook
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic 
root=UUID=5893fc24-8d35-43ea-8baf-d032c38f7919 ro nomodeset quiet splash 
vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2017-07-29 (5 days ago)
dmi.bios.date: 07/14/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.10
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 80B0
dmi.board.vendor: HP
dmi.board.version: 81.27
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.10:bd07/14/2015:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B0:rvr81.27:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion Notebook
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Aug  3 15:34:47 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.3

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  no hdmi signal

Status in xorg package in Ubuntu:
  New

Bug description:
  i cant connect my laptop to my tv through an hdmi it says no signal

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Aug  3 15:38:45 2017
  DistUpgraded: 2017-07-29 00:23:28,354 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Carrizo [103c:80b0]
  InstallationDate: Installed on 2017-07-14 (20 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic 
root=UUID=5893fc24-8d35-43ea-8baf-d032c38f7919 ro nomodeset quiet splash 
vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-07-29 (5 days ago)
  dmi.bios.date: 07/14/2015
  

[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

[NJ]

I experience the same state of affairs on Linux Mint x64 18.2 Cinnamon.

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Touch-packages] [Bug 1708511] [NEW] package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installier

[Carsten Hofmann]

Public bug reported:

in screen there is the information for a conflict

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8
ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
Uname: Linux 4.4.0-70-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Aug  3 21:10:17 2017
DpkgHistoryLog:
 Start-Date: 2017-08-03  21:10:10
 Commandline: apt-get install -f
 Requested-By: carsten (1000)
 Upgrade: grub-common:amd64 (2.02~beta2-36ubuntu3.11, 2.02~beta2-36ubuntu3.12), 
grub2-common:amd64 (2.02~beta2-36ubuntu3.11, 2.02~beta2-36ubuntu3.12), 
grub-pc:amd64 (2.02~beta2-36ubuntu3.11, 2.02~beta2-36ubuntu3.12), 
grub-pc-bin:amd64 (2.02~beta2-36ubuntu3.11, 2.02~beta2-36ubuntu3.12)
ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
InstallationDate: Installed on 2017-02-11 (173 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssl
Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 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)

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


** Tags: apport-package i386 xenial

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade:
  Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie
  sollten es  nochmal installieren, bevor Sie die Konfiguration
  versuchen.

Status in openssl package in Ubuntu:
  New

Bug description:
  in screen there is the information for a conflict

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8
  ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
  Uname: Linux 4.4.0-70-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Aug  3 21:10:17 2017
  DpkgHistoryLog:
   Start-Date: 2017-08-03  21:10:10
   Commandline: apt-get install -f
   Requested-By: carsten (1000)
   Upgrade: grub-common:amd64 (2.02~beta2-36ubuntu3.11, 
2.02~beta2-36ubuntu3.12), grub2-common:amd64 (2.02~beta2-36ubuntu3.11, 
2.02~beta2-36ubuntu3.12), grub-pc:amd64 (2.02~beta2-36ubuntu3.11, 
2.02~beta2-36ubuntu3.12), grub-pc-bin:amd64 (2.02~beta2-36ubuntu3.11, 
2.02~beta2-36ubuntu3.12)
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  InstallationDate: Installed on 2017-02-11 (173 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 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/openssl/+bug/1708511/+subscriptions

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

[Touch-packages] [Bug 1708166] Re: systemd/udev does not rename network interfaces specified in .link files

[Wladimir Mutel]

steps 1) and 2) really helped me to make this work

now I am wondering where in the Ubuntu documentation I could find about
this ?

I see similar questions on the Internet, with most responses like
'revert to the old way of /etc/udev/rules.d/70-persistent-net.rules',
'disable net.ifnames', 'link /dev/null into /etc/udev/rules.d/80-net-
setup-link.rules', etc.

Only here on Launchpad I was able to get the proper and working response from 
you
How did you learn about doing this right ? :>

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

Title:
  systemd/udev does not rename network interfaces specified in .link
  files

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  $ ip link show
  ...
  2: enp2s0:  mtu 1500 qdisc pfifo_fast state 
UP mode DEFAULT group default qlen 1000
  link/ether d0:50:99:76:a1:bf brd ff:ff:ff:ff:ff:ff

  $ cat /etc/systemd/network/eth0.link
  [Match]
  MACAddress=d0:50:99:76:a1:bf
  [Link]
  Name=eth0

  I am pretty sure that MAC addresses do match
  And I don't change net.ifnames to 0 :

  $ cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic.efi.signed 
root=/dev/mapper/vg_smart-root_smart ro

  then :

  $ sudo udevadm test-builtin net_setup_link /sys/class/net/enp2s0
  [sudo] password for mwg:
  calling: test-builtin
  === trie on-disk ===
  tool version:  229
  file size: 6841778 bytes
  header size 80 bytes
  strings1755242 bytes
  nodes  5086456 bytes
  Load module index
  timestamp of '/etc/systemd/network' changed
  Parsed configuration file /etc/systemd/network/eth0.link
  Parsed configuration file /lib/systemd/network/99-default.link
  Created link configuration context.
  ID_NET_DRIVER=r8169
  Config file /lib/systemd/network/99-default.link applies to device enp2s0
  ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
  Unload module index
  Unloaded link configuration context.

  (and, surely, the interface is renamed from eth0 to enp2s0 on boot,
  but not renamed back afterwards)

  can you please tell where I could be wrong ?

  on my existing systems I still keep MAC->ifname relations in
  /etc/udev/rules.d/70-persistent-net.rules inherited from past Ubuntu
  versions. But this is a new setup of Ubuntu 16.04 and I would like to
  configure it in the new & recommended way.

  thanks in advance for your replies

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

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

[Touch-packages] [Bug 1708500] [NEW] [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] No sound at all. Rebooting does not fix & unmuting via alsamixer addresses the issue but audio plays

[Miguel Mendoza]

Public bug reported:

Rebooting does not fix & unmuting via alsamixer addresses the issue but
audio plays from internal speakers AND headphones

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
Uname: Linux 4.4.0-87-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mmendoza   2636 F pulseaudio
 /dev/snd/controlC1:  mmendoza   2636 F pulseaudio
CurrentDesktop: Unity
Date: Thu Aug  3 10:28:03 2017
InstallationDate: Installed on 2015-09-29 (674 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mmendoza   2636 F pulseaudio
 /dev/snd/pcmC1D0p:   mmendoza   2636 F...m pulseaudio
 /dev/snd/controlC1:  mmendoza   2636 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] No sound 
at all
UpgradeStatus: Upgraded to xenial on 2016-10-01 (305 days ago)
dmi.bios.date: 05/13/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 06HN6G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/13/2015:svnDellInc.:pnLatitudeE7450:pvr01:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7450
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] No sound
  at all. Rebooting does not fix & unmuting via alsamixer addresses the
  issue but audio plays from internal speakers AND headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Rebooting does not fix & unmuting via alsamixer addresses the issue
  but audio plays from internal speakers AND headphones

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mmendoza   2636 F pulseaudio
   /dev/snd/controlC1:  mmendoza   2636 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Aug  3 10:28:03 2017
  InstallationDate: Installed on 2015-09-29 (674 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mmendoza   2636 F pulseaudio
   /dev/snd/pcmC1D0p:   mmendoza   2636 F...m pulseaudio
   /dev/snd/controlC1:  mmendoza   2636 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] No sound 
at all
  UpgradeStatus: Upgraded to xenial on 2016-10-01 (305 days ago)
  dmi.bios.date: 05/13/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 06HN6G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/13/2015:svnDellInc.:pnLatitudeE7450:pvr01:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

[dlotton]

Just did a fresh install of Mint Mate 18.2 onto a new machine. Same
problem exists.  While connected to VPN DNS queries are leaking to non-
VPN interface.

This needs to be fixed!

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6-0ubuntu0.16.04.1

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid

Bug description:
  I use my company's cisco vpn via network-manager in Ubuntu 16.04.2
  LTS. After recent upgrade of network-manager:amd64 from version
  1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS
  resolution of VPN's server hostnames does not work. Roll back to
  version 1.2.2-0ubuntu0.16.04.4 solves the problem.

  Steps for reproducing:
  1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to 
version 1.2.6-0ubuntu0.16.04.1
  2. connect to VPN via network-manager applet
  3. nslookop servername.internal --> ** server can't find servername.internal: 
NXDOMAIN
  4. disconnect from VPN via network-manager applet
  5. roll back network-manager via command: sudo apt-get install 
network-manager=1.2.2-0ubuntu0.16.04.4
  6. restart network-manager via sudo service network-manager restart
  7. connect to VPN via network-manager applet
  8. nslookop servername.internal --> the server is resolved correctly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  9 19:49:55 2017
  InstallationDate: Installed on 2015-10-05 (520 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1702741] Re: QtCreator crashes when opening a filechooser under wayland

[Launchpad Bug Tracker]

This bug was fixed in the package qtbase-opensource-src - 5.7.1+dfsg-
2ubuntu4~1.17.04.1

---
qtbase-opensource-src (5.7.1+dfsg-2ubuntu4~1.17.04.1) zesty; urgency=medium

  * Backport upstream fix to fix GTK+ file dialog crash on Wayland
(gtkdialogs_wayland.diff; closes: #850746) (LP: #1702741)

 -- Jeremy Bicha   Thu, 06 Jul 2017 15:42:37 -0400

** Changed in: qtbase-opensource-src (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

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

Title:
  QtCreator crashes when opening a filechooser under wayland

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

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

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

  The file chooser should open without crashing the app

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

  
  == Upstream ==

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

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

  == Debug output ==

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

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

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

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

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

[Touch-packages] [Bug 1702741] Update Released

[Brian Murray]

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

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

Title:
  QtCreator crashes when opening a filechooser under wayland

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

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

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

  The file chooser should open without crashing the app

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

  
  == Upstream ==

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

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

  == Debug output ==

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

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

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

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

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

[Touch-packages] [Bug 1708453] Re: package dnsmasq-base 2.75-1ubuntu0.16.04.2 failed to install/upgrade: package dnsmasq-base is not ready for configuration cannot configure (current status 'half-inst

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: hardware-error

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

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

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

Title:
  package dnsmasq-base 2.75-1ubuntu0.16.04.2 failed to install/upgrade:
  package dnsmasq-base is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in dnsmasq package in Ubuntu:
  Invalid

Bug description:
  it was half installed. so I reinstalled it. when I restarted my
  computer, this error popped up

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq-base 2.75-1ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   unity-control-center: Remove
   dnsmasq-base: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Aug  3 14:48:10 2017
  DuplicateSignature:
   package:dnsmasq-base:2.75-1ubuntu0.16.04.2
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package dnsmasq-base (--configure):
package dnsmasq-base is not ready for configuration
  ErrorMessage: package dnsmasq-base is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-08-18 (349 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: dnsmasq
  Title: package dnsmasq-base 2.75-1ubuntu0.16.04.2 failed to install/upgrade: 
package dnsmasq-base 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/dnsmasq/+bug/1708453/+subscriptions

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

[Touch-packages] [Bug 1708314] Re: Regression test-namespace fails on armhf in lxc1 container on arm64 kernel

[Brian Murray]

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

** Tags removed: rls-aa-incoming

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

Title:
  Regression test-namespace fails on armhf in lxc1 container on arm64
  kernel

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Artful:
  New

Bug description:
  Regression test-namespace fails on armhf in lxc1 container on arm64
  kernel

  # /usr/lib/systemd/tests/test-namespace 
  Assertion 'r >= 0' failed at ../src/test/test-namespace.c:84, function 
test_netns(). Aborting.
  Assertion 'r >= 0' failed at ../src/test/test-namespace.c:93, function 
test_netns(). Aborting.
  Assertion 'r >= 0' failed at ../src/test/test-namespace.c:102, function 
test_netns(). Aborting.
  Assertion 'si.si_code == CLD_EXITED' failed at 
../src/test/test-namespace.c:108, function test_netns(). Aborting.
  Aborted (core dumped)

  This appears to be related to
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1708313

  to check: lxd (privileged / not priviledged)
  to check: lxc privileged
  to check: armhf on armhf
  to check: priviledged armhf on armhf
  to do: git bisect regression

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

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

[Touch-packages] [Bug 1707880] Re: newly installed additional units are not started on upgrade

[Dimitri John Ledkov]

Or as per adam. If the deb-systemd-invoke tracks magic state at install
time, and knows which units are brand new, it should do start on those,
and retry-start on the known updated units.

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

Title:
  newly installed additional units are not started on upgrade

Status in apt package in Ubuntu:
  New
Status in debhelper package in Ubuntu:
  New
Status in apt source package in Zesty:
  New
Status in debhelper source package in Zesty:
  New
Status in apt source package in Artful:
  New
Status in debhelper source package in Artful:
  New

Bug description:
  Upon upgrading apt from a version that only ships apt-daily.timer to
  the one that ships apt-daily.timer and apt-daily-upgrade.timer, the
  latter is not started on zesty and later.

  I believe this may be a bug in dh_systemd_start:

  # Automatically added by dh_systemd_start
  if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
if [ -n "$2" ]; then
_dh_action=try-restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action apt-daily-upgrade.timer apt-daily.timer 
>/dev/null || true
  fi
  # End automatically added section

  This reduces to:
  deb-systemd-invoke try-restart apt-daily-upgrade.timer apt-daily.timer 
>/dev/null || true

  which is (after calling/checking policy-rc.d) is:
  systemctl try-restart apt-daily-upgrade.timer apt-daily.timer >/dev/null || 
true

  This is correct, for the apt-daily.timer and does nothing for the apt-
  daily-upgrade.timer. Since apt-daily-upgrade.timer is not active, try-
  restart does not start it.

  Imho, there should be an extra snippet in apt.postinst which does
  this:

  if [ -d /run/systemd/system ]; then
if dpkg --compare $2 with version that introduces 
apt-daily-upgrade.timer; then
deb-systemd-invoke start apt-daily-upgrade.timer >/dev/null || 
true
fi
  fi

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

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

[Touch-packages] [Bug 1708313] Re: PrivateNetwork=yes fails in lxc1 armhf on arm64 kernel

[Dimitri John Ledkov]

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

** Tags removed: rls-aa-incoming

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

Title:
  PrivateNetwork=yes fails in lxc1 armhf on arm64 kernel

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Artful:
  New

Bug description:
  PrivateNetwork=yes fails in lxc1 armhf on arm64 kernel

  this thus results in failure to start systemd-hostnamed which leads to
  hostnamed failure.

  to check: lxd
  to check: armhf on armhf

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

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

[Touch-packages] [Bug 1707880] Re: newly installed additional units are not started on upgrade

[Dimitri John Ledkov]

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

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

** Tags removed: rls-aa-incoming

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

Title:
  newly installed additional units are not started on upgrade

Status in apt package in Ubuntu:
  New
Status in debhelper package in Ubuntu:
  New
Status in apt source package in Zesty:
  New
Status in debhelper source package in Zesty:
  New
Status in apt source package in Artful:
  New
Status in debhelper source package in Artful:
  New

Bug description:
  Upon upgrading apt from a version that only ships apt-daily.timer to
  the one that ships apt-daily.timer and apt-daily-upgrade.timer, the
  latter is not started on zesty and later.

  I believe this may be a bug in dh_systemd_start:

  # Automatically added by dh_systemd_start
  if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
if [ -n "$2" ]; then
_dh_action=try-restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action apt-daily-upgrade.timer apt-daily.timer 
>/dev/null || true
  fi
  # End automatically added section

  This reduces to:
  deb-systemd-invoke try-restart apt-daily-upgrade.timer apt-daily.timer 
>/dev/null || true

  which is (after calling/checking policy-rc.d) is:
  systemctl try-restart apt-daily-upgrade.timer apt-daily.timer >/dev/null || 
true

  This is correct, for the apt-daily.timer and does nothing for the apt-
  daily-upgrade.timer. Since apt-daily-upgrade.timer is not active, try-
  restart does not start it.

  Imho, there should be an extra snippet in apt.postinst which does
  this:

  if [ -d /run/systemd/system ]; then
if dpkg --compare $2 with version that introduces 
apt-daily-upgrade.timer; then
deb-systemd-invoke start apt-daily-upgrade.timer >/dev/null || 
true
fi
  fi

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

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

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

[Jeremy Bicha]

gnome-software in artful-proposed uses PackageKit instead of aptdaemon
https://launchpad.net/ubuntu/+source/gnome-software/3.25.4-1ubuntu1

** Changed in: gnome-software (Ubuntu)
   Status: New => Fix Committed

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1708476] Re: package libgtk2.0-common 2.24.30-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libgtk2.0-common 2.24.30-1ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgtk2.0-common 2.24.30-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   libglib2.0-0: Install
   libglib2.0-0: Configure
   libglib2.0-bin: Configure
   libgtk2.0-common: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Thu Aug  3 20:45:10 2017
  DuplicateSignature:
   package:libgtk2.0-common:2.24.30-1ubuntu1
   Setting up libglib2.0-bin (2.48.2-0ubuntu1) ...
   dpkg: error processing package libgtk2.0-common (--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-03 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: gtk+2.0
  Title: package libgtk2.0-common 2.24.30-1ubuntu1 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/gtk+2.0/+bug/1708476/+subscriptions

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

[Touch-packages] [Bug 1708476] [NEW] package libgtk2.0-common 2.24.30-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

[Zulfikar]

Public bug reported:

update

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgtk2.0-common 2.24.30-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
AptOrdering:
 libglib2.0-0: Install
 libglib2.0-0: Configure
 libglib2.0-bin: Configure
 libgtk2.0-common: Configure
 NULL: ConfigurePending
Architecture: i386
Date: Thu Aug  3 20:45:10 2017
DuplicateSignature:
 package:libgtk2.0-common:2.24.30-1ubuntu1
 Setting up libglib2.0-bin (2.48.2-0ubuntu1) ...
 dpkg: error processing package libgtk2.0-common (--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-03 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: gtk+2.0
Title: package libgtk2.0-common 2.24.30-1ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package libgtk2.0-common 2.24.30-1ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgtk2.0-common 2.24.30-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   libglib2.0-0: Install
   libglib2.0-0: Configure
   libglib2.0-bin: Configure
   libgtk2.0-common: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Thu Aug  3 20:45:10 2017
  DuplicateSignature:
   package:libgtk2.0-common:2.24.30-1ubuntu1
   Setting up libglib2.0-bin (2.48.2-0ubuntu1) ...
   dpkg: error processing package libgtk2.0-common (--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-03 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: gtk+2.0
  Title: package libgtk2.0-common 2.24.30-1ubuntu1 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/gtk+2.0/+bug/1708476/+subscriptions

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

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[Kevin Ard]

again, confirming: `sudo apt-get remove --purge dbus-user-session` and
reboot resolved it for me on Ubuntu 16.04. No side-effects. On reboot,
the Passwords>Login keyring was available, where before it wasn't.

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

Title:
  gnome-keyring not unlocked on boot

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Confirmed
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1676912] Re: Kernel 4.9+ regression: Suspend - Freezing of tasks failed

[Emile Heitor]

Same issue with kernel 4.9+ on a Macbook Pro on suspend from resume,
either with lid or suspend from shutdown menu.

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

Title:
  Kernel 4.9+ regression: Suspend - Freezing of tasks failed

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu
  Gnome 17.04 and since then sometimes my Laptop won't suspend when I
  close the lid. The power led does not blink like it is supposed to do
  and when I open the Laptop the lockscreen appears but freezes after a
  short time, followed by a blackscreen until eventually it reappears
  and allows me to unlock it. After that certain application can not be
  started anymore and would freeze if they were running before. These
  include Chrome, Gedit and Gnome System Monitor for example. Also my
  Laptop will not connect to my WLAN until I restart it.

  In syslog I found the line:

  "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to
  freeze, wq_busy=0):"

  According to syslog

  network-nanaeger
  whoopsie
  cups-browsed
  wpa-supplicant
  geoclue
  packagekitd
  several evolution-related processes
  goa-daemon
  gnome-software
  geary
  dropbox
  deja-dup-monitor

  are responsible.
  I tried disabling some of them, but it did not solve the problem.

  Update: I tested different Kernel versions in the last days. So far
  there were no issues with suspend/resume using Kernel 4.8 and 4.9. The
  problem is present in 4.10 and 4.11.

  Update 2: I just encountered this issue with Kernel 4.9.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 28 16:27:34 2017
  InstallationDate: Installed on 2017-03-24 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 80J8
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed 
root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B8CN31WW(V2.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Paganini
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 3 11
  dmi.modalias: 
dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311:
  dmi.product.name: 80J8
  dmi.product.version: Lenovo Yoga 3 11
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Jamie Strandboge]

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: In Progress => Won't Fix

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

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Won't Fix
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Currently snaps on Ubuntu Classic may declare in their snap.yaml that they 
want access to pulseaudio. When installed, snapd will auto-connect the 
pulseaudio interface giving the snap access to the pulseaudio server for 
playback and recording. Because recording is allowed, snaps are allowed to 
eavesdrop on users without the user knowing. Phase 1 of the pulseaudio 
interface should block recording for snaps while the details of phase 2 (which 
combines pulseaudio/snappy interfaces and trust-store) are worked out.

  [Test Case]
  First, install pulseaudio then reboot (alternatively can 'killall pulseaudio' 
from within your session or logout then killall pulseaudio from a vt and then 
log back in). pulseaudio needs to be restarted for the changes to be in effect 
and a reboot is the easiest way to achieve that.

  1. unconfined can play audio
  2. unconfined can record audio
  3. non-snap confined can play audio
  4. non-snap confined can record audio
  5. snap confined can play audio
  6. snap confined cannot record audio
  7. snap confined devmode can record audio
  8. indicator-sound and 'Sound Settings... works'
  9. click can record audio if trust-store allows (eg, 'SnapRecorder' from the 
store)
  10. click can play audio (eg, playback of recording from 'SnapRecorder' from 
the store)

  Currently '6' is not implemented and all snaps may record audio. When
  this bug is fixed, no snaps should be able to record audio (until
  phase 2 is implemented which will be in a different bug).

  The attached script tests 1-7. 9 and 10 require testing on a device
  and using

  [Regression Potential]
  The patch is quite small and easy to understand and is implemented to only 
affect processes that want to record and are running with a security label that 
starts with 'snap.' Unconfined processes and process running under other 
security labels should not be affected.

  Original description:
  Until we have a proper trust-store implementation with snappy and on the 
desktop/ubuntu core we want pulseaudio to simply deny any audio recording 
request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

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

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

[Touch-packages] [Bug 1708453] Re: package dnsmasq-base 2.75-1ubuntu0.16.04.2 failed to install/upgrade: package dnsmasq-base is not ready for configuration cannot configure (current status 'half-inst

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package dnsmasq-base 2.75-1ubuntu0.16.04.2 failed to install/upgrade:
  package dnsmasq-base is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  it was half installed. so I reinstalled it. when I restarted my
  computer, this error popped up

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq-base 2.75-1ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   unity-control-center: Remove
   dnsmasq-base: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Aug  3 14:48:10 2017
  DuplicateSignature:
   package:dnsmasq-base:2.75-1ubuntu0.16.04.2
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package dnsmasq-base (--configure):
package dnsmasq-base is not ready for configuration
  ErrorMessage: package dnsmasq-base is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-08-18 (349 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: dnsmasq
  Title: package dnsmasq-base 2.75-1ubuntu0.16.04.2 failed to install/upgrade: 
package dnsmasq-base 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/dnsmasq/+bug/1708453/+subscriptions

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

[Touch-packages] [Bug 1708453] [NEW] package dnsmasq-base 2.75-1ubuntu0.16.04.2 failed to install/upgrade: package dnsmasq-base is not ready for configuration cannot configure (current status 'half-in

[imrul kayesh ashraf]

Public bug reported:

it was half installed. so I reinstalled it. when I restarted my
computer, this error popped up

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: dnsmasq-base 2.75-1ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
Uname: Linux 4.4.0-87-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptOrdering:
 unity-control-center: Remove
 dnsmasq-base: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Aug  3 14:48:10 2017
DuplicateSignature:
 package:dnsmasq-base:2.75-1ubuntu0.16.04.2
 Processing triggers for mime-support (3.59ubuntu1) ...
 dpkg: error processing package dnsmasq-base (--configure):
  package dnsmasq-base is not ready for configuration
ErrorMessage: package dnsmasq-base is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2016-08-18 (349 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: dnsmasq
Title: package dnsmasq-base 2.75-1ubuntu0.16.04.2 failed to install/upgrade: 
package dnsmasq-base is not ready for configuration  cannot configure (current 
status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package dnsmasq-base 2.75-1ubuntu0.16.04.2 failed to install/upgrade:
  package dnsmasq-base is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  it was half installed. so I reinstalled it. when I restarted my
  computer, this error popped up

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq-base 2.75-1ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   unity-control-center: Remove
   dnsmasq-base: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Aug  3 14:48:10 2017
  DuplicateSignature:
   package:dnsmasq-base:2.75-1ubuntu0.16.04.2
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package dnsmasq-base (--configure):
package dnsmasq-base is not ready for configuration
  ErrorMessage: package dnsmasq-base is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-08-18 (349 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: dnsmasq
  Title: package dnsmasq-base 2.75-1ubuntu0.16.04.2 failed to install/upgrade: 
package dnsmasq-base 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/dnsmasq/+bug/1708453/+subscriptions

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

[Touch-packages] [Bug 1708326] Re: RM: obsolete product

[Dimitri John Ledkov]

Is qtmir a false removal as well then?
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1708327

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

Title:
  RM: obsolete product

Status in qtubuntu package in Ubuntu:
  Invalid

Bug description:
  qtubuntu was a component of Ubuntu Phone which is no longer developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:qtubuntu
  No reverse dependencies found

  $ reverse-depends -b src:qtubuntu
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1708326] Re: RM: obsolete product

[Dimitri John Ledkov]

Ack.

I have now seeded qtubuntu-desktop into supported-kiosk seed, with a
comment pointing at this bug.

This should prevent removal of qtubuntu. Sorry for the misshap here.

Regards,

Dimitri.

** Changed in: qtubuntu (Ubuntu)
   Status: Triaged => Invalid

** Tags removed: u8rm

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

Title:
  RM: obsolete product

Status in qtubuntu package in Ubuntu:
  Invalid

Bug description:
  qtubuntu was a component of Ubuntu Phone which is no longer developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:qtubuntu
  No reverse dependencies found

  $ reverse-depends -b src:qtubuntu
  No reverse dependencies found

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

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

[Touch-packages] [Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups

[LocutusOfBorg]

Only precise is still supported and affected by this bug, I don't think
this is worth the effort fixing it

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

Title:
  mdns listed in nsswitch.conf causes excessive time  for dns lookups

Status in avahi package in Ubuntu:
  Fix Released
Status in nss-mdns package in Ubuntu:
  Fix Released
Status in nss-mdns package in Debian:
  Fix Released

Bug description:
  Binary package hint: avahi-daemon

  I encountered this problem on a machine that is integrated into our
  work network. I performed a dist-upgrade to Feisty on my desktop and
  all went well. I've noticed recently that any dns based work seemed to
  take a significantly longer time then normal.

  My system is getting dns information on our company internal systems
  from two dns servers. Previously, if I tried to establish an ssh
  connection with another system I could generally expect the connection
  in under 3 secs.

  After the dist-upgrade the time went from under 3 seconds to
  approximately 25 seconds. After searching around the system I found an
  entry in /etc/nsswitch.conf that cause me a little concern. The line
  in question is:

 hosts:  files mdns4_minimal [NOTFOUND=return] dns mdns4

  I looked around a bit and it seems that the references to mdns are
  really talking about communication with the Avahi mDNS/DNS-SD daemon.
  Since this looks to be a part of a zeroconf configuration I wasn't
  expecting too much in my current environment, as we really only have
  three Mac's.

  What concerned me is the idea that if we hit files with no answer
  there is a delay while we hit the other options until we hit dns,
  which is where the information I seek existed.

  For an experiment I tried two separate tests. The first changed the
  line to looks like:

  hosts:  files dns mdns4_minimal [NOTFOUND=return] mdns

  The change should have improved the time, but I was still looking at
  approximately 23 seconds to return a command prompt on the destination
  machine.

  Finally, I change the entry to simply:

  hosts:  files dns

  After this change I was again receiving the destination command prompt
  in under 3 seconds. I don't know if simply changing the file will
  correct the problem long-term or not. Seems to help me, but might be
  the way to go for most Ubuntu users.

  ProblemType: Bug
  Architecture: i386
  Date: Thu Mar 22 18:10:54 2007
  DistroRelease: Ubuntu 7.04
  Uname: Linux samdesk 2.6.20-12-generic #2 SMP Wed Mar 21 20:55:46 UTC 2007 
i686 GNU/Linux

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

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

[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Ilja Polivanovas]

Ok Sorry for misleading report on #113.
It actually works, however the problem was with Tweak tool setting which 
silently adds autostart script preventing notebook to suspend on lid closed 
regardless settings in /etc/systemd/logind.conf
More: 
https://unix.stackexchange.com/questions/307497/gnome-disable-sleep-on-lid-close

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

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

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

[Touch-packages] [Bug 1708436] [NEW] package apport 2.20.4-0ubuntu4.5 failed to install/upgrade: problèmes de dépendances - laissé non configuré

[Lantam-Napo Tchamami]

Public bug reported:

I don't know more details about it, sorry!

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: apport 2.20.4-0ubuntu4.5
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportLog:
 
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Thu Aug  3 13:21:10 2017
ErrorMessage: problèmes de dépendances - laissé non configuré
InstallationDate: Installed on 2016-06-15 (413 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: apport
Title: package apport 2.20.4-0ubuntu4.5 failed to install/upgrade: problèmes de 
dépendances - laissé non configuré
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package apport 2.20.4-0ubuntu4.5 failed to install/upgrade: problèmes
  de dépendances - laissé non configuré

Status in apport package in Ubuntu:
  New

Bug description:
  I don't know more details about it, sorry!

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4.5
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Thu Aug  3 13:21:10 2017
  ErrorMessage: problèmes de dépendances - laissé non configuré
  InstallationDate: Installed on 2016-06-15 (413 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package apport 2.20.4-0ubuntu4.5 failed to install/upgrade: problèmes 
de dépendances - laissé non configuré
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Isaias Alves]

Public bug reported:

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)

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


** Tags: amd64 apport-package zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 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/util-linux/+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 1708375] Re: Add support for purple-telegram (telepathy-haze)

[Khurshid Alam]

> - I don't understand the line `/usr/lib/purple-2*/`.

You are right. Telegram-purple only creates /usr/lib/purple-2/, so
asterix can be removed. In fact I think we don't need
"/usr/lib/purple-2*/ r",  as "/usr/lib/purple-2/*.so mr", will do the
job.


> telegram-purple is supposed to detect telepathy, and avoid the path 
> `@{HOME}/.purple/telegram-purple/`. Was it really necessary?

It should but it doesn't at the moment.

And yes, it is necessary with 1.3.x. The plugin stores data after
authentication in either @{HOME}/.purple/telegram-purple/ or @{HOME
}/.telegram-purple/ depending on plugin version number. So telepathy-
haze would require read/write access to that folder, otherwise apparmor
give access-denied and users have to re-authenticate each time after
opening the client (empathy).

I will update the patch. Thanks.

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

Title:
  Add support for purple-telegram (telepathy-haze)

Status in telepathy-mission-control-5 package in Ubuntu:
  New

Bug description:
  When using purple telegram through telepathy-haze, it requires
  following permissions:

  # for purple telegram
  /etc/telegram-purple/server.tglpub r,
  /usr/lib/purple-2*/   r,
  /usr/lib/purple-2/*.somr,
  /usr/share/locale/*/LC_MESSAGES/*.mo r,
  /usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
  @{HOME}/.purple/telegram-purple/** rw,
  @{HOME}/.telegram-purple/**   rw,

  under /usr/lib/telepathy/telepathy-* section. See issue
  https://github.com/majn/telegram-purple/issues/346 for more details.

  I have attached the necessary patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions

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

[Touch-packages] [Bug 1708429] [NEW] package coreutils 8.25-2ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Sameerali]

Public bug reported:

cant update operating system

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: coreutils 8.25-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Thu Aug  3 16:15:05 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DpkgHistoryLog:
 Start-Date: 2017-08-03  16:15:05
 Commandline: aptdaemon role='role-install-packages' sender=':1.85'
 Install: homebank-data:amd64 (5.0.3-2, automatic), libofx6:amd64 
(1:0.9.10-1build2, automatic), libosp5:amd64 (1.5.2-13ubuntu1, automatic), 
homebank:amd64 (5.0.3-2)
DpkgTerminalLog:
 dpkg: error processing package coreutils (--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 2016-11-13 (263 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: coreutils
Title: package coreutils 8.25-2ubuntu2 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

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

Status in coreutils package in Ubuntu:
  New

Bug description:
  cant update operating system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: coreutils 8.25-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Aug  3 16:15:05 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DpkgHistoryLog:
   Start-Date: 2017-08-03  16:15:05
   Commandline: aptdaemon role='role-install-packages' sender=':1.85'
   Install: homebank-data:amd64 (5.0.3-2, automatic), libofx6:amd64 
(1:0.9.10-1build2, automatic), libosp5:amd64 (1.5.2-13ubuntu1, automatic), 
homebank:amd64 (5.0.3-2)
  DpkgTerminalLog:
   dpkg: error processing package coreutils (--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 2016-11-13 (263 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: coreutils
  Title: package coreutils 8.25-2ubuntu2 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/coreutils/+bug/1708429/+subscriptions

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

[Touch-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

[Frank Heimes]

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

** Changed in: ubuntu-power-systems
   Importance: Undecided => High

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

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

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+subscriptions

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

[Touch-packages] [Bug 1708375] Re: Add support for purple-telegram (telepathy-haze)

[bewied]

I did some work on telegram-purple.

- I don't understand the line `/usr/lib/purple-2*/`.  Is the asterisk 
misplaced, or does telepathy-haze truly create directories with unpredictable 
names in `/usr/lib/`?
- Heads up: `/etc/telegram-purple/server.tglpub` can be removed once we release 
1.4.0.  (But doesn't hurt either.)
- telegram-purple is supposed to detect telepathy, and avoid the path 
`@{HOME}/.purple/telegram-purple/`.  Was it really necessary?  Please open a 
bug report and tell us what's in the directory.  Was it just "to make sure"?  
Oh well, doesn't hurt, but shouldn't be necessary either.

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

Title:
  Add support for purple-telegram (telepathy-haze)

Status in telepathy-mission-control-5 package in Ubuntu:
  New

Bug description:
  When using purple telegram through telepathy-haze, it requires
  following permissions:

  # for purple telegram
  /etc/telegram-purple/server.tglpub r,
  /usr/lib/purple-2*/   r,
  /usr/lib/purple-2/*.somr,
  /usr/share/locale/*/LC_MESSAGES/*.mo r,
  /usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
  @{HOME}/.purple/telegram-purple/** rw,
  @{HOME}/.telegram-purple/**   rw,

  under /usr/lib/telepathy/telepathy-* section. See issue
  https://github.com/majn/telegram-purple/issues/346 for more details.

  I have attached the necessary patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions

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

[Touch-packages] [Bug 1708409] sosreport

[bugproxy]

Default Comment by Bridge

** Attachment added: "sosreport"
   
https://bugs.launchpad.net/bugs/1708409/+attachment/4926428/+files/sosreport-ltc-test-ci2.kdump-20170803012543.tar.xz

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

** Package changed: 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/1708409

Title:
  kdump service does not start after configure/reboot

Status in systemd package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

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

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

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

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

[Touch-packages] [Bug 1708409] [NEW] kdump service does not start after configure/reboot

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
kdump service does not start after configure/reboot

--Problem Description---
kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

# kdump-config status
current state   : Not ready to kdump


---uname output---
Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
 
Machine Type/Model = Power 8/8247-22L 

Additional Info-
# cat /proc/cmdline
root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
 
---Steps to Reproduce---
1. installed linux-crashdump
2. edited the kdump-tools.cfg crashkernel cmdline to above
3. update-grub
4. reboot

Expected:
kdump-config to be loaded by default after reboot

# kdump-config status
current state   : Not ready to kdump

# service kdump-tools status
* kdump-tools.service - Kernel crash dump capture service
   Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor pres
   Active: inactive (dead)

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

systemd in artful is not properly picking up the unit files in 
/etc/systemd/system/default.target.wants

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-157224 severity-high 
targetmilestone-inin---
-- 
kdump service does not start after configure/reboot
https://bugs.launchpad.net/bugs/1708409
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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

[Touch-packages] [Bug 1708326] Re: RM: obsolete product

[Michał Sawicz]

qtubuntu is not obsolete yet - it's the Qt platform support for Mir.

We've started cleaning up its dependencies in:

https://code.launchpad.net/~albaguirre/qtubuntu/papi-
cleanup/+merge/324886

We'll need a follow-up to drop the content-hub dependency.

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

Title:
  RM: obsolete product

Status in qtubuntu package in Ubuntu:
  Triaged

Bug description:
  qtubuntu was a component of Ubuntu Phone which is no longer developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:qtubuntu
  No reverse dependencies found

  $ reverse-depends -b src:qtubuntu
  No reverse dependencies found

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

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

[Touch-packages] [Bug 1708326] Re: RM: obsolete product

[Alan Griffiths]

qtubuntu supports Qt applications running on Mir, it is selected at
runtime, so it has no "depends".

It is still needed for the artful cycle, we're removing it's dependency
on platform-api (lp:~albaguirre/qtubuntu/papi-cleanup/+merge/324886)

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

Title:
  RM: obsolete product

Status in qtubuntu package in Ubuntu:
  Triaged

Bug description:
  qtubuntu was a component of Ubuntu Phone which is no longer developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:qtubuntu
  No reverse dependencies found

  $ reverse-depends -b src:qtubuntu
  No reverse dependencies found

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

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

[Touch-packages] [Bug 972077] Re: apt repository disk format has race conditions

[the835t]

affects me too

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

Title:
  apt repository disk format has race conditions

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released

Bug description:
  Apt archives are accessed over HTTP; this has resulted in a cluster of
  bugs (reported here, and upstream) about problems behind intercepting
  caches, problems with squid etc.

  There are 3 interlocking issues:
  A - mirror networks may be out of sync with each other (e.g. a file named on 
one mirror may no longer exist, or may not yet exist, on another mirror)
  B - updating files on a single mirror is not atomic - and even small windows 
of inconsistency will, given enough clients, cause headaches.
  C - caches exacerbate race conditions - when one happens, until the cached 
data expires, all clients of the cache will suffer from the race

  Solving this requires one of several things:
   - file system transactions
   - an archive format that requires only weakly ordered updates to the files 
at particular urls with the assumption that only one file may be observed to 
change at a time (because a lookup of file A, then B, may get a cache miss on A 
and a cache hit on B, so even if all clients strictly go A, then B, updates may 
still see old files when paths are reused).
   - super robust clients that repeatedly retry with progressively less cache 
friendly headers until they have a consistent view. (This is very tricky to do).

  It may be possible to do a tweak to the apt repository format though,
  which would allow publishing a race-free format in parallel with the
  existing layout, while clients migrate. To be safe against issue (A)
  the mirror network would need some care around handling of dns round-
  robin mirrors [to minimise the situation where referenced data is not
  available], but this should be doable - or alternatively clients doing
  'apt-get update' may need to be willing to retry to accommodate round-
  robin skew.

  What would such an archive format look like?
  It would have only one well known file name (InRelease), which would be 
internally signed. Rather than signing e.g. Packages.gz, it would sign a 
uniquely named packages and sources file - e.g. Packages-$HASH.gz or 
Packages-$serialno.gz.

  Backwards compatibility is achieved by using the same filenames for
  deb's and the like. We need to keep writing Packages.gz though, and
  Releases, until we no longer worry about old apt clients. We can
  optimise disk space a little by making Packages.gz a symlink to a
  Packages-$HASH.gz (and so on for Sources..), but it may be simpler and
  less prone to unexpected behaviour to keep using regular files.

  tl;dr
   * Unique file names for all unique file content with one exception
   * InRelease, a self-signed file that provides hashes and names the index 
files (Packages, Sources, Translations etc)
   * Coexists with existing archive layout

  Related bugs:
   * bug 804252: Please support InRelease files
   * bug 1430011: support apt by-hash mirrors

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

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

[Touch-packages] [Bug 1708375] [NEW] Add support for purple-telegram (telepathy-haze)

[Khurshid Alam]

Public bug reported:

When using purple telegram through telepathy-haze, it requires following
permissions:

# for purple telegram
/etc/telegram-purple/server.tglpub r,
/usr/lib/purple-2*/ r,
/usr/lib/purple-2/*.so  mr,
/usr/share/locale/*/LC_MESSAGES/*.mo r,
/usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
@{HOME}/.purple/telegram-purple/** rw,
@{HOME}/.telegram-purple/** rw,

under /usr/lib/telepathy/telepathy-* section. See issue
https://github.com/majn/telegram-purple/issues/346 for more details.

I have attached the necessary patch

** Affects: telepathy-mission-control-5 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful patch

** Attachment added: "telepathy-purple.patch"
   
https://bugs.launchpad.net/bugs/1708375/+attachment/4926407/+files/telepathy-purple.patch

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

Title:
  Add support for purple-telegram (telepathy-haze)

Status in telepathy-mission-control-5 package in Ubuntu:
  New

Bug description:
  When using purple telegram through telepathy-haze, it requires
  following permissions:

  # for purple telegram
  /etc/telegram-purple/server.tglpub r,
  /usr/lib/purple-2*/   r,
  /usr/lib/purple-2/*.somr,
  /usr/share/locale/*/LC_MESSAGES/*.mo r,
  /usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
  @{HOME}/.purple/telegram-purple/** rw,
  @{HOME}/.telegram-purple/**   rw,

  under /usr/lib/telepathy/telepathy-* section. See issue
  https://github.com/majn/telegram-purple/issues/346 for more details.

  I have attached the necessary patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions

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

[Touch-packages] [Bug 1692566] Re: package python-pkg-resources 20.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: python-setuptools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package python-pkg-resources 20.7.0-1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in python-setuptools package in Ubuntu:
  Confirmed

Bug description:
  I need a fix

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-pkg-resources 20.7.0-1
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon May 22 17:17:57 2017
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-05-21 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: python-setuptools
  Title: package python-pkg-resources 20.7.0-1 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/python-setuptools/+bug/1692566/+subscriptions

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

[Touch-packages] [Bug 1708355] Re: package python2.7 2.7.6-8ubuntu0.3 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python2.7 2.7.6-8ubuntu0.3 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in python2.7 package in Ubuntu:
  New

Bug description:
  es una basura este SO

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python2.7 2.7.6-8ubuntu0.3
  ProcVersionSignature: Ubuntu 3.16.0-51.69~14.04.1-generic 3.16.7-ckt17
  Uname: Linux 3.16.0-51-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Wed Aug  2 16:00:05 2017
  DuplicateSignature: package:python2.7:2.7.6-8ubuntu0.3:el subproceso 
instalado el script post-installation devolvió el código de salida de error 1
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2015-06-17 (777 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: python2.7
  Title: package python2.7 2.7.6-8ubuntu0.3 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: Upgraded to trusty on 2017-08-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1708355/+subscriptions

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

[Touch-packages] [Bug 1708355] [NEW] package python2.7 2.7.6-8ubuntu0.3 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[Jimmy Steven]

Public bug reported:

es una basura este SO

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python2.7 2.7.6-8ubuntu0.3
ProcVersionSignature: Ubuntu 3.16.0-51.69~14.04.1-generic 3.16.7-ckt17
Uname: Linux 3.16.0-51-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
Date: Wed Aug  2 16:00:05 2017
DuplicateSignature: package:python2.7:2.7.6-8ubuntu0.3:el subproceso instalado 
el script post-installation devolvió el código de salida de error 1
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
InstallationDate: Installed on 2015-06-17 (777 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: python2.7
Title: package python2.7 2.7.6-8ubuntu0.3 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
UpgradeStatus: Upgraded to trusty on 2017-08-02 (0 days ago)

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package python2.7 2.7.6-8ubuntu0.3 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in python2.7 package in Ubuntu:
  New

Bug description:
  es una basura este SO

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python2.7 2.7.6-8ubuntu0.3
  ProcVersionSignature: Ubuntu 3.16.0-51.69~14.04.1-generic 3.16.7-ckt17
  Uname: Linux 3.16.0-51-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Wed Aug  2 16:00:05 2017
  DuplicateSignature: package:python2.7:2.7.6-8ubuntu0.3:el subproceso 
instalado el script post-installation devolvió el código de salida de error 1
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2015-06-17 (777 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: python2.7
  Title: package python2.7 2.7.6-8ubuntu0.3 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: Upgraded to trusty on 2017-08-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1708355/+subscriptions

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

[Touch-packages] [Bug 1681046] Re: package libuuid1:i386 2.27.1-6ubuntu3.2 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente

[Vittorio]

ma perchè non parlate in italiano?? non siamo tutti inglesi a questo
mondo

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

Title:
  package libuuid1:i386 2.27.1-6ubuntu3.2 failed to install/upgrade: il
  pacchetto si trova in uno stato di inconsistenza critico: è
  consigliato  installarlo nuovamente prima di tentare la
  configurazione.

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libuuid1:i386 2.27.1-6ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Apr  6 22:30:09 2017
  DpkgHistoryLog:
   Start-Date: 2017-04-06  22:29:37
   Commandline: /usr/bin/unattended-upgrade
   Install: linux-headers-4.4.0-72-generic:amd64 (4.4.0-72.93, automatic), 
linux-headers-4.4.0-72:amd64 (4.4.0-72.93, automatic), 
linux-image-4.4.0-72-generic:amd64 (4.4.0-72.93, automatic), 
linux-image-extra-4.4.0-72-generic:amd64 (4.4.0-72.93, automatic)
   Upgrade: linux-headers-generic:amd64 (4.4.0.71.77, 4.4.0.72.78), 
linux-libc-dev:amd64 (4.4.0-71.92, 4.4.0-72.93), linux-image-generic:amd64 
(4.4.0.71.77, 4.4.0.72.78), chromium-codecs-ffmpeg-extra:amd64 
(56.0.2924.76-0ubuntu0.16.04.1268, 57.0.2987.98-0ubuntu0.16.04.1276), 
linux-generic:amd64 (4.4.0.71.77, 4.4.0.72.78), lightdm:amd64 (1.18.3-0ubuntu1, 
1.18.3-0ubuntu1.1), liblightdm-gobject-1-0:amd64 (1.18.3-0ubuntu1, 
1.18.3-0ubuntu1.1)
  ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è 
consigliato  installarlo nuovamente prima di tentare la configurazione.
  InstallationDate: Installed on 2016-05-22 (320 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: util-linux
  Title: package libuuid1:i386 2.27.1-6ubuntu3.2 failed to install/upgrade: il 
pacchetto si trova in uno stato di inconsistenza critico: è consigliato  
installarlo nuovamente prima di tentare la configurazione.
  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/1681046/+subscriptions

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