[Touch-packages] [Bug 2063328] Re: FTBFS in eglibc

2024-05-02 Thread Leonidas S. Barbosa
** Changed in: eglibc (Ubuntu)
   Status: In Progress => Fix Released

** Also affects: eglibc (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  FTBFS in eglibc

Status in eglibc package in Ubuntu:
  Fix Released
Status in eglibc source package in Trusty:
  New

Bug description:
  == Summary ==

  A FTBFS occurs in eglibc that affects trusty-esm to be build.

  == What happens ==
  # Format: , Error  [(ignored)]
  #
  annexc.out, Error 1 (ignored)
  bug22.out, Error 1
  run-conformtest.out, Error 1 (ignored)
  tst-mutex7.out, Error 1
  tst-mutex7a.out, Error 1
  tst-mutexpi7.out, Error 1
  tst-mutexpi7a.out, Error 1
  tst-once2.out, Error 1
  tst-setlocale3.out, Error 1
  ***
  Encountered regressions that don't match expected failures 
(debian/testsuite-checking/expected-results-x86_64-linux-gnu-libc):
  bug22.out, Error 1
  tst-mutex7.out, Error 1
  tst-mutex7a.out, Error 1
  tst-mutexpi7.out, Error 1
  tst-mutexpi7a.out, Error 1
  tst-once2.out, Error 1
  tst-setlocale3.out, Error 1
  TEST bug22.out:
  ret = -1
  ret = -1
  ret = -1
  ret = -1
  TEST tst-mutex7.out:
  creating thread 63 failed
  TEST tst-mutex7a.out:
  creating thread 63 failed
  TEST tst-mutexpi7.out:
  creating thread 63 failed
  TEST tst-mutexpi7a.out:
  creating thread 63 failed
  TEST tst-once2.out:
  creation of thread 63 failed
  TEST tst-setlocale3.out:
  malloc failure
  Encountered progressions that don't match expected failures:
  tst-backtrace6.out, Error 1
  tst-cpuclock2.out, Error 1
  tst-cputimer1.out, Error 1
  tst-mqueue5.out, Error 1
  tst-timer.out, Error 139
  tst-waitid.out, Error 1
  tst-writev.out, Error 1
  make: *** [/<>/stamp-dir/check_libc] Error 1

  == Fix commit/related ==
  https://sourceware.org/bugzilla/show_bug.cgi?id=19648
  
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=36234ceda21820d2f874067553e7faae763a40cf

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


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


[Touch-packages] [Bug 2063328] Re: FTBFS in eglibc

2024-04-24 Thread Leonidas S. Barbosa
** Changed in: eglibc (Ubuntu)
   Importance: Undecided => High

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

Title:
  FTBFS in eglibc

Status in eglibc package in Ubuntu:
  In Progress

Bug description:
  == Summary ==

  A FTBFS occurs in eglibc that affects trusty-esm to be build.

  == What happens ==
  # Format: , Error  [(ignored)]
  #
  annexc.out, Error 1 (ignored)
  bug22.out, Error 1
  run-conformtest.out, Error 1 (ignored)
  tst-mutex7.out, Error 1
  tst-mutex7a.out, Error 1
  tst-mutexpi7.out, Error 1
  tst-mutexpi7a.out, Error 1
  tst-once2.out, Error 1
  tst-setlocale3.out, Error 1
  ***
  Encountered regressions that don't match expected failures 
(debian/testsuite-checking/expected-results-x86_64-linux-gnu-libc):
  bug22.out, Error 1
  tst-mutex7.out, Error 1
  tst-mutex7a.out, Error 1
  tst-mutexpi7.out, Error 1
  tst-mutexpi7a.out, Error 1
  tst-once2.out, Error 1
  tst-setlocale3.out, Error 1
  TEST bug22.out:
  ret = -1
  ret = -1
  ret = -1
  ret = -1
  TEST tst-mutex7.out:
  creating thread 63 failed
  TEST tst-mutex7a.out:
  creating thread 63 failed
  TEST tst-mutexpi7.out:
  creating thread 63 failed
  TEST tst-mutexpi7a.out:
  creating thread 63 failed
  TEST tst-once2.out:
  creation of thread 63 failed
  TEST tst-setlocale3.out:
  malloc failure
  Encountered progressions that don't match expected failures:
  tst-backtrace6.out, Error 1
  tst-cpuclock2.out, Error 1
  tst-cputimer1.out, Error 1
  tst-mqueue5.out, Error 1
  tst-timer.out, Error 139
  tst-waitid.out, Error 1
  tst-writev.out, Error 1
  make: *** [/<>/stamp-dir/check_libc] Error 1

  == Fix commit/related ==
  https://sourceware.org/bugzilla/show_bug.cgi?id=19648
  
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=36234ceda21820d2f874067553e7faae763a40cf

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


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


[Touch-packages] [Bug 2063328] [NEW] FTBFS in eglibc

2024-04-24 Thread Leonidas S. Barbosa
Public bug reported:

== Summary ==

A FTBFS occurs in eglibc that affects trusty-esm to be build.

== What happens ==
# Format: , Error  [(ignored)]
#
annexc.out, Error 1 (ignored)
bug22.out, Error 1
run-conformtest.out, Error 1 (ignored)
tst-mutex7.out, Error 1
tst-mutex7a.out, Error 1
tst-mutexpi7.out, Error 1
tst-mutexpi7a.out, Error 1
tst-once2.out, Error 1
tst-setlocale3.out, Error 1
***
Encountered regressions that don't match expected failures 
(debian/testsuite-checking/expected-results-x86_64-linux-gnu-libc):
bug22.out, Error 1
tst-mutex7.out, Error 1
tst-mutex7a.out, Error 1
tst-mutexpi7.out, Error 1
tst-mutexpi7a.out, Error 1
tst-once2.out, Error 1
tst-setlocale3.out, Error 1
TEST bug22.out:
ret = -1
ret = -1
ret = -1
ret = -1
TEST tst-mutex7.out:
creating thread 63 failed
TEST tst-mutex7a.out:
creating thread 63 failed
TEST tst-mutexpi7.out:
creating thread 63 failed
TEST tst-mutexpi7a.out:
creating thread 63 failed
TEST tst-once2.out:
creation of thread 63 failed
TEST tst-setlocale3.out:
malloc failure
Encountered progressions that don't match expected failures:
tst-backtrace6.out, Error 1
tst-cpuclock2.out, Error 1
tst-cputimer1.out, Error 1
tst-mqueue5.out, Error 1
tst-timer.out, Error 139
tst-waitid.out, Error 1
tst-writev.out, Error 1
make: *** [/<>/stamp-dir/check_libc] Error 1

== Fix commit/related ==
https://sourceware.org/bugzilla/show_bug.cgi?id=19648
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=36234ceda21820d2f874067553e7faae763a40cf

** Affects: eglibc (Ubuntu)
 Importance: Undecided
 Assignee: Leonidas S. Barbosa (leosilvab)
 Status: In Progress

** Package changed: google-osconfig-agent (Ubuntu) => eglibc (Ubuntu)

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

** Changed in: eglibc (Ubuntu)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

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

Title:
  FTBFS in eglibc

Status in eglibc package in Ubuntu:
  In Progress

Bug description:
  == Summary ==

  A FTBFS occurs in eglibc that affects trusty-esm to be build.

  == What happens ==
  # Format: , Error  [(ignored)]
  #
  annexc.out, Error 1 (ignored)
  bug22.out, Error 1
  run-conformtest.out, Error 1 (ignored)
  tst-mutex7.out, Error 1
  tst-mutex7a.out, Error 1
  tst-mutexpi7.out, Error 1
  tst-mutexpi7a.out, Error 1
  tst-once2.out, Error 1
  tst-setlocale3.out, Error 1
  ***
  Encountered regressions that don't match expected failures 
(debian/testsuite-checking/expected-results-x86_64-linux-gnu-libc):
  bug22.out, Error 1
  tst-mutex7.out, Error 1
  tst-mutex7a.out, Error 1
  tst-mutexpi7.out, Error 1
  tst-mutexpi7a.out, Error 1
  tst-once2.out, Error 1
  tst-setlocale3.out, Error 1
  TEST bug22.out:
  ret = -1
  ret = -1
  ret = -1
  ret = -1
  TEST tst-mutex7.out:
  creating thread 63 failed
  TEST tst-mutex7a.out:
  creating thread 63 failed
  TEST tst-mutexpi7.out:
  creating thread 63 failed
  TEST tst-mutexpi7a.out:
  creating thread 63 failed
  TEST tst-once2.out:
  creation of thread 63 failed
  TEST tst-setlocale3.out:
  malloc failure
  Encountered progressions that don't match expected failures:
  tst-backtrace6.out, Error 1
  tst-cpuclock2.out, Error 1
  tst-cputimer1.out, Error 1
  tst-mqueue5.out, Error 1
  tst-timer.out, Error 139
  tst-waitid.out, Error 1
  tst-writev.out, Error 1
  make: *** [/<>/stamp-dir/check_libc] Error 1

  == Fix commit/related ==
  https://sourceware.org/bugzilla/show_bug.cgi?id=19648
  
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=36234ceda21820d2f874067553e7faae763a40cf

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


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


[Touch-packages] [Bug 2037340] Re: Four Screens

2023-09-27 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  Four Screens

Status in xorg package in Ubuntu:
  New

Bug description:
  I apologize for any grammar issues, but I can barely see what I am
  typing. Essentially, when I installed Ubuntu, I had to do so in safe
  graphics mode, as the screen would otherwise split itself into four
  different displays that had small amounts of resolution and are rather
  pale. I managed to install it, but once that happend, and it
  restarted, it went back to being four screens. I am not sure what to
  do, as I cannot really read any lines of code. Thank you for your
  help. I am using an iMac a1311, with an HDD and installed  from a
  flashed usb.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 20:33:11 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 
4670] [1002:9488] (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. RV730/M96-XT [Mobility Radeon HD 4670] [106b:00b6]
  InstallationDate: Installed on 2023-09-24 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Apple Inc. iMac10,1
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=be40ad74-149a-443c-99b3-2dbae10973a3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2019
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 215.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F2268CC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2268CC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvr215.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268CC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268CC8:skuSystemSKU#:
  dmi.product.family: Mac
  dmi.product.name: iMac10,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Touch-packages] [Bug 2027679] Re: package iptables 1.8.4-3ubuntu2.1 failed to install/upgrade: installed iptables package post-installation script subprocess returned error exit status 2

2023-07-13 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package iptables 1.8.4-3ubuntu2.1 failed to install/upgrade: installed
  iptables package post-installation script subprocess returned error
  exit status 2

Status in iptables package in Ubuntu:
  New

Bug description:
  The system keeps sending a pop up display saying the System detected a
  problem

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: iptables 1.8.4-3ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-73.80~20.04.1-generic 5.15.98
  Uname: Linux 5.15.0-73-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  AptOrdering:
   accountsservice:amd64: Install
   libaccountsservice0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jul  9 21:15:09 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  DpkgHistoryLog:
   Start-Date: 2023-07-09  21:15:08
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: accountsservice:amd64 (0.6.55-0ubuntu12~20.04.5, 
0.6.55-0ubuntu12~20.04.6), libaccountsservice0:amd64 (0.6.55-0ubuntu12~20.04.5, 
0.6.55-0ubuntu12~20.04.6)
  DuplicateSignature:
   package:iptables:1.8.4-3ubuntu2.1
   Setting up google-chrome-stable (114.0.5735.90-1) ...
   update-alternatives: error: cannot stat file '/usr/bin/nodejs': Too many 
levels of symbolic links
   dpkg: error processing package google-chrome-stable (--configure):
installed google-chrome-stable package post-installation script subprocess 
returned error exit status 2
  ErrorMessage: installed iptables package post-installation script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2023-03-09 (125 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: iptables
  Title: package iptables 1.8.4-3ubuntu2.1 failed to install/upgrade: installed 
iptables package post-installation script subprocess returned error exit status 
2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1998785] Re: Remove Trustcor certificates

2022-12-05 Thread Leonidas S. Barbosa
** Changed in: ca-certificates (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: ca-certificates (Ubuntu Xenial)
   Status: New => In Progress

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

Title:
  Remove Trustcor certificates

Status in ca-certificates package in Ubuntu:
  In Progress
Status in ca-certificates source package in Trusty:
  In Progress
Status in ca-certificates source package in Xenial:
  In Progress
Status in ca-certificates source package in Bionic:
  Fix Released
Status in ca-certificates source package in Focal:
  Fix Released
Status in ca-certificates source package in Jammy:
  Fix Released
Status in ca-certificates source package in Kinetic:
  Fix Released
Status in ca-certificates source package in Lunar:
  In Progress

Bug description:
  The ca-certificates packages should remove the Trustcor certificates.

  Background:
  
https://www.washingtonpost.com/technology/2022/11/30/trustcor-internet-authority-mozilla/

  Upstream decision:
  
https://groups.google.com/a/mozilla.org/g/dev-security-policy/c/oxX69KFvsm4/m/yLohoVqtCgAJ

  Upstream commit:
  
https://hg.mozilla.org/projects/nss/rev/a871902c05907db3150ac8b7f6a80dd01b5d38c9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1998785/+subscriptions


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


[Touch-packages] [Bug 1998785] Re: Remove Trustcor certificates

2022-12-05 Thread Leonidas S. Barbosa
** Changed in: ca-certificates (Ubuntu Trusty)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

** Changed in: ca-certificates (Ubuntu Xenial)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

** Changed in: ca-certificates (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: ca-certificates (Ubuntu Xenial)
   Importance: Undecided => High

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

Title:
  Remove Trustcor certificates

Status in ca-certificates package in Ubuntu:
  In Progress
Status in ca-certificates source package in Trusty:
  New
Status in ca-certificates source package in Xenial:
  New
Status in ca-certificates source package in Bionic:
  In Progress
Status in ca-certificates source package in Focal:
  In Progress
Status in ca-certificates source package in Jammy:
  In Progress
Status in ca-certificates source package in Kinetic:
  In Progress
Status in ca-certificates source package in Lunar:
  In Progress

Bug description:
  The ca-certificates packages should remove the Trustcor certificates.

  Background:
  
https://www.washingtonpost.com/technology/2022/11/30/trustcor-internet-authority-mozilla/

  Upstream decision:
  
https://groups.google.com/a/mozilla.org/g/dev-security-policy/c/oxX69KFvsm4/m/yLohoVqtCgAJ

  Upstream commit:
  
https://hg.mozilla.org/projects/nss/rev/a871902c05907db3150ac8b7f6a80dd01b5d38c9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1998785/+subscriptions


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


[Touch-packages] [Bug 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic

2022-09-16 Thread Leonidas S. Barbosa
Cool!

Thanks for testing :)

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

Title:
  "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu
  Bionic

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on
  Ubuntu Bionic but "goo/gmem.h" still has the statement `#include
  "GooCheckedOps.h"`. As a result, a compile error will happen when
  compiling code that uses poppler:

  /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h:
  No such file or directory

  I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the
  previous version) installed. I confirmed that "goo/gmem.h" doesn't
  have the `#include "GooCheckedOps.h"` statement.

  I found this issue when I was compiling gdal on my Docker container.
  The Docker container was installed the problematic version
  0.62.0-2ubuntu2.13 and I ran into the "No such file or directory"
  error.

  I compiled on both Amd64 and AArch64 and I ran into the same error on
  both platforms.

  By reading the diff between 2.12 and 2.13
  
(https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz),
  the patch looks quite right. But when I examined the contents of the
  built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h".

  Kind of weird, because the problem seems to be caused by applying
  "CVE-2022-38784-pre.patch" in half: the first part that creates
  "goo/GooCheckedOps.h" was not applied during the build process and the
  second part that modifies "goo/gmem.h" was applied.

  Any thoughts? Ideas?

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


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


[Touch-packages] [Bug 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic

2022-09-14 Thread Leonidas S. Barbosa
Ok, i did find the issue  -Thanks Security folks - and I'm issuing a
security regression update.

Thanks.

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

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

Title:
  "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu
  Bionic

Status in poppler package in Ubuntu:
  In Progress

Bug description:
  Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on
  Ubuntu Bionic but "goo/gmem.h" still has the statement `#include
  "GooCheckedOps.h"`. As a result, a compile error will happen when
  compiling code that uses poppler:

  /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h:
  No such file or directory

  I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the
  previous version) installed. I confirmed that "goo/gmem.h" doesn't
  have the `#include "GooCheckedOps.h"` statement.

  I found this issue when I was compiling gdal on my Docker container.
  The Docker container was installed the problematic version
  0.62.0-2ubuntu2.13 and I ran into the "No such file or directory"
  error.

  I compiled on both Amd64 and AArch64 and I ran into the same error on
  both platforms.

  By reading the diff between 2.12 and 2.13
  
(https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz),
  the patch looks quite right. But when I examined the contents of the
  built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h".

  Kind of weird, because the problem seems to be caused by applying
  "CVE-2022-38784-pre.patch" in half: the first part that creates
  "goo/GooCheckedOps.h" was not applied during the build process and the
  second part that modifies "goo/gmem.h" was applied.

  Any thoughts? Ideas?

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


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


[Touch-packages] [Bug 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic

2022-09-14 Thread Leonidas S. Barbosa
Hi,

Could you please provide with any steps in how to reproduce it?

Thanks!

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

Title:
  "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu
  Bionic

Status in poppler package in Ubuntu:
  New

Bug description:
  Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on
  Ubuntu Bionic but "goo/gmem.h" still has the statement `#include
  "GooCheckedOps.h"`. As a result, a compile error will happen when
  compiling code that uses poppler:

  /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h:
  No such file or directory

  I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the
  previous version) installed. I confirmed that "goo/gmem.h" doesn't
  have the `#include "GooCheckedOps.h"` statement.

  I found this issue when I was compiling gdal on my Docker container.
  The Docker container was installed the problematic version
  0.62.0-2ubuntu2.13 and I ran into the "No such file or directory"
  error.

  I compiled on both Amd64 and AArch64 and I ran into the same error on
  both platforms.

  By reading the diff between 2.12 and 2.13
  
(https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz),
  the patch looks quite right. But when I examined the contents of the
  built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h".

  Kind of weird, because the problem seems to be caused by applying
  "CVE-2022-38784-pre.patch" in half: the first part that creates
  "goo/GooCheckedOps.h" was not applied during the build process and the
  second part that modifies "goo/gmem.h" was applied.

  Any thoughts? Ideas?

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


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


[Touch-packages] [Bug 1965791] Re: Update tzdata to version 2022a

2022-03-23 Thread Leonidas S. Barbosa
Thanks Brian, trusty/xenial esm sponsored/building :)

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

Title:
  Update tzdata to version 2022a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Impish:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Released

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Asia/Gaza

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Asia/Gaza | grep 'Mar.*2022'

  With the version of the package from -proposed this will show Mar 26
  not Mar 25.

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); 
print(str(tz.utcoffset(datetime(2022, 3, 26'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

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


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


[Touch-packages] [Bug 1962332] Re: xenial systemd fails to start if cgroup2 is mounted

2022-03-15 Thread Leonidas S. Barbosa
Just for clarification, and doc, this approach was took as since it
needs to go the archive, it need to be handled as an SRU bye the SRU
team.

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

Title:
  xenial systemd fails to start if cgroup2 is mounted

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

Bug description:
  [impact]

  now that jammy has moved to using unified cgroup2, containers started
  on jammy must also use unified cgroup2 (since the cgroup subsystems
  can only be mounted as v1 or v2 throughout the entire system,
  including inside containers).

  However, the systemd in xenial does not include support for cgroup2,
  and doesn't recognize its magic (added in upstream commit
  099619957a0), so it fails to start completely.

  [workaround]
  On Jammy host edit default kernel command line to include

  systemd.unified_cgroup_hierarchy=false

  update your bootloader configuration; and reboot

  then hybrid cgroups will be on the host, and one can launch xenial
  container then.

  
  [test case]

  create a jammy system, that has unified cgroup2 mounted. Then:

  $ lxc launch ubuntu:xenial test-x
  ...
  $ lxc shell test-x

  (inside xenial container):
  $ mv /sbin/init /sbin/init.old
  $ cat > /sbin/init <+a q
  Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted
  [!!] Failed to mount API filesystems, freezing.
  Freezing execution.

  [regression potential]

  any regression would likely break xenial containers from starting at
  all, or cause cgroup-related problems with systemd starting and/or
  managing services.

  [scope]

  this is needed only for xenial. However, as xenial is out of standard
  support, this would need to be an exception.

  this is fixed upstream with commit 099619957a0 (and possibly others -
  needs closer investigation and testing) which is first included in
  v230, so this is fixed already in b and later.

  this is not needed - by default - for trusty because upstart is used
  there; however, I think it's possible to change trusty over to use
  systemd instead of upstart. But since trusty is out of standard
  support, and it doesn't fail by default, it doesn't seem like it
  should be fixed.

  [other info]

  An alternative appears to be to change the host system back to using
  the 'hybrid' cgroup, however that obviously is awful and would remove
  the benefits of cgroup v2 from the host system, and force all
  containers on the host system to also use the 'hybrid' cgroup.

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


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


[Touch-packages] [Bug 1962332] Re: xenial systemd fails to start if cgroup2 is mounted

2022-03-15 Thread Leonidas S. Barbosa
I see, I do agree, sorry for noise. I did remove the one from -esm ppas
and here is the debdiff. Could someone please sponsor/follow with it?
Thanks!

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

Title:
  xenial systemd fails to start if cgroup2 is mounted

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

Bug description:
  [impact]

  now that jammy has moved to using unified cgroup2, containers started
  on jammy must also use unified cgroup2 (since the cgroup subsystems
  can only be mounted as v1 or v2 throughout the entire system,
  including inside containers).

  However, the systemd in xenial does not include support for cgroup2,
  and doesn't recognize its magic (added in upstream commit
  099619957a0), so it fails to start completely.

  [workaround]
  On Jammy host edit default kernel command line to include

  systemd.unified_cgroup_hierarchy=false

  update your bootloader configuration; and reboot

  then hybrid cgroups will be on the host, and one can launch xenial
  container then.

  
  [test case]

  create a jammy system, that has unified cgroup2 mounted. Then:

  $ lxc launch ubuntu:xenial test-x
  ...
  $ lxc shell test-x

  (inside xenial container):
  $ mv /sbin/init /sbin/init.old
  $ cat > /sbin/init <+a q
  Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted
  [!!] Failed to mount API filesystems, freezing.
  Freezing execution.

  [regression potential]

  any regression would likely break xenial containers from starting at
  all, or cause cgroup-related problems with systemd starting and/or
  managing services.

  [scope]

  this is needed only for xenial. However, as xenial is out of standard
  support, this would need to be an exception.

  this is fixed upstream with commit 099619957a0 (and possibly others -
  needs closer investigation and testing) which is first included in
  v230, so this is fixed already in b and later.

  this is not needed - by default - for trusty because upstart is used
  there; however, I think it's possible to change trusty over to use
  systemd instead of upstart. But since trusty is out of standard
  support, and it doesn't fail by default, it doesn't seem like it
  should be fixed.

  [other info]

  An alternative appears to be to change the host system back to using
  the 'hybrid' cgroup, however that obviously is awful and would remove
  the benefits of cgroup v2 from the host system, and force all
  containers on the host system to also use the 'hybrid' cgroup.

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


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


[Touch-packages] [Bug 1962332] Re: xenial systemd fails to start if cgroup2 is mounted

2022-03-15 Thread Leonidas S. Barbosa
** Patch added: "systemd_229-4ubuntu22.32.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962332/+attachment/5569222/+files/systemd_229-4ubuntu22.32.debdiff

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

Title:
  xenial systemd fails to start if cgroup2 is mounted

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

Bug description:
  [impact]

  now that jammy has moved to using unified cgroup2, containers started
  on jammy must also use unified cgroup2 (since the cgroup subsystems
  can only be mounted as v1 or v2 throughout the entire system,
  including inside containers).

  However, the systemd in xenial does not include support for cgroup2,
  and doesn't recognize its magic (added in upstream commit
  099619957a0), so it fails to start completely.

  [workaround]
  On Jammy host edit default kernel command line to include

  systemd.unified_cgroup_hierarchy=false

  update your bootloader configuration; and reboot

  then hybrid cgroups will be on the host, and one can launch xenial
  container then.

  
  [test case]

  create a jammy system, that has unified cgroup2 mounted. Then:

  $ lxc launch ubuntu:xenial test-x
  ...
  $ lxc shell test-x

  (inside xenial container):
  $ mv /sbin/init /sbin/init.old
  $ cat > /sbin/init <+a q
  Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted
  [!!] Failed to mount API filesystems, freezing.
  Freezing execution.

  [regression potential]

  any regression would likely break xenial containers from starting at
  all, or cause cgroup-related problems with systemd starting and/or
  managing services.

  [scope]

  this is needed only for xenial. However, as xenial is out of standard
  support, this would need to be an exception.

  this is fixed upstream with commit 099619957a0 (and possibly others -
  needs closer investigation and testing) which is first included in
  v230, so this is fixed already in b and later.

  this is not needed - by default - for trusty because upstart is used
  there; however, I think it's possible to change trusty over to use
  systemd instead of upstart. But since trusty is out of standard
  support, and it doesn't fail by default, it doesn't seem like it
  should be fixed.

  [other info]

  An alternative appears to be to change the host system back to using
  the 'hybrid' cgroup, however that obviously is awful and would remove
  the benefits of cgroup v2 from the host system, and force all
  containers on the host system to also use the 'hybrid' cgroup.

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


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


[Touch-packages] [Bug 1962332] Re: xenial systemd fails to start if cgroup2 is mounted

2022-03-14 Thread Leonidas S. Barbosa
I have update ongoing on esm-infa-staging for it, but without consider
these issues Dimitri pointed, so, with the clean patch pointed here. It
would be nice if any of you folks could give a test on it. Also adding
other folks from security to this discussion with better background.

Also, tips on how to test it would be nice. I was trying lxc image
export with a systemd updated and a non systemd update xenial, but
hadn't any luck as both work as the same if you lxc import into a jammy
from .tar.gz image exported.

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

Title:
  xenial systemd fails to start if cgroup2 is mounted

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

Bug description:
  [impact]

  now that jammy has moved to using unified cgroup2, containers started
  on jammy must also use unified cgroup2 (since the cgroup subsystems
  can only be mounted as v1 or v2 throughout the entire system,
  including inside containers).

  However, the systemd in xenial does not include support for cgroup2,
  and doesn't recognize its magic (added in upstream commit
  099619957a0), so it fails to start completely.

  [workaround]
  On Jammy host edit default kernel command line to include

  systemd.unified_cgroup_hierarchy=false

  update your bootloader configuration; and reboot

  then hybrid cgroups will be on the host, and one can launch xenial
  container then.

  
  [test case]

  create a jammy system, that has unified cgroup2 mounted. Then:

  $ lxc launch ubuntu:xenial test-x
  ...
  $ lxc shell test-x

  (inside xenial container):
  $ mv /sbin/init /sbin/init.old
  $ cat > /sbin/init <+a q
  Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted
  [!!] Failed to mount API filesystems, freezing.
  Freezing execution.

  [regression potential]

  any regression would likely break xenial containers from starting at
  all, or cause cgroup-related problems with systemd starting and/or
  managing services.

  [scope]

  this is needed only for xenial. However, as xenial is out of standard
  support, this would need to be an exception.

  this is fixed upstream with commit 099619957a0 (and possibly others -
  needs closer investigation and testing) which is first included in
  v230, so this is fixed already in b and later.

  this is not needed - by default - for trusty because upstart is used
  there; however, I think it's possible to change trusty over to use
  systemd instead of upstart. But since trusty is out of standard
  support, and it doesn't fail by default, it doesn't seem like it
  should be fixed.

  [other info]

  An alternative appears to be to change the host system back to using
  the 'hybrid' cgroup, however that obviously is awful and would remove
  the benefits of cgroup v2 from the host system, and force all
  containers on the host system to also use the 'hybrid' cgroup.

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


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


[Touch-packages] [Bug 1963903] Re: expat relax fix for CVE-2022-25236 and possible regressions

2022-03-07 Thread Leonidas S. Barbosa
https://github.com/exxamalte/python-aio-georss-client/issues/29

** Bug watch added: github.com/exxamalte/python-aio-georss-client/issues #29
   https://github.com/exxamalte/python-aio-georss-client/issues/29

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

Title:
  expat relax fix for CVE-2022-25236 and possible regressions

Status in expat package in Ubuntu:
  In Progress

Bug description:
  Sebastian Pipping report to us that these additional fixes are
  required to fix properly CVE-2022-25236 in regard to RCF 3986 URI
  characters and possibly regressions as the merge request points.

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


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


[Touch-packages] [Bug 1963903] Re: expat relax fix for CVE-2022-25236 and possible regressions

2022-03-07 Thread Leonidas S. Barbosa
https://github.com/libexpat/libexpat/pull/577

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

Title:
  expat relax fix for CVE-2022-25236 and possible regressions

Status in expat package in Ubuntu:
  In Progress

Bug description:
  Sebastian Pipping report to us that these additional fixes are
  required to fix properly CVE-2022-25236 in regard to RCF 3986 URI
  characters and possibly regressions as the merge request points.

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


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


[Touch-packages] [Bug 1963903] [NEW] expat relax fix for CVE-2022-25236 and possible regressions

2022-03-07 Thread Leonidas S. Barbosa
Public bug reported:

Sebastian Pipping report to us that these additional fixes are required
to fix properly CVE-2022-25236 in regard to RCF 3986 URI characters and
possibly regressions as the merge request points.

** Affects: expat (Ubuntu)
 Importance: Undecided
 Assignee: Leonidas S. Barbosa (leosilvab)
 Status: In Progress

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

Title:
  expat relax fix for CVE-2022-25236 and possible regressions

Status in expat package in Ubuntu:
  In Progress

Bug description:
  Sebastian Pipping report to us that these additional fixes are
  required to fix properly CVE-2022-25236 in regard to RCF 3986 URI
  characters and possibly regressions as the merge request points.

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


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


[Touch-packages] [Bug 1955533] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-02-07 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I am not able to install anything qith the sudo apt

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  AptOrdering:
   libcurl4:amd64: Install
   curl:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Dec 22 12:27:58 2021
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-12-21 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1955678] Re: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: el subproceso instalado paquete sudo script pre-removal devolvió el código de salida de error 1

2022-02-07 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: el
  subproceso instalado paquete sudo script pre-removal devolvió el
  código de salida de error 1

Status in sudo package in Ubuntu:
  New

Bug description:
  the update or aplication do not install

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: sudo 1.8.31-1ubuntu1.2
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.21
  AptOrdering:
   sudo:amd64: Remove
   sudo-ldap:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Dec 13 12:34:44 2021
  ErrorMessage: el subproceso instalado paquete sudo script pre-removal 
devolvió el código de salida de error 1
  InstallationDate: Installed on 2021-12-01 (22 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.1
   apt  2.0.6
  SourcePackage: sudo
  Title: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: el 
subproceso instalado paquete sudo script pre-removal devolvió el código de 
salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers análisis OK
   /etc/sudoers.d/README análisis OK

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


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


[Touch-packages] [Bug 1956268] Re: package systemd 248.3-1ubuntu8 failed to install/upgrade: o subprocesso instalado, do pacote systemd, o script post-installation retornou erro do status de saída 127

2022-02-07 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package systemd 248.3-1ubuntu8 failed to install/upgrade: o
  subprocesso instalado, do pacote systemd, o script post-installation
  retornou erro do status de saída 127

Status in systemd package in Ubuntu:
  New

Bug description:
  nunca completa as atualizações

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: systemd 248.3-1ubuntu8
  ProcVersionSignature: Ubuntu 5.11.0-41.45-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Jan  3 22:27:50 2022
  ErrorMessage: o subprocesso instalado, do pacote systemd, o script 
post-installation retornou erro do status de saída 127
  InstallationDate: Installed on 2019-08-17 (870 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5659 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7580
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic 
root=UUID=dadf5e69-ec04-414c-bf27-44bc7f2b4936 ro mem_sleep_default=deep 
nvidia-drm.modeset=1 quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.2.4ubuntu0.1
  SourcePackage: systemd
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  Title: package systemd 248.3-1ubuntu8 failed to install/upgrade: o 
subprocesso instalado, do pacote systemd, o script post-installation retornou 
erro do status de saída 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/24/2019
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0W83FH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd03/24/2019:br1.6:svnDellInc.:pnInspiron7580:pvr:sku08A6:rvnDellInc.:rn0W83FH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7580
  dmi.product.sku: 08A6
  dmi.sys.vendor: Dell Inc.

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


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


[Touch-packages] [Bug 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable

2022-01-09 Thread Leonidas S. Barbosa
Sure thing, working on it, till Tuesday it will be done as I need to
test it and so for all releases.

Thanks

** Changed in: exiv2 (Ubuntu)
 Assignee: Ubuntu Security Team (ubuntu-security) => Leonidas S. Barbosa 
(leosilvab)

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

Title:
  Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening
  images exported by darktable

Status in Gwenview:
  Fix Released
Status in exiv2 package in Ubuntu:
  Confirmed
Status in gwenview package in Ubuntu:
  Confirmed

Bug description:
  Since the recent security update of exiv2, Gwenview crashes when
  trying to open image files that got exported by darktable.

  Steps to reproduce:

  * Make a test installation of Kubuntu 21.04 in VirtualBox
  * Install all updates
  * Install darktable
  * Copy one of the images in /usr/share/wallpapers (or any other image) to 
your home directory and open it with darktable
  * Within darktable, export a copy of the image (no need to do any actual 
modifications)
  * Try to open that copy with Gwenview. Gwenview will crash.

  I'm attaching a crash report hinting that this is related to exiv2.

  Temporary workaround:
  If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so 
it seems the crash is related to changes in 0.27.3-3ubuntu1.5.

  I don't know if the underlying cause is actually some bug in exiv2,
  Gwenview or darktable.

  Kind regards, Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libexiv2-27 0.27.3-3ubuntu1.5
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug 26 15:16:47 2021
  InstallationDate: Installed on 2021-08-26 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: exiv2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1948575] Re: package linux-firmware 1.187.19 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

2021-11-02 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package linux-firmware 1.187.19 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  verly long and old maintained authentication keys in trusted software
  repository of ubuntu software updater.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.19
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arun   1871 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sun Oct 24 15:12:21 2021
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-09-08 (46 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 80T7
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-34-generic 
root=UUID=99f31926-b2b0-4b03-a8ba-a15f3b4a9fcd ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.187.19 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 1GCN15WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: 00RD15IPG076
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15IBR
  dmi.ec.firmware.release: 1.15
  dmi.modalias: 
dmi:bvnLENOVO:bvr1GCN15WW:bd04/07/2016:br1.15:efr1.15:svnLENOVO:pn80T7:pvrLenovoideapad110-15IBR:skuLENOVO_MT_80T7_BU_idea_FM_Lenovoideapad110-15IBR:rvnLENOVO:rn00RD15IPG076:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad110-15IBR:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80T7
  dmi.product.sku: LENOVO_MT_80T7_BU_idea_FM_Lenovo ideapad 110-15IBR
  dmi.product.version: Lenovo ideapad 110-15IBR
  dmi.sys.vendor: LENOVO

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


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


[Touch-packages] [Bug 1949233] Re: Baloo File Extractor Closed Unexpectedly

2021-11-02 Thread Leonidas S. Barbosa
** Attachment removed: "acpidump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1949233/+attachment/5537070/+files/acpidump.txt

** Information type changed from Private Security to Public

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

Title:
  Baloo File Extractor Closed Unexpectedly

Status in xorg package in Ubuntu:
  New

Bug description:
  Ballo File Extractor Closed Unexpectedly
  please report this error to help improve this software.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143
  Uname: Linux 5.4.0-89-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Oct 29 15:26:00 2021
  DistUpgraded: 2021-01-08 14:56:49,798 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Wrestler [Radeon HD 6310] [17aa:397f]
  InstallationDate: Installed on 2020-12-18 (315 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 2181
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic 
root=UUID=c44a1ac5-9dee-4bf8-a246-6303f68e5c24 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2021-01-08 (294 days ago)
  dmi.bios.date: 10/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6CCN93WW(V8.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo G585
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G585
  dmi.modalias: 
dmi:bvnLENOVO:bvr6CCN93WW(V8.05):bd10/02/2012:svnLENOVO:pn2181:pvrLenovoG585:rvnLENOVO:rnLenovoG585:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG585:
  dmi.product.family: IDEAPAD
  dmi.product.name: 2181
  dmi.product.sku: LENOVO_MT_2181
  dmi.product.version: Lenovo G585
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sun Oct 17 09:09:38 2021
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.11-1ubuntu1~20.04.2

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


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


[Touch-packages] [Bug 1949187] Re: package libgstreamer-plugins-base1.0-0:i386 1.16.2-4ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before

2021-11-02 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package libgstreamer-plugins-base1.0-0:i386 1.16.2-4ubuntu0.1 failed
  to install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in gst-plugins-base1.0 package in Ubuntu:
  New

Bug description:
  sometime system freezes

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libgstreamer-plugins-base1.0-0:i386 1.16.2-4ubuntu0.1
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  AptOrdering:
   systemd-timesyncd:amd64: Configure
   systemd:amd64: Configure
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct 29 16:00:03 2021
  DuplicateSignature:
   package:libgstreamer-plugins-base1.0-0:i386:1.16.2-4ubuntu0.1
   Setting up libgstreamer1.0-0:i386 (1.16.2-2) ...
   Setcap worked! gst-ptp-helper is not suid!
   dpkg: error processing package libgstreamer-plugins-base1.0-0:i386 
(--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 2021-10-28 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: gst-plugins-base1.0
  Title: package libgstreamer-plugins-base1.0-0:i386 1.16.2-4ubuntu0.1 failed 
to install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1949187/+subscriptions


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


[Touch-packages] [Bug 1942357] Re: Regression in openssl 1.0.1f for trusty/esm after last update

2021-09-01 Thread Leonidas S. Barbosa
https://ubuntu.com/security/notices/USN-5051-4

** Changed in: openssl (Ubuntu Trusty)
   Status: Confirmed => Fix Released

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

Title:
  Regression in openssl 1.0.1f for trusty/esm after last update

Status in openssl package in Ubuntu:
  In Progress
Status in openssl source package in Trusty:
  Fix Released

Bug description:
  A security regression was reported by Johannes Wegener that is causing
  a regression in the last openssl1.0.1f in trusty/esm.

  [How to reproduce]
  1. Install Openssl/libssl1.0.0 Version 1.0.1f-1ubuntu2.27+esm3 on
  ubuntu 14.04
  2. openssl s_client -connect wikipedia.org:443 2>&1 < /dev/null | sed -n 
'/-BEGIN/,/-END/p' > wikipedia.pem 
  3. openssl x509 -noout -ocsp_uri -in wikipedia.pem 

  Expected it prints: http://r3.o.lencr.org
  Issue: it's not printing anything.

  Thanks Johannes for report this issue.

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


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


[Touch-packages] [Bug 1942357] [NEW] Regression in openssl 1.0.1f for trusty/esm after last update

2021-09-01 Thread Leonidas S. Barbosa
Public bug reported:

A security regression was reported by Johannes Wegener that is causing a
regression in the last openssl1.0.1f in trusty/esm.

[How to reproduce]
1. Install Openssl/libssl1.0.0 Version 1.0.1f-1ubuntu2.27+esm3 on
ubuntu 14.04
2. openssl s_client -connect wikipedia.org:443 2>&1 < /dev/null | sed -n 
'/-BEGIN/,/-END/p' > wikipedia.pem 
3. openssl x509 -noout -ocsp_uri -in wikipedia.pem 

Expected it prints: http://r3.o.lencr.org
Issue: it's not printing anything.

Thanks Johannes for report this issue.

** Affects: openssl (Ubuntu)
 Importance: Undecided
     Assignee: Leonidas S. Barbosa (leosilvab)
 Status: In Progress

** Affects: openssl (Ubuntu Trusty)
 Importance: Undecided
 Status: Confirmed

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

** Changed in: openssl (Ubuntu)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

** Also affects: openssl (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

Title:
  Regression in openssl 1.0.1f for trusty/esm after last update

Status in openssl package in Ubuntu:
  In Progress
Status in openssl source package in Trusty:
  Confirmed

Bug description:
  A security regression was reported by Johannes Wegener that is causing
  a regression in the last openssl1.0.1f in trusty/esm.

  [How to reproduce]
  1. Install Openssl/libssl1.0.0 Version 1.0.1f-1ubuntu2.27+esm3 on
  ubuntu 14.04
  2. openssl s_client -connect wikipedia.org:443 2>&1 < /dev/null | sed -n 
'/-BEGIN/,/-END/p' > wikipedia.pem 
  3. openssl x509 -noout -ocsp_uri -in wikipedia.pem 

  Expected it prints: http://r3.o.lencr.org
  Issue: it's not printing anything.

  Thanks Johannes for report this issue.

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


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


[Touch-packages] [Bug 1923479] Re: out of buffer access and Integer overflow in Exiv2

2021-04-26 Thread Leonidas S. Barbosa
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-29458

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

Title:
  out of buffer access and Integer overflow in Exiv2

Status in exiv2 package in Ubuntu:
  In Progress

Bug description:
  An out of buffer access: 
https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d
  and a Integer overflow : 
https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0

  affects Exiv2 in ubuntu releases

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

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


[Touch-packages] [Bug 1923479] Re: out of buffer access and Integer overflow in Exiv2

2021-04-20 Thread Leonidas S. Barbosa
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-29457

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

Title:
  out of buffer access and Integer overflow in Exiv2

Status in exiv2 package in Ubuntu:
  In Progress

Bug description:
  An out of buffer access: 
https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d
  and a Integer overflow : 
https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0

  affects Exiv2 in ubuntu releases

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

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


[Touch-packages] [Bug 1923479] Re: out of buffer access and Integer overflow in Exiv2

2021-04-12 Thread Leonidas S. Barbosa
A security update will be issue in next days to fix it on Ubuntu
releases.

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

Title:
  out of buffer access and Integer overflow in Exiv2

Status in exiv2 package in Ubuntu:
  In Progress

Bug description:
  An out of buffer access: 
https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d
  and a Integer overflow : 
https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0

  affects Exiv2 in ubuntu releases

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

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


[Touch-packages] [Bug 1923479] Re: out of buffer access and Integer overflow in Exiv2

2021-04-12 Thread Leonidas S. Barbosa
issued*

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

Title:
  out of buffer access and Integer overflow in Exiv2

Status in exiv2 package in Ubuntu:
  In Progress

Bug description:
  An out of buffer access: 
https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d
  and a Integer overflow : 
https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0

  affects Exiv2 in ubuntu releases

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

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


[Touch-packages] [Bug 1923479] Re: out of buffer access and Integer overflow in Exiv2

2021-04-12 Thread Leonidas S. Barbosa
There are no CVEs for this issues so far.

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

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

Title:
  out of buffer access and Integer overflow in Exiv2

Status in exiv2 package in Ubuntu:
  In Progress

Bug description:
  An out of buffer access: 
https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d
  and a Integer overflow : 
https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0

  affects Exiv2 in ubuntu releases

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

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


[Touch-packages] [Bug 1923479] [NEW] out of buffer access and Integer overflow in Exiv2

2021-04-12 Thread Leonidas S. Barbosa
Public bug reported:

An out of buffer access: 
https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d
and a Integer overflow : 
https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0

affects Exiv2 in ubuntu releases

** Affects: exiv2 (Ubuntu)
 Importance: Undecided
 Assignee: Leonidas S. Barbosa (leosilvab)
 Status: In Progress

** Changed in: exiv2 (Ubuntu)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

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

Title:
  out of buffer access and Integer overflow in Exiv2

Status in exiv2 package in Ubuntu:
  In Progress

Bug description:
  An out of buffer access: 
https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d
  and a Integer overflow : 
https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0

  affects Exiv2 in ubuntu releases

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

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


[Touch-packages] [Bug 1916893] Re: Regression - upate python2.7 for cover CVE-2021-3177 modifying unicode parts cause serious regressions

2021-02-25 Thread Leonidas S. Barbosa
Regression update reverting the CVE-2021-3177 patch was made:
https://ubuntu.com/security/notices/USN-4754-2

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

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

Title:
  Regression - upate python2.7 for cover CVE-2021-3177 modifying unicode
  parts cause serious regressions

Status in python2.7 package in Ubuntu:
  New

Bug description:
  [Scenario]
  A security update was made for python2.7 in xenial and bionic that can cause 
a serious regression since it is modifying unicode code for python2.7.

  [Issue]
  It can cause a serious break in the way python prints, rprs, unicode 
information, causing serious damage for any application that is running 
python2.7 in that scenario.

  [More info]
  https://ubuntu.com/security/CVE-2021-3177

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

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


[Touch-packages] [Bug 1916893] [NEW] Regression - upate python2.7 for cover CVE-2021-3177 modifying unicode parts cause serious regressions

2021-02-25 Thread Leonidas S. Barbosa
*** This bug is a security vulnerability ***

Private security bug reported:

[Scenario]
A security update was made for python2.7 in xenial and trusty-esm that can 
cause a serious regression since it is modifying unicode code for python2.7. 

[Issue]
It can cause a serious break in the way python prints, rprs, unicode 
information, causing serious damage for any application that is running 
python2.7 in that scenario.

[More info]
https://ubuntu.com/security/CVE-2021-3177

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

** Information type changed from Public to Private Security

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

Title:
  Regression - upate python2.7 for cover CVE-2021-3177 modifying unicode
  parts cause serious regressions

Status in python2.7 package in Ubuntu:
  New

Bug description:
  [Scenario]
  A security update was made for python2.7 in xenial and trusty-esm that can 
cause a serious regression since it is modifying unicode code for python2.7. 

  [Issue]
  It can cause a serious break in the way python prints, rprs, unicode 
information, causing serious damage for any application that is running 
python2.7 in that scenario.

  [More info]
  https://ubuntu.com/security/CVE-2021-3177

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

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


[Touch-packages] [Bug 1893569] Re: The mouse freezes

2020-08-31 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  The mouse freezes

Status in xorg package in Ubuntu:
  New

Bug description:
  The mouse freezes in the middle of work. I connected others and the
  same thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 30 20:44:30 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Toshiba Corporation HD Graphics 5500 [1179:f920]
 Subsystem: Toshiba Corporation Jet PRO [Radeon R5 M230 / R7 M260DX / 
Radeon 520 Mobile] [1179:f923]
  InstallationDate: Installed on 2020-06-15 (76 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA SATELLITE L50-B
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sr_RS
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=8f2dae7e-98af-440c-adfc-c31f5c18bb4a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 2.00
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr2.00:bd12/02/2014:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTQE-00500DY4:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: INVALID
  dmi.product.name: SATELLITE L50-B
  dmi.product.sku: INVALID
  dmi.product.version: PSKTQE-00500DY4
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1892134] Re: software-properties-gtk crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'com.ubuntu.So

2020-08-19 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  software-properties-gtk crashed with dbus.exceptions.DBusException in
  call_blocking(): org.freedesktop.DBus.Error.TimedOut: Failed to
  activate service 'com.ubuntu.SoftwareProperties': timed out
  (service_start_timeout=25000ms)

Status in software-properties package in Ubuntu:
  New

Bug description:
  help meto fix this

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: software-properties-gtk 0.99.3
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu44
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 19 06:58:30 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-05-17 (459 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonArgs: ['/usr/bin/software-properties-gtk']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with dbus.exceptions.DBusException in 
call_blocking(): org.freedesktop.DBus.Error.TimedOut: Failed to activate 
service 'com.ubuntu.SoftwareProperties': timed out 
(service_start_timeout=25000ms)
  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/software-properties/+bug/1892134/+subscriptions

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


[Touch-packages] [Bug 1888086] Re: Fehler : Ubuntu 18.04.4 LTS

2020-08-17 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  Fehler : Ubuntu 18.04.4 LTS

Status in xorg package in Ubuntu:
  New

Bug description:
  Fehler : Ubuntu 18.04.4 LTS

  
  Details
  Do you want to start the upgrade?

  1 package is going to be removed

  To prevent data loss close all open applications and  documents

  
  Details: Remove (1)  systemd-shim-shim for systemd

  
  Could not install 'systemd-shim'

  The upgrade will continue but the 'systemd-shim' package may not be in
  a working state. Please consider submitting a bug report about it.

  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

  Could not install the upgrades

  
  The upgrade has aborted. Your system could be in an unusable state. A 
recovery will run now (dpkg --configure -a).

  
  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Jul 18 23:24:46 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000]
  InstallationDate: Installed on 2020-07-17 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 R2
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=744ad588-c7b1-4684-b3e5-fc7ffaef78ea ro access=v1 quiet splash 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2017
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: GA-78LMT-USB3 R2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: sex
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3R2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3R2:rvrsex:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 R2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Jul 18 01:11:31 2020
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   input  USB Keyboard   KEYBOARD, id 8
   input  USB Keyboard   KEYBOARD, id 9
   inputCypress Sem PS2/USB Browser Combo Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1890011] Re: Could not install 'systemd-shim'

2020-08-17 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  Could not install 'systemd-shim'

Status in xorg package in Ubuntu:
  New

Bug description:
  The upgrade will continue but the 'systemd-shim' package may not be in
  a working state. Please consider submitting a bug report about it.

  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

  Could not install the upgrades

  The upgrade has aborted. Your system could be in an unusable state. A
  recovery will run now (dpkg --configure -a).

  
  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Aug  2 00:58:13 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000]
  InstallationDate: Installed on 2020-07-17 (15 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 R2
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=744ad588-c7b1-4684-b3e5-fc7ffaef78ea ro access=v1 quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2017
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: GA-78LMT-USB3 R2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: sex
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3R2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3R2:rvrsex:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 R2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Jul 18 01:11:31 2020
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   input  USB Keyboard   KEYBOARD, id 8
   input  USB Keyboard   KEYBOARD, id 9
   inputCypress Sem PS2/USB Browser Combo Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1886722] Re: package rsyslog 8.2001.0-1ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote rsyslog, o script post-installation retornou erro do status de saída

2020-07-08 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package rsyslog 8.2001.0-1ubuntu1 failed to install/upgrade: o
  subprocesso instalado, do pacote rsyslog, o script post-installation
  retornou erro do status de saída 10

Status in rsyslog package in Ubuntu:
  New

Bug description:
  esta com algums problemas

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: rsyslog 8.2001.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41
  Uname: Linux 5.4.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   firefox:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jul  6 07:18:47 2020
  ErrorMessage: o subprocesso instalado, do pacote rsyslog, o script 
post-installation retornou erro do status de saída 10
  InstallationDate: Installed on 2020-04-24 (74 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: rsyslog
  Title: package rsyslog 8.2001.0-1ubuntu1 failed to install/upgrade: o 
subprocesso instalado, do pacote rsyslog, o script post-installation retornou 
erro do status de saída 10
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1881982] Re: DoS vulnerability: cause resource exhaustion

2020-07-06 Thread Leonidas S. Barbosa
** Changed in: whoopsie (Ubuntu)
   Status: New => Confirmed

** Changed in: whoopsie (Ubuntu)
 Assignee: (unassigned) => Alex Murray (alexmurray)

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

Title:
  DoS vulnerability: cause resource exhaustion

Status in whoopsie package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  # Vulnerability description
  The parse_report() function in whoopsie.c allows attackers to cause a denial 
of service (memory leak) via a crafted file. 
  Exploitation of this issue causes excessive memory consumption which results 
in the Linux kernel triggering OOM killer on arbitrary process.
  This results in the process being terminated by the OOM killer.

  
  # Details 
  We have found a memory leak vulnerability during the parsing the crash file, 
when a collision occurs on GHashTable through g_hash_table_insert().
  According to [1], if the key already exists in the GHashTable, its current 
value is replaced with the new value.
  If 'key_destory_func' and 'value_destroy_func' are supplied when creating the 
table, the old value and the passed key are freed using that function.
  Unfortunately, whoopsie does not handle the old value and the passed key when 
collision happens.
  If a crash file contains same repetitive key-value pairs, it leads to memory 
leak as much as the amount of repetition and results in denial-of-service.

  [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g
  -hash-table-insert

  
  # PoC (*Please check the below PoC: whoopsie_killer.py)
  1) Generates a certain malformed crash file that contains same repetitive 
key-value pairs.
  2) Trigger the whoopsie to read the generated crash file.
  3) After then, the whoopsie process has been killed.

  
  # Mitigation (*Please check the below patch: g_hash_table_memory_leak.patch)
  We should use g_hash_table_new_full() with ‘key_destroy_func’ and 
‘value_destroy_func’ functions instead of g_hash_table_new().
  Otherwise, before g_hash_table_insert(), we should check the collision via 
g_hash_table_lookup_extended() and obtain pointer to the old value and remove 
it.

  Sincerely,

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

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


[Touch-packages] [Bug 1886412] Re: $ ubuntu-bug xorg

2020-07-06 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
$ ubuntu-bug xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  I cannot open system settings so I can set up a sleep mode after
  leaving offfor a spell.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18
  Uname: Linux 4.15.0-109-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.137  Thu Sep 14 13:51:03 
PDT 2017
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jul  6 11:57:21 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 304.137, 4.15.0-108-generic, x86_64: installed
   nvidia, 304.137, 4.15.0-109-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. C61 [GeForce 7025 / nForce 630a] 
[1043:83a4]
  InstallationDate: Installed on 2012-09-29 (2837 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic 
root=UUID=6eb98a42-bc12-42f1-992b-97782d05bb24 ro splash quiet
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4N68T-M-LE-V2
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd01/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T-M-LE-V2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Fri Jul  3 12:16:20 2020
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.4

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

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


[Touch-packages] [Bug 1878738] Re: program abort by "lh_table_new: calloc failed"

2020-05-19 Thread Leonidas S. Barbosa
Hi, thanks for report his issue. That issue was already reverted and a
new version is available. Run apt-get update; apt-get upgrade -y , and
it should install that last reverted version.

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

Title:
  program abort  by "lh_table_new: calloc failed"

Status in json-c package in Ubuntu:
  Confirmed

Bug description:
  I wrote small sample program which abort by lh_table_new calloc failed.
  see this.
  https://gist.github.com/735eec6fd0869df1facb08da5baa402c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878738/+subscriptions

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


[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed

2020-01-29 Thread Leonidas S. Barbosa
Hi,

Could you downgrade to the previous version and check if it happens
there too? And so re upgrade and re-test?

Thanks!

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

Title:
  _sasl_plugin_load failed

Status in cyrus-sasl2 package in Ubuntu:
  New

Bug description:
  We are seeing the following in the journal after upgrading to these
  sets of packages:

  libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 
amd64
  libsasl2-modules/bionic-updates,bionic-security 
2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64
  libsasl2-modules-db/bionic-updates,bionic-security 
2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 
  libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 
2.1.27~101-g0780600+dfsg-3ubuntu2.1 

  Here are the errors:

  Jan 28 15:58:43 my-hostname sssd[20949]: Starting up
  Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up
  Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb
  Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on 
sasl_canonuser_init
  Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found
  Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found
  Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found
  Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+subscriptions

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


[Touch-packages] [Bug 1840396] Re: do not display two screen

2019-08-16 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  do not display two screen

Status in xorg package in Ubuntu:
  New

Bug description:
  maybe error drivers graphics for del

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 16 08:50:25 2019
  DistUpgraded: 2019-06-26 14:49:28,001 ERROR Cache can not be locked (Can not 
lock '/var/lib/apt/lists/lock' )
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:078b]
 Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 
M520] [1028:078b]
  InstallationDate: Installed on 2019-06-25 (51 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 15-3567
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=981f9e6c-b414-4dbc-8a43-1e260574e929 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-06-26 (50 days ago)
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.3:bd08/25/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1840397] Re: do not display two screen

2019-08-16 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  do not display two screen

Status in xorg package in Ubuntu:
  New

Bug description:
  maybe error drivers graphics for del

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 16 08:50:25 2019
  DistUpgraded: 2019-06-26 14:49:28,001 ERROR Cache can not be locked (Can not 
lock '/var/lib/apt/lists/lock' )
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:078b]
 Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 
M520] [1028:078b]
  InstallationDate: Installed on 2019-06-25 (51 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 15-3567
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=981f9e6c-b414-4dbc-8a43-1e260574e929 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-06-26 (50 days ago)
  dmi.bios.date: 08/25/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.3:bd08/25/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.product.sku: 078B
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1838890] Re: Suspected memory leak in xenial backport of fix for CVE-2019-13012

2019-08-05 Thread Leonidas S. Barbosa
** Changed in: glib2.0 (Ubuntu)
   Status: New => In Progress

** Also affects: glib2.0 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: glib2.0 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: glib2.0 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: glib2.0 (Ubuntu Precise)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Precise)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

** Changed in: glib2.0 (Ubuntu Trusty)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

** Changed in: glib2.0 (Ubuntu Xenial)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

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

Title:
  Suspected memory leak in xenial backport of fix for CVE-2019-13012

Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 source package in Precise:
  In Progress
Status in glib2.0 source package in Trusty:
  In Progress
Status in glib2.0 source package in Xenial:
  In Progress

Bug description:
  (This is only from source code inspection, not tested in real use - I
  don't actually use Ubuntu.)

  The upstream fix for CVE-2019-13012 included this change:

  -  g_file_make_directory_with_parents (kfsb->dir, NULL, NULL);
  +  g_mkdir_with_parents (g_file_peek_path (kfsb->dir), 0700);

  However, g_file_peek_path() was only introduced in GLib 2.56. The
  backport in the xenial package has this instead:

  -  g_file_make_directory_with_parents (kfsb->dir, NULL, NULL);
  +  g_mkdir_with_parents (g_file_get_path (kfsb->dir), 0700);

  This is not equivalent. The difference between g_file_peek_path() and
  the older g_file_get_path() is that g_file_get_path() makes a copy,
  which must be freed with g_free() after use. As a result, there is now
  a memory leak.

  A non-leaky backport would look something like this, which is what
  I've done in a proposed backport for Debian 9 'stretch':

  + char *dir;
  ...
  -  g_file_make_directory_with_parents (kfsb->dir, NULL, NULL);
  +  dir = g_file_get_path (kfsb->dir);
  +  g_mkdir_with_parents (dir, 0700);
  +  g_free (dir);

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

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


[Touch-packages] [Bug 1803441] Re: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch)

2019-08-05 Thread Leonidas S. Barbosa
Fixed released https://usn.ubuntu.com/4058-2/

** Changed in: bash (Ubuntu Trusty)
   Status: In Progress => Fix Released

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

Title:
  BASH_CMDS is writable in restricted bash shells (fixed upstream, need
  to backport patch)

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Trusty:
  Fix Released

Bug description:
  In 14.04 LTS, the BASH_CMDS variable is writable in rbash. This allows
  a trivial escape from rbash to run arbitrary shell commands.

  This issue is fixed upstream:
  http://git.savannah.gnu.org/cgit/bash.git/tree/CHANGES?h=bash-4.4-testing#n65

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

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


[Touch-packages] [Bug 1838890] Re: Suspected memory leak in xenial backport of fix for CVE-2019-13012

2019-08-05 Thread Leonidas S. Barbosa
** Changed in: glib2.0 (Ubuntu)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

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

Title:
  Suspected memory leak in xenial backport of fix for CVE-2019-13012

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  (This is only from source code inspection, not tested in real use - I
  don't actually use Ubuntu.)

  The upstream fix for CVE-2019-13012 included this change:

  -  g_file_make_directory_with_parents (kfsb->dir, NULL, NULL);
  +  g_mkdir_with_parents (g_file_peek_path (kfsb->dir), 0700);

  However, g_file_peek_path() was only introduced in GLib 2.56. The
  backport in the xenial package has this instead:

  -  g_file_make_directory_with_parents (kfsb->dir, NULL, NULL);
  +  g_mkdir_with_parents (g_file_get_path (kfsb->dir), 0700);

  This is not equivalent. The difference between g_file_peek_path() and
  the older g_file_get_path() is that g_file_get_path() makes a copy,
  which must be freed with g_free() after use. As a result, there is now
  a memory leak.

  A non-leaky backport would look something like this, which is what
  I've done in a proposed backport for Debian 9 'stretch':

  + char *dir;
  ...
  -  g_file_make_directory_with_parents (kfsb->dir, NULL, NULL);
  +  dir = g_file_get_path (kfsb->dir);
  +  g_mkdir_with_parents (dir, 0700);
  +  g_free (dir);

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

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


[Touch-packages] [Bug 1803441] Re: BASH_CMDS is writable in restricted bash shells (fixed upstream, need to backport patch)

2019-08-02 Thread Leonidas S. Barbosa
** Also affects: bash (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Changed in: bash (Ubuntu Trusty)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

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

Title:
  BASH_CMDS is writable in restricted bash shells (fixed upstream, need
  to backport patch)

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Trusty:
  In Progress

Bug description:
  In 14.04 LTS, the BASH_CMDS variable is writable in rbash. This allows
  a trivial escape from rbash to run arbitrary shell commands.

  This issue is fixed upstream:
  http://git.savannah.gnu.org/cgit/bash.git/tree/CHANGES?h=bash-4.4-testing#n65

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

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


[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-07-03 Thread Leonidas S. Barbosa
Thanks a lot @Mark for the quick fix!

:)

** Changed in: bzip2 (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  In Progress
Status in bzip2 source package in Xenial:
  New
Status in bzip2 source package in Bionic:
  New
Status in bzip2 source package in Cosmic:
  New
Status in bzip2 source package in Disco:
  New
Status in bzip2 package in Debian:
  Confirmed

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

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

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


[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-07-02 Thread Leonidas S. Barbosa
Hey @Mark, Thanks for provide these tests 
(https://sourceware.org/git/?p=bzip2-tests.git;a=summary). I ran our internal 
regression tests on the version patched and also the tests you provided. Our 
tests passed, but yours fails (believe is the same you mentioned in Debian-bug).
 
See bellow:

!!! 1 .bz files did not decompressed/recompressed correctly.

Testing detection of bad input data...

Processing ./go/compress/fail-issue5747.bz2.bad
  Trying to decompress...

bzip2: Data integrity error when decompressing.
  Trying to decompress (small)...

bzip2: Data integrity error when decompressing.
Processing ./lbzip2/cve.bz2.bad
  Trying to decompress...

bzip2: Data integrity error when decompressing.
  Trying to decompress (small)...

bzip2: Data integrity error when decompressing.
Processing ./lbzip2/cve2.bz2.bad
  Trying to decompress...

bzip2: Data integrity error when decompressing.
  Trying to decompress (small)...

bzip2: Data integrity error when decompressing.
Processing ./lbzip2/overrun.bz2.bad
  Trying to decompress...

bzip2: Data integrity error when decompressing.
  Trying to decompress (small)...

bzip2: Data integrity error when decompressing.
Processing ./lbzip2/void.bz2.bad
  Trying to decompress...
  Trying to decompress (small)...
Processing ./lbzip2/crc1.bz2.bad
  Trying to decompress...

bzip2: Data integrity error when decompressing.
  Trying to decompress (small)...

bzip2: Data integrity error when decompressing.
Processing ./lbzip2/crc2.bz2.bad
  Trying to decompress...

bzip2: Data integrity error when decompressing.
  Trying to decompress (small)...

bzip2: Data integrity error when decompressing.
Processing ./lbzip2/overrun2.bz2.bad
  Trying to decompress...

bzip2: Data integrity error when decompressing.
  Trying to decompress (small)...

bzip2: Data integrity error when decompressing.

Correctly found all bad file data integrity errors.

Bad results, look for !!! in the logs above

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  Confirmed
Status in bzip2 source package in Xenial:
  New
Status in bzip2 source package in Bionic:
  New
Status in bzip2 source package in Cosmic:
  New
Status in bzip2 source package in Disco:
  New
Status in bzip2 package in Debian:
  Confirmed

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

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

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


[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-07-01 Thread Leonidas S. Barbosa
I did test the patch suggested and can confirm that it fixes the issue.

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  Confirmed
Status in bzip2 source package in Xenial:
  New
Status in bzip2 source package in Bionic:
  New
Status in bzip2 source package in Cosmic:
  New
Status in bzip2 source package in Disco:
  New
Status in bzip2 package in Debian:
  Confirmed

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

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

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


[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-06-28 Thread Leonidas S. Barbosa
** Also affects: bzip2 (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  Confirmed
Status in bzip2 source package in Xenial:
  New
Status in bzip2 source package in Bionic:
  New
Status in bzip2 source package in Cosmic:
  New
Status in bzip2 source package in Disco:
  New

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

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

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


[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-06-28 Thread Leonidas S. Barbosa
** Also affects: bzip2 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  New
Status in bzip2 package in Ubuntu:
  Confirmed
Status in bzip2 source package in Xenial:
  New
Status in bzip2 source package in Bionic:
  New
Status in bzip2 source package in Disco:
  New

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

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

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


[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-06-28 Thread Leonidas S. Barbosa
** Also affects: bzip2 (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2:
  Unknown
Status in bzip2 package in Ubuntu:
  Confirmed
Status in bzip2 source package in Bionic:
  New
Status in bzip2 source package in Disco:
  New

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

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

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


[Touch-packages] [Bug 1834494] Re: latest bzip2 reports crc errors incorrectly

2019-06-27 Thread Leonidas S. Barbosa
Hi,

Thanks for report this issue.
I added a comment in commit fix that caused this regression in upstream 
project: 
https://gitlab.com/federicomenaquintero/bzip2/commit/74de1e2e6ffc9d51ef9824db71a8ffee5962cdbc
 

Soon they update there with some notes we can look for a fix. For now,
as you already did, please try downgrade to the previous version. Also,
if possible, could you please test it using upstream version?

We apologize for the inconvenience.

** Changed in: bzip2 (Ubuntu)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

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

Title:
  latest bzip2 reports crc errors incorrectly

Status in bzip2 package in Ubuntu:
  Confirmed

Bug description:
  I just got the bzip2 1.0.6-8.1ubuntu0.1 updates pushed to my machine
  and am now having problems with some .tbz2 archives.  In particular, I
  can no longer extract this one:

  https://developer.nvidia.com/embedded/dlc/l4t-jetson-xavier-driver-
  package-31-1-0

  Downloading this and running:

  bunzip2 -tvv Jetson_Linux_R31.1.0_aarch64.tbz2

  ...yields a CRC error.  The previous version of bunzip2 does not
  report any errors with this archive.

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

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


[Touch-packages] [Bug 1823422] Re: heimdal ftbfs in disco

2019-05-16 Thread Leonidas S. Barbosa
hi there,

I was attempting to update a security issue on heimdal and had these
issues with tests (maybe also related)

FAIL test_ca (exit status: 1)

FAIL: test_chain


cert -> root
FAIL test_chain (exit status: 1)

FAIL: test_cms
==

not testing ECDSA since hcrypto doesnt support ECDSA
create signed data
verify signed data
hxtool: hx509_cms_verify_signed: Failed to find certificate with id 
CE776EDE0BF421F878C01A7CC3B966EC4C3D4A23
FAIL test_cms (exit status: 1)


Testsuite summary for Heimdal 7.5.0

# TOTAL: 16
# PASS:  13
# SKIP:  0
# XFAIL: 0
# FAIL:  3
# XPASS: 0
# ERROR: 0

See lib/hx509/test-suite.log
Please report to https://github.com/heimdal/heimdal/issues


>From upstream, it seems there is a probably fix, but the issue is still
open and it seems not to work for 32 Oses - see here:
https://github.com/heimdal/heimdal/issues/533

If anyone has any clue how to fix this FTBFS it would be appreciate :) -
tks!

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

Title:
  heimdal ftbfs in disco

Status in Heimdal:
  New
Status in heimdal package in Ubuntu:
  Triaged

Bug description:
  https://launchpadlibrarian.net/417925401/buildlog_ubuntu-disco-
  amd64.heimdal_7.5.0+dfsg-2.1_BUILDING.txt.gz

  =
 Heimdal 7.5.0: lib/hx509/test-suite.log
  =

  # TOTAL: 16
  # PASS:  15
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0

  .. contents:: :depth: 2

  FAIL: test_chain
  

  cert -> root
  cert -> root
  cert -> root
  sub-cert -> root
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca -> root
  sub-cert -> sub-ca -> root
  max depth 2 (ok)
  max depth 1 (fail)
  ocsp non-ca responder
  ocsp ca responder
  ocsp no-ca responder, missing cert
  ocsp no-ca responder, missing cert, in pool
  ocsp no-ca responder, keyHash
  ocsp revoked cert
  ocsp print reply resp1-ocsp-no-cert
  ocsp print reply resp1-ca
  ocsp print reply resp1-keyhash
  ocsp print reply resp2
  ocsp verify exists
  ocsp verify not exists
  ocsp verify revoked
  crl non-revoked cert
  FAIL test_chain (exit status: 1)

  
  Testsuite summary for Heimdal 7.5.0
  
  # TOTAL: 16
  # PASS:  15
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0
  
  See lib/hx509/test-suite.log
  Please report to https://github.com/heimdal/heimdal/issues

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

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


[Touch-packages] [Bug 1826546] Re: falha ao atualizar o sistema operacional

2019-04-26 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  falha ao atualizar o sistema operacional

Status in hud package in Ubuntu:
  New

Bug description:
  nao estou conseguindo instalar programas pelo terminal

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

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


[Touch-packages] [Bug 1808415] Re: i dont no

2018-12-14 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
   i dont no

Status in xorg package in Ubuntu:
  New

Bug description:
  plus de son en sortie et la clef bluethoot pas detecter

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: pata_acpi r8169 radeon pata_atiixp wmi
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Dec 13 21:27:17 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Wrestler [Radeon HD 6310] [1043:101c]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2017-05-23 (569 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ASUSTeK Computer Inc. K53BY
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=a12e05bc-12f2-4433-9815-2d789360b75c ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K53BY
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr210:bd05/12/2011:svnASUSTeKComputerInc.:pnK53BY:pvr1.0:rvnASUSTeKComputerInc.:rnK53BY:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K53BY
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Dec 13 21:22:15 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1808203] Re: ddfs

2018-12-13 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  ddfs

Status in xorg package in Ubuntu:
  New

Bug description:
  sdfsf

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Dec 12 21:07:13 2018
  DistUpgraded: 2018-12-12 20:39:45,935 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Wrestler [Radeon HD 7340] [104d:90ad]
  InstallationDate: Installed on 2016-04-24 (962 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Sony Corporation SVE1112M1EW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=40da7131-b99a-4e5b-9c5e-81ba4975e74c ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-12-12 (0 days ago)
  dmi.bios.date: 08/22/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0120D8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0120D8:bd08/22/2012:svnSonyCorporation:pnSVE1112M1EW:pvrC60B8BEP:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVE1112M1EW
  dmi.product.version: C60B8BEP
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Dec 12 18:07:04 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1803059] Re: Nullpointer dereference

2018-12-11 Thread Leonidas S. Barbosa
Fix released for trusty, bionic, xenial and cosmic
https://usn.ubuntu.com/3837-2/

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

Title:
  Nullpointer dereference

Status in poppler package in Ubuntu:
  Fix Released
Status in poppler source package in Bionic:
  Fix Released
Status in poppler source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  Evince segfaults on some pdf documents

  * Test case
  Download and try to open 
https://bugs.freedesktop.org/attachment.cgi?id=138927 with evince, it shouldn't 
segfault

  * Regression potential
  Nothing special to test, make sure evince still opens pdfs without issue

  -

  System Info: Linux zero 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10
  10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Evince version: GNOME Document Viewer 3.28.4

  While fuzzing evince v3.28.4, on linux 4.15.0-38-generic (Ubuntu 18.04
  LTS), a null-pointer dereference was observed, initially this was
  reported to evince but the evince team advised that the issue is in
  poppler, the library used by evince to render PDF, poppler version:
  0.62.0-2ubuntu2.2 is vulnerable to null-pointer dereference, however
  the issue is already fixed in poppler 0.70, but this will still crash
  your evince v3.28.4 in ubuntu if poppler is not updated to v.0.70.

  Fuzzing result showing a very important vulnerability in a package
  currently shipped by a major Linux distribution is still of interest,
  even if that Linux distribution does not package the latest released
  upstream version. I think Ubuntu is still using,

  Source: poppler
  Version: 0.62.0-2ubuntu2.2

  So, most of the systems will be affected to this issue.

  Upstream: https://gitlab.freedesktop.org/poppler/poppler/issues/664

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

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


[Touch-packages] [Bug 1807504] Re: Evince segfaults when opening PDF

2018-12-11 Thread Leonidas S. Barbosa
Fix released for trusty, bionic, xenial and cosmic
https://usn.ubuntu.com/3837-2/

** Changed in: poppler (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Evince segfaults when opening PDF

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  After a recent poppler update neither Evince nor Qpdfview will open
  pdf files that opened before the update.  These files open properly
  using gv (which uses Ghostview instead of poppler).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libpoppler73 0.62.0-2ubuntu2.4
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Dec  8 08:48:01 2018
  InstallationDate: Installed on 2016-08-25 (834 days ago)
  InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: poppler
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (116 days ago)

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

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


[Touch-packages] [Bug 1807494] Re: [Aspire 5745, Intel IbexPeak HDMI, Digital Out, HDMI] Underruns, dropouts or crackling sound

2018-12-11 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  [Aspire 5745, Intel IbexPeak HDMI, Digital Out, HDMI] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I am not able to hear high quality sound. It may be related to driver
  issue or any other configuration issue. Please do the needful.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  manu   1605 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  8 15:03:05 2018
  InstallationDate: Installed on 2018-12-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulseAudioLog: Dec 08 14:18:18 Indian dbus-daemon[853]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.31' (uid=121 pid=1281 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Aspire 5745, Intel IbexPeak HDMI, Digital Out, HDMI] Underruns, 
dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/09/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: V1.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: ZR7
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrV1.16:bd08/09/2010:svnAcer:pnAspire5745:pvrV1.16:rvnAcer:rnZR7:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: Aspire 5745
  dmi.product.version: V1.16
  dmi.sys.vendor: Acer

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

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


[Touch-packages] [Bug 1803059] Re: Nullpointer dereference

2018-12-10 Thread Leonidas S. Barbosa
Hi Miguel,

Sorry for the inconvenient,  I`m aware of the situation and I`m working
to fix this issue.

Thanks tor report this.

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

Title:
  Nullpointer dereference

Status in poppler package in Ubuntu:
  Confirmed
Status in poppler source package in Bionic:
  Fix Released
Status in poppler source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  Evince segfaults on some pdf documents

  * Test case
  Download and try to open 
https://bugs.freedesktop.org/attachment.cgi?id=138927 with evince, it shouldn't 
segfault

  * Regression potential
  Nothing special to test, make sure evince still opens pdfs without issue

  -

  System Info: Linux zero 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10
  10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Evince version: GNOME Document Viewer 3.28.4

  While fuzzing evince v3.28.4, on linux 4.15.0-38-generic (Ubuntu 18.04
  LTS), a null-pointer dereference was observed, initially this was
  reported to evince but the evince team advised that the issue is in
  poppler, the library used by evince to render PDF, poppler version:
  0.62.0-2ubuntu2.2 is vulnerable to null-pointer dereference, however
  the issue is already fixed in poppler 0.70, but this will still crash
  your evince v3.28.4 in ubuntu if poppler is not updated to v.0.70.

  Fuzzing result showing a very important vulnerability in a package
  currently shipped by a major Linux distribution is still of interest,
  even if that Linux distribution does not package the latest released
  upstream version. I think Ubuntu is still using,

  Source: poppler
  Version: 0.62.0-2ubuntu2.2

  So, most of the systems will be affected to this issue.

  Upstream: https://gitlab.freedesktop.org/poppler/poppler/issues/664

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

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


[Touch-packages] [Bug 1799738] Re: dose not work rite

2018-10-24 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  dose not work rite

Status in xorg package in Ubuntu:
  New

Bug description:
  dose not work rite

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Oct 24 11:36:58 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:fde0]
 Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:fde0]
  InstallationDate: Installed on 2018-03-07 (231 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: TOSHIBA Satellite C655
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=61e48a6a-7e5a-4c7e-aa64-e126e56af5b5 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.70:bd07/07/2011:svnTOSHIBA:pnSatelliteC655:pvrPSC08U-03C01K:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: Satellite C655
  dmi.product.sku: Montevina_Fab
  dmi.product.version: PSC08U-03C01K
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Sat Mar 17 11:24:42 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5760 
   vendor CMO
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1794690] Re: Backport 0.8.2 for a CVE update

2018-10-04 Thread Leonidas S. Barbosa
Is there any POC for check CVE-2018-15856? Trusty hasn't the file
affected, but I'm wondering if it handles the same thing and is
vulnerable and the only way to check this would be if we have any POC.

Tks!

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

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

Title:
  Backport 0.8.2 for a CVE update

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  In Progress

Bug description:
  [Impact]
  0.8.2 has completed the fuzzing work started in 0.8.1, so backport the 
package from cosmic to fix these CVE's:

  CVE-2018-15853 CVE-2018-15854 CVE-2018-15855 CVE-2018-15856
  CVE-2018-15857 CVE-2018-15858 CVE-2018-15859 CVE-2018-15861
  CVE-2018-15862 CVE-2018-15863 CVE-2018-15864.

  upstream NEWS:

  libxkbcommon 0.8.2 - 2018-08-05
  ==

  - Fix various problems found with fuzzing (see commit messages for
    more details):

  - Fix a few NULL-dereferences, out-of-bounds access and undefined behavior
    in the XKB text format parser.

  libxkbcommon 0.8.1 - 2018-08-03
  ==

  - Fix various problems found in the meson build (see commit messages for more
    details):

  - Fix compilation on Darwin.

  - Fix compilation of the x11 tests and demos when XCB is installed in a
    non-standard location.

  - Fix xkbcommon-x11.pc missing the Requires specification.

  - Fix various problems found with fuzzing and Coverity (see commit messages 
for
    more details):

  - Fix stack overflow in the XKB text format parser when evaluating boolean
    negation.

  - Fix NULL-dereferences in the XKB text format parser when some 
unsupported
    tokens appear (the tokens are still parsed for backward compatibility).

  - Fix NULL-dereference in the XKB text format parser when parsing an
    xkb_geometry section.

  - Fix an infinite loop in the Compose text format parser on some
  inputs.

  - Fix an invalid free() when using multiple keysyms.

  - Replace the Unicode characters for the leftanglebracket and 
rightanglebracket
    keysyms from the deprecated LEFT/RIGHT-POINTING ANGLE BRACKET to
    MATHEMATICAL LEFT/RIGHT ANGLE BRACKET.

  - Reject out-of-range Unicode codepoints in xkb_keysym_to_utf8 and
    xkb_keysym_to_utf32.

  [Test case]
  install the update, check that nothing breaks wrt keyboard handling

  [Regression potential]
  slim, this has been in cosmic for some time already, and upstream 
specifically asked to backport this to stable releases

  There are some other changes to the packaging, but these are harmless
  and won't regress anything.

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

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


[Touch-packages] [Bug 1794690] Re: Backport 0.8.2 for a CVE update

2018-10-03 Thread Leonidas S. Barbosa
Hi Timo,

Are you planning to update only for bionic or will you do this also for trusty 
and xenial? 
Asking that because I was/am planning to put that update in my stack for xenial 
and trusty.

[]'s

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

Title:
  Backport 0.8.2 for a CVE update

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  In Progress

Bug description:
  [Impact]
  0.8.2 has completed the fuzzing work started in 0.8.1, so backport the 
package from cosmic to fix these CVE's:

  CVE-2018-15853 CVE-2018-15854 CVE-2018-15855 CVE-2018-15856
  CVE-2018-15857 CVE-2018-15858 CVE-2018-15859 CVE-2018-15861
  CVE-2018-15862 CVE-2018-15863 CVE-2018-15864.

  upstream NEWS:

  libxkbcommon 0.8.2 - 2018-08-05
  ==

  - Fix various problems found with fuzzing (see commit messages for
    more details):

  - Fix a few NULL-dereferences, out-of-bounds access and undefined behavior
    in the XKB text format parser.

  libxkbcommon 0.8.1 - 2018-08-03
  ==

  - Fix various problems found in the meson build (see commit messages for more
    details):

  - Fix compilation on Darwin.

  - Fix compilation of the x11 tests and demos when XCB is installed in a
    non-standard location.

  - Fix xkbcommon-x11.pc missing the Requires specification.

  - Fix various problems found with fuzzing and Coverity (see commit messages 
for
    more details):

  - Fix stack overflow in the XKB text format parser when evaluating boolean
    negation.

  - Fix NULL-dereferences in the XKB text format parser when some 
unsupported
    tokens appear (the tokens are still parsed for backward compatibility).

  - Fix NULL-dereference in the XKB text format parser when parsing an
    xkb_geometry section.

  - Fix an infinite loop in the Compose text format parser on some
  inputs.

  - Fix an invalid free() when using multiple keysyms.

  - Replace the Unicode characters for the leftanglebracket and 
rightanglebracket
    keysyms from the deprecated LEFT/RIGHT-POINTING ANGLE BRACKET to
    MATHEMATICAL LEFT/RIGHT ANGLE BRACKET.

  - Reject out-of-range Unicode codepoints in xkb_keysym_to_utf8 and
    xkb_keysym_to_utf32.

  [Test case]
  install the update, check that nothing breaks wrt keyboard handling

  [Regression potential]
  slim, this has been in cosmic for some time already, and upstream 
specifically asked to backport this to stable releases

  There are some other changes to the packaging, but these are harmless
  and won't regress anything.

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

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


[Touch-packages] [Bug 1795230] Re: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver

2018-10-01 Thread Leonidas S. Barbosa
Thanks a lot Vishnu!

Since it's not a security udpate issue I'll notice and add the desktop
team to handle with this bug.

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

Title:
  Product crashes after upgrading  to glib2.0 2.56.2 in Ubuntu 18.04
  Bionic Beaver

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  Our product is using LibAppIndicator
  Please find the dependency tree below for libappindicator, it is using libglib

  libappindicator.so.1 => /usr/lib/i386-linux-gnu/libappindicator.so.1
  libindicator.so.7 => /usr/lib/i386-linux-gnu/libindicator.so.7
  libgtk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
  libgdk-x11-2.0.so.0 => 
/usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
  libpangocairo-1.0.so.0 => 
/usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0
  libpango-1.0.so.0 => 
/usr/lib/i386-linux-gnu/libpango-1.0.so.0
  libgobject-2.0.so.0 => 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  libglib-2.0.so.0 => 
/lib/i386-linux-gnu/libglib-2.0.so.0

  Our product is crashing after upgrading libglib to the latest version
  glib2.0 2.56.2 released on 19-Sep-2018.

  https://launchpad.net/ubuntu/+source/glib2.0/2.56.2-0ubuntu0.18.04.2

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

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


[Touch-packages] [Bug 1795230] Re: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver

2018-10-01 Thread Leonidas S. Barbosa
By the changelog, glib2.0 was update to a new upstream release from
2.56.1-2 to 2.56.2 and so a security update was done over it.

In order to figure out if it's an issue in the security update or the
original version glib 2.56.2-0ubuntu0.18.04.1. Could you please try this
pkg version and check if the regression segfault persist:

AMD64 - https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3389-deletedppa/+build/15310024

I386 - https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3389-deletedppa/+build/15310027

Thanks!

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

Title:
  Product crashes after upgrading  to glib2.0 2.56.2 in Ubuntu 18.04
  Bionic Beaver

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Our product is using LibAppIndicator
  Please find the dependency tree below for libappindicator, it is using libglib

  libappindicator.so.1 => /usr/lib/i386-linux-gnu/libappindicator.so.1
  libindicator.so.7 => /usr/lib/i386-linux-gnu/libindicator.so.7
  libgtk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
  libgdk-x11-2.0.so.0 => 
/usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
  libpangocairo-1.0.so.0 => 
/usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0
  libpango-1.0.so.0 => 
/usr/lib/i386-linux-gnu/libpango-1.0.so.0
  libgobject-2.0.so.0 => 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  libglib-2.0.so.0 => 
/lib/i386-linux-gnu/libglib-2.0.so.0

  Our product is crashing after upgrading libglib to the latest version
  glib2.0 2.56.2 released on 19-Sep-2018.

  https://launchpad.net/ubuntu/+source/glib2.0/2.56.2-0ubuntu0.18.04.2

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

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


[Touch-packages] [Bug 1795230] Re: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver

2018-10-01 Thread Leonidas S. Barbosa
Can you reproduce the issue in a previous version, such as 
2.56.2-0ubuntu0.18.04.1?
Also, is there any POC/test in how to reproduce this?

Thanks!

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

Title:
  Product crashes after upgrading  to glib2.0 2.56.2 in Ubuntu 18.04
  Bionic Beaver

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Our product is using LibAppIndicator
  Please find the dependency tree below for libappindicator, it is using libglib

  libappindicator.so.1 => /usr/lib/i386-linux-gnu/libappindicator.so.1
  libindicator.so.7 => /usr/lib/i386-linux-gnu/libindicator.so.7
  libgtk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
  libgdk-x11-2.0.so.0 => 
/usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
  libpangocairo-1.0.so.0 => 
/usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0
  libpango-1.0.so.0 => 
/usr/lib/i386-linux-gnu/libpango-1.0.so.0
  libgobject-2.0.so.0 => 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  libglib-2.0.so.0 => 
/lib/i386-linux-gnu/libglib-2.0.so.0

  Our product is crashing after upgrading libglib to the latest version
  glib2.0 2.56.2 released on 19-Sep-2018.

  https://launchpad.net/ubuntu/+source/glib2.0/2.56.2-0ubuntu0.18.04.2

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

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


[Touch-packages] [Bug 1795230] Re: Product crashes after upgrading to glib2.0 2.56.2 in Ubuntu 18.04 Bionic Beaver

2018-10-01 Thread Leonidas S. Barbosa
Hi Amit,

The last update/sec update touched glib2.0 regarding gMarkup and UTF structure. 
Were them: 
- Fix crash in error handling path for closing elements - 
fccef3cc822af74699cca84cd202719ae61ca3b9 
- Fix unvalidated UTF-8 read in markup parsing error path - 
cec71705406f0b2790422f0c1aa0ff3b4b464b1b 

That can give us a clue about that segfault. Could be possible to
provide any way in how to reproduce this issue?

Thanks!

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

Title:
  Product crashes after upgrading  to glib2.0 2.56.2 in Ubuntu 18.04
  Bionic Beaver

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Our product is using LibAppIndicator
  Please find the dependency tree below for libappindicator, it is using libglib

  libappindicator.so.1 => /usr/lib/i386-linux-gnu/libappindicator.so.1
  libindicator.so.7 => /usr/lib/i386-linux-gnu/libindicator.so.7
  libgtk-x11-2.0.so.0 => /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
  libgdk-x11-2.0.so.0 => 
/usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
  libpangocairo-1.0.so.0 => 
/usr/lib/i386-linux-gnu/libpangocairo-1.0.so.0
  libpango-1.0.so.0 => 
/usr/lib/i386-linux-gnu/libpango-1.0.so.0
  libgobject-2.0.so.0 => 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  libglib-2.0.so.0 => 
/lib/i386-linux-gnu/libglib-2.0.so.0

  Our product is crashing after upgrading libglib to the latest version
  glib2.0 2.56.2 released on 19-Sep-2018.

  https://launchpad.net/ubuntu/+source/glib2.0/2.56.2-0ubuntu0.18.04.2

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

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


[Touch-packages] [Bug 1790951] Re: Black vertical line on Right Side of the Screen

2018-09-06 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  Black vertical line on Right Side of the Screen

Status in xorg package in Ubuntu:
  New

Bug description:
  The OS appears to not recognize the monitors size and no mater if I
  select the native resolution, the black line still there. I've notice
  also that there are 2 display options, LVDS and VGA, but the problem
  is that the VGA doesn't exist, only the LVDS. I've already done the
  xrandr commands, and added the resolutions witch fitted better to the
  machine, but my guess is that it is not the resolution, it is a
  miscommunication between the OS and the hardware.

  Please help, I'm a linux user with less experience, but I like it a
  lot and I wish to stay in Ubuntu(even with that black line, but it
  would be better to not).

  Thanks for your awesome work

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep  5 14:57:14 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e22] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation 4 Series Chipset Integrated Graphics 
Controller [104d:9044]
 Subsystem: Sony Corporation 4 Series Chipset Integrated Graphics 
Controller [104d:9044]
  InstallationDate: Installed on 2018-08-31 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Sony Corporation VGC-JS160J
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=d74eae8d-b73a-4fd9-ac75-8f3ea6bed617 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0201T4
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 13
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0201T4:bd08/29/2008:svnSonyCorporation:pnVGC-JS160J:pvrC6U09RL6:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct13:cvrN/A:
  dmi.product.family: N/A
  dmi.product.name: VGC-JS160J
  dmi.product.version: C6U09RL6
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Touch-packages] [Bug 1790960] Re: I ve installed ubuntu and upgraded it + some apps.

2018-09-06 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  I ve installed ubuntu and upgraded it + some apps.

Status in xorg package in Ubuntu:
  New

Bug description:
  I don't know from where I catch that bug.
  Can U help me terminate it ?
  Thanks .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Sep  5 22:22:09 2018
  DistUpgraded: 2018-09-02 10:47:36,007 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Wrestler [Radeon HD 7340] [103c:188b]
  InstallationDate: Installed on 2018-09-01 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP 255 G1 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=41406866-69b5-46b7-b891-b3c847e2be2b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-02 (3 days ago)
  dmi.bios.date: 06/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.37
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 188B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 69.18
  dmi.chassis.asset.tag: 5CG33351SV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.37:bd06/26/2013:svnHewlett-Packard:pnHP255G1NotebookPC:pvr08881330591620110:rvnHewlett-Packard:rn188B:rvrKBCVersion69.18:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP 255 G1 Notebook PC
  dmi.product.version: 08881330591620110
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun Sep  2 03:55:29 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1790370] Re: package libavahi-common3:i386 0.7-3.1ubuntu1 failed to install/upgrade: a csomag nagyon rossz, következetlen állapotban van - újra kell telepítenie a beállítási kís

2018-09-04 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package libavahi-common3:i386 0.7-3.1ubuntu1 failed to
  install/upgrade: a csomag nagyon rossz, következetlen állapotban van -
  újra  kell telepítenie a beállítási kísérlet előtt

Status in avahi package in Ubuntu:
  New

Bug description:
  h

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libavahi-common3:i386 0.7-3.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Sep  2 18:29:31 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libavahi-common-data 0.7-3.1ubuntu1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ErrorMessage: a csomag nagyon rossz, következetlen állapotban van - újra  
kell telepítenie a beállítási kísérlet előtt
  InstallationDate: Installed on 2018-08-28 (5 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: avahi
  Title: package libavahi-common3:i386 0.7-3.1ubuntu1 failed to 
install/upgrade: a csomag nagyon rossz, következetlen állapotban van - újra  
kell telepítenie a beállítási kísérlet előtt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1788448] Re: CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11

2018-08-30 Thread Leonidas S. Barbosa
Fix update was released:  https://usn.ubuntu.com/3758-1/

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

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

Title:
  CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11

Status in libx11 package in Ubuntu:
  Fix Released

Bug description:
  There are 3 security issues reported in libx11 that are fixed upstream
  in libx11 1.6.6.

  Bugs announced:
  https://lists.x.org/archives/xorg-announce/2018-August/002915.html

  Release announcement of libx11 1.6.6 with commits fixing them listed:
  https://lists.x.org/archives/xorg-announce/2018-August/002916.html

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

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


[Touch-packages] [Bug 1788448] Re: CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11

2018-08-29 Thread Leonidas S. Barbosa
Hi Joseph!

Yep, I'm working on this. Soon as possible it'll be released/update.

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

Title:
  CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11

Status in libx11 package in Ubuntu:
  New

Bug description:
  There are 3 security issues reported in libx11 that are fixed upstream
  in libx11 1.6.6.

  Bugs announced:
  https://lists.x.org/archives/xorg-announce/2018-August/002915.html

  Release announcement of libx11 1.6.6 with commits fixing them listed:
  https://lists.x.org/archives/xorg-announce/2018-August/002916.html

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

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


[Touch-packages] [Bug 1781716] Re: package cups-daemon 2.1.3-4ubuntu0.5 failed to install/upgrade: end of file on stdin at conffile prompt

2018-07-16 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package cups-daemon 2.1.3-4ubuntu0.5 failed to install/upgrade: end of
  file on stdin at conffile prompt

Status in cups package in Ubuntu:
  New

Bug description:
  I do not know, there is a bug report, but it is the system, I do not
  understand anything

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4ubuntu0.5
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CupsErrorLog:
   
  Date: Thu Jul 12 07:47:13 2018
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2018-02-21 (142 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat:
   device for ML-1660-Series: 
usb://Samsung/ML-1660%20Series?serial=Z4S2BKDZB05423Y.
   device for Stylus-CX5600: usb://EPSON/Stylus%20CX5600?serial=0=1
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles:
   ML-1660-Series: Samsung ML-1660, 2.0.0
   Stylus-CX5600: Epson Stylus CX5600 - CUPS+Gutenprint v5.2.11
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=220f47cc-2dd0-4ffb-9a2d-677aaa1a535c ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=220f47cc-2dd0-4ffb-9a2d-677aaa1a535c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4ubuntu0.5 failed to install/upgrade: end of 
file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pam.d.cups:
   @include common-auth
   @include common-account
   @include common-session
  modified.conffile..etc.ufw.applications.d.cups:
   [CUPS]
   title=Common UNIX Printing System server
   description=CUPS is a printing system with support for IPP, samba, lpd, and 
other protocols.
   ports=631
  mtime.conffile..etc.apparmor.d.usr.sbin.cupsd: 2016-03-25T14:42:02
  mtime.conffile..etc.cups.cups-files.conf: 2016-03-25T14:41:32
  mtime.conffile..etc.init.cups.conf: 2016-03-25T14:42:00
  mtime.conffile..etc.init.d.cups: 2016-02-13T12:37:50
  mtime.conffile..etc.logrotate.d.cups-daemon: 2016-02-13T12:37:50
  mtime.conffile..etc.pam.d.cups: 2016-02-13T12:37:50
  mtime.conffile..etc.ufw.applications.d.cups: 2016-03-25T14:42:02

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

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


[Touch-packages] [Bug 1779901] Re: CVE-2018-12910

2018-07-03 Thread Leonidas S. Barbosa
https://usn.ubuntu.com/3701-1/

** Changed in: libsoup2.4 (Ubuntu Xenial)
   Status: Confirmed => Fix Released

** Changed in: libsoup2.4 (Ubuntu Artful)
   Status: Confirmed => Fix Released

** Changed in: libsoup2.4 (Ubuntu Bionic)
   Status: Confirmed => Fix Released

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

Title:
  CVE-2018-12910

Status in libsoup2.4 package in Ubuntu:
  Fix Released
Status in libsoup2.4 source package in Xenial:
  Fix Released
Status in libsoup2.4 source package in Artful:
  Fix Released
Status in libsoup2.4 source package in Bionic:
  Fix Released

Bug description:
  If you have appropriate permissions, you can view details at the
  following links:

  https://gitlab.gnome.org/GNOME/libsoup/issues/3
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12910

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1779901/+subscriptions

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


[Touch-packages] [Bug 1779901] Re: CVE-2018-12910

2018-07-03 Thread Leonidas S. Barbosa
Hi,

We already have updates going through QA. Soon as possibly they'll be
published.

Thanks!

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

Title:
  CVE-2018-12910

Status in libsoup2.4 package in Ubuntu:
  Fix Released
Status in libsoup2.4 source package in Xenial:
  Confirmed
Status in libsoup2.4 source package in Artful:
  Confirmed
Status in libsoup2.4 source package in Bionic:
  Confirmed

Bug description:
  If you have appropriate permissions, you can view details at the
  following links:

  https://gitlab.gnome.org/GNOME/libsoup/issues/3
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12910

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1779901/+subscriptions

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


[Touch-packages] [Bug 1776860] Re: package linux-image-4.15.0-23-generic 4.15.0-23.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127

2018-06-14 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package linux-image-4.15.0-23-generic 4.15.0-23.25 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal
  exited with return code 127

Status in apt package in Ubuntu:
  New

Bug description:
  ???

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fred   1439 F pulseaudio
   /dev/snd/controlC2:  fred   1439 F pulseaudio
   /dev/snd/controlC0:  fred   1439 F pulseaudio
  Date: Thu Jun 14 10:38:07 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 127
  InstallationDate: Installed on 2018-05-29 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: HP-Pavilion VN433AA-ABF p6235fr
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=cde7b5ab-35ce-4bcf-8860-4a9b313d78e9 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8
  RfKill:
   
  SourcePackage: apt
  Title: package linux-image-4.15.0-23-generic 4.15.0-23.25 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.14
  dmi.board.name: Eureka3
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: Asset-1234
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.14:bd11/13/2009:svnHP-Pavilion:pnVN433AA-ABFp6235fr:pvr:rvnPEGATRONCORPORATION:rnEureka3:rvr1.02:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.family: 103C_53316J
  dmi.product.name: VN433AA-ABF p6235fr
  dmi.sys.vendor: HP-Pavilion

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

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


[Touch-packages] [Bug 1776098] Re: package patch 2.7.5-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2018-06-11 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package patch 2.7.5-1ubuntu0.16.04.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in patch package in Ubuntu:
  New

Bug description:
  no idea about this bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: patch 2.7.5-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-116.140-lowlatency 4.4.98
  Uname: Linux 4.4.0-116-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Jun 10 23:47:14 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu10
   libgcc1 1:6.0.1-0ubuntu1
  DpkgHistoryLog:
   Start-Date: 2018-06-10  23:47:03
   Commandline: apt-get install -f
   Requested-By: dhiliptg (1000)
   Upgrade: update-notifier-common:amd64 (3.168.7, 3.168.8)
  DpkgTerminalLog:
   Preparing to unpack .../update-notifier-common_3.168.8_all.deb ...
   Unpacking update-notifier-common (3.168.8) over (3.168.7) ...
   dpkg: error processing package patch (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature:
   package:patch:2.7.5-1ubuntu0.16.04.1
   Unpacking update-notifier-common (3.168.8) over (3.168.7) ...
   dpkg: error processing package patch (--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 2016-11-17 (570 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: patch
  Title: package patch 2.7.5-1ubuntu0.16.04.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1770290] Re: package openssh-server 1:7.6p1-4 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Broken pipe)

2018-05-10 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package openssh-server 1:7.6p1-4 failed to install/upgrade: installed
  openssh-server package post-installation script subprocess was killed
  by signal (Broken pipe)

Status in openssh package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May 10 05:37:21 2018
  DuplicateSignature:
   package:openssh-server:1:7.6p1-4
   Setting up openssh-server (1:7.6p1-4) ...
   dpkg: error processing package openssh-server (--configure):
installed openssh-server package post-installation script subprocess was 
killed by signal (Broken pipe)
  ErrorMessage: installed openssh-server package post-installation script 
subprocess was killed by signal (Broken pipe)
  InstallationDate: Installed on 2018-02-17 (81 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config: No such file or directory
  SourcePackage: openssh
  Title: package openssh-server 1:7.6p1-4 failed to install/upgrade: installed 
openssh-server package post-installation script subprocess was killed by signal 
(Broken pipe)
  UpgradeStatus: Upgraded to bionic on 2018-05-08 (1 days ago)

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

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


[Touch-packages] [Bug 1769368] Re: package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to install/upgrade: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de

2018-05-07 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to
  install/upgrade: el paquete está en un estado muy malo e inconsistente
  - debe reinstalarlo  antes de intentar desinstalarlo.

Status in opencv package in Ubuntu:
  New

Bug description:
  Estaba haciendo un sudo apt-get autoremove

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sat May  5 10:54:05 2018
  DpkgTerminalLog:
   dpkg: error al procesar el paquete libopencv-contrib3.2:amd64 (--remove):
el paquete está en un estado muy malo e inconsistente - debe reinstalarlo
antes de intentar desinstalarlo.
  ErrorMessage: el paquete está en un estado muy malo e inconsistente - debe 
reinstalarlo  antes de intentar desinstalarlo.
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No existe el archivo o el directorio: "/root/Error: 
command ['which', 'python'] failed with exit code 1:": "/root/Error: command 
['which', 'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: opencv
  Title: package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to 
install/upgrade: el paquete está en un estado muy malo e inconsistente - debe 
reinstalarlo  antes de intentar desinstalarlo.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1769369] Re: package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to install/upgrade: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de

2018-05-07 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to
  install/upgrade: el paquete está en un estado muy malo e inconsistente
  - debe reinstalarlo  antes de intentar desinstalarlo.

Status in opencv package in Ubuntu:
  New

Bug description:
  Estaba haciendo un sudo apt-get autoremove

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sat May  5 10:54:05 2018
  DpkgTerminalLog:
   dpkg: error al procesar el paquete libopencv-contrib3.2:amd64 (--remove):
el paquete está en un estado muy malo e inconsistente - debe reinstalarlo
antes de intentar desinstalarlo.
  ErrorMessage: el paquete está en un estado muy malo e inconsistente - debe 
reinstalarlo  antes de intentar desinstalarlo.
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No existe el archivo o el directorio: "/root/Error: 
command ['which', 'python'] failed with exit code 1:": "/root/Error: command 
['which', 'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: opencv
  Title: package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to 
install/upgrade: el paquete está en un estado muy malo e inconsistente - debe 
reinstalarlo  antes de intentar desinstalarlo.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1769370] Re: package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to install/upgrade: el paquete está en un estado muy malo e inconsistente - debe reinstalarlo antes de

2018-05-07 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to
  install/upgrade: el paquete está en un estado muy malo e inconsistente
  - debe reinstalarlo  antes de intentar desinstalarlo.

Status in opencv package in Ubuntu:
  New

Bug description:
  Estaba haciendo un sudo apt-get autoremove

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sat May  5 10:54:05 2018
  DpkgTerminalLog:
   dpkg: error al procesar el paquete libopencv-contrib3.2:amd64 (--remove):
el paquete está en un estado muy malo e inconsistente - debe reinstalarlo
antes de intentar desinstalarlo.
  ErrorMessage: el paquete está en un estado muy malo e inconsistente - debe 
reinstalarlo  antes de intentar desinstalarlo.
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No existe el archivo o el directorio: "/root/Error: 
command ['which', 'python'] failed with exit code 1:": "/root/Error: command 
['which', 'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: opencv
  Title: package libopencv-contrib3.2:amd64 3.2.0+dfsg-4build2 failed to 
install/upgrade: el paquete está en un estado muy malo e inconsistente - debe 
reinstalarlo  antes de intentar desinstalarlo.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1769375] Re: package gstreamer1.0-opencv:amd64 1.14.0-1ubuntu1 failed to install/upgrade: problemas de dependencias - se deja sin configurar

2018-05-07 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package gstreamer1.0-opencv:amd64 1.14.0-1ubuntu1 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

Status in gst-plugins-bad1.0 package in Ubuntu:
  New

Bug description:
  No estaba haciendo nada, solo salió ese mensaje

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-opencv:amd64 1.14.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   libgstreamer-opencv1.0-0:amd64: Install
   gstreamer1.0-opencv:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  5 11:19:05 2018
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No existe el archivo o el directorio: "/root/Error: 
command ['which', 'python'] failed with exit code 1:": "/root/Error: command 
['which', 'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: gst-plugins-bad1.0
  Title: package gstreamer1.0-opencv:amd64 1.14.0-1ubuntu1 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1769375/+subscriptions

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


[Touch-packages] [Bug 1769500] Re: will not update

2018-05-07 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  will not update

Status in xorg package in Ubuntu:
  New

Bug description:
  will not update. Gives error msg public key 8BAF9A6F

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun May  6 15:07:21 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6250] [1002:9804] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Wrestler [Radeon HD 6250] [103c:3577]
  InstallationDate: Installed on 2017-11-26 (161 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=ed27f603-858e-45f5-9ba1-0b1789b36c0f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.48
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.4A
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.48:bd12/18/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068C11000320491620100:rvnHewlett-Packard:rn3577:rvr24.4A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=CO S=PRE
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 068C11000320491620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat May  5 13:58:50 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1761267] Re: issue is regarding boot hanging between work

2018-04-04 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  issue is regarding boot hanging between work

Status in xorg package in Ubuntu:
  New

Bug description:
  while getting started it is hanged and sometime it doesnot open the
  required folder any software downloaded from internet is not installed
  in "exe." file especially sometime keyboard stops working

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   UBUNTU: clean, 272012/29777920 files, 3537812/119111424 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Apr  4 23:11:32 2018
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0767]
  InstallationDate: Installed on 2018-02-22 (41 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=a581e6e4-3ec8-44a1-96df-744ef70e8b7e ro acpi_rev_override locale=en_US
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 0C6XG5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn0C6XG5:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 5567
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr  4 20:29:12 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1317 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1761084] Re: NA

2018-04-04 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  NA

Status in xorg package in Ubuntu:
  New

Bug description:
  NA

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Apr  4 12:48:47 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:3809]
  InstallationDate: Installed on 2018-03-04 (31 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 04f2:b50e Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80Q7
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed 
root=UUID=6443b635-7581-4cac-989d-220941f038da ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D5CN47WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Paris 5A8
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 300-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrD5CN47WW:bd08/26/2016:svnLENOVO:pn80Q7:pvrLenovoideapad300-15ISK:rvnLENOVO:rnParis5A8:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad300-15ISK:
  dmi.product.name: 80Q7
  dmi.product.version: Lenovo ideapad 300-15ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr  4 15:51:47 2018
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5574 
   vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1760411] Re: I don know

2018-04-02 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  I don know

Status in xorg package in Ubuntu:
  New

Bug description:
  i don know

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Apr  1 16:29:14 2018
  DistUpgraded: 2018-03-31 14:06:35,805 DEBUG /openCache(), new cache size 86473
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.1.34, 4.13.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:80c1]
  InstallationDate: Installed on 2018-03-26 (5 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: HP HP Notebook
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2018-03-31 (1 days ago)
  dmi.bios.date: 10/27/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C1
  dmi.board.vendor: HP
  dmi.board.version: 96.51
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd10/27/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn80C1:rvr96.51:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Mar 31 13:56:55 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1752728] Re: My pc is going in blank after sleep and nothing works

2018-03-02 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  My pc is going in blank after sleep and nothing works

Status in xorg package in Ubuntu:
  New

Bug description:
  My pc is going in blank after sleep and nothing works

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Mar  1 17:12:11 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Subsystem: Dell Device [1028:0774]
   NVIDIA Corporation Device [10de:1c60] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07c0]
  InstallationDate: Installed on 2017-09-27 (155 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Alienware Alienware 15 R3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed 
root=UUID=55e321af-6860-4c50-a132-9e8fe6024cd7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2017
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.0
  dmi.board.name: Alienware 15 R3
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.2.0:bd09/14/2017:svnAlienware:pnAlienware15R3:pvr1.2.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware 15 R3
  dmi.product.version: 1.2.0
  dmi.sys.vendor: Alienware
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Touch-packages] [Bug 1752269] Re: package linux-image-extra-4.13.0-36-generic 4.13.0-36.40~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code

2018-02-28 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package linux-image-extra-4.13.0-36-generic 4.13.0-36.40~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:
  sudo dpkg --configure -a executed the bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.13.0-36-generic 4.13.0-36.40~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Feb 28 09:44:33 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2018-02-27 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.13.0-36-generic 4.13.0-36.40~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/1752269/+subscriptions

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


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

2018-01-26 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

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

Status in curl package in Ubuntu:
  New

Bug description:
  Not too sure

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: curl 7.35.0-1ubuntu2.13
  ProcVersionSignature: Ubuntu 3.13.0-141.190-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-141-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Fri Jan 26 20:23:37 2018
  DuplicateSignature: package:curl:7.35.0-1ubuntu2.13:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-11-09 (808 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: curl
  Title: package curl 7.35.0-1ubuntu2.13 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/curl/+bug/1745605/+subscriptions

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


[Touch-packages] [Bug 1741262] [NEW] regression in dnsmasq breaks DNS resolution for precise ESM

2018-01-04 Thread Leonidas S. Barbosa
untu.com/ubuntu/ precise/main amd64 Packages
 *** 2.59-4ubuntu0.2 0
500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 
Packages
100 /var/lib/dpkg/status

** Affects: dnsmasq (Ubuntu)
 Importance: Medium
 Assignee: Leonidas S. Barbosa (leosilvab)
 Status: In Progress

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

** Information type changed from Public to Private Security

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

** Changed in: dnsmasq (Ubuntu)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

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

Title:
  regression in dnsmasq  breaks DNS resolution for precise ESM

Status in dnsmasq package in Ubuntu:
  In Progress

Bug description:
  Haw Loeung reports the follow issue in dnsmasq

  ubuntu@instance-lcy01:~$ host www.googleapis.com
  ;; Warning: Message parser reports malformed message packet.
  ;; Warning: Message parser reports malformed message packet.
  www.googleapis.com is an alias for googleapis.l.google.com.
  ubuntu@instance-lcy01:$ grep nameserver /etc/resolv.conf
  nameserver 10.55.60.1

  ubuntu@instance-lcy02:~$ host www.googleapis.com
  ;; Warning: Message parser reports malformed message packet.
  ;; Warning: Message parser reports malformed message packet.
  www.googleapis.com is an alias for googleapis.l.google.com.
  ubuntu@instance-lcy02:~$ grep nameserver /etc/resolv.conf
  nameserver 10.55.32.1

  [hloeung@silver ~]$ host www.googleapis.com 10.55.32.1 | grep Warning
  ;; Warning: Message parser reports malformed message packet.
  ;; Warning: Message parser reports malformed message packet.

  [hloeung@silver ~]$ host www.googleapis.com 10.55.59.1 | grep Warning
  [hloeung@silver ~]$ host www.googleapis.com 10.55.59.1 | grep Warning
  [hloeung@silver ~]$ host www.googleapis.com 10.55.59.1 | grep Warning
  [hloeung@silver ~]$ host www.googleapis.com 10.55.59.1 | grep Warning

  
  [hloeung@dziban ~]$ host www.googleapis.com 10.55.60.1 | grep Warning
  ;; Warning: Message parser reports malformed message packet.
  ;; Warning: Message parser reports malformed message packet.

  [hloeung@dziban ~]$ host www.googleapis.com 10.55.59.1 | grep Warning
  [hloeung@dziban ~]$ host www.googleapis.com 10.55.59.1 | grep Warning
  [hloeung@dziban ~]$ host www.googleapis.com 10.55.59.1 | grep Warning

  
  [hloeung@dziban ~]$ apt-cache policy dnsmasq-base
  dnsmasq-base:
Installed: 2.59-4ubuntu0.3

  [hloeung@silver ~]$ apt-cache policy dnsmasq-base
  dnsmasq-base:
Installed: 2.59-4ubuntu0.3
Candidate: 2.59-4ubuntu0.3
Version table:
   *** 2.59-4ubuntu0.3 0
  500 https://esm.ubuntu.com/ubuntu/ precise/main amd64 Packages

  
  [hloeung@silver ~]$ dig +tcp a www.googleapis.com @10.55.32.1
  ;; Warning: Message parser reports malformed message packet.
  ...
  ;; WARNING: Messages has 109 extra bytes at end
  ...
  ;; MSG SIZE  rcvd: 157

  [hloeung@silver ~]$ sudo strace -f -p 2418 -s 1024 2>&1 | grep googleapis 
-B3 -A3
  [pid 11479] getpeername(10, {sa_family=AF_INET, sin_port=htons(33976), 
sin_addr=inet_addr("10.55.32.1")}, [16]) = 0
  [pid 11479] read(10, "\0", 1)   = 1
  [pid 11479] read(10, "$", 1)= 1
  [pid 11479] read(10, 
"\334r\1\0\0\1\0\0\0\0\0\0\3www\ngoogleapis\3com\0\0\1\0\1", 36) = 36
  [pid 11479] write(10, "\0", 1)  = 1
  [pid 11479] write(10, "\235", 1)= 1
  [pid 11479] write(10, 
"\334r\201\200\0\1\0\6\0\0\0\0\3www\ngoogleapis\3com\0\0\1\0\1\300\f\0\5\0\1\0\0\10\2\0\35\ngoogleapis.\1l.\6google.\3com\0\0\3000\0\1\0\1\0\0\0%\0\4\330:\301J\3000\0\1\0\1\0\0\0%\0\4\254\331\3\312\3000\0\1\0\1\0\0\0%\0\4\254\331\3\252\3000\0\1\0\1\0\0\0%\0\4\330:\330\252\3000\0\1\0\1\0\0\0%\0\4\330:\330\212",
 157) = 157
  [pid 11479] read(10, "", 1) = 0
  [pid 11479] shutdown(10, 2 /* send and receive */) = 0
  [pid 11479] close(10)   = 0
  --
  [pid 11491] getpeername(10, {sa_family=AF_INET, sin_port=htons(54452), 
sin_addr=inet_addr("10.55.32.1")}, [16]) = 0
  [pid 11491] read(10, "\0", 1)   = 1
  [pid 11491] read(10, "$", 1)= 1
  [pid 11491] read(10, 
"\352t\1\0\0\1\0\0\0\0\0\0\3www\ngoogleapis\3com\0\0\1\0\1", 36) = 36
  [pid 11491] write(10, "\0", 1)  = 1
  [pid 11491] write(10, "\235", 1)= 1
  [pid 11491] write(10, 
"\352t\201\200\0\1\0\6\0\0\0\0\3www\ngoogleapis\3com\0\0\1\0\1\300\f\0\5\0\1\0\0\10\1\0\35\ngoogleapis.\1l.\6google.\3com\0\0\3000\0\1\0\1\0\0\0$\0\4\330:\301J\3000\0\1\0\1\0\0\0$\0\4\254\331\3\312\3000\0\1\0\1\0\0\0$\0\4\254\331\3\252\300

[Touch-packages] [Bug 1738382] Re: package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2017-12-15 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  apport:
Installed: 2.20.1-0ubuntu2.13
Candidate: 2.20.1-0ubuntu2.14
Version table:
   2.20.1-0ubuntu2.14 500
  500 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://in.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
   *** 2.20.1-0ubuntu2.13 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   2.20.1-0ubuntu2 500
  500 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://in.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  
  The system reported this bug to me at start-up.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.13
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Fri Dec 15 06:24:34 2017
  DuplicateSignature:
   package:apport:2.20.1-0ubuntu2.13
   Unpacking linux-headers-generic-hwe-16.04 (4.10.0.42.44) over (4.10.0.40.42) 
...
   dpkg: error processing package apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-08-28 (108 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.13 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/apport/+bug/1738382/+subscriptions

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


[Touch-packages] [Bug 1737803] Re: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-12-12 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  im not sure about the cause of the issue.. i upgraded from ubuntu 14
  to 16.. from the first launch im getting this issue

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.8
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  Date: Tue Dec 12 23:47:05 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-10-29 (44 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-12-12 (0 days ago)

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

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


[Touch-packages] [Bug 1737544] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu9.3 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de

2017-12-11 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu9.3 failed to install/upgrade:
  le paquet est dans un état vraiment incohérent; vous devriez  le
  réinstaller avant de tenter de le configurer.

Status in openssl package in Ubuntu:
  New

Bug description:
  wifi doesn't work anymore

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu9.3
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.7
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Mon Dec 11 14:02:32 2017
  DpkgHistoryLog:
   Start-Date: 2017-12-11  14:02:32
   Commandline: apt-get upgrade
   Requested-By: niko (1000)
  DpkgTerminalLog:
   dpkg: erreur de traitement du paquet libssl1.0.0:i386 (--configure) :
le paquet est dans un état vraiment incohérent; vous devriez
le réinstaller avant de tenter de le configurer.
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2016-06-27 (532 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu9.3 failed to install/upgrade: 
le paquet est dans un état vraiment incohérent; vous devriez  le réinstaller 
avant de tenter de le configurer.
  UpgradeStatus: Upgraded to yakkety on 2017-04-29 (226 days ago)

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

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


[Touch-packages] [Bug 1728988] Re: poppler crashes on this file

2017-10-31 Thread Leonidas S. Barbosa
Ways to reproduce using poppler-utils:

pdftocairo -q -svg print2s.pdf

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

Title:
  poppler crashes on this file

Status in cairo package in Ubuntu:
  Confirmed
Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  When opening the PDF file available at:
  https://mega.nz/#!QUlxRabb!CkbkbKanfjFCO6OaKCoFq2_yHoIWChV-ruc3PHB87E8

  evince/pdftocairo are core dumping.

  As far as I can tell it's because the underlying lib (cairo/poppler)
  has a bug.

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

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


[Touch-packages] [Bug 1728988] Re: poppler crashes on this file

2017-10-31 Thread Leonidas S. Barbosa
It seems to be a known bug in cairo. Here is the fix. I'll also make this 
public.
https://cgit.freedesktop.org/cairo/commit/?id=5fd0b8710f125bb33c55d75fcc8252996b403e2d

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

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

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

** Information type changed from Private Security to Public Security

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

Title:
  poppler crashes on this file

Status in cairo package in Ubuntu:
  Confirmed
Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  When opening the PDF file available at:
  https://mega.nz/#!QUlxRabb!CkbkbKanfjFCO6OaKCoFq2_yHoIWChV-ruc3PHB87E8

  evince/pdftocairo are core dumping.

  As far as I can tell it's because the underlying lib (cairo/poppler)
  has a bug.

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

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


  1   2   >