[Touch-packages] [Bug 1708785] Re: package linux-image-4.10.0-30-generic 4.10.0-30.34~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1708785

Title:
  package linux-image-4.10.0-30-generic 4.10.0-30.34~16.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I think this was my fault, stopped apport early with SIGKILL, ignore
  this bug thing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-30-generic 4.10.0-30.34~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Aug  5 02:14:45 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2017-08-01 (3 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: initramfs-tools
  Title: package linux-image-4.10.0-30-generic 4.10.0-30.34~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1708785] [NEW] package linux-image-4.10.0-30-generic 4.10.0-30.34~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Joseph Banks]

Public bug reported:

I think this was my fault, stopped apport early with SIGKILL, ignore
this bug thing

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.10.0-30-generic 4.10.0-30.34~16.04.1
ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Sat Aug  5 02:14:45 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2017-08-01 (3 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: initramfs-tools
Title: package linux-image-4.10.0-30-generic 4.10.0-30.34~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package linux-image-4.10.0-30-generic 4.10.0-30.34~16.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I think this was my fault, stopped apport early with SIGKILL, ignore
  this bug thing

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-30-generic 4.10.0-30.34~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Aug  5 02:14:45 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2017-08-01 (3 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: initramfs-tools
  Title: package linux-image-4.10.0-30-generic 4.10.0-30.34~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1708769] Re: package linux-image-4.10.0-30-lowlatency 4.10.0-30.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1708769

Title:
  package linux-image-4.10.0-30-lowlatency 4.10.0-30.34 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  package linux-image-4.10.0-30-lowlatency 4.10.0-30.34 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-30-lowlatency 4.10.0-30.34
  ProcVersionSignature: Ubuntu 4.10.0-26.30-lowlatency 4.10.17
  Uname: Linux 4.10.0-26-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adrian 3328 F pulseaudio
   /dev/snd/controlC1:  adrian 3328 F pulseaudio
  Date: Fri Aug  4 20:53:43 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=869d82f8-9abb-472a-a8ca-72be1f64d9d7
  InstallationDate: Installed on 2017-01-18 (198 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: BANGHO MAX G0101
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-lowlatency 
root=UUID=e9a000c0-6306-474d-b5cd-bd215872dd3a ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-4.10.0-30-lowlatency 4.10.0-30.34 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: MAX G0101
  dmi.board.vendor: BANGHO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: BANGHO
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/29/2015:svnBANGHO:pnMAXG0101:pvrMAXG0101:rvnBANGHO:rnMAXG0101:rvrNotApplicable:cvnBANGHO:ct9:cvrN/A:
  dmi.product.name: MAX G0101
  dmi.product.version: MAX G0101
  dmi.sys.vendor: BANGHO

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

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

[Touch-packages] [Bug 1708769] [NEW] package linux-image-4.10.0-30-lowlatency 4.10.0-30.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Adrian Ciriaci]

Public bug reported:

package linux-image-4.10.0-30-lowlatency 4.10.0-30.34 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
exited with return code 1

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-30-lowlatency 4.10.0-30.34
ProcVersionSignature: Ubuntu 4.10.0-26.30-lowlatency 4.10.17
Uname: Linux 4.10.0-26-lowlatency x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  adrian 3328 F pulseaudio
 /dev/snd/controlC1:  adrian 3328 F pulseaudio
Date: Fri Aug  4 20:53:43 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=869d82f8-9abb-472a-a8ca-72be1f64d9d7
InstallationDate: Installed on 2017-01-18 (198 days ago)
InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
MachineType: BANGHO MAX G0101
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-lowlatency 
root=UUID=e9a000c0-6306-474d-b5cd-bd215872dd3a ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: initramfs-tools
Title: package linux-image-4.10.0-30-lowlatency 4.10.0-30.34 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: MAX G0101
dmi.board.vendor: BANGHO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: BANGHO
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/29/2015:svnBANGHO:pnMAXG0101:pvrMAXG0101:rvnBANGHO:rnMAXG0101:rvrNotApplicable:cvnBANGHO:ct9:cvrN/A:
dmi.product.name: MAX G0101
dmi.product.version: MAX G0101
dmi.sys.vendor: BANGHO

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

Title:
  package linux-image-4.10.0-30-lowlatency 4.10.0-30.34 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  package linux-image-4.10.0-30-lowlatency 4.10.0-30.34 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-30-lowlatency 4.10.0-30.34
  ProcVersionSignature: Ubuntu 4.10.0-26.30-lowlatency 4.10.17
  Uname: Linux 4.10.0-26-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adrian 3328 F pulseaudio
   /dev/snd/controlC1:  adrian 3328 F pulseaudio
  Date: Fri Aug  4 20:53:43 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=869d82f8-9abb-472a-a8ca-72be1f64d9d7
  InstallationDate: Installed on 2017-01-18 (198 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: BANGHO MAX G0101
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-lowlatency 
root=UUID=e9a000c0-6306-474d-b5cd-bd215872dd3a ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-4.10.0-30-lowlatency 4.10.0-30.34 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: MAX G0101
  dmi.board.vendor: BANGHO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: BANGHO
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/29/2015:svnBANGHO:pnMAXG0101:pvrMAXG0101:rvnBANGHO:rnMAXG0101:rvrNotApplicable:cvnBANGHO:ct9:cvrN/A:
  dmi.product.name: MAX G0101
  dmi.product.version: MAX G0101
  dmi.sys.vendor: BANGHO

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

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

[Touch-packages] [Bug 1555331] Re: mate-panel crashed with SIGSEGV in g_slist_remove_all()

[Launchpad Bug Tracker]

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

** Changed in: gtk+2.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  mate-panel crashed with SIGSEGV in g_slist_remove_all()

Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Won't Fix

Bug description:
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: mate-panel 1.12.2-1
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Mar  9 22:49:55 2016
  ExecutablePath: /usr/bin/mate-panel
  InstallationDate: Installed on 2016-02-25 (12 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  ProcCmdline: mate-panel
  SegvAnalysis:
   Segfault happened at: 0x7f4fa6439b1c :cmp
%rbp,(%rdi)
   PC (0x7f4fa6439b1c) ok
   source "%rbp" ok
   destination "(%rdi)" (0x160016) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-panel
  StacktraceTop:
   g_slist_remove_all () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gtk_rc_reset_styles () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  Title: mate-panel crashed with SIGSEGV in g_slist_remove_all()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 203169] Re: "status" function for init scripts

[Bug Watch Updater]

** Changed in: debian-policy (Debian)
   Status: New => Fix Released

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

Title:
  "status" function for init scripts

Status in nis:
  Invalid
Status in apache2 package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Invalid
Status in at package in Ubuntu:
  Fix Released
Status in bind9 package in Ubuntu:
  Fix Released
Status in cron package in Ubuntu:
  Fix Released
Status in dovecot package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in nis package in Ubuntu:
  Invalid
Status in openssh package in Ubuntu:
  Fix Released
Status in postgresql-8.3 package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in sysklogd package in Ubuntu:
  Fix Released
Status in udev package in Ubuntu:
  Invalid
Status in debian-policy package in Debian:
  Fix Released
Status in lsb package in Debian:
  Fix Released
Status in samba package in Debian:
  Fix Released

Bug description:
  Binary package hint: lsb

  Ubuntu Hardy, lsb-base 3.1-24ubuntu2

  This bug has been discussed on the Ubuntu-devel mailing list [1].

  Only a very few of the service init scripts in /etc/init.d, (apparmor,
  cupsys, mysql, postfix, postgresql) have implemented the "status"
  action.

  The Linux Standard Base init script specification [2] describes the
  status action in detail, and requires it for LSB compliance.  It
  provides a centralized and direct way of determine if a given service
  is running or not, with a more sophistication than grepping a process
  listing.  It logs a message to standard out, and exits with one of a
  number of meaningful codes, also defined in [2].

  Users and system administrators with experience in LSB-compliant
  distributions can be frustrated by a lack of a standard way to
  determine if a given service is running or not in Ubuntu.  Given the
  LTS designation of Hardy and our interest in furthering the Ubuntu
  Server, we'd like to add this functionality to several of the init
  scripts for core daemons that ship on the Ubuntu Server ISO.  It will
  also facilitate the integration with ebox and other status gathering
  and reporting tools.

  We suggest solving this by adding a function to /lib/lsb/init-
  functions, which is already sourced by most scripts in /etc/init.d.
  The heavy lifting is performed by the pidofproc() function, which is
  already defined in that same file.  (A proper debdiff will follow.)

  +status_of_proc () {
  +local daemon name status
  +daemon="$1"
  +name="$2"
  +pidofproc $daemon >/dev/null
  +status=$?
  +if [ $status -eq 0 ]; then
  +log_success_msg "$name is running."
  +else
  +log_failure_msg "$name is not running."
  +fi
  +return $status
  +}

  
  This addition would be followed by patches to init scripts essentially adding 
a case handler:

  + status)
  +   status_of_proc "$DAEMON" "$NAME"
  +   exit $?
  +   ;;

  The risk should be minimal.  It will clearly not affect the
  functionality of starting and stopping daemons, and thus a minimal
  chance of regression.  We will push the changes to Debian, as there is
  a similar bug in Debian's bug tracker [3].

  
  [1] https://lists.ubuntu.com/archives/ubuntu-devel/2008-March/025176.html
  [2] 
http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
  [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291148

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

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

Re: [Touch-packages] [Bug 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con

[Jean Louis Schmitz]

Thanks, it worked for me too.


On 04/08/17 14:55, Jeremy Gabriel wrote:
> Did you run the dpkg -l | awk '/^iH/ { print $2 }' command that Seth posted
> earlier in the thread? If so, you need to run the reinstall line for any
> package listed.
>
> Unfortunately that's the limit to what I will be able to help with. Good
> luck
>
>
> On Fri, Aug 4, 2017 at 10:07 AM, Sandra Viktoria Mueller 
> wrote:
>
>> Hi Jeremy,
>>
>> Thank you very much. I tried your command. I've put the result you in the
>> attachment. Unfortunately it is in part in italian, but maybe you could
>> understand something. Please let me know.
>>
>> Sandra
>>
>> 2017-08-04 17:59 GMT+02:00 Jeremy Gabriel :
>>
>>> Hi Sandra,
>>> I had to use
>>>
>>> sudo apt-get install --reinstall libssl1.0.0:i386
>>>
>>> Hope this helps,
>>> Jeremy
>>>
>>> On Thu, Jul 27, 2017 at 2:28 AM, Sandra Viktoria Mueller <
>>> savi...@gmail.com>
>>> wrote:
>>>
 I wrote in the terminal this: sudo apt-get install --reinstall
 libssl-dev:amd64
 1.0.2g-1ubuntu11.2
 Unfortunately it doesn't work. The problem remains.

 Please If you have another command which I can try? Thank you

 Sandra

 2017-07-25 0:09 GMT+02:00 Seth Arnold <1692...@bugs.launchpad.net>:

> ** Changed in: dpkg (Ubuntu)
> Status: Fix Released => Confirmed
>
> ** Changed in: openssl (Ubuntu)
> Status: Fix Released => Confirmed
>
> --
> You received this bug notification because you are subscribed to the
>>> bug
> report.
> https://bugs.launchpad.net/bugs/1692981
>
> Title:
>package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
>>> install/upgrade:
>package is in a very bad inconsistent state; you should  reinstall
>> it
>before attempting configuration
>
> Status in dpkg package in Ubuntu:
>Confirmed
> Status in openssl package in Ubuntu:
>Confirmed
>
> Bug description:
>package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
>>> install/upgrade:
>package is in a very bad inconsistent state; you should  reinstall
>> it
>before attempting configuration
>
>ProblemType: Package
>DistroRelease: Ubuntu 17.04
>Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
>ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
>Uname: Linux 4.10.0-21-generic x86_64
>ApportVersion: 2.20.4-0ubuntu4.1
>AptOrdering:
> libssl1.0.0:amd64: Install
> NULL: ConfigurePending
>Architecture: amd64
>Date: Tue May 23 21:47:55 2017
>DuplicateSignature:
> package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
> Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
> dpkg: error processing package libssl-dev:amd64 (--configure):
>  package is in a very bad inconsistent state; you should
>ErrorMessage: package is in a very bad inconsistent state; you
>> should
> reinstall it before attempting configuration
>InstallationDate: Installed on 2017-05-15 (7 days ago)
>InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64
 (20170412)
>RelatedPackageVersions:
> dpkg 1.18.10ubuntu2
> apt  1.4
>SourcePackage: openssl
>Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> install/upgrade: package is in a very bad inconsistent state; you
>>> should
> reinstall it before attempting configuration
>UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/
 1692981/+subscriptions
 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1696799).
 https://bugs.launchpad.net/bugs/1692981

 Title:
package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
>> install/upgrade:
package is in a very bad inconsistent state; you should  reinstall it
before attempting configuration

 Status in dpkg package in Ubuntu:
Confirmed
 Status in openssl package in Ubuntu:
Confirmed

 Bug description:
package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
>> install/upgrade:
package is in a very bad inconsistent state; you should  reinstall it
before attempting configuration

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
AptOrdering:
 libssl1.0.0:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Tue May 23 21:47:55 2017
DuplicateSignature:
 

[Touch-packages] [Bug 1588917] Re: Upgrade ping to latest version that doesn't require SUID or NET_RAW capability

[Seth Arnold]

I believe that section of the kernel code has had three user->ring0
vulnerabilities so far. It might be worth waiting a bit longer before
enabling its use by default.

Thanks

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

Title:
  Upgrade ping to latest version that doesn't require SUID or NET_RAW
  capability

Status in iputils package in Ubuntu:
  Triaged

Bug description:
  The latest version of iputils have the option of using SOCK_DGRAM
  packets instead of SOCK_RAW, provided that the
  net.ipv4.ping_group_range sysctl is set to a different value.  This
  helps a lot with security in -not just- Linux containers by dropping
  support for the NET_RAW capability.

  Also, the ubuntu-minimal packages should not include this package as a
  hard dependency in case I want to uninstall iputils-ping to substitute
  it for another package like oping which just works if I turn off the
  setuid bit.

  This would help a lot with secure Linux containers with no NET_RAW
  capabilities.

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

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

Re: [Touch-packages] [Bug 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con

[Jeremy Gabriel]

Did you run the dpkg -l | awk '/^iH/ { print $2 }' command that Seth posted
earlier in the thread? If so, you need to run the reinstall line for any
package listed.

Unfortunately that's the limit to what I will be able to help with. Good
luck


On Fri, Aug 4, 2017 at 10:07 AM, Sandra Viktoria Mueller 
wrote:

> Hi Jeremy,
>
> Thank you very much. I tried your command. I've put the result you in the
> attachment. Unfortunately it is in part in italian, but maybe you could
> understand something. Please let me know.
>
> Sandra
>
> 2017-08-04 17:59 GMT+02:00 Jeremy Gabriel :
>
> > Hi Sandra,
> > I had to use
> >
> > sudo apt-get install --reinstall libssl1.0.0:i386
> >
> > Hope this helps,
> > Jeremy
> >
> > On Thu, Jul 27, 2017 at 2:28 AM, Sandra Viktoria Mueller <
> > savi...@gmail.com>
> > wrote:
> >
> > > I wrote in the terminal this: sudo apt-get install --reinstall
> > > libssl-dev:amd64
> > > 1.0.2g-1ubuntu11.2
> > > Unfortunately it doesn't work. The problem remains.
> > >
> > > Please If you have another command which I can try? Thank you
> > >
> > > Sandra
> > >
> > > 2017-07-25 0:09 GMT+02:00 Seth Arnold <1692...@bugs.launchpad.net>:
> > >
> > > > ** Changed in: dpkg (Ubuntu)
> > > >Status: Fix Released => Confirmed
> > > >
> > > > ** Changed in: openssl (Ubuntu)
> > > >Status: Fix Released => Confirmed
> > > >
> > > > --
> > > > You received this bug notification because you are subscribed to the
> > bug
> > > > report.
> > > > https://bugs.launchpad.net/bugs/1692981
> > > >
> > > > Title:
> > > >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> > install/upgrade:
> > > >   package is in a very bad inconsistent state; you should  reinstall
> it
> > > >   before attempting configuration
> > > >
> > > > Status in dpkg package in Ubuntu:
> > > >   Confirmed
> > > > Status in openssl package in Ubuntu:
> > > >   Confirmed
> > > >
> > > > Bug description:
> > > >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> > install/upgrade:
> > > >   package is in a very bad inconsistent state; you should  reinstall
> it
> > > >   before attempting configuration
> > > >
> > > >   ProblemType: Package
> > > >   DistroRelease: Ubuntu 17.04
> > > >   Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
> > > >   ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
> > > >   Uname: Linux 4.10.0-21-generic x86_64
> > > >   ApportVersion: 2.20.4-0ubuntu4.1
> > > >   AptOrdering:
> > > >libssl1.0.0:amd64: Install
> > > >NULL: ConfigurePending
> > > >   Architecture: amd64
> > > >   Date: Tue May 23 21:47:55 2017
> > > >   DuplicateSignature:
> > > >package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
> > > >Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
> > > >dpkg: error processing package libssl-dev:amd64 (--configure):
> > > > package is in a very bad inconsistent state; you should
> > > >   ErrorMessage: package is in a very bad inconsistent state; you
> should
> > > > reinstall it before attempting configuration
> > > >   InstallationDate: Installed on 2017-05-15 (7 days ago)
> > > >   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64
> > > (20170412)
> > > >   RelatedPackageVersions:
> > > >dpkg 1.18.10ubuntu2
> > > >apt  1.4
> > > >   SourcePackage: openssl
> > > >   Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> > > > install/upgrade: package is in a very bad inconsistent state; you
> > should
> > > > reinstall it before attempting configuration
> > > >   UpgradeStatus: No upgrade log present (probably fresh install)
> > > >
> > > > To manage notifications about this bug go to:
> > > > https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/
> > > 1692981/+subscriptions
> > > >
> > >
> > > --
> > > You received this bug notification because you are subscribed to a
> > > duplicate bug report (1696799).
> > > https://bugs.launchpad.net/bugs/1692981
> > >
> > > Title:
> > >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> install/upgrade:
> > >   package is in a very bad inconsistent state; you should  reinstall it
> > >   before attempting configuration
> > >
> > > Status in dpkg package in Ubuntu:
> > >   Confirmed
> > > Status in openssl package in Ubuntu:
> > >   Confirmed
> > >
> > > Bug description:
> > >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> install/upgrade:
> > >   package is in a very bad inconsistent state; you should  reinstall it
> > >   before attempting configuration
> > >
> > >   ProblemType: Package
> > >   DistroRelease: Ubuntu 17.04
> > >   Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
> > >   ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
> > >   Uname: Linux 4.10.0-21-generic x86_64
> > >   ApportVersion: 2.20.4-0ubuntu4.1
> > >   AptOrdering:
> > >libssl1.0.0:amd64: Install
> > >NULL: ConfigurePending
> > >   Architecture: amd64
> > >   Date: Tue May 23 21:47:55 2017
> > >   DuplicateSignature:
> > >

[Touch-packages] [Bug 1503762] Re: Provide systemd service

[Christian Boltz]

Just a quick update about the situation on openSUSE - in the meantime,
we got rid of the initscript and switched to a small wrapper script -
see apparmor.systemd and apparmor.service on
https://build.opensuse.org/package/show/security:apparmor/apparmor

That's obviously not the final solution, but at least better than the
old initscript ;-)

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

Title:
  Provide systemd service

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New
Status in apparmor package in Debian:
  Confirmed
Status in apparmor package in Gentoo Linux:
  New

Bug description:
  AppArmor is in the critical path for bootup for any systems that use
  it.  Let's specify a systemd service file instead of having systemd
  use sysv compatibility mode.

  There seems to be a few bugs tracking the precursor this work, like
  https://bugs.launchpad.net/apparmor/+bug/1488179, but no actual bug
  for the systemd service itself.

  AUR has a simple service file, not sure if that would be useful -
  https://aur.archlinux.org/packages/apparmor/

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

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

[Touch-packages] [Bug 1266675] Re: newusers error adding more than one user

[Seth Arnold]

Use CVE-2017-12424.


** Information type changed from Public to Public Security

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

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

Title:
  newusers error adding more than one user

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  1)
  mcegielka@ftp-geodezja:~$ lsb_release -rd
  Description:Ubuntu 13.10
  Release:13.10

  2)
  mcegielka@ftp-geodezja:~$ sudo apt-cache policy passwd
  passwd:
Installed: 1:4.1.5.1-1ubuntu6
Candidate: 1:4.1.5.1-1ubuntu6

  3)
  Expected: add system users from file given as argument:

  mcegielka@ftp-geodezja:~$ cat testusers.txt
  test1:a:::test user 1,,,:/home/test1:/bin/bash
  test2:b:::test user 2,,,:/home/test2:/bin/bash

  4)
  Instead: errors:

  mcegielka@ftp-geodezja:~$ sudo newusers testusers.txt
  *** Error in `newusers': free(): invalid next size (fast): 0x09319cd0 ***
  *** Error in `newusers': malloc(): memory corruption: 0x09319d00 ***

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: passwd 1:4.1.5.1-1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  Date: Tue Jan  7 09:04:11 2014
  InstallationDate: Installed on 2014-01-07 (0 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release i386 
(20131016)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1674680] Re: Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

[Eric Desrochers]

Hi Dariusz,

Accordint to : https://merges.ubuntu.com/main.html
Jeremy Bicha is the one that did the last merge for bluez.

You could also asked him if there is any plan to merge bluez debian
upstream to Artful before the freeze.

 bluez | 5.43-0ubuntu1 | zesty   | source, amd64, arm64, armhf, 
i386, ppc64el, s390x
 bluez | 5.45-0ubuntu2 | artful  | source, amd64, arm64, armhf, 
i386, ppc64el, s390x

Regards,
Eric


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

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

Title:
  Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Xenial:
  New
Status in bluez source package in Yakkety:
  Won't Fix
Status in bluez package in Debian:
  New

Bug description:
  [Impact]

   * The package contains misleading documentation mentioning the use of
  /etc/bluetooth/rfcomm.conf for rfcomm setup while the support for
  config file has been dropped after 14.04 release. I have directly
  received a question about it from a user mislead by the documentation.

  * Additionally deprecated -f option is still used in legacy upstart
  /etc/init/bluetooth.conf. Actually this does not seem longer required
  due to upstart being removed.

  [Test Case]

   * Install bluez.

   * Look for misleading rfcomm.conf mentions in
  /etc/init/bluetooth.conf, /usr/share/doc/bluez/README.Debian.gz

  [Regression Potential]

   * This is mostly a documentation correction, however if somebody
  still depends bluetooth started with Ubuntu 16.04+ by upstart (or
  possibly some kind of upstart compatibility in systemd, is that even
  possible?) he/she may end up with bluetooth not being started. This
  seems highly unlikely.

  [Other Info]

   * Original bug description:

  Support for config files has been dropped upstream in 2012 (however
  version shipped with Trusty still supports it), but the latest
  versions (including Xenial and Zesty) still mention it in the docs and
  in the legacy /etc/init/bluetooth.conf file.

  Additionally the /etc/init/bluetooth.conf don't seem necessary these
  days. In fact it has been dropped by Debian already.

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

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

[Touch-packages] [Bug 1674680] Re: Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

[Eric Desrochers]

Hi Dariusz,

Since no upload has been done since last April for this particular bug,
this now need to be in devel release, thus Artful, before proceeding
with affected stable releases (if relevant).

I would suggest you prepare a debdiff for Artful get it sponsored by a
CoreDev, and then I'll be able to help with the SRU sponsorship for the
affected stable releases (again if relevant)

Regards,
Eric

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

Title:
  Deprecated rfcomm.conf still mentioned in bluetooth.conf and README

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Xenial:
  New
Status in bluez source package in Yakkety:
  Won't Fix
Status in bluez package in Debian:
  New

Bug description:
  [Impact]

   * The package contains misleading documentation mentioning the use of
  /etc/bluetooth/rfcomm.conf for rfcomm setup while the support for
  config file has been dropped after 14.04 release. I have directly
  received a question about it from a user mislead by the documentation.

  * Additionally deprecated -f option is still used in legacy upstart
  /etc/init/bluetooth.conf. Actually this does not seem longer required
  due to upstart being removed.

  [Test Case]

   * Install bluez.

   * Look for misleading rfcomm.conf mentions in
  /etc/init/bluetooth.conf, /usr/share/doc/bluez/README.Debian.gz

  [Regression Potential]

   * This is mostly a documentation correction, however if somebody
  still depends bluetooth started with Ubuntu 16.04+ by upstart (or
  possibly some kind of upstart compatibility in systemd, is that even
  possible?) he/she may end up with bluetooth not being started. This
  seems highly unlikely.

  [Other Info]

   * Original bug description:

  Support for config files has been dropped upstream in 2012 (however
  version shipped with Trusty still supports it), but the latest
  versions (including Xenial and Zesty) still mention it in the docs and
  in the legacy /etc/init/bluetooth.conf file.

  Additionally the /etc/init/bluetooth.conf don't seem necessary these
  days. In fact it has been dropped by Debian already.

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

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

Hell, believe or not, I had read along man system.link several times, but I 
would wish to be able to understand all these little subtleties.
"All link files are collectively sorted and processed in lexical order, 
regardless of the directories in which they live. However, files with identical 
filenames replace each other. Files in /etc have the highest priority, files in 
/run take precedence over files with the same name in /usr/lib."
Go figure...

There are plenty of recipes on the Internet telling the reader to disable the 
damned "novelty"
https://askubuntu.com/questions/767786/changing-network-interfaces-name-ubuntu-16-04
https://serverfault.com/questions/837454/interface-will-not-rename-under-systemd
etc
https://www.google.com.ua/search?q=ubuntu+systemd+link+rename+interfaces

Most often, what is forgotten, is regeneration of initramfs file after .link 
changes
But also, sometimes numeric prefix of the .link file name is forgotten as well
So, this is not working, frustrating, infuriating the user and making him want 
to disable the damned thing altogether.

As for me, just now, I managed to guess that .links preventing renaming of VLAN 
interfaces should have earlier prefixes than ones binding known interface names 
to their MAC addresses (as VLAN iface has the same MAC)
This was a really hard-earned knowledge because there are no usable HOWTOs 
about these "novelties"
https://askubuntu.com/questions/791149/prevent-vlan-and-bridge-interface-rename-to-renamex-form
https://www.prolixium.com/blog?id=1023
https://www.google.com.ua/search?q=ubuntu+systemd+vlan+link+rename

So, with current system documentation, unless you don't have an existing
working sample for copying, you are doomed to guessworks, spitting and
cursing until you guess what to write where and how to name it.

-- 
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:
  Invalid

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 1679704] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From lagar...@br.ibm.com 2017-08-04 13:56 EDT---
Hi Christian,

Do you have any updates on this one?

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

Title:
  libvirt profile is blocking global setrlimit despite having no rlimit
  rule

Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  Hi,
  while debugging bug 1678322 I was running along apparmor issues.
  Thanks to jjohansen we debugged some of it and eventually I was asked to 
report to a bug.

  Symptom:
  [ 8976.950635] audit: type=1400 audit(1491310016.224:48): apparmor="DENIED" 
operation="setrlimit" profile="/usr/sbin/libvirtd" pid=10034 comm="libvirtd" 
rlimit=memlock value=1610612736

  But none of the profiles has any rlimit statement in it:
  $ grep -Hirn limit /etc/apparmor*
  /etc/apparmor.d/sbin.dhclient:58:  # such, if the dhclient3 daemon is 
subverted, this effectively limits it to
  /etc/apparmor.d/abstractions/ubuntu-helpers:16:# Limitations:
  /etc/apparmor.d/abstractions/ubuntu-helpers:64:  # in limited libraries so 
glibc's secure execution should be enough to not
  /etc/apparmor.d/cache/.features:13:rlimit {mask {cpu fsize data stack core 
rss nproc nofile memlock as locks sigpending msgqueue nice rtprio rttime

  
  The profile contains a child profile which makes reading the dumps a bit 
painful, but I'll attach them anyway for you to take a look.
  To "recreate" if needed check out bug 1678322 - TL;DR hot-add some VFs via 
libvirt.

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

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

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Andrei Aldea]

SD Card hasn't been fixed yet but sound works after you use the kernel I have 
compiled:
https://github.com/Grippentech/Asus-E200HA-Linux-Post-Install-Script

I'm working on making a smaller version of the kernel as the one I have
right now is quite bloated (has support for almost every device that can
be supported) but that's 2+ weeks away as I'm on vacation without the
E200ha.

Hopefully the changes that Takashi Iwai made with the rest of the guys
working on the Sound side will get merged into mainstream kernel 4.13
but that's just speculation, not based on anything. I know they're
trying to get it into mainstream tho, if Linus and the devs approve it
is another issue entirely.

I'm not aware on anybody working on the SD card side of things, I'm not
sure where I'd start either. If someone has some insight feel free to
chip in.

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

Re: [Touch-packages] [Bug 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con

[Sandra Viktoria Mueller]

Hi Jeremy,

Thank you very much. I tried your command. I've put the result you in the
attachment. Unfortunately it is in part in italian, but maybe you could
understand something. Please let me know.

Sandra

2017-08-04 17:59 GMT+02:00 Jeremy Gabriel :

> Hi Sandra,
> I had to use
>
> sudo apt-get install --reinstall libssl1.0.0:i386
>
> Hope this helps,
> Jeremy
>
> On Thu, Jul 27, 2017 at 2:28 AM, Sandra Viktoria Mueller <
> savi...@gmail.com>
> wrote:
>
> > I wrote in the terminal this: sudo apt-get install --reinstall
> > libssl-dev:amd64
> > 1.0.2g-1ubuntu11.2
> > Unfortunately it doesn't work. The problem remains.
> >
> > Please If you have another command which I can try? Thank you
> >
> > Sandra
> >
> > 2017-07-25 0:09 GMT+02:00 Seth Arnold <1692...@bugs.launchpad.net>:
> >
> > > ** Changed in: dpkg (Ubuntu)
> > >Status: Fix Released => Confirmed
> > >
> > > ** Changed in: openssl (Ubuntu)
> > >Status: Fix Released => Confirmed
> > >
> > > --
> > > You received this bug notification because you are subscribed to the
> bug
> > > report.
> > > https://bugs.launchpad.net/bugs/1692981
> > >
> > > Title:
> > >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> install/upgrade:
> > >   package is in a very bad inconsistent state; you should  reinstall it
> > >   before attempting configuration
> > >
> > > Status in dpkg package in Ubuntu:
> > >   Confirmed
> > > Status in openssl package in Ubuntu:
> > >   Confirmed
> > >
> > > Bug description:
> > >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> install/upgrade:
> > >   package is in a very bad inconsistent state; you should  reinstall it
> > >   before attempting configuration
> > >
> > >   ProblemType: Package
> > >   DistroRelease: Ubuntu 17.04
> > >   Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
> > >   ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
> > >   Uname: Linux 4.10.0-21-generic x86_64
> > >   ApportVersion: 2.20.4-0ubuntu4.1
> > >   AptOrdering:
> > >libssl1.0.0:amd64: Install
> > >NULL: ConfigurePending
> > >   Architecture: amd64
> > >   Date: Tue May 23 21:47:55 2017
> > >   DuplicateSignature:
> > >package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
> > >Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
> > >dpkg: error processing package libssl-dev:amd64 (--configure):
> > > package is in a very bad inconsistent state; you should
> > >   ErrorMessage: package is in a very bad inconsistent state; you should
> > > reinstall it before attempting configuration
> > >   InstallationDate: Installed on 2017-05-15 (7 days ago)
> > >   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64
> > (20170412)
> > >   RelatedPackageVersions:
> > >dpkg 1.18.10ubuntu2
> > >apt  1.4
> > >   SourcePackage: openssl
> > >   Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> > > install/upgrade: package is in a very bad inconsistent state; you
> should
> > > reinstall it before attempting configuration
> > >   UpgradeStatus: No upgrade log present (probably fresh install)
> > >
> > > To manage notifications about this bug go to:
> > > https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/
> > 1692981/+subscriptions
> > >
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1696799).
> > https://bugs.launchpad.net/bugs/1692981
> >
> > Title:
> >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
> >   package is in a very bad inconsistent state; you should  reinstall it
> >   before attempting configuration
> >
> > Status in dpkg package in Ubuntu:
> >   Confirmed
> > Status in openssl package in Ubuntu:
> >   Confirmed
> >
> > Bug description:
> >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
> >   package is in a very bad inconsistent state; you should  reinstall it
> >   before attempting configuration
> >
> >   ProblemType: Package
> >   DistroRelease: Ubuntu 17.04
> >   Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
> >   ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
> >   Uname: Linux 4.10.0-21-generic x86_64
> >   ApportVersion: 2.20.4-0ubuntu4.1
> >   AptOrdering:
> >libssl1.0.0:amd64: Install
> >NULL: ConfigurePending
> >   Architecture: amd64
> >   Date: Tue May 23 21:47:55 2017
> >   DuplicateSignature:
> >package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
> >Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
> >dpkg: error processing package libssl-dev:amd64 (--configure):
> > package is in a very bad inconsistent state; you should
> >   ErrorMessage: package is in a very bad inconsistent state; you should
> > reinstall it before attempting configuration
> >   InstallationDate: Installed on 2017-05-15 (7 days ago)
> >   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64
> (20170412)
> >   RelatedPackageVersions:
> >dpkg 1.18.10ubuntu2
> >apt  1.4
> >   SourcePackage: openssl
> >   

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Eric Desrochers]

Hi Frode,

Now that cyphermox sponsored it for Artful ... Could you prepare the
debdiff(s) for the affected supported releases ? and I'll sponsored
them.

Regards,
Eric

** Changed in: rsyslog (Ubuntu Artful)
   Status: In Progress => Fix Committed

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

Title:
  Add a trigger to reload rsyslog when a new configuration file is
  dropped in /etc/rsyslog.d

Status in rsyslog package in Ubuntu:
  Fix Committed
Status in rsyslog source package in Trusty:
  New
Status in rsyslog source package in Xenial:
  New
Status in rsyslog source package in Yakkety:
  New
Status in rsyslog source package in Zesty:
  New
Status in rsyslog source package in Artful:
  Fix Committed
Status in rsyslog package in Debian:
  Fix Released

Bug description:
  [Impact]
  Servers or cloud instances will not log important messages after initial 
deployment. Manual reboot or restart of services is necessary to get expected 
behaviour.

  [Test Case]
  1) Install, enable and start haproxy
  2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed
  3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT 
created
  4) Restart rsyslog service
  5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created
  6) Restart haproxy service and observe that log now is filled with entries

  With the patched deb steps 3,4 and 6 becomes irrelevant and everything
  works out of the box.

  [Regression Potential]
  Minimal.

  This patch merges a patch from Debian where a trigger is added to the
  rsyslog package that fires when other debs drop files into
  /etc/rsyslog.d.

  
  [Original Bug Description]
  rsyslog should reload its configuration when other packages drop 
configuration in /etc/rsyslog.d

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337

  https://anonscm.debian.org/cgit/collab-
  maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f

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

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

[Touch-packages] [Bug 1708693] [NEW] package isc-dhcp-client 4.3.3-5ubuntu12.7 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installiere

[David Schmidt]

Public bug reported:

gir1.2-webkit2-4.0:amd64 (2.16.6-0ubuntu0.16.04.1) wird eingerichtet ...
imagemagick-6.q16 (8:6.8.9.9-7ubuntu5.9) wird eingerichtet ...
imagemagick (8:6.8.9.9-7ubuntu5.9) wird eingerichtet ...
libmagickcore-6.q16-2-extra:amd64 (8:6.8.9.9-7ubuntu5.9) wird eingerichtet ...
linux-libc-dev:amd64 (4.4.0-89.112) wird eingerichtet ...
unattended-upgrades (0.90ubuntu0.7) wird eingerichtet ...
Trigger für libc-bin (2.23-0ubuntu9) werden verarbeitet ...
Trigger für shim-signed (1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) werden 
verarbeitet ...
No DKMS packages installed: not changing Secure Boot validation state.
Fehler traten auf beim Bearbeiten von:
 isc-dhcp-client
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: isc-dhcp-client 4.3.3-5ubuntu12.7
ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-27-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Aug  4 18:49:02 2017
DhclientLeases:
 
ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
InstallationDate: Installed on 2017-05-31 (64 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic.efi.signed 
root=UUID=507a1f26-305d-4a62-b708-6ad478301961 ro quiet splash vt.handoff=7
SourcePackage: isc-dhcp
Title: package isc-dhcp-client 4.3.3-5ubuntu12.7 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: isc-dhcp (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 isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1708693

Title:
  package isc-dhcp-client 4.3.3-5ubuntu12.7 failed to install/upgrade:
  Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie
  sollten es  nochmal installieren, bevor Sie die Konfiguration
  versuchen.

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  gir1.2-webkit2-4.0:amd64 (2.16.6-0ubuntu0.16.04.1) wird eingerichtet ...
  imagemagick-6.q16 (8:6.8.9.9-7ubuntu5.9) wird eingerichtet ...
  imagemagick (8:6.8.9.9-7ubuntu5.9) wird eingerichtet ...
  libmagickcore-6.q16-2-extra:amd64 (8:6.8.9.9-7ubuntu5.9) wird eingerichtet ...
  linux-libc-dev:amd64 (4.4.0-89.112) wird eingerichtet ...
  unattended-upgrades (0.90ubuntu0.7) wird eingerichtet ...
  Trigger für libc-bin (2.23-0ubuntu9) werden verarbeitet ...
  Trigger für shim-signed (1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) werden 
verarbeitet ...
  No DKMS packages installed: not changing Secure Boot validation state.
  Fehler traten auf beim Bearbeiten von:
   isc-dhcp-client
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu12.7
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Aug  4 18:49:02 2017
  DhclientLeases:
   
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  InstallationDate: Installed on 2017-05-31 (64 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic.efi.signed 
root=UUID=507a1f26-305d-4a62-b708-6ad478301961 ro quiet splash vt.handoff=7
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-client 4.3.3-5ubuntu12.7 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/isc-dhcp/+bug/1708693/+subscriptions

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

[Touch-packages] [Bug 1503762] Re: Provide systemd service

[Bug Watch Updater]

** Changed in: apparmor (Debian)
   Status: Unknown => Confirmed

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

Title:
  Provide systemd service

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New
Status in apparmor package in Debian:
  Confirmed
Status in apparmor package in Gentoo Linux:
  New

Bug description:
  AppArmor is in the critical path for bootup for any systems that use
  it.  Let's specify a systemd service file instead of having systemd
  use sysv compatibility mode.

  There seems to be a few bugs tracking the precursor this work, like
  https://bugs.launchpad.net/apparmor/+bug/1488179, but no actual bug
  for the systemd service itself.

  AUR has a simple service file, not sure if that would be useful -
  https://aur.archlinux.org/packages/apparmor/

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

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

[Touch-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

[Leandro Heck]

Same on Linux rock 4.10.0-30-generic. Sound card keeps disappearing.

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

Title:
  [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
  while

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing a strange behavior with a headphone jack on my
  laptop.

  I have an external audio speaker connected to it. When I disconnect the 
speaker and reconnect it again it stops working.
  Even more, laptop audio stops working too. And after the reboot, I don't even 
see any of the audio devices.

  I've googled a lot and tried different fixes from forums with no luck.
  After a while, I've accidentally discovered that putting the laptop to
  the sleep mode and rebooting system after brings audio back to live.
  Even more, if speakers were attached during this sleep-reboot
  procedure, they are starting to work as well.

  However, after the next reboot speakers are not working again. And if
  I will plug them out and in - problem with completely missing audio
  returns.

  P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
  hibernation made me believe that it's somehow related. But after
  uninstalling this package nothing really changed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   kop3224 F...m pulseaudio
   /dev/snd/controlC0:  kop3224 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 26 12:17:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Встроенное аудио - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after 
a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

Re: [Touch-packages] [Bug 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con

[Jeremy Gabriel]

Hi Sandra,
I had to use

sudo apt-get install --reinstall libssl1.0.0:i386

Hope this helps,
Jeremy

On Thu, Jul 27, 2017 at 2:28 AM, Sandra Viktoria Mueller 
wrote:

> I wrote in the terminal this: sudo apt-get install --reinstall
> libssl-dev:amd64
> 1.0.2g-1ubuntu11.2
> Unfortunately it doesn't work. The problem remains.
>
> Please If you have another command which I can try? Thank you
>
> Sandra
>
> 2017-07-25 0:09 GMT+02:00 Seth Arnold <1692...@bugs.launchpad.net>:
>
> > ** Changed in: dpkg (Ubuntu)
> >Status: Fix Released => Confirmed
> >
> > ** Changed in: openssl (Ubuntu)
> >Status: Fix Released => Confirmed
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1692981
> >
> > Title:
> >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
> >   package is in a very bad inconsistent state; you should  reinstall it
> >   before attempting configuration
> >
> > Status in dpkg package in Ubuntu:
> >   Confirmed
> > Status in openssl package in Ubuntu:
> >   Confirmed
> >
> > Bug description:
> >   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
> >   package is in a very bad inconsistent state; you should  reinstall it
> >   before attempting configuration
> >
> >   ProblemType: Package
> >   DistroRelease: Ubuntu 17.04
> >   Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
> >   ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
> >   Uname: Linux 4.10.0-21-generic x86_64
> >   ApportVersion: 2.20.4-0ubuntu4.1
> >   AptOrdering:
> >libssl1.0.0:amd64: Install
> >NULL: ConfigurePending
> >   Architecture: amd64
> >   Date: Tue May 23 21:47:55 2017
> >   DuplicateSignature:
> >package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
> >Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
> >dpkg: error processing package libssl-dev:amd64 (--configure):
> > package is in a very bad inconsistent state; you should
> >   ErrorMessage: package is in a very bad inconsistent state; you should
> > reinstall it before attempting configuration
> >   InstallationDate: Installed on 2017-05-15 (7 days ago)
> >   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64
> (20170412)
> >   RelatedPackageVersions:
> >dpkg 1.18.10ubuntu2
> >apt  1.4
> >   SourcePackage: openssl
> >   Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> > install/upgrade: package is in a very bad inconsistent state; you should
> > reinstall it before attempting configuration
> >   UpgradeStatus: No upgrade log present (probably fresh install)
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/
> 1692981/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1696799).
> https://bugs.launchpad.net/bugs/1692981
>
> Title:
>   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
>   package is in a very bad inconsistent state; you should  reinstall it
>   before attempting configuration
>
> Status in dpkg package in Ubuntu:
>   Confirmed
> Status in openssl package in Ubuntu:
>   Confirmed
>
> Bug description:
>   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade:
>   package is in a very bad inconsistent state; you should  reinstall it
>   before attempting configuration
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 17.04
>   Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2
>   ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
>   Uname: Linux 4.10.0-21-generic x86_64
>   ApportVersion: 2.20.4-0ubuntu4.1
>   AptOrdering:
>libssl1.0.0:amd64: Install
>NULL: ConfigurePending
>   Architecture: amd64
>   Date: Tue May 23 21:47:55 2017
>   DuplicateSignature:
>package:libssl-dev:amd64:1.0.2g-1ubuntu11.2
>Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ...
>dpkg: error processing package libssl-dev:amd64 (--configure):
> package is in a very bad inconsistent state; you should
>   ErrorMessage: package is in a very bad inconsistent state; you should
> reinstall it before attempting configuration
>   InstallationDate: Installed on 2017-05-15 (7 days ago)
>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
>   RelatedPackageVersions:
>dpkg 1.18.10ubuntu2
>apt  1.4
>   SourcePackage: openssl
>   Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to
> install/upgrade: package is in a very bad inconsistent state; you should
> reinstall it before attempting configuration
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1692981/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[David Potter]

Hi Jarno

I would suggest that most desktop users get notified by the updater that
there are updates and run the updater accordingly to apply them.  As
such, I think the unclogging activity needs to run  automatically as the
users that are using the default boot partition size almost certainly
have no interest in having to run the software themselves or even making
a decision about how many old kernels to keep. In fact I suggest that
there are a goodly number of users that wouldn't know what to do with an
old kernel anyway.

My suggestion would be that there should be a default number of kernels
to keep (2 or maybe 3 would be my vote) but have a configuration file
that would allow the number to be altered for those users that wanted to
change the default. In fact you could even use a 0 value to indicate
that the user does not want the un-clogging to happen automatically.

It seems like all the commands and scripts have been sorted out over
time and the work is really to apply them in an automated fashion. I do
recognise that, there may be a more elegant solution that might be
preferable though.  In which case that is going to be more work.

If we are talking about putting this in place to run automatically and
definitely removing the "out of space" issue with no effort on behalf of
the user, then I would be happy to contribute towards the bounty.  Can
you confirm that this would be the intention?

I don't think that the default size of the boot partition should be
ignored though.  Surely it's not going to break anyone's system to up
the size to 500Mb.  Whilst I'm not a developer, I can't believe it would
take much effort to increase the default size.

Thanks for your persistence and help moving this bug along Jarno.

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/RemoveOldKernels

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

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

[Touch-packages] [Bug 1708682] [NEW] package whoopsie 0.2.55 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración.

[Jose Manuel Santa]

Public bug reported:

I don't know anything about this error.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: whoopsie 0.2.55
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CrashReports:
 600:113:122:0:2017-07-28 18:00:51.198155694 +0200:2017-07-28 
18:00:51.198155694 +0200:/var/crash/_usr_share_spotify_spotify.1000.uploaded
 644:1000:122:0:2017-07-28 18:00:50.166505810 +0200:2017-07-28 
18:00:50.166505810 +0200:/var/crash/_usr_share_spotify_spotify.1000.upload
 640:1000:122:12888503:2017-07-28 18:00:49.162507057 +0200:2017-07-28 
18:00:50.166505810 +0200:/var/crash/_usr_share_spotify_spotify.1000.crash
 600:0:122:121616:2017-08-04 17:29:46.850206375 +0200:2017-08-04 
17:29:47.850206375 +0200:/var/crash/whoopsie.0.crash
Date: Fri Aug  4 17:29:47 2017
ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
InstallationDate: Installed on 2017-05-19 (76 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions: apport-noui N/A
SourcePackage: whoopsie
Title: package whoopsie 0.2.55 failed to install/upgrade: El paquete está en un 
estado grave de inconsistencia - debe reinstalarlo  antes de intentar su 
configuración.
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package autoreport-false zesty

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

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

Status in whoopsie package in Ubuntu:
  New

Bug description:
  I don't know anything about this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: whoopsie 0.2.55
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CrashReports:
   600:113:122:0:2017-07-28 18:00:51.198155694 +0200:2017-07-28 
18:00:51.198155694 +0200:/var/crash/_usr_share_spotify_spotify.1000.uploaded
   644:1000:122:0:2017-07-28 18:00:50.166505810 +0200:2017-07-28 
18:00:50.166505810 +0200:/var/crash/_usr_share_spotify_spotify.1000.upload
   640:1000:122:12888503:2017-07-28 18:00:49.162507057 +0200:2017-07-28 
18:00:50.166505810 +0200:/var/crash/_usr_share_spotify_spotify.1000.crash
   600:0:122:121616:2017-08-04 17:29:46.850206375 +0200:2017-08-04 
17:29:47.850206375 +0200:/var/crash/whoopsie.0.crash
  Date: Fri Aug  4 17:29:47 2017
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-05-19 (76 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  Title: package whoopsie 0.2.55 failed to install/upgrade: El paquete está en 
un estado grave de inconsistencia - debe reinstalarlo  antes de intentar su 
configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1707522] Re: Unable to login after locking screen, unable to lock screen via gui menu

[Brian Murray]

** Package changed: apport (Ubuntu) => kubuntu-meta (Ubuntu)

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

Title:
  Unable to login after locking screen, unable to lock screen via gui
  menu

Status in kubuntu-meta package in Ubuntu:
  New

Bug description:
  Using AMDGPU-Pro
  dpkg -l amdgpu-pro
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name Version   Architecture  Description
  
+++--=-=-=
  ii  amdgpu-pro   17.10-450821  amd64 Meta package to install 
amdgpu Pro co

  
  Upgraded from amdgpu-pro-17.10-429170 where it was also broken, installed all 
available updates prior to the driver being installed. Can manually lock the 
screen using Ctrl-Alt-L but have to use loginctl unlock-sessions to unlock

  Not seeing the debugging symbols needed to properly look into this
  issue to install to provide more information

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport-kde 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Jul 30 12:38:33 2017
  ExecutablePath: /usr/share/apport/apport-kde
  InstallationDate: Installed on 2016-09-18 (314 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: apport fails to inform when not sending report

[Brian Murray]

Crash reports from apport are only sent to Launchpad, where you would
have a browser window opened to add more details, if you are running the
development release of Ubuntu (currently Artful Aardvark).  Otherwise,
crash reports are silently sent to errors.ubuntu.com.  If I recall
correctly, the design decision was to make apport as unintrusive as
possible hence there is not a second dialog displayed saying "Yes, it
was sent".  That being said perhaps the dialog about sending the crash
could be modified to notify you that no further action is required.

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

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

** Summary changed:

- apport fails to inform when not sending report
+ apport silently sends crash reports to errors.ubuntu.com

** Tags added: likely-dup

-- 
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 silently sends crash reports to errors.ubuntu.com

Status in apport package in Ubuntu:
  Triaged

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 1447099] Re: /sbin/upstart:indicator-session-unknown-user-error

[Michael Lee]

This bugs still exists here, 16.04, but only presents in some specific
user account.

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

Title:
  /sbin/upstart:indicator-session-unknown-user-error

Status in upstart :
  New
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Vivid:
  Confirmed
Status in upstart source package in Wily:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding upstart.  This problem was most recently seen with version
  1.13.2-0ubuntu13, the problem page at
  https://errors.ubuntu.com/problem/09ab1b2ed4cff7556ed135307deb9f99c107193a
  contains more details.

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

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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Mathieu Trudel-Lapierre]

Looks like this is still missing one additional commit from when it was
included in Debian; namely the addition of init-system-helpers in the
Depends: field for rsyslog (this makes sure we have a new-enough init-
system-helpers so try-restart works).

I'll add it for you in this case. It feels counterproductive for me to
reject the change again when you already did go back on it before.

By the way, this means that for a xenial SRU, this would need to be
adjusted to the right version number, or that feature will need to be
backported...

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

Title:
  Add a trigger to reload rsyslog when a new configuration file is
  dropped in /etc/rsyslog.d

Status in rsyslog package in Ubuntu:
  In Progress
Status in rsyslog source package in Trusty:
  New
Status in rsyslog source package in Xenial:
  New
Status in rsyslog source package in Yakkety:
  New
Status in rsyslog source package in Zesty:
  New
Status in rsyslog source package in Artful:
  In Progress
Status in rsyslog package in Debian:
  Fix Released

Bug description:
  [Impact]
  Servers or cloud instances will not log important messages after initial 
deployment. Manual reboot or restart of services is necessary to get expected 
behaviour.

  [Test Case]
  1) Install, enable and start haproxy
  2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed
  3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT 
created
  4) Restart rsyslog service
  5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created
  6) Restart haproxy service and observe that log now is filled with entries

  With the patched deb steps 3,4 and 6 becomes irrelevant and everything
  works out of the box.

  [Regression Potential]
  Minimal.

  This patch merges a patch from Debian where a trigger is added to the
  rsyslog package that fires when other debs drop files into
  /etc/rsyslog.d.

  
  [Original Bug Description]
  rsyslog should reload its configuration when other packages drop 
configuration in /etc/rsyslog.d

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337

  https://anonscm.debian.org/cgit/collab-
  maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f

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

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Jarno Suni]

The reason why 'apt-get autoremove' is stated there is that it is a
simple working way in 16.04 and later for most users, if your system is
not broken already. purge-old-kernels is included in some Ubuntu
package; consequently it is supported by Launchpad's bug reporting
system. But as said in the document, it is currently deprecated and its
bugs will likely not be fixed. It might still be useful for some users
in some cases.

If one wants to use unattended-upgrades manually, he/she could disable
it from being called automatically. One should avoid installing security
updates manually by Software Updater in 14.04, if one expects to use apt
/unattended-upgrades for removing kernels automatically.

I have developed some software that makes the un-clogging part easier;
link to related bountysource.com page is included in the document. Just
feel free to post a bounty and/or give some feedback about the interface
in the respective Launchpad page. I guess the software could be launched
automatically in case of kernel clog when it happens in interactive
session (or even in non-interactive session, if the software is made to
support completely non-interactive un-clogging).

If you install a kernel manually in command line by say
sudo apt-get install linux-image-4.4.0-87-generic
which kernel(s) that command should remove in turn in your opinion? Or could it 
be that the user who runs the command should take care of it? User possibly 
wants to keep some spare kernels, in case the one that is just installed is 
bad. Or a developer may want to keep some testing kernels etc.

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

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/RemoveOldKernels

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

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

[Touch-packages] [Bug 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random

[Alan Griffiths]

Not sure how to test this, but...

index b93b9ba47..cfa82d13c 100644
--- a/lib/randutils.c
+++ b/lib/randutils.c
@@ -81,8 +81,10 @@ void random_get_bytes(void *buf, size_t nbytes)
while (n > 0) {
ssize_t x = read(fd, cp, n);
if (x <= 0) {
-   if (lose_counter++ > 16)
+   if (lose_counter++ > 16) {
+   while (n--) *cp++ = rand();
break;
+   }
continue;
}
n -= x;

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

Title:
  Valgrind reports " Uninitialised value was created by a stack
  allocation" in  __uuid_generate_random

Status in util-linux package in Ubuntu:
  New

Bug description:
  This has shown up in lp:mir CI on Artful amd64 (and no other
  architecture or series we're using)

  For example:

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=artful/4870/consoleFull

  Marking the memory with VALGRIND_MAKE_MEM_DEFINED() suppresses the
  error.

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

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

[Touch-packages] [Bug 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random

[Alan Griffiths]

PS I suspect this only manifests in CI because the builders have an
older kernel than development machines.

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

Title:
  Valgrind reports " Uninitialised value was created by a stack
  allocation" in  __uuid_generate_random

Status in util-linux package in Ubuntu:
  New

Bug description:
  This has shown up in lp:mir CI on Artful amd64 (and no other
  architecture or series we're using)

  For example:

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=artful/4870/consoleFull

  Marking the memory with VALGRIND_MAKE_MEM_DEFINED() suppresses the
  error.

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

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

[Touch-packages] [Bug 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random

[Alan Griffiths]

Looking at the util-linux source it seems that this could arise if:

1. opening /dev/urandom succeeds; and,
2. a subsequent read() fails

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

Title:
  Valgrind reports " Uninitialised value was created by a stack
  allocation" in  __uuid_generate_random

Status in util-linux package in Ubuntu:
  New

Bug description:
  This has shown up in lp:mir CI on Artful amd64 (and no other
  architecture or series we're using)

  For example:

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=artful/4870/consoleFull

  Marking the memory with VALGRIND_MAKE_MEM_DEFINED() suppresses the
  error.

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

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

[Touch-packages] [Bug 1503762] Re: Provide systemd service

[intrigeri]

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

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

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

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

Title:
  Provide systemd service

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New
Status in apparmor package in Debian:
  Unknown
Status in apparmor package in Gentoo Linux:
  New

Bug description:
  AppArmor is in the critical path for bootup for any systems that use
  it.  Let's specify a systemd service file instead of having systemd
  use sysv compatibility mode.

  There seems to be a few bugs tracking the precursor this work, like
  https://bugs.launchpad.net/apparmor/+bug/1488179, but no actual bug
  for the systemd service itself.

  AUR has a simple service file, not sure if that would be useful -
  https://aur.archlinux.org/packages/apparmor/

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

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

[Touch-packages] [Bug 1708648] [NEW] [HP Pavilion 15 Notebook PC, ATI R6xx HDMI, Digital Out, HDMI] No sound at all

[Anil]

Public bug reported:

unable to hear the audio

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic i686
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
CurrentDesktop: Unity
Date: Fri Aug  4 17:06:56 2017
InstallationDate: Installed on 2017-07-24 (11 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
Symptom_Card: Built-in Audio - HDA ATI HDMI
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [HP Pavilion 15 Notebook PC, ATI R6xx HDMI, Digital Out, HDMI] No sound 
at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/13/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.16
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 216C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 30.25
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd11/13/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr088210305E0610100:rvnHewlett-Packard:rn216C:rvr30.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion 15 Notebook PC
dmi.product.version: 088210305E0610100
dmi.sys.vendor: Hewlett-Packard

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


** Tags: apport-bug i386 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/1708648

Title:
  [HP Pavilion 15 Notebook PC, ATI R6xx HDMI, Digital Out, HDMI] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  unable to hear the audio

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Aug  4 17:06:56 2017
  InstallationDate: Installed on 2017-07-24 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Built-in Audio - HDA ATI HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [HP Pavilion 15 Notebook PC, ATI R6xx HDMI, Digital Out, HDMI] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 216C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 30.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd11/13/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr088210305E0610100:rvnHewlett-Packard:rn216C:rvr30.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 088210305E0610100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1588917] Re: Upgrade ping to latest version that doesn't require SUID or NET_RAW capability

[Jamie Strandboge]

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

** Changed in: iputils (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Upgrade ping to latest version that doesn't require SUID or NET_RAW
  capability

Status in iputils package in Ubuntu:
  Triaged

Bug description:
  The latest version of iputils have the option of using SOCK_DGRAM
  packets instead of SOCK_RAW, provided that the
  net.ipv4.ping_group_range sysctl is set to a different value.  This
  helps a lot with security in -not just- Linux containers by dropping
  support for the NET_RAW capability.

  Also, the ubuntu-minimal packages should not include this package as a
  hard dependency in case I want to uninstall iputils-ping to substitute
  it for another package like oping which just works if I turn off the
  setuid bit.

  This would help a lot with secure Linux containers with no NET_RAW
  capabilities.

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

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

[Touch-packages] [Bug 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random

[Alan Griffiths]

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

** No longer affects: valgrind (Ubuntu)

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

Title:
  Valgrind reports " Uninitialised value was created by a stack
  allocation" in  __uuid_generate_random

Status in util-linux package in Ubuntu:
  New

Bug description:
  This has shown up in lp:mir CI on Artful amd64 (and no other
  architecture or series we're using)

  For example:

  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=artful/4870/consoleFull

  Marking the memory with VALGRIND_MAKE_MEM_DEFINED() suppresses the
  error.

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

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

[Piotr Trembecki]

I can confirm as well that removing dbus-user-session and reboot worked
like a charm. Thx all.

-- 
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 1708642] [NEW] package apport 2.20.1-0ubuntu2.6 failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 2

[Akvilon]

Public bug reported:

Bug during upgrade procedure.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.6
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic i686
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: i386
CrashReports:
 600:0:118:52652:2017-08-02 17:56:26.070915699 +0300:2017-08-02 
17:56:27.070915699 +0300:/var/crash/apport.0.crash
 600:0:118:85461:2017-07-28 21:55:53.830601959 +0300:2017-08-04 
14:01:22.232576075 +0300:/var/crash/python-samba.0.crash
Date: Wed Aug  2 17:56:26 2017
DpkgHistoryLog:
 Start-Date: 2017-08-02  17:56:16
 Commandline: /usr/bin/unattended-upgrade
 Upgrade: python-samba:i386 (2:4.3.11+dfsg-0ubuntu0.16.04.7, 
2:4.3.11+dfsg-0ubuntu0.16.04.9), apport:i386 (2.20.1-0ubuntu2.6, 
2.20.1-0ubuntu2.10), libwebkit2gtk-4.0-37:i386 (2.16.3-0ubuntu0.16.04.1, 
2.16.6-0ubuntu0.16.04.1), gir1.2-webkit2-4.0:i386 (2.16.3-0ubuntu0.16.04.1, 
2.16.6-0ubuntu0.16.04.1), libjavascriptcoregtk-4.0-18:i386 
(2.16.3-0ubuntu0.16.04.1, 2.16.6-0ubuntu0.16.04.1), 
libwebkit2gtk-4.0-37-gtk2:i386 (2.16.3-0ubuntu0.16.04.1, 
2.16.6-0ubuntu0.16.04.1), gir1.2-javascriptcoregtk-4.0:i386 
(2.16.3-0ubuntu0.16.04.1, 2.16.6-0ubuntu0.16.04.1)
ErrorMessage: подпроцесс новый сценарий pre-removal возвратил код ошибки 2
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: apport
Title: package apport 2.20.1-0ubuntu2.6 failed to install/upgrade: подпроцесс 
новый сценарий pre-removal возвратил код ошибки 2
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package apport 2.20.1-0ubuntu2.6 failed to install/upgrade: подпроцесс
  новый сценарий pre-removal возвратил код ошибки 2

Status in apport package in Ubuntu:
  New

Bug description:
  Bug during upgrade procedure.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.6
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CrashReports:
   600:0:118:52652:2017-08-02 17:56:26.070915699 +0300:2017-08-02 
17:56:27.070915699 +0300:/var/crash/apport.0.crash
   600:0:118:85461:2017-07-28 21:55:53.830601959 +0300:2017-08-04 
14:01:22.232576075 +0300:/var/crash/python-samba.0.crash
  Date: Wed Aug  2 17:56:26 2017
  DpkgHistoryLog:
   Start-Date: 2017-08-02  17:56:16
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: python-samba:i386 (2:4.3.11+dfsg-0ubuntu0.16.04.7, 
2:4.3.11+dfsg-0ubuntu0.16.04.9), apport:i386 (2.20.1-0ubuntu2.6, 
2.20.1-0ubuntu2.10), libwebkit2gtk-4.0-37:i386 (2.16.3-0ubuntu0.16.04.1, 
2.16.6-0ubuntu0.16.04.1), gir1.2-webkit2-4.0:i386 (2.16.3-0ubuntu0.16.04.1, 
2.16.6-0ubuntu0.16.04.1), libjavascriptcoregtk-4.0-18:i386 
(2.16.3-0ubuntu0.16.04.1, 2.16.6-0ubuntu0.16.04.1), 
libwebkit2gtk-4.0-37-gtk2:i386 (2.16.3-0ubuntu0.16.04.1, 
2.16.6-0ubuntu0.16.04.1), gir1.2-javascriptcoregtk-4.0:i386 
(2.16.3-0ubuntu0.16.04.1, 2.16.6-0ubuntu0.16.04.1)
  ErrorMessage: подпроцесс новый сценарий pre-removal возвратил код ошибки 2
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.6 failed to install/upgrade: подпроцесс 
новый сценарий pre-removal возвратил код ошибки 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1708639] Re: [P640RF, Realtek ALC892, Black Headphones Out, Rear] Playback problem

[Proc]

** Description changed:

  No sound over headphones since upgrade to 17.04.
  Sound only from Speakers of Laptop. Alsamixer shows not muted / I can unmute 
it, doesn't matter.
- [I've used ubuntu-bug -s audio and landed here after being shown multiple 
["Text"* - Yes No Cancel] Dialogs.
+ PulseAudio Volume Control lists Headpgones always as "non plugged in"
+ 
+ [I've used ubuntu-bug -s audio and landed here after being shown
+ multiple ["Text"* - Yes No Cancel] Dialogs.
+ 
  
  *Yes, no real message only "Text"
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC0D0c:   aron   4433 F...m pulseaudio
-  /dev/snd/pcmC0D0p:   aron   4433 F...m pulseaudio
-  /dev/snd/controlC0:  aron   4433 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC0D0c:   aron   4433 F...m pulseaudio
+  /dev/snd/pcmC0D0p:   aron   4433 F...m pulseaudio
+  /dev/snd/controlC0:  aron   4433 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Aug  4 12:36:36 2017
  InstallationDate: Installed on 2017-07-02 (32 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black SPDIF Out, Rear
  Symptom_Type: None of the above
  Title: [P640RF, Realtek ALC892, Black SPDIF Out, Rear] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P640RF
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd09/19/2016:svnNotebook:pnP640RF:pvrNotApplicable:rvnNotebook:rnP640RF:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P640RF
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-07-26T01:53:12.758805

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

Title:
  [P640RF, Realtek ALC892, Black Headphones Out, Rear] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound over headphones since upgrade to 17.04.
  Sound only from Speakers of Laptop. Alsamixer shows not muted / I can unmute 
it, doesn't matter.
  PulseAudio Volume Control lists Headpgones always as "non plugged in"

  [I've used ubuntu-bug -s audio and landed here after being shown
  multiple ["Text"* - Yes No Cancel] Dialogs.

  
  *Yes, no real message only "Text"

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   aron   4433 F...m pulseaudio
   /dev/snd/pcmC0D0p:   aron   4433 F...m pulseaudio
   /dev/snd/controlC0:  aron   4433 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Aug  4 12:36:36 2017
  InstallationDate: Installed on 2017-07-02 (32 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black SPDIF Out, Rear
  Symptom_Type: None of the above
  Title: [P640RF, Realtek ALC892, Black SPDIF Out, Rear] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P640RF
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd09/19/2016:svnNotebook:pnP640RF:pvrNotApplicable:rvnNotebook:rnP640RF:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P640RF
  

[Touch-packages] [Bug 1694600] Re: package whoopsie 0.2.52.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Launchpad Bug Tracker]

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

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

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

Title:
  package whoopsie 0.2.52.3 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in whoopsie package in Ubuntu:
  Confirmed

Bug description:
  I ran "sudo apt-get install -f" on my terminal and selected "y" on prompt.
  After that, I got the following logs:

  (Reading database ... 305447 files and directories currently installed.)
  Preparing to unpack .../libwhoopsie0_0.2.52.3_amd64.deb ...
  Unpacking libwhoopsie0:amd64 (0.2.52.3) over (0.2.52.2) ...
  Processing triggers for libc-bin (2.23-0ubuntu7) ...
  Setting up libwhoopsie0:amd64 (0.2.52.3) ...
  dpkg: error processing package whoopsie (--configure):
   package is in a very bad inconsistent state; you should
   reinstall it before attempting configuration
  Processing triggers for libc-bin (2.23-0ubuntu7) ...
  Errors were encountered while processing:
   whoopsie
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: whoopsie 0.2.52.3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   libwhoopsie0: Install
   libwhoopsie0: Configure
   whoopsie: Configure
   NULL: ConfigurePending
  Architecture: amd64
  CrashReports:
   640:1000:116:38189263:2017-05-30 11:10:06.496968406 +0530:2017-05-30 
11:10:07.008974568 +0530:/var/crash/_usr_share_nylas-mail_nylas.1000.crash
   640:1000:116:75985:2017-05-31 10:59:36.494395912 +0530:2017-05-31 
10:59:36.710448121 +0530:/var/crash/_usr_bin_update-manager.1000.crash
   600:0:116:416287:2017-05-31 11:00:14.342133998 +0530:2017-05-31 
11:00:15.342133998 +0530:/var/crash/whoopsie.0.crash
   640:1000:116:54173:2017-05-30 11:10:08.964998106 +0530:2017-05-30 
11:10:09.201000946 +0530:/var/crash/_usr_share_apport_apport-gtk.1000.crash
  Date: Wed May 31 11:00:14 2017
  DuplicateSignature:
   package:whoopsie:0.2.52.3
   Setting up libwhoopsie0:amd64 (0.2.52.3) ...
   dpkg: error processing package whoopsie (--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-01-21 (129 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  Title: package whoopsie 0.2.52.3 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1708639] [NEW] [P640RF, Realtek ALC892, Black Headphones Out, Rear] Playback problem

[Proc]

Public bug reported:

No sound over headphones since upgrade to 17.04.
Sound only from Speakers of Laptop. Alsamixer shows not muted / I can unmute 
it, doesn't matter.
[I've used ubuntu-bug -s audio and landed here after being shown multiple 
["Text"* - Yes No Cancel] Dialogs.

*Yes, no real message only "Text"

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
Uname: Linux 4.10.0-30-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   aron   4433 F...m pulseaudio
 /dev/snd/pcmC0D0p:   aron   4433 F...m pulseaudio
 /dev/snd/controlC0:  aron   4433 F pulseaudio
CurrentDesktop: KDE
Date: Fri Aug  4 12:36:36 2017
InstallationDate: Installed on 2017-07-02 (32 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Black SPDIF Out, Rear
Symptom_Type: None of the above
Title: [P640RF, Realtek ALC892, Black SPDIF Out, Rear] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.06
dmi.board.asset.tag: Tag 12345
dmi.board.name: P640RF
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd09/19/2016:svnNotebook:pnP640RF:pvrNotApplicable:rvnNotebook:rnP640RF:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.name: P640RF
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-07-26T01:53:12.758805

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


** Tags: amd64 apport-bug zesty

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

Title:
  [P640RF, Realtek ALC892, Black Headphones Out, Rear] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound over headphones since upgrade to 17.04.
  Sound only from Speakers of Laptop. Alsamixer shows not muted / I can unmute 
it, doesn't matter.
  [I've used ubuntu-bug -s audio and landed here after being shown multiple 
["Text"* - Yes No Cancel] Dialogs.

  *Yes, no real message only "Text"

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   aron   4433 F...m pulseaudio
   /dev/snd/pcmC0D0p:   aron   4433 F...m pulseaudio
   /dev/snd/controlC0:  aron   4433 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Aug  4 12:36:36 2017
  InstallationDate: Installed on 2017-07-02 (32 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black SPDIF Out, Rear
  Symptom_Type: None of the above
  Title: [P640RF, Realtek ALC892, Black SPDIF Out, Rear] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P640RF
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd09/19/2016:svnNotebook:pnP640RF:pvrNotApplicable:rvnNotebook:rnP640RF:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P640RF
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-07-26T01:53:12.758805

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

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

[Touch-packages] [Bug 1698795] Re: Humanity should provide symbolic versions of custom icons for GNOME Shell

[Sebastien Bacher]

We discussed it at GUADEC, the GNOME design is to use symbolic icons in
the panel and our theme is missing ones to match our icons which creates
the difference. But even if we fix the theme third party apps (and some
of the default ones) are going to display a colored icon (e.g firefox)
and it's going to be difficult to have visual conistency. One way would
be to change the Ubuntu session to not display symbolic icons but always
the normal one...

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

Title:
  Humanity should provide symbolic versions of custom icons for GNOME
  Shell

Status in gnome-shell package in Ubuntu:
  New
Status in humanity-icon-theme package in Ubuntu:
  New

Bug description:
  The app icon in top panel next to application menu entry is the
  default adwaita icons and don't match the current theming.

  It's either:
  - the fact that we don't provide the correct icon size in our themes, and so, 
the icons are defaulted
  - a bug in G-S

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

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

[Touch-packages] [Bug 1705269] Re: Wifi disconnect every few hours, show two arrows instead of wifi symbol

[eezacque]

** Description changed:

- Every few hours, wifi disconnects, and instead of the wifi icon I get
+ Every day or so, wifi disconnects, and instead of the wifi icon I get
  the ethernet icon (two arrows), which makes no sense, as there is no
  ethernet cable attached. When this happens, the entire gui slows down,
  mouse becomes jittery. This can be fixed by switched wireless off and on
  in the network control panel.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 19 15:56:54 2017
  InstallationDate: Installed on 2014-10-24 (998 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IpRoute:
-  default via 192.168.178.1 dev wlan0  proto static  metric 600 
-  169.254.0.0/16 dev virbr0  scope link  metric 1000 linkdown 
-  192.168.0.0/24 dev tap0  proto kernel  scope link  src 192.168.0.1 linkdown 
-  192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown 
-  192.168.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.15  
metric 600
+  default via 192.168.178.1 dev wlan0  proto static  metric 600
+  169.254.0.0/16 dev virbr0  scope link  metric 1000 linkdown
+  192.168.0.0/24 dev tap0  proto kernel  scope link  src 192.168.0.1 linkdown
+  192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
+  192.168.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.15  
metric 600
  NetworkManager.state:
-  [main]
-  NetworkingEnabled=true
-  WirelessEnabled=true
-  WWANEnabled=true
-  WimaxEnabled=true
+  [main]
+  NetworkingEnabled=true
+  WirelessEnabled=true
+  WWANEnabled=true
+  WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-08-22T17:40:36.563689
  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
+  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
+  running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

** Summary changed:

- Wifi disconnect every few hours, show two arrows instead of wifi symbol
+ Wifi disconnect every day or so, shows two arrows instead of wifi symbol

** Summary changed:

- Wifi disconnect every day or so, shows two arrows instead of wifi symbol
+ Wifi disconnects every day or so, shows two arrows instead of wifi symbol

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

Title:
  Wifi disconnects every day or so, shows two arrows instead of wifi
  symbol

Status in network-manager package in Ubuntu:
  New

Bug description:
  Every day or so, wifi disconnects, and instead of the wifi icon I get
  the ethernet icon (two arrows), which makes no sense, as there is no
  ethernet cable attached. When this happens, the entire gui slows down,
  mouse becomes jittery. This can be fixed by switched wireless off and
  on in the network control panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 19 15:56:54 2017
  InstallationDate: Installed on 2014-10-24 (998 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IpRoute:
   default via 192.168.178.1 dev wlan0  proto static  metric 600
   169.254.0.0/16 dev virbr0  scope link  metric 1000 linkdown
   192.168.0.0/24 dev tap0  proto kernel  scope link  src 192.168.0.1 linkdown
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
   192.168.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.15  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-08-22T17:40:36.563689
  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:

[Touch-packages] [Bug 1708628] Re: INTERNAL ERROR

[Neville Shepherdson]

Problem appears to be well documented.

Thank you

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

Title:
  INTERNAL ERROR

Status in xorg package in Ubuntu:
  New

Bug description:
  After start-up my Ubuntu 17.04 has a message is on screen "This
  computer has an internal error".

  Cancel message and appears to run; not as it should though,

  Thank you

  Neville Shepherdson

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  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 19:15:49 2017
  DistUpgraded: 2017-06-06 10:44:16,052 DEBUG icon theme changed, re-reading
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell OptiPlex 755 [1028:0211]
 Subsystem: Dell OptiPlex 755 [1028:0211]
  InstallationDate: Installed on 2017-06-05 (60 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic 
root=UUID=7c6836e2-8dff-4656-b696-a03a3fa554b3 ro quiet drm.debug=0xe splash 
plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to zesty on 2017-06-06 (59 days ago)
  dmi.bios.date: 08/04/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0R092H
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/04/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0R092H:rvr:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Fri Aug  4 19:14:09 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   input USB OPTICAL MOUSE   MOUSE, id 8
   inputLite-On Technology Corp. USB Multimedia Keyboard KEYBOARD, id 9
   inputLite-On Technology Corp. USB Multimedia Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu1.1

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

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

[Touch-packages] [Bug 1708628] [NEW] INTERNAL ERROR

[Neville Shepherdson]

Public bug reported:

After start-up my Ubuntu 17.04 has a message is on screen "This computer
has an internal error".

Cancel message and appears to run; not as it should though,

Thank you

Neville Shepherdson

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
Uname: Linux 4.10.0-30-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: i386
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 19:15:49 2017
DistUpgraded: 2017-06-06 10:44:16,052 DEBUG icon theme changed, re-reading
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell OptiPlex 755 [1028:0211]
   Subsystem: Dell OptiPlex 755 [1028:0211]
InstallationDate: Installed on 2017-06-05 (60 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
MachineType: Dell Inc. OptiPlex 755
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic 
root=UUID=7c6836e2-8dff-4656-b696-a03a3fa554b3 ro quiet drm.debug=0xe splash 
plymouth:debug
SourcePackage: xorg
UpgradeStatus: Upgraded to zesty on 2017-06-06 (59 days ago)
dmi.bios.date: 08/04/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0R092H
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 16
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/04/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0R092H:rvr:cvnDellInc.:ct16:cvr:
dmi.product.name: OptiPlex 755
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Fri Aug  4 19:14:09 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 input USB OPTICAL MOUSE   MOUSE, id 8
 inputLite-On Technology Corp. USB Multimedia Keyboard KEYBOARD, id 9
 inputLite-On Technology Corp. USB Multimedia Keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.3-1ubuntu1.1

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


** Tags: apport-bug compiz-0.9 i386 ubuntu zesty

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

Title:
  INTERNAL ERROR

Status in xorg package in Ubuntu:
  New

Bug description:
  After start-up my Ubuntu 17.04 has a message is on screen "This
  computer has an internal error".

  Cancel message and appears to run; not as it should though,

  Thank you

  Neville Shepherdson

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  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 19:15:49 2017
  DistUpgraded: 2017-06-06 10:44:16,052 DEBUG icon theme changed, re-reading
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell OptiPlex 755 [1028:0211]
 Subsystem: Dell OptiPlex 755 [1028:0211]
  InstallationDate: Installed on 2017-06-05 (60 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  MachineType: Dell Inc. OptiPlex 755
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic 

[Touch-packages] [Bug 1708137] Re: application crashes due to rival protobuffers versions

[henning hinze]

** Package changed: protobuf (Ubuntu) => mesa (Ubuntu)

** Also affects: gstreamer-vaapi (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  application crashes due to rival protobuffers versions

Status in gstreamer-vaapi package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  So somewhen in last week there were made some changes in the ubuntu
  repository which effect libEGL. This lib newly uses libmirclient.so.9
  which itself uses libprotobuf-lite.so.9. The default protobuffers
  version shipped with ubuntu is 2.6.1. My application uses libgstvaapi
  which uses libEGL. My application as well uses protobuffers but I link
  it statically to version 3.0.0 due to its json compatibility. So when
  now starting the application it crashes immediately due to rivaling
  protobuffers version. This problem first occured last week somewhen.
  This makes it impossible to use libEGL/libmir and a not-default
  protobuffers version in one application. Please let me how you're
  going to deal with that.

  Best,
  Henning

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

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

[Dimitri John Ledkov]

If there are wrong documentation out there, please provide links such
that we could update it. (E.g. a popular question on askubuntu.com or
some such)

-- 
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:
  Invalid

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 1708166] Re: systemd/udev does not rename network interfaces specified in .link files

[Dimitri John Ledkov]

Local: $ man systemd.link

Ubuntu any release: http://manpages.ubuntu.com/cgi-
bin/search.py?q=systemd.link

Upstream latest:
https://www.freedesktop.org/software/systemd/man/systemd.link.html

...
The first (in lexical order) of the link files that matches a given device is 
applied. Note that a default file 99-default.link is shipped by the system, any 
user-supplied .link should hence have a lexically earlier name to be considered 
at all.

In general all systemd commands and units are documented. E.g. $ man
systemd.service systemd.path systemd.link systemd.network and so on and
so worth should give you authoritative documentation about every little
detail.

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

-- 
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:
  Invalid

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 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Jarno Suni]

Note that the patch in #15 removes the leftovers related to the kernel
version being removed currently. Removing leftovers related to already
purged kernels still have to be done manually, for example by linux-
purge https://www.bountysource.com/issues/38300038-feature-request-the-
command-should-work-like-this together with other extra kernel related
stuff.

-- 
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 1686344] Re: Mesa 17.0.x stable release

[Bart Willemsen]

Thanks, I hope it can be rolled out soon since this release fixes a bug
that affected me :)

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

Title:
  Mesa 17.0.x stable release

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

  Mesa stable release for zesty & backport to xenial. Xenial needs newer
  libdrm from zesty. These are part of the hwe-16.04 stack refresh.

  [Test case]

  Install, run desktop session, test xonotic.

  the important hw drivers to test:
  - i965 (Intel)
  - radeonsi (AMD)

  [Regression potential]

  Spec compliance test suites are already run by Intel and others, so
  feature regressions should not be possible. GLESv1 support has been
  dropped from the packaging though, but packages that depend on
  libgles1-mesa have been pushed to proposed to drop the dependency, see
  bug 1676845 (applies to xenial).

  17.0.x has been available for xenial and yakkety users for a while,
  and so far no-one has complained about driver regressions.

  [Other info]

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

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

[Touch-packages] [Bug 1708602] [NEW] package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevo

[Michael Groppel]

Public bug reported:

?

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: bsdutils 1:2.29-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
Uname: Linux 4.10.0-24-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Wed Aug  2 20:08:22 2017
DpkgTerminalLog:
 dpkg: Fehler beim Bearbeiten des Paketes bsdutils (--configure):
  Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es
  nochmal installieren, bevor Sie die Konfiguration versuchen.
ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
InstallationDate: Installed on 2017-04-15 (110 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: util-linux
Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: Paket ist 
in einem sehr schlechten inkonsistenten Zustand - Sie sollten es  nochmal 
installieren, bevor Sie die Konfiguration versuchen.
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: Paket
  ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es
  nochmal installieren, bevor Sie die Konfiguration versuchen.

Status in util-linux package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed Aug  2 20:08:22 2017
  DpkgTerminalLog:
   dpkg: Fehler beim Bearbeiten des Paketes bsdutils (--configure):
Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es
nochmal installieren, bevor Sie die Konfiguration versuchen.
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  InstallationDate: Installed on 2017-04-15 (110 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: Paket 
ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es  nochmal 
installieren, bevor Sie die Konfiguration versuchen.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Manfred Hampl]

@Karl Schindler:
What you see is probably a bug in Eclipse, see 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=479646
Something that eclipse has to work on.

** Bug watch added: Eclipse bugs #479646
   https://bugs.eclipse.org/bugs/show_bug.cgi?id=479646

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