date:20190222

Public bug reported:

Hi guys

There is an option for livepacth, but there is information that is not
yet available for Ubuntu Disk 19.04. Will the livepatch be available for
Ubuntu Disk 19.04?

"Livepacth is not available for this system"

See attached

Thank you

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: software-properties-gtk 0.97.6
ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
Uname: Linux 4.19.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 22 14:08:04 2019
ExecutablePath: /usr/bin/software-properties-gtk
InstallationDate: Installed on 2019-02-11 (10 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
InterpreterPath: /usr/bin/python3.7
PackageArchitecture: all
Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1
PythonDetails: /usr/bin/python2.7, Python 2.7.16rc1, python-minimal, 2.7.15-4
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

** Attachment added: "Livepacth is not available for this system"
   
https://bugs.launchpad.net/bugs/1817352/+attachment/5240994/+files/Captura%20de%20tela%20de%202019-02-22%2014-12-22.png

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

Title:
  Livepacth is not available for this system Ubuntu Disco 19.04

Status in software-properties package in Ubuntu:
  New

Bug description:
  Hi guys

  There is an option for livepacth, but there is information that is not
  yet available for Ubuntu Disk 19.04. Will the livepatch be available
  for Ubuntu Disk 19.04?

  "Livepacth is not available for this system"

  See attached

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: software-properties-gtk 0.97.6
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 22 14:08:04 2019
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-02-11 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16rc1, python-minimal, 2.7.15-4
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1817302] Re: growpart changes diskid of mbr disks

2019-02-22 Thread Juerg Haefliger

On 32-bit sfdisk fails to parse the label-id if the MSB is set and thus
generates a new one. We happen to be unlucky with our (i386) cloud image
in that the original label-id has the MSB set. So when growpart run
(which calls sfdisk), the disk ID is regenerated and subsequent boots
fail because the kernel can't find the root device.


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

** No longer affects: cloud-utils (Ubuntu)

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

Title:
  growpart changes diskid of mbr disks

Status in util-linux package in Ubuntu:
  New

Bug description:
  When growpart is run against a disk with a dos partition table, it
  evidently changes the disk id in the MBR.  This was noticed because
  the diskid is part of the "PARTUUID" that is synthesized for DOS
  partitions (unlike GPT, which has UUIDs for each partition as part of
  the partition table).

  This means that if someone is using root=PARTUUID=foo on the kernel
  commandline, the cloud image will successfully boot exactly once, and
  subsequently fail to boot because the partition uuid has changed.

  I don't know at this point if this is a bug in cloud-utils or in
  sfdisk (util-linux).

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

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

[Touch-packages] [Bug 1817302] Re: growpart changes diskid of mbr disks

2019-02-22 Thread Juerg Haefliger

https://lore.kernel.org/util-
linux/20190222160412.26652-1-jue...@canonical.com

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

Title:
  growpart changes diskid of mbr disks

Status in util-linux package in Ubuntu:
  New

Bug description:
  When growpart is run against a disk with a dos partition table, it
  evidently changes the disk id in the MBR.  This was noticed because
  the diskid is part of the "PARTUUID" that is synthesized for DOS
  partitions (unlike GPT, which has UUIDs for each partition as part of
  the partition table).

  This means that if someone is using root=PARTUUID=foo on the kernel
  commandline, the cloud image will successfully boot exactly once, and
  subsequently fail to boot because the partition uuid has changed.

  I don't know at this point if this is a bug in cloud-utils or in
  sfdisk (util-linux).

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

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

[Touch-packages] [Bug 1817338] [NEW] HDMI sound output not available

2019-02-22 Thread Franck

Public bug reported:

In 19.04, HDMI sound stopped working after some upgrade.

The sink is somehow availalbe, but cannot be selected.
In gnome-control-center, HDMI output device is listed, but if I choose it, no 
configuration list appears (see screen capture attached).

aplay -l gives me:
~$ aplay -l
 Liste des Périphériques Matériels PLAYBACK 
carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog]
  Sous-périphériques: 0/1
  Sous-périphérique #0: subdevice #0
carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0
carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2]
  Sous-périphériques: 1/1
  Sous-périphérique #0: subdevice #0

pavucontrol shows HDMI as unplugged.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: pulseaudio 1:12.2-2ubuntu1
ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
Uname: Linux 4.19.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  franck 5998 F pulseaudio
 /dev/snd/pcmC1D0c:   franck 5998 F...m pulseaudio
 /dev/snd/controlC0:  franck 5998 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Feb 22 16:16:56 2019
EcryptfsInUse: Yes
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/27/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: G7ETA9WW (2.69 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2353CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T430s
dmi.product.name: 2353CTO
dmi.product.sku: LENOVO_MT_2353
dmi.product.version: ThinkPad T430s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug disco wayland-session

** Attachment added: "gnome-control-center not showing configuration options 
for HDMI"
   
https://bugs.launchpad.net/bugs/1817338/+attachment/5240948/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202019-02-22%2016-24-51.png

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

Title:
  HDMI sound output not available

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  In 19.04, HDMI sound stopped working after some upgrade.

  The sink is somehow availalbe, but cannot be selected.
  In gnome-control-center, HDMI output device is listed, but if I choose it, no 
configuration list appears (see screen capture attached).

  aplay -l gives me:
  ~$ aplay -l
   Liste des Périphériques Matériels PLAYBACK 
  carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC 
Analog]
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0

  pavucontrol shows HDMI as unplugged.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  franck 5998 F pulseaudio
   /dev/snd/pcmC1D0c:   franck 5998 F...m pulseaudio
   /dev/snd/controlC0:  franck 5998 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 22 16:16:56 2019
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ETA9WW (2.69 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2353CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information

[Touch-packages] [Bug 1817317] Re: OpenSSH is not "OpenBSD Secure Shell" and never be. /etc/init.d/ssh

2019-02-22 Thread Hocus Pocus

forgot to put complete patch

--- openssh-server.ssh.init 2018-11-07 22:52:49.0 +0900
+++ openssh-server.ssh.init.new 2019-02-23 00:13:24.329123504 +0900
@@ -6,12 +6,12 @@
 # Required-Stop:   $remote_fs $syslog
 # Default-Start:   2 3 4 5
 # Default-Stop:
-# Short-Description:   OpenBSD Secure Shell server
+# Short-Description:   OpenSSH server
 ### END INIT INFO
 
 set -e
 
-# /etc/init.d/ssh: start and stop the OpenBSD "secure shell(tm)" daemon
+# /etc/init.d/ssh: start and stop the OpenSSH daemon
 
 test -x /usr/sbin/sshd || exit 0
 ( /usr/sbin/sshd -\? 2>&1 | grep -q OpenSSH ) 2>/dev/null || exit 0
@@ -40,7 +40,7 @@
log_end_msg 0 || true
fi
if ! run_by_init; then
-   log_action_msg "OpenBSD Secure Shell server not in use 
(/etc/ssh/sshd_not_to_be_run)" || true
+   log_action_msg "OpenSSH server not in use 
(/etc/ssh/sshd_not_to_be_run)" || true
fi
exit 0
 fi
@@ -79,7 +79,7 @@
check_privsep_dir
check_for_no_start
check_dev_null
-   log_daemon_msg "Starting OpenBSD Secure Shell server" "sshd" || true
+   log_daemon_msg "Starting OpenSSH server" "sshd" || true
if start-stop-daemon --start --quiet --oknodo --pidfile /run/sshd.pid 
--exec /usr/sbin/sshd -- $SSHD_OPTS; then
log_end_msg 0 || true
else
@@ -87,7 +87,7 @@
fi
;;
   stop)
-   log_daemon_msg "Stopping OpenBSD Secure Shell server" "sshd" || true
+   log_daemon_msg "Stopping OpenSSH server" "sshd" || true
if start-stop-daemon --stop --quiet --oknodo --pidfile /run/sshd.pid; 
then
log_end_msg 0 || true
else
@@ -98,7 +98,7 @@
   reload|force-reload)
check_for_no_start
check_config
-   log_daemon_msg "Reloading OpenBSD Secure Shell server's configuration" 
"sshd" || true
+   log_daemon_msg "Reloading OpenSSH server's configuration" "sshd" || true
if start-stop-daemon --stop --signal 1 --quiet --oknodo --pidfile 
/run/sshd.pid --exec /usr/sbin/sshd; then
log_end_msg 0 || true
else
@@ -109,7 +109,7 @@
   restart)
check_privsep_dir
check_config
-   log_daemon_msg "Restarting OpenBSD Secure Shell server" "sshd" || true
+   log_daemon_msg "Restarting OpenSSH server" "sshd" || true
start-stop-daemon --stop --quiet --oknodo --retry 30 --pidfile 
/run/sshd.pid
check_for_no_start log_end_msg
check_dev_null log_end_msg
@@ -123,7 +123,7 @@
   try-restart)
check_privsep_dir
check_config
-   log_daemon_msg "Restarting OpenBSD Secure Shell server" "sshd" || true
+   log_daemon_msg "Restarting OpenSSH server" "sshd" || true
RET=0
start-stop-daemon --stop --quiet --retry 30 --pidfile /run/sshd.pid || 
RET="$?"
case $RET in

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

Title:
  OpenSSH is not "OpenBSD Secure Shell" and never be. /etc/init.d/ssh

Status in openssh package in Ubuntu:
  New

Bug description:
  openssh-server.ssh.init.new
  --- openssh-server.ssh.init 2018-11-07 22:52:49.0 +0900
  +++ openssh-server.ssh.init.new 2019-02-22 21:50:05.010233405 +0900
  @@ -6,7 +6,7 @@
   # Required-Stop:   $remote_fs $syslog
   # Default-Start:   2 3 4 5
   # Default-Stop:
  -# Short-Description:   OpenBSD Secure Shell server
  +# Short-Description:   OpenSSH server
   ### END INIT INFO
   
   set -e

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

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

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

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

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

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

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

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of multiple packages into the security pocket as well.

  The packages are being build on PPAs under the
  https://launchpad.net/~openjdk-11-transition team. The PPAs depend
  solely on the security pocket and are separated in stages.

  The agreed process among foundations and the security team is that
  packages in the PPAs will be binary copied into bionic-proposed,
  checked for migration issues, and - no issues pending - copied into
  bionic-security.

  NOTE TO SRU MEMBERS: The packages are to be released into bionic-
  security ONLY. This will be done/decided by the security team.

  A few packages might also need to be updated in Cosmic, but as an
  exception that will be done after the Bionic transition is worked out.

  [2019-02-21]
  Packages in stage 1 and stage 2 have been verified by the security team and 
are ready to be copied into bionic-proposed.

  Notes:
   - jtreg and testng are new versions required as build dependencies of 
openjdk-11
   - all other packages are backports that must be build/bootstrapped with 
openjdk-10

  PPAs:
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2

  Please copy them in the following order/grouping.

  Group 1:
  * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 2:
  * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05)
  * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05)

  Please upload libcommons-lang3-java from stage 2 (ignore the version
  in stage 1).

  Group 3:
  * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06)
  * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx 
(2019-02-05)
  * surefire 2.22.0-1~18.04.1 Tiago Stürmer

[Touch-packages] [Bug 1817033] Re: Unable to correctly print PDF file: Error: Ignoring spurious ET operator.

2019-02-22 Thread Sebastien Bacher

The fix has been backported/uploaded to Debian and will be synced to
Ubuntu later today. It would probably also be a good candidate for SRUs

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

** Changed in: cairo (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Unable to correctly print PDF file: Error: Ignoring spurious ET
  operator.

Status in cairo package in Ubuntu:
  Fix Committed

Bug description:
  Upstream bug report https://github.com/OpenPrinting/cups-
  filters/issues/93.

  The university document
  [antrag_exmatrikulation.pdf](https://github.com/OpenPrinting/cups-
  filters/files/2881078/antrag_exmatrikulation.pdf) causes problems on
  different printers.

  Printing on the Canon iR-ADV C2225i using the Canon PCL, an error page
  is first printed, and on the first page after _Email_ everything is
  missing. The second page is fine.

  ```
    Error: Ignoring spurious ET operator. Output may be inco 
  ```

  For that printer a special filter `sicgsfilter` has to be used, and is
  distributed by Canon. This also happens with their CQue 4.0-1 release
  from September 2018.

  ```
   *FoomaticRIPCommandLine: "gs -q -dBATCH %F -dPARANOIDSAFER -dNOPAUSE %B%A%C 
-dPDFFitPage  -sOutputFile=- - %D%E | sicgsfilter -MPCL -NP %G%H%I -u 
-V -n "
  ```

  On the Epson printer _WorkForce WF-2660_, no error page is printed,
  but on the first page everything after _Email_ _is missing_ too.

  Trying to use different pdftops renderers did not make any difference.
  For example,

  ```
   lpr -o pdftops-renderer=pdftops -P chipprinterpcl antrag_exmatrikulation.pdf
  ```

  gave the same result, the same with `pdftocairo`, `acroread`, `mupdf`.

  Following `/usr/share/doc/cups-filters/README.gz` and
  https://wiki.ubuntu.com/DebuggingPrintingProblems, I verified that the
  exact same PDF is put into the CUPS spool directory, and I captured
  the data sent to the printer with the commands below.

  $ lpadmin -p chipprinterpclfile -E -v file:/tmp/printout -P 
~/chipprinterpcl.ppd
  $ lpr -P chipprinterpclfile -o psdebug ~/antrag_exmatrikulation.pdf

  I get the attached Postscript file, which indeed contains the error
  messages.

  ```
  ESC%-12345X@PJL CQue4.0-1 x86_64
  @PJL COMMENT CANPJL SET USERNAME="pmenzel@localhost"
  @PJL COMMENT CANPJL SET DOCNAME="antrag_exmatrikulation.pdf!pmenz"
  @PJL SET RENDERMODE=COLOR
  @PJL COMMENT CANPJL SET FORCEMONOCHROME=FALSE
  @PJL COMMENT CANPJL SET SORTERMODE=GENERICON
  @PJL COMMENT CANPJL SET STAPLE=GENERICOFF
  @PJL COMMENT CANPJL SET BOOKLET=GENERICOFF
  @PJL SET DENSITY=0
  @PJL ENTER LANGUAGE=PCL
  Error: Ignoring spurious ET operator.
 Output may be incorrect.
  Error: Executing Do inside a text block, attempting to recover
 Output may be incorrect.
  Error: Executing Do inside a text block, attempting to recover
 Output may be incorrect.
  Error: Ignoring spurious ET operator.
 Output may be incorrect.
  Error: Executing Do inside a text block, attempting to recover
 Output may be incorrect.
  Error: illegal nested BT operator detected.
 Output may be incorrect.
  Error: Ignoring spurious ET operator.
 Output may be incorrect.
  Error: Executing Do inside a text block, attempting to recover
 Output may be incorrect.
  Error: illegal nested BT operator detected.
 Output may be incorrect.
  […]
  ```

  Please find that file attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: cups 2.2.8-5ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  Date: Thu Feb 21 10:23:08 2019
  InstallationDate: Installed on 2017-03-20 (702 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lpstat:
   device for Canon-iR-ADV-C2225: lpd://winprima.molgen.mpg.de/test
   device for DCP375CW: socket://141.14.220.198
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04f3:2234 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Papersize: a4
  PpdFiles:
   Canon-iR-ADV-C2225: Canon iR-ADV C2225 PCL
   DCP375CW: Brother DCP-375CW CUPS
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash initcall_debug log_buf_len=16M 
vt.handoff=1
  SourcePackage: cups
  UpgradeStatus:

[Touch-packages] [Bug 1814133]

affects Ubuntu/jabref
affects Ubuntu/scilab
affects Ubuntu/scilab
affects Ubuntu/pdfsam

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of multiple packages into the security pocket as well.

  The packages are being build on PPAs under the
  https://launchpad.net/~openjdk-11-transition team. The PPAs depend
  solely on the security pocket and are separated in stages.

  The agreed process among foundations and the security team is that
  packages in the PPAs will be binary copied into bionic-proposed,
  checked for migration issues, and - no issues pending - copied into
  bionic-security.

  NOTE TO SRU MEMBERS: The packages are to be released into bionic-
  security ONLY. This will be done/decided by the security team.

  A few packages might also need to be updated in Cosmic, but as an
  exception that will be done after the Bionic transition is worked out.

  [2019-02-21]
  Packages in stage 1 and stage 2 have been verified by the security team and 
are ready to be copied into bionic-proposed.

  Notes:
   - jtreg and testng are new versions required as build dependencies of 
openjdk-11
   - all other packages are backports that must be build/bootstrapped with 
openjdk-10

  PPAs:
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2

  Please copy them in the following order/grouping.

  Group 1:
  * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 2:
  * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05)
  * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05)

  Please upload libcommons-lang3-java from stage 2 (ignore the version
  in stage 1).

  Group 3:
  * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06)
  * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx 
(2019-02-05)
  * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 4:
  * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 5:
  * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  
  [2019-02-22]
  Packages in stage 3

[Touch-packages] [Bug 1800839] Re: Dualshock3 hid_sony accelerometer not registering as joystick

2019-02-22 Thread Kai-Heng Feng

Does it use to work on previous Ubuntu releases?

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

Title:
  Dualshock3 hid_sony accelerometer not registering as joystick

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [12649.015762] input: Sony PLAYSTATION(R)3 Controller Motion Sensors as 
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input25
  [12649.015925] input: Sony PLAYSTATION(R)3 Controller as 
/devices/pci:00/:00:14.0/usb1/1-6/1-6:1.0/bluetooth/hci0/hci0:512/0005:054C:0268.0004/input/input24
  [12649.016117] sony 0005:054C:0268.0004: input,hidraw3: BLUETOOTH HID v80.00 
Joystick [Sony PLAYSTATION(R)3 Controller] on 60:f6:77:dd:db:90

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

  
  perhaps this is only a config issue as when the new split gyro & analog 
sticks/buttons/triggers 
  both appeared as  joysticks while you can now see only Sony PLAYSTATION(R)3 
Controller(input24) registers as a joystick while Sony PLAYSTATION(R)3 
Controller Motion Sensors (input25) does not.

  Any questions I am happy to respond, I have every reason to believe this is 
actually not a bluez issue but google gives me no returns other than general 
compatibility issues over the new hid_sony driver splitting the gyro from the 
pad.  I use this to stay current on instrument flying while working out of town 
using FlightGear flight simulator, the PS3 gyro is an excellent yoke simulator 
that fis in my laptop bag.
  thanks
  dave

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Oct 31 15:06:00 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. GL503VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=ec87be72-8832-43e4-a6d1-08c4d60d73b1 ro quiet splash 
modprobe.blacklist=nouveau vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-08-01 (90 days ago)
  dmi.bios.date: 03/13/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL503VD.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL503VD
  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.:bvrGL503VD.307:bd03/13/2018:svnASUSTeKCOMPUTERINC.:pnGL503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 60:F6:77:DD:DB:90  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:624605 acl:10743 sco:0 events:125 errors:0
TX bytes:5814 acl:12 sco:0 commands:106 errors:0

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

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

Re: [Touch-packages] [Openjdk] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

> > Just a question, is this update going to affect these packages:
> > jabref
> > scilab
> > octave
> > pdfsam
> > ?
> >
> > Also, I hope this update brings 18.04 LTS closer to Debian 10 regarding
> > OpenJdk-11 and its dependant packages to facilitate the maintenance
> > burden.
>
> Yes, we are planning to update java apps that are affected by this transition.

To be more specific, any package that fails to run correctly with
openjdk-11 will be investigated and is a candidate for a update. The
update does not necessarily imply we will use the latest version: we
might simply apply or backport changes that allow them to work under
openjdk-11.

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of multiple packages into the security pocket as well.

  The packages are being build on PPAs under the
  https://launchpad.net/~openjdk-11-transition team. The PPAs depend
  solely on the security pocket and are separated in stages.

  The agreed process among foundations and the security team is that
  packages in the PPAs will be binary copied into bionic-proposed,
  checked for migration issues, and - no issues pending - copied into
  bionic-security.

  NOTE TO SRU MEMBERS: The packages are to be released into bionic-
  security ONLY. This will be done/decided by the security team.

  A few packages might also need to be updated in Cosmic, but as an
  exception that will be done after the Bionic transition is worked out.

  [2019-02-21]
  Packages in stage 1 and stage 2 have been verified by the security team and 
are ready to be copied into bionic-proposed.

  Notes:
   - jtreg and testng are new versions required as build dependencies of 
openjdk-11
   - all other packages are backports that must be build/bootstrapped with 
openjdk-10

  PPAs:
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2

  Please copy them in the following order/grouping.

  Group 1:
  * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 2:
  * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05)
  * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05)

  Please upload libcommons-lang3-java from stage 2 (ignore the version
  in stage 1).

  Group 3:
  * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06)
  * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * jtreg

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

2019-02-22 Thread Amr Ibrahim

Thanks Tiago for the answer. Those four apps specifically are widely
used in the scientific and academic fields, as seen in my university for
example. And I'm ready for testing when needed.

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of multiple packages into the security pocket as well.

  The packages are being build on PPAs under the
  https://launchpad.net/~openjdk-11-transition team. The PPAs depend
  solely on the security pocket and are separated in stages.

  The agreed process among foundations and the security team is that
  packages in the PPAs will be binary copied into bionic-proposed,
  checked for migration issues, and - no issues pending - copied into
  bionic-security.

  NOTE TO SRU MEMBERS: The packages are to be released into bionic-
  security ONLY. This will be done/decided by the security team.

  A few packages might also need to be updated in Cosmic, but as an
  exception that will be done after the Bionic transition is worked out.

  [2019-02-21]
  Packages in stage 1 and stage 2 have been verified by the security team and 
are ready to be copied into bionic-proposed.

  Notes:
   - jtreg and testng are new versions required as build dependencies of 
openjdk-11
   - all other packages are backports that must be build/bootstrapped with 
openjdk-10

  PPAs:
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2

  Please copy them in the following order/grouping.

  Group 1:
  * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 2:
  * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05)
  * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05)

  Please upload libcommons-lang3-java from stage 2 (ignore the version
  in stage 1).

  Group 3:
  * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06)
  * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx 
(2019-02-05)
  * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 4:
  * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 5:
  * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  
  [2019-02-22]
  Packages in stage 3 that are waiting for security team review. Copy only 
after OK is

Re: [Touch-packages] [Openjdk] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

> Just a question, is this update going to affect these packages:
> jabref
> scilab
> octave
> pdfsam
> ?
>
> Also, I hope this update brings 18.04 LTS closer to Debian 10 regarding
> OpenJdk-11 and its dependant packages to facilitate the maintenance
> burden.

Yes, we are planning to update java apps that are affected by this
transition.

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of multiple packages into the security pocket as well.

  The packages are being build on PPAs under the
  https://launchpad.net/~openjdk-11-transition team. The PPAs depend
  solely on the security pocket and are separated in stages.

  The agreed process among foundations and the security team is that
  packages in the PPAs will be binary copied into bionic-proposed,
  checked for migration issues, and - no issues pending - copied into
  bionic-security.

  NOTE TO SRU MEMBERS: The packages are to be released into bionic-
  security ONLY. This will be done/decided by the security team.

  A few packages might also need to be updated in Cosmic, but as an
  exception that will be done after the Bionic transition is worked out.

  [2019-02-21]
  Packages in stage 1 and stage 2 have been verified by the security team and 
are ready to be copied into bionic-proposed.

  Notes:
   - jtreg and testng are new versions required as build dependencies of 
openjdk-11
   - all other packages are backports that must be build/bootstrapped with 
openjdk-10

  PPAs:
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2

  Please copy them in the following order/grouping.

  Group 1:
  * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 2:
  * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05)
  * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05)

  Please upload libcommons-lang3-java from stage 2 (ignore the version
  in stage 1).

  Group 3:
  * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06)
  * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx 
(2019-02-05)
  * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 4:
  * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 5:
  * groovy

[Touch-packages] [Bug 1817317] Re: OpenSSH is not "OpenBSD Secure Shell" and never be. /etc/init.d/ssh

2019-02-22 Thread Sebastien Bacher

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

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

Title:
  OpenSSH is not "OpenBSD Secure Shell" and never be. /etc/init.d/ssh

Status in openssh package in Ubuntu:
  New

Bug description:
  openssh-server.ssh.init.new
  --- openssh-server.ssh.init 2018-11-07 22:52:49.0 +0900
  +++ openssh-server.ssh.init.new 2019-02-22 21:50:05.010233405 +0900
  @@ -6,7 +6,7 @@
   # Required-Stop:   $remote_fs $syslog
   # Default-Start:   2 3 4 5
   # Default-Stop:
  -# Short-Description:   OpenBSD Secure Shell server
  +# Short-Description:   OpenSSH server
   ### END INIT INFO
   
   set -e

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

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

[Touch-packages] [Bug 1781176] Re: Blacklisted packages are included in the "upgradable origin", while they should not

Tested with 1.1ubuntu1.18.04.9 on Bionic:

...
root@bb-uu-lp-1781176-2:~# apt list --upgradable 
Listing... Done
e2fsprogs/bionic-updates 1.44.1-1ubuntu1.1 amd64 [upgradable from: 1.44.1-1]
ebtables/bionic-updates 2.0.10.4-3.5ubuntu2.18.04.3 amd64 [upgradable from: 
2.0.10.4-3.5ubuntu2]
libext2fs2/bionic-updates 1.44.1-1ubuntu1.1 amd64 [upgradable from: 1.44.1-1]
wireshark-common/bionic-updates,bionic-security 2.6.6-1~ubuntu18.04.0 amd64 
[upgradable from: 2.4.5-1]
...
root@bb-uu-lp-1781176-2:~# unattended-upgrade --verbose --debug
Initial blacklisted packages: ebtables
Initial whitelisted packages: 
Starting unattended upgrades script
...
fetch.run() result: 0
blacklist: ['ebtables']
whitelist: []
Packages that will be upgraded:=20
InstCount=3D0 DelCount=3D0 BrokenCount=3D0
Extracting content from /var/log/unattended-upgrades/unattended-upgrades-dp=
kg.log since 2019-02-22 13:20:19
Sending mail to root

>From r...@bb-uu-lp-1781176-2.lxd Fri Feb 22 13:43:21 2019
Return-path: 
Envelope-to: r...@bb-uu-lp-1781176-2.lxd
Delivery-date: Fri, 22 Feb 2019 13:43:21 +
Received: from root by bb-uu-lp-1781176-2.lxd with local (Exim 4.90_1)
(envelope-from )
id 1gxB6n-0001bL-Kz
for r...@bb-uu-lp-1781176-2.lxd; Fri, 22 Feb 2019 13:43:21 +
Subject: unattended-upgrades result for bb-uu-lp-1781176-2: True
To: r...@bb-uu-lp-1781176-2.lxd
Auto-Submitted: auto-generated
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: root 
Message-Id: 
Date: Fri, 22 Feb 2019 13:43:21 +

Unattended upgrade returned: True

Packages that were upgraded:
 wireshark-common=20

Packages that were auto-removed:
 libwsutil8 libwiretap7 libwireshark10 libwscodecs1=20


...

root@bb-uu-lp-1781176-2:~# apt list --upgradable 
Listing... Done
e2fsprogs/bionic-updates 1.44.1-1ubuntu1.1 amd64 [upgradable from: 1.44.1-1]
ebtables/bionic-updates 2.0.10.4-3.5ubuntu2.18.04.3 amd64 [upgradable from: 
2.0.10.4-3.5ubuntu2]
libext2fs2/bionic-updates 1.44.1-1ubuntu1.1 amd64 [upgradable from: 1.44.1-1]


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

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

Title:
  Blacklisted packages are included in the "upgradable origin", while
  they should not

Status in unattended-upgrades:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in unattended-upgrades source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * Reports from u-u incorrectly list packages from non-upgradable
  origins as "Packages with upgradable origin but kept back"

   * Listing the packages incorrectly is a result of
  is_pkgname_in_blacklist() having a side effect and removing the side
  effect is part of fixing LP: #1396787 which fix is also being SRU-d.

   * The fix is removing the side effect of is_pkgname_in_blacklist()

  [Test Case]

   * There is a build-time test in test/test_blacklisted_wrong_origin.py
   * To reproduce the original problem set up a system where all security 
updates are installed but ebtables (from bionic-updates) is not updated:
  $ sudo unattended-upgrade  --verbose
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  No packages found that can be upgraded unattended and no pending auto-removals
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be upgraded:
    apt apt-utils ebtables initramfs-tools initramfs-tools-bin 
initramfs-tools-core libapt-inst2.0 libapt-pkg5.0
    liblxc-common liblxc1 libpython3-stdlib lxcfs lxd lxd-client netplan.io 
networkd-dispatcher nplan
    python-apt-common python3 python3-apt python3-minimal 
python3-update-manager snapd squashfs-tools
    unattended-upgrades update-manager-core update-notifier-common
  27 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 24.1 MB of archives.
  After this operation, 1454 kB of additional disk space will be used.
  Do you want to continue? [Y/n] n
  Abort.

  * blacklist ebtables, set up emails from u-u, then run u-u again:
  $ sudo echo 'Unattended-Upgrade::Package-Blacklist {"ebtables";};' > 
/etc/apt/apt.conf.d/51unattended-upgrades-blacklist-ebtables
  $ sudo echo 'Unattended-Upgrade::Mail "root";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-mail
  $ sudo unattended-upgrade  --verbose
  Initial blacklisted packages: ebtables
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security,

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

** Also affects: libhibernate-validator-java (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: maven-bundle-plugin (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: maven-enforcer (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: maven-jaxb2-plugin (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: maven-plugin-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of multiple packages into the security pocket as well.

  The packages are being build on PPAs under the
  https://launchpad.net/~openjdk-11-transition team. The PPAs depend
  solely on the security pocket and are separated in stages.

  The agreed process among foundations and the security team is that
  packages in the PPAs will be binary copied into bionic-proposed,
  checked for migration issues, and - no issues pending - copied into
  bionic-security.

  NOTE TO SRU MEMBERS: The packages are to be released into bionic-
  security ONLY. This will be done/decided by the security team.

  A few packages might also need to be updated in Cosmic, but as an
  exception that will be done after the Bionic transition is worked out.

  [2019-02-21]
  Packages in stage 1 and stage 2 have been verified by the security team and 
are ready to be copied into bionic-proposed.

  Notes:
   - jtreg and testng are new versions required as build dependencies of 
openjdk-11
   - all other packages are backports that must be build/bootstrapped with 
openjdk-10

  PPAs:
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2

  Please copy them in the following order/grouping.

  Group 1:
  * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 2:
  * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05)
  * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05)

  Please upload libcommons-lang3-java from stage 2 (ignore the version
  in stage 1).

  Group 3:
  * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06)
  * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer

[Touch-packages] [Bug 1775018] Re: Fix for openssl 1.0.2 backport

2019-02-22 Thread Francis Ginther

** Tags added: id-5c6e7940730252541b970add

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

Title:
  Fix for openssl 1.0.2 backport

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl1.0 package in Ubuntu:
  Confirmed
Status in openssl source package in Xenial:
  Invalid
Status in openssl1.0 source package in Xenial:
  Invalid
Status in openssl source package in Bionic:
  Fix Released
Status in openssl1.0 source package in Bionic:
  Confirmed
Status in openssl source package in Cosmic:
  Fix Released
Status in openssl1.0 source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

   * Fix hw accelerated performance impact on s390x with non-default
  openssl1.0.

  [Test Case]

   * Test that performance of hw accelerated crypto is improved / i.e.
  ssl speed test

   * Test that openssh still works, just in case.

  [Regression Potential]

   * This only changes accelerated codepath on s390x, for specific algos when 
CPACF is enabled on the system cpu, which is usually on.
   * Same fix is already in use by 1.1.0 default openssl package, and well 
excercised on bionic and up.

  [Other Info]
   
   * original bug report.

  
  This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and 
upstream code are not affected ).

  Original LP ticket :
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750

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

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

[Touch-packages] [Bug 1817097] Re: pvmove causes file system corruption without notice upon move from 512 -> 4096 logical block size devices

2019-02-22 Thread Dimitri John Ledkov

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

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

Title:
  pvmove causes file system corruption without notice upon move from 512
  -> 4096 logical block size devices

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Problem Description---
  Summary
  ===
  Environment: IBM Z13 LPAR and z/VM Guest
   IBM Type: 2964 Model: 701 NC9
  OS:  Ubuntu 18.10 (GNU/Linux 4.18.0-13-generic s390x)
   Package: lvm2 version 2.02.176-4.1ubuntu3
  LVM: pvmove operation corrupts file system when using 4096 (4k) logical block 
size
   and default block size being 512 bytes in the underlying devices
  The problem is immediately reproducible.

  We see a real usability issue with data destruction as consequence - which is 
not acceptable.
  We expect 'pvmove' to fail with error in such situations to prevent fs 
destruction,
  which might possibly be overridden by a force flag.

  
  Details
  ===
  After a 'pvmove' operation is run to move a physical volume onto an ecrypted
  device with 4096 bytes logical block size we experience a file system 
corruption.
  There is no need for the file system to be mounted, but the problem surfaces
  differently if so.

  Either, the 'pvs' command after the pvmove shows
/dev/LOOP_VG/LV: read failed after 0 of 1024 at 0: Invalid argument
/dev/LOOP_VG/LV: read failed after 0 of 1024 at 314507264: Invalid argument
/dev/LOOP_VG/LV: read failed after 0 of 1024 at 314564608: Invalid argument
/dev/LOOP_VG/LV: read failed after 0 of 1024 at 4096: Invalid argument

  or

  a subsequent mount shows (after umount if the fs had previously been mounted 
as in our
  setup)
  mount: /mnt: wrong fs type, bad option, bad superblock on 
/dev/mapper/LOOP_VG-LV, missing codepage or helper program, or other error.

  A minimal setup of LVM using one volume group with one logical volume defined,
  based on one physical volume is sufficient to raise the problem. One more 
physical
  volume of the same size is needed to run the pvmove operation to. 

LV
 |
  VG: LOOP_VG [ ]
 |
  PV: /dev/loop0   -->   /dev/mapper/enc-loop
  ( backed by /dev/mapper/enc-loop )

  The physical volumes are backed by loopback devices (losetup) to base the
  problem report on, but we have seen the error on real SCSI multipath volumes
  also, with and without cryptsetup mapper devices in use.

  
  Further discussion
  ==
  https://www.saout.de/pipermail/dm-crypt/2019-February/006078.html
  The problem does not occur on block devices with native size of 4k.
  E.g. DASDs, or file systems with mkfs -b 4096 option.

  
  Terminal output
  ===
  See attached file pvmove-error.txt

  
  Debug data
  ==
  pvmove was run with -dd (maximum debug level)
  See attached journal file.
   
  Contact Information = christian.r...@de.ibm.com 
   
  ---uname output---
  Linux system 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:00:35 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = IBM Type: 2964 Model: 701 NC9 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1.) Create two image files of 500MB in size
  and set up two loopback devices with 'losetup -fP FILE'
  2.) Create one physical volume and one volume group 'LOOP_VG',
  and one logical volume 'VG'
  Run:
  pvcreate /dev/loop0
  vgcreate LOOP_VG /dev/loop0
  lvcreate -L 300MB LOOP_VG -n LV /dev/loop0
  3.) Create a file system on the logical volume device:
  mkfs.ext4 /dev/mapper/LOOP_VG-LV
  4.) mount the file system created in the previous step to some empty 
available directory:
  mount /dev/mapper/LOOP_VG-LV /mnt
  5.) Set up a second physical volume, this time encrypted with LUKS2,
  and open the volume to make it available:
  cryptsetup luksFormat --type luks2 --sector-size 4096 /dev/loop1
  cryptsetup luksOpen /dev/loop1 enc-loop
  6.) Create the second physical volume, and add it to the LOOP_VG
  pvcreate /dev/mapper/enc-loop
  vgextend LOOP_VG /dev/mapper/enc-loop
  7.) Ensure the new physical volume is part of the volume group:
  pvs
  8.) Move the /dev/loop0 volume onto the encrypted volume with maximum debug 
option:
  pvmove -dd /dev/loop0 /dev/mapper/enc-loop
  9.) The previous step succeeds, but corrupts the file system on the logical 
volume
   We expect an error here. 
   There might be a command line flag to override used because corruption 
does not cause a data loss.
  
   
  Userspace tool common name: pvmove 
   
  The userspace tool has the following bit modes: 64bit 

  Userspace rpm: lvm2 in versoin

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

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

** Also affects: maven-javadoc-plugin (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in libcommons-lang3-java source package in Bionic:
  Fix Committed
Status in maven-compiler-plugin source package in Bionic:
  Fix Committed
Status in maven-debian-helper source package in Bionic:
  Fix Committed
Status in plexus-languages source package in Bionic:
  Fix Committed
Status in surefire source package in Bionic:
  Fix Committed
Status in testng source package in Bionic:
  Fix Committed

Bug description:
  Transition OpenJDK 11 to 18.04 LTS.

  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of multiple packages into the security pocket as well.

  The packages are being build on PPAs under the
  https://launchpad.net/~openjdk-11-transition team. The PPAs depend
  solely on the security pocket and are separated in stages.

  The agreed process among foundations and the security team is that
  packages in the PPAs will be binary copied into bionic-proposed,
  checked for migration issues, and - no issues pending - copied into
  bionic-security.

  NOTE TO SRU MEMBERS: The packages are to be released into bionic-
  security ONLY. This will be done/decided by the security team.

  A few packages might also need to be updated in Cosmic, but as an
  exception that will be done after the Bionic transition is worked out.

  [2019-02-21]
  Packages in stage 1 and stage 2 have been verified by the security team and 
are ready to be copied into bionic-proposed.

  Notes:
   - jtreg and testng are new versions required as build dependencies of 
openjdk-11
   - all other packages are backports that must be build/bootstrapped with 
openjdk-10

  PPAs:
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2

  Please copy them in the following order/grouping.

  Group 1:
  * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 2:
  * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05)
  * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05)

  Please upload libcommons-lang3-java from stage 2 (ignore the version
  in stage 1).

  Group 3:
  * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06)
  * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx 
(2019-02-05)
  * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 4:
  * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  Group 5:
  * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05)

  
  [2019-02-22]
  Packages in stage 3 that are waiting for security team review. Copy only 
after OK is received.

  PPAs:
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage3

  Please copy them in the following order/grouping.
  Group 1:
  * java-common 0.68ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-21)
  *

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

** Description changed:

  Transition OpenJDK 11 to 18.04 LTS.
  
  This transition is a security update of openjdk-lts from openjdk-10 to
  openjdk-11. This introduces runtime and FTBFS issues which requires
  backports of multiple packages into the security pocket as well.
  
  The packages are being build on PPAs under the
  https://launchpad.net/~openjdk-11-transition team. The PPAs depend
  solely on the security pocket and are separated in stages.
  
  The agreed process among foundations and the security team is that
  packages in the PPAs will be binary copied into bionic-proposed, checked
  for migration issues, and - no issues pending - copied into bionic-
  security.
  
  NOTE TO SRU MEMBERS: The packages are to be released into bionic-
  security ONLY. This will be done/decided by the security team.
  
  A few packages might also need to be updated in Cosmic, but as an
  exception that will be done after the Bionic transition is worked out.
  
- [2018-02-21]
+ [2019-02-21]
  Packages in stage 1 and stage 2 have been verified by the security team and 
are ready to be copied into bionic-proposed.
  
  Notes:
   - jtreg and testng are new versions required as build dependencies of 
openjdk-11
   - all other packages are backports that must be build/bootstrapped with 
openjdk-10
  
  PPAs:
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1
  https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2
  
  Please copy them in the following order/grouping.
  
  Group 1:
  * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  
  Group 2:
  * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05)
  * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05)
  
  Please upload libcommons-lang3-java from stage 2 (ignore the version in
  stage 1).
  
  Group 3:
  * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06)
  * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx 
(2019-02-05)
  * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  
  Group 4:
  * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  
  Group 5:
  * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
  
- Packages from stage 3 and later are not yet reviewed and should not be
+ 
+ [2019-02-22]
+ Packages in stage 3 that are waiting for security team review. Copy only 
after OK is received.
+ 
+ PPAs:
+ https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage3
+ 
+ Please copy them in the following order/grouping.
+ Group 1:
+ * java-common 0.68ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-21)
+ * javatools 0.72.1~18.04.1 Tiago Stürmer Daitx (2019-02-20)
+ * openjdk-lts 11.0.2+9-3ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-07)
+ 
+ Group 2:
+ * gettext 0.19.8.1-6ubuntu0.2 Matthias Klose (18 hours ago)
+ * insubstantial 7.3+dfsg3-4~18.04.1 Tiago Stürmer Daitx (2019-02-20)
+ * jython 2.7.1+repack-5~18.04 Matthias Klose (2019-02-20)
+ * libgpars-groovy-java 1.2.1-10~18.04.1 Tiago Stürmer Daitx (2019-02-20)
+ * logback 1:1.2.3-2ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-20)
+ * maven-javadoc-plugin 3.0.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-20)
+ * openjdk-11-jre-dcevm 11.0.1+7-1ubuntu0.1 Matthias Klose (2019-02-19)
+ * openjfx 11.0.2+1-1~18.04.1 Matthias Klose (2019-02-19)
+ * saaj 1.4.0-3~18.04.1 Tiago Stürmer Daitx (2019-02-20)
+ * scala 2.11.12-4~18.04 Matthias Klose (2019-02-20)
+ 
+ Packages from stage 4 and later are not yet reviewed and should not be
  uploaded.

** Also affects: java-common (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** No longer affects: saaj-ri (Ubuntu)

** Also affects: libgpars-groovy-java (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:

[Touch-packages] [Bug 1775018] Re: Fix for openssl 1.0.2 backport

2019-02-22 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: Triaged => 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/1775018

Title:
  Fix for openssl 1.0.2 backport

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl1.0 package in Ubuntu:
  Confirmed
Status in openssl source package in Xenial:
  Invalid
Status in openssl1.0 source package in Xenial:
  Invalid
Status in openssl source package in Bionic:
  Fix Released
Status in openssl1.0 source package in Bionic:
  Confirmed
Status in openssl source package in Cosmic:
  Fix Released
Status in openssl1.0 source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

   * Fix hw accelerated performance impact on s390x with non-default
  openssl1.0.

  [Test Case]

   * Test that performance of hw accelerated crypto is improved / i.e.
  ssl speed test

   * Test that openssh still works, just in case.

  [Regression Potential]

   * This only changes accelerated codepath on s390x, for specific algos when 
CPACF is enabled on the system cpu, which is usually on.
   * Same fix is already in use by 1.1.0 default openssl package, and well 
excercised on bionic and up.

  [Other Info]
   
   * original bug report.

  
  This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and 
upstream code are not affected ).

  Original LP ticket :
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750

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

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

[Touch-packages] [Bug 1817317] [NEW] OpenSSH is not "OpenBSD Secure Shell" and never be. /etc/init.d/ssh

2019-02-22 Thread Hocus Pocus

Public bug reported:

openssh-server.ssh.init.new
--- openssh-server.ssh.init 2018-11-07 22:52:49.0 +0900
+++ openssh-server.ssh.init.new 2019-02-22 21:50:05.010233405 +0900
@@ -6,7 +6,7 @@
 # Required-Stop:   $remote_fs $syslog
 # Default-Start:   2 3 4 5
 # Default-Stop:
-# Short-Description:   OpenBSD Secure Shell server
+# Short-Description:   OpenSSH server
 ### END INIT INFO
 
 set -e

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

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

Title:
  OpenSSH is not "OpenBSD Secure Shell" and never be. /etc/init.d/ssh

Status in openssh package in Ubuntu:
  New

Bug description:
  openssh-server.ssh.init.new
  --- openssh-server.ssh.init 2018-11-07 22:52:49.0 +0900
  +++ openssh-server.ssh.init.new 2019-02-22 21:50:05.010233405 +0900
  @@ -6,7 +6,7 @@
   # Required-Stop:   $remote_fs $syslog
   # Default-Start:   2 3 4 5
   # Default-Stop:
  -# Short-Description:   OpenBSD Secure Shell server
  +# Short-Description:   OpenSSH server
   ### END INIT INFO
   
   set -e

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

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

[Touch-packages] [Bug 566690] Re: My microphone does not work in ubuntu lucid

Further to above comments, closing now as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  My microphone does not work in ubuntu lucid

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  i don't have microphone in Ubuntu lucid , I hope this report is not too late 
and until the final  release the problem disappears.
  I'm Checking volume levels with "alsamixer" Command.
   All volume associated with the microphone (Front mic,mic, mic boost)  is at 
the highest.
  http://www.ubuntu-pics.de/bild/52970/navid_ubuntu012_gXbFc6.png

  in sound Preferences my input volume is zero .

  http://www.ubuntu-pics.de/bild/52972/sound_preferences_013_MU88Oi.png
  And of course, I test my microphone In practice with sound recorder! the 
input audio is zero

  And finally:

  navid@ubuntu:~$ grep "^Codec\|^Vendor Id\|^Subsystem Id\|^Revision Id"
  /proc/asound/card*/*codec*{,/*} | grep -B2 -A1 $(lspci -nv | grep -A1
  0403 | grep Subsystem | sed 's/://g' | awk '{ print $2 }')

  grep: /proc/asound/card*/*codec*/*: No such file or directory
  /proc/asound/card0/codec#0:Codec: Realtek ALC1200
  /proc/asound/card0/codec#0:Vendor Id: 0x10ec0888
  /proc/asound/card0/codec#0:Subsystem Id: 0x104382fe
  /proc/asound/card0/codec#0:Revision Id: 0x100101

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  navid  1555 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf9ff8000 irq 22'
     Mixer name : 'Realtek ALC1200'
     Components : 'HDA:10ec0888,104382fe,00100101'
     Controls  : 40
     Simple ctrls  : 22
  Date: Mon Apr 19 18:54:40 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100317.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  dmi.bios.date: 04/07/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2102
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2102:bd04/07/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 659732] Re: [EMU10K1X - Dell Sound Blaster Live!] ALSA test tone not correctly played back

Further to above comments changing to "Fix Released" to close.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [EMU10K1X - Dell Sound Blaster Live!] ALSA test tone not correctly
  played back

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  The test sound pulses rapidly.

  Music tracks play in a patchy manner and at a fast pace.

  Using Ubuntu 10.10; alsa-base 1.0.23+dfsg-1ubuntu4, kernel 2.6.35-22.

  When I switch to kernel 2.6.32-25 sound reproduction is flawless.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: alsa-base 1.0.23+dfsg-1ubuntu4
  ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'Audio'/'Elan USB Audio at usb-:00:1d.7-3.4, full speed'
 Mixer name : 'USB Mixer'
 Components : 'USB04f3:0a11'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.info:
   Card hw:1 'Q9000'/'Logitech, Inc. QuickCam Pro 9000 at usb-:00:1a.7-4, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0990'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 3072
 Mono: Capture 574 [19%] [20.24dB] [on]
  Card2.Amixer.info:
   Card hw:2 'Live'/'Dell Sound Blaster Live! at 0x1400 irq 18'
 Mixer name : 'SigmaTel STAC9758,59'
 Components : 'AC97a:83847658'
 Controls  : 57
 Simple ctrls  : 38
  Card3.Amixer.info:
   Card hw:3 'default'/'Burr-Brown from TI   USB Audio CODEC  at 
usb-:00:1d.1-2, full s'
 Mixer name : 'USB Mixer'
 Components : 'USB08bb:2900'
 Controls  : 2
 Simple ctrls  : 1
  Date: Wed Oct 13 18:40:57 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_AU.utf8
   SHELL=/bin/bash
  SelectedCard: 2 Live EMU10K1X - Dell Sound Blaster Live!
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [EMU10K1X - Dell Sound Blaster Live!] ALSA test tone not correctly 
played back
  dmi.bios.date: 08/11/2008
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: MQ96510J.86A.1751.2008.0811.0002
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DG965WH
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD41692-304
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrMQ96510J.86A.1751.2008.0811.0002:bd08/11/2008:svn:pn:pvr:rvnIntelCorporation:rnDG965WH:rvrAAD41692-304:cvn:ct3:cvr:

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

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

[Touch-packages] [Bug 629171] Re: Microphone not working in Lenovo 3000 V100

Further to comment #11, closing now as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Microphone not working in Lenovo 3000 V100

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  Canonical's Ubuntu Advantage service told me to open this bug.  I've
  reproduced it in the Live CD from Ubuntu 10.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2762 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd824 irq 22'
 Mixer name : 'Realtek ALC883'
 Components : 'HDA:10ec0883,17aa1205,0012 
HDA:10573055,10573055,00100700'
 Controls  : 22
 Simple ctrls  : 14
  CurrentDmesg:
   [   80.951326] lp: driver loaded but no devices found
   [   81.238558] ppdev: user-space parallel port driver
   [   81.916045] eth0: no IPv6 routers present
   [  203.624632] eth0: link down
   [  206.662161] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
  Date: Fri Sep  3 00:00:12 2010
  LiveMediaBuild: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  dmi.bios.date: 04/20/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 62ETC1WW (1.11 )
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr62ETC1WW(1.11):bd04/20/2007:svnLENOVO:pn076346G:pvrLENOVO3000V100:rvnLENOVO:rnINVALID:rvrNotApplicable:cvnLENOVO:ct10:cvrN/A:
  dmi.product.name: 076346G
  dmi.product.version: LENOVO3000 V100
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 637586] Re: [Realtek ALC269] Playback problem

Further to comment #2, closing now as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [Realtek ALC269] Playback problem

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  When I play movies or audio files, sound does go "continuosly" to
  speakers, but in small steps.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: alsa-base 1.0.23+dfsg-1ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
  Uname: Linux 2.6.35-20-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  serras 1657 F pulseaudio
   /dev/snd/pcmC0D0p:   serras 1657 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe9f4000 irq 45'
 Mixer name : 'Realtek ALC269'
 Components : 'HDA:10ec0269,104314e3,0014'
 Controls  : 11
 Simple ctrls  : 7
  Date: Mon Sep 13 23:14:28 2010
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=nl_NL.utf8
   SHELL=/bin/bash
  SelectedCard: 0 Intel HDA-Intel - HDA Intel
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [Realtek ALC269] Playback problem
  dmi.bios.date: 11/02/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UL20A
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr207:bd11/02/2009:svnASUSTeKComputerInc.:pnUL20A:pvr1.0:rvnASUSTeKComputerInc.:rnUL20A:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UL20A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Touch-packages] [Bug 1734520] Re: Enable atomic write support for f2fs

2019-02-22 Thread Mateusz Mikuła

** Tags added: f2fs

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

Title:
  Enable atomic write support for f2fs

Status in sqlite3 package in Ubuntu:
  Confirmed

Bug description:
  SQLite 3.21 supports atomic write to boost performance quite a lot for
  f2fs partitions.

  As I looked into 3.21's buildlog, Ubuntu didn't supply the build flag
  to enable atomic write.

  Please add -DSQLITE_ENABLE_BATCH_ATOMIC_WRITE to the build flag and
  enable atomic write support.

  Thanks.

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

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

[Touch-packages] [Bug 1734520] Re: Enable atomic write support for f2fs

2019-02-22 Thread Launchpad Bug Tracker

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

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

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

Title:
  Enable atomic write support for f2fs

Status in sqlite3 package in Ubuntu:
  Confirmed

Bug description:
  SQLite 3.21 supports atomic write to boost performance quite a lot for
  f2fs partitions.

  As I looked into 3.21's buildlog, Ubuntu didn't supply the build flag
  to enable atomic write.

  Please add -DSQLITE_ENABLE_BATCH_ATOMIC_WRITE to the build flag and
  enable atomic write support.

  Thanks.

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

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

[Touch-packages] [Bug 1421118] Re: [20-2110nz, Realtek ALC280, Speaker, Internal] Playback problem : headphones ok, speaker ko

Further to comment #2, closing now as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [20-2110nz, Realtek ALC280, Speaker, Internal] Playback problem :
  headphones ok, speaker ko

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  Speaker doesn't work at all under Ubuntu, but sound through headphones is 
working fine.
  The machine is an hp 20 all-in-one. The hardware is fine, as the speaker does 
work in the original Windows 8 that came with the computer. We played with 
alsamixer and tried to tweak /etc/modprobe.d/alsa-base.conf to no avail. We 
never managed to get a single sound through the internal speakers in Ubuntu.

  --
  Hardware:  hp 20 all-in-one
  O.S.:  Ubuntu 14.04.1 LTS
  package: alsa-base 1.0.25+dfsg-0ubuntu4
  expected:   internal speakers to produce sound with "sound settings test", 
vlc or web browser
  happened:  no sound through internal speakers ever in Ubuntu (but yes through 
headphones in Ubuntu and through internal  
speakers in Windows)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oriana 1848 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Feb 12 09:59:05 2015
  InstallationDate: Installed on 2015-02-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [20-2110nz, Realtek ALC280, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/12/2014
  dmi.bios.vendor: AMI
  dmi.bios.version: 80.13
  dmi.board.asset.tag: 4CH4457MH7
  dmi.board.name: 2B15
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.02A
  dmi.chassis.asset.tag: 4CH4457MH7
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr80.13:bd06/12/2014:svnHewlett-Packard:pn20-2110nz:pvr:rvnHewlett-Packard:rn2B15:rvr1.02A:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: 20-2110nz
  dmi.sys.vendor: Hewlett-Packard
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-02-12T09:58:59.506131

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

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

[Touch-packages] [Bug 463796] Re: Alsa doesn't detect external mic

Further to comments #3 and #5, closing now as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Alsa doesn't detect external mic

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  I have a Logitech mini-jack headset with a mic. Sound playback works,
  but recording does not; it only works through the computer's built-in
  microphone.

  ProblemType: Bug
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  josh   2688 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0x9240 irq 16'
 Mixer name : 'IDT 92HD71B7X'
 Components : 'HDA:111d76b2,103c3600,00100302'
 Controls  : 35
 Simple ctrls  : 22
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0x9231 irq 19'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,0010'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined
 Playback channels: Mono
 Mono: Playback [off]
  CheckboxSubmission: 6bacad257d07e21537e077802a955e05
  CheckboxSystem: e704f33cc0866ff0f0256a33de39ea1c
  Date: Thu Oct 29 17:31:38 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: fglrx
  Package: alsa-base 1.0.20+dfsg-1ubuntu5
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: alsa-driver
  Uname: Linux 2.6.31-14-generic x86_64

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

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

[Touch-packages] [Bug 1817033] Re: Unable to correctly print PDF file: Error: Ignoring spurious ET operator.

2019-02-22 Thread Paul Menzel

Tobias, you were right. Sorry for not understanding your original
comment better.

Updating to Cairo 1.17.2 also fixes the problem, as it includes [commit
4c8813f0 (pdf: add missing
flush)](https://gitlab.freedesktop.org/cairo/cairo/commit/4c8813f0eaacc32c27126ad2296951a626300b89)
fixing issue [Cairo generates incorrect PDF
files](https://gitlab.freedesktop.org/cairo/cairo/issues/342). Thank you
to Tobias Hoffmann for mentioning that in the Launchpad bug report.

Distributions should probably back port that commit. I’ll ask the Cairo
developers to cherry-pick this into the 1.16 branch.

I’ll reassign this to the libcairo2.

** Package changed: cups-filters (Ubuntu) => cairo (Ubuntu)

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

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

Title:
Unable to correctly print PDF file: Error: Ignoring spurious ET
operator.

Status in cairo package in Ubuntu:
Confirmed

Bug description:
Upstream bug report https://github.com/OpenPrinting/cups-
filters/issues/93.

The university document
[antrag_exmatrikulation.pdf](https://github.com/OpenPrinting/cups-
filters/files/2881078/antrag_exmatrikulation.pdf) causes problems on
different printers.

Printing on the Canon iR-ADV C2225i using the Canon PCL, an error page
is first printed, and on the first page after _Email_ everything is
missing. The second page is fine.

```
Error: Ignoring spurious ET operator. Output may be inco
```

For that printer a special filter `sicgsfilter` has to be used, and is
distributed by Canon. This also happens with their CQue 4.0-1 release
from September 2018.

```
*FoomaticRIPCommandLine: "gs -q -dBATCH %F -dPARANOIDSAFER -dNOPAUSE %B%A%C
-dPDFFitPage -sOutputFile=- - %D%E | sicgsfilter -MPCL -NP %G%H%I -u
-V -n "
```

On the Epson printer _WorkForce WF-2660_, no error page is printed,
but on the first page everything after _Email_ _is missing_ too.

Trying to use different pdftops renderers did not make any difference.
For example,

```
lpr -o pdftops-renderer=pdftops -P chipprinterpcl antrag_exmatrikulation.pdf
```

gave the same result, the same with `pdftocairo`, `acroread`, `mupdf`.

Following `/usr/share/doc/cups-filters/README.gz` and
https://wiki.ubuntu.com/DebuggingPrintingProblems, I verified that the
exact same PDF is put into the CUPS spool directory, and I captured
the data sent to the printer with the commands below.

$ lpadmin -p chipprinterpclfile -E -v file:/tmp/printout -P
~/chipprinterpcl.ppd
$ lpr -P chipprinterpclfile -o psdebug ~/antrag_exmatrikulation.pdf

I get the attached Postscript file, which indeed contains the error
messages.

```
ESC%-12345X@PJL CQue4.0-1 x86_64
@PJL COMMENT CANPJL SET USERNAME="pmenzel@localhost"
@PJL COMMENT CANPJL SET DOCNAME="antrag_exmatrikulation.pdf!pmenz"
@PJL SET RENDERMODE=COLOR
@PJL COMMENT CANPJL SET FORCEMONOCHROME=FALSE
@PJL COMMENT CANPJL SET SORTERMODE=GENERICON
@PJL COMMENT CANPJL SET STAPLE=GENERICOFF
@PJL COMMENT CANPJL SET BOOKLET=GENERICOFF
@PJL SET DENSITY=0
@PJL ENTER LANGUAGE=PCL
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
[…]
```

Please find that file attached.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: cups 2.2.8-5ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
Date: Thu Feb 21 10:23:08 2019
InstallationDate: Installed on 2017-03-20 (702 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
Lpstat:
device for Canon-iR-ADV-C2225: lpd://winprima.molgen.mpg.de/test
device for DCP375CW: socket://141.14.220.198
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp.
Bus 001 Device 003: ID 04f3:2234 Elan Microelectronics

[Touch-packages] [Bug 535361] Re: MacBook Pro's nVidia soundcard not seen by new kernel 2.6.31-20

Further to comment #28, closing now as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  MacBook Pro's nVidia soundcard not seen by new kernel 2.6.31-20

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  Card type/model : nVidia Corporation MCP79 High Definition Audio (rev b1)
  found on MacBook Pro 5,5 (and other similar series)

  Until kernel 2.6.31-19, the sound works well when compiling alsa-
  driver from snapshot. Following insctructions found on this page for
  example : https://help.ubuntu.com/community/MacBookPro5-3/Karmic#Sound

  Since 2.6.31-20 update, the sound card is not recognized at all. After the 
update, I did remove : 
  sudo rm -rf /lib/modules/2.6.31-20/kernel/sound
  and reinstall the linux headers
  sudo aptitude reinstall linux-headers-2.6.31-20 linux-image-2.6.31-20
  Then rebooted and recompiled the alsa-driver (from snapshot).

  No sound. Issuing the alsamixer command returns that : No mixer elems
  found. Everything is empty in every alsa cli or gui, just as if I had
  removed the audio card.

  Booting back in 2.6.31-29, sounds works well.

  Michel Roche
  France.

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

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

[Touch-packages] [Bug 600096] Re: No headphone jack output on T400s

No reply from reporter, others say fixed so closing now.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  No headphone jack output on T400s

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  Sound out of speakers works fine.
  When plugging in headphones into the headphone jack, no sound comes out of 
the speakers (as expected) but then no sound comes out of the headphones (not 
expected).

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
  Uname: Linux 2.6.35-999-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  will   1499 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf292 irq 48'
 Mixer name : 'Conexant CX20585'
 Components : 'HDA:14f15069,17aa2132,00100300'
 Controls  : 12
 Simple ctrls  : 10
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
6HHT14WW-1.02'
 Mixer name : 'ThinkPad EC 6HHT14WW-1.02'
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  CheckboxSubmission: 51faabf3890cfea94341cf57731e3dd8
  CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
  Date: Wed Jun 30 15:57:24 2010
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en
   LANG=ja_JP.utf8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  dmi.bios.date: 04/21/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6HET29WW (1.14 )
  dmi.board.name: 2801CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6HET29WW(1.14):bd04/21/2010:svnLENOVO:pn2801CTO:pvrThinkPadT400s:rvnLENOVO:rn2801CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2801CTO
  dmi.product.version: ThinkPad T400s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1817033] [NEW] Unable to correctly print PDF file: Error: Ignoring spurious ET operator.

2019-02-22 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Upstream bug report https://github.com/OpenPrinting/cups-
filters/issues/93.

The university document
[antrag_exmatrikulation.pdf](https://github.com/OpenPrinting/cups-
filters/files/2881078/antrag_exmatrikulation.pdf) causes problems on
different printers.

Printing on the Canon iR-ADV C2225i using the Canon PCL, an error page
is first printed, and on the first page after _Email_ everything is
missing. The second page is fine.

```
  Error: Ignoring spurious ET operator. Output may be inco 
```

For that printer a special filter `sicgsfilter` has to be used, and is
distributed by Canon. This also happens with their CQue 4.0-1 release
from September 2018.

```
 *FoomaticRIPCommandLine: "gs -q -dBATCH %F -dPARANOIDSAFER -dNOPAUSE %B%A%C 
-dPDFFitPage  -sOutputFile=- - %D%E | sicgsfilter -MPCL -NP %G%H%I -u 
-V -n "
```

On the Epson printer _WorkForce WF-2660_, no error page is printed, but
on the first page everything after _Email_ _is missing_ too.

Trying to use different pdftops renderers did not make any difference.
For example,

```
 lpr -o pdftops-renderer=pdftops -P chipprinterpcl antrag_exmatrikulation.pdf
```

gave the same result, the same with `pdftocairo`, `acroread`, `mupdf`.

Following `/usr/share/doc/cups-filters/README.gz` and
https://wiki.ubuntu.com/DebuggingPrintingProblems, I verified that the
exact same PDF is put into the CUPS spool directory, and I captured the
data sent to the printer with the commands below.

$ lpadmin -p chipprinterpclfile -E -v file:/tmp/printout -P 
~/chipprinterpcl.ppd
$ lpr -P chipprinterpclfile -o psdebug ~/antrag_exmatrikulation.pdf

I get the attached Postscript file, which indeed contains the error
messages.

```
ESC%-12345X@PJL CQue4.0-1 x86_64
@PJL COMMENT CANPJL SET USERNAME="pmenzel@localhost"
@PJL COMMENT CANPJL SET DOCNAME="antrag_exmatrikulation.pdf!pmenz"
@PJL SET RENDERMODE=COLOR
@PJL COMMENT CANPJL SET FORCEMONOCHROME=FALSE
@PJL COMMENT CANPJL SET SORTERMODE=GENERICON
@PJL COMMENT CANPJL SET STAPLE=GENERICOFF
@PJL COMMENT CANPJL SET BOOKLET=GENERICOFF
@PJL SET DENSITY=0
@PJL ENTER LANGUAGE=PCL
    Error: Ignoring spurious ET operator.
   Output may be incorrect.
    Error: Executing Do inside a text block, attempting to recover
   Output may be incorrect.
    Error: Executing Do inside a text block, attempting to recover
   Output may be incorrect.
    Error: Ignoring spurious ET operator.
   Output may be incorrect.
    Error: Executing Do inside a text block, attempting to recover
   Output may be incorrect.
    Error: illegal nested BT operator detected.
   Output may be incorrect.
    Error: Ignoring spurious ET operator.
   Output may be incorrect.
    Error: Executing Do inside a text block, attempting to recover
   Output may be incorrect.
    Error: illegal nested BT operator detected.
   Output may be incorrect.
[…]
```

Please find that file attached.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: cups 2.2.8-5ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
Date: Thu Feb 21 10:23:08 2019
InstallationDate: Installed on 2017-03-20 (702 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lpstat:
 device for Canon-iR-ADV-C2225: lpd://winprima.molgen.mpg.de/test
 device for DCP375CW: socket://141.14.220.198
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 04f3:2234 Elan Microelectronics Corp. 
 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9360
Papersize: a4
PpdFiles:
 Canon-iR-ADV-C2225: Canon iR-ADV C2225 PCL
 DCP375CW: Brother DCP-375CW CUPS
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash initcall_debug log_buf_len=16M 
vt.handoff=1
SourcePackage: cups
UpgradeStatus: Upgraded to cosmic on 2018-10-30 (113 days ago)
dmi.bios.date: 09/27/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.10.0
dmi.board.name: 0839Y6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.10.0:bd09/27/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.

** Affects: cairo (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug cosmic
-- 
Unable to correctly print PDF file: Error: Ignoring spurious ET operator.
https://bugs.launchpad.net/bugs/1817033
You received this bug notification

[Touch-packages] [Bug 678017] Re: [Realtek ALC268] Playback problem

Further to comments #5 and #6, closing now as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [Realtek ALC268] Playback problem

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  media player even audio or video get stucks after a few minutes,when
  press any key on the keyboard or touch the touch pad the problem
  solved!none of the answers in the internet solved the problems.i am
  using acer extensa 5630 laptop,and there is no problem with
  ubuntu10.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: alsa-base 1.0.23+dfsg-1ubuntu4
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vishnu 3450 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf480 irq 47'
 Mixer name : 'Intel Cantiga HDMI'
 Components : 'HDA:10ec0268,1025013c,00100101 
HDA:14f12c06,10250093,0010 HDA:80862802,80860101,0010'
 Controls  : 20
 Simple ctrls  : 11
  Date: Sun Nov 21 08:54:49 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_IN
   SHELL=/bin/bash
  SelectedCard: 0 Intel HDA-Intel - HDA Intel
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [Realtek ALC268] Playback problem
  dmi.bios.date: 10/30/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.36
  dmi.board.name: Homa
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.36:bd10/30/2009:svnAcer:pnExtensa5630:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5630
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 616945] Re: [Realtek ID 665] ALSA test tone not correctly played back

Further to comment #3, closing now as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [Realtek ID 665] ALSA test tone not correctly played back

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  I installed Ubuntu 10.04 on a new Dell Studio 14 Laptop, and there has
  been no sound output from it. I did try following steps on various
  posts, but of no use.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sri1849 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf070 irq 22'
 Mixer name : 'Realtek ID 665'
 Components : 'HDA:10ec0665,10280414,0013'
 Controls  : 4
 Simple ctrls  : 3
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xcfedc000 irq 17'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [off]
  Date: Thu Aug 12 23:25:48 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_IN
   SHELL=/bin/bash
  SelectedCard: 0 Intel HDA-Intel - HDA Intel
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [Realtek ID 665] ALSA test tone not correctly played back
  dmi.bios.date: 04/13/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0133D9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A04
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd04/13/2010:svnDellInc.:pnStudio1458:pvrA04:rvnDellInc.:rn0133D9:rvrA04:cvnDellInc.:ct8:cvrA04:
  dmi.product.name: Studio 1458
  dmi.product.version: A04
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 672568] Re: No sound

Further to comment #3, closing as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  No sound

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  I did a fresh install of 10.10 with an ISO I downloaded today and ran
  updates, but no sound, I have tried a number of the things in this
  thread without any luck. System dual boots to XP and sound is fine
  there. Note I am trying to use the on board sound, not the HDMI built
  into the video card. Any help would be appreciated.

  Thanks

  GIGABYTE GA-G41M-ES2L LGA 775 Intel G41 Micro ATX Intel Motherboard

  
  ALSA Information Script v 0.4.59
  

  This script visits the following commands/files to collect diagnostic
  information about your ALSA installation and sound related hardware.

  dmesg
  lspci
  lsmod
  aplay
  amixer
  alsactl
  /proc/asound/
  /sys/class/sound/
  ~/.asoundrc (etc.)

  See 'alsa-info.sh --help' for command line options.

  /sbin/alsactl: get_control:239: Cannot read control info '2,0,0,Front 
Playback Volume,0': Invalid argument
  cat: /tmp/alsa-info.KmM1rFJbUa/alsactl.tmp: No such file or directory
  Automatically upload ALSA information to www.alsa-project.org? [y/N] : y
  Uploading information to www.alsa-project.org ... Done!

  Your ALSA information is located at http://www.alsa-
  project.org/db/?f=ae...422d9b72e314eb

  From lidex on Ubuntu Forums:

  Another gigabyte board. We need you to submit a bug report please. Start 
here. Try running this command in a terminal for 10.04 or later:
  Code:

  ubuntu-bug audio

  Reference the Ubuntu-Bug Audio link in my sig.
  https://wiki.ubuntu.com/DebuggingSoundProblems

  After that try using a different kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: alsa-base 1.0.23+dfsg-1ubuntu4
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info:
   Error: command ['amixer', '-c', '0', 'info'] failed with exit code 1: 
amixer: Mixer load hw:0 error: Invalid argument
   Card hw:0 'Intel'/'HDA Intel at 0xfdff8000 irq 44'
 Mixer name : 'Realtek ALC887'
 Components : 'HDA:10ec0887,1458a002,00100302'
 Controls  : 38
  Card0.Amixer.values: Error: command ['amixer', '-c', '0'] failed with exit 
code 1: amixer: Mixer hw:0 load error: Invalid argument
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xfddfc000 irq 45'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Mon Nov  8 07:18:41 2010
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Soundcard not detected
  dmi.bios.date: 06/21/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: G41M-ES2L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd06/21/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-ES2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-ES2L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1425257] Re: [SATELLITE P50-B-11M, Realtek ALC284, Speaker, Internal] No sound at all

Further to comment #5, closing now as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [SATELLITE P50-B-11M, Realtek ALC284, Speaker, Internal] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  Other outputs (eg HDMI audio out) seem to work fine, but the internal
  speakers do nothing. They work in Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   matt   3099 F...m pulseaudio
   /dev/snd/controlC1:  matt   3099 F pulseaudio
   /dev/snd/controlC0:  matt   3099 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Feb 24 19:38:57 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-02-19 (4 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   matt   3099 F...m pulseaudio
   /dev/snd/controlC1:  matt   3099 F pulseaudio
   /dev/snd/controlC0:  matt   3099 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [SATELLITE P50-B-11M, Realtek ALC284, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.40
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG20SQ
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.40:bd11/26/2014:svnTOSHIBA:pnSATELLITEP50-B-11M:pvrPSPNUE-02L04KEN:rvnTOSHIBA:rnVG20SQ:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: SATELLITE P50-B-11M
  dmi.product.version: PSPNUE-02L04KEN
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 709889] Re: [IDT ID 76c1] ALSA test tone not correctly played back

Further to above comments, closing as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [IDT ID 76c1] ALSA test tone not correctly played back

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  alsamixer updated from ubuntu-audio-dev ppa this morning (29Jan2011).
  Sound stopped working immediately after reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
  Uname: Linux 2.6.32-28-generic i686
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf9ffc000 irq 16'
 Mixer name : 'IDT ID 76c1'
 Components : 'HDA:111d76c1,12974001,00100102'
 Controls  : 11
 Simple ctrls  : 6
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x805'/'USB Device 0x46d:0x805 at usb-:00:1d.7-1.3, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0805'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 6144
 Mono: Capture 2238 [36%] [14.74dB] [on]
  Date: Sat Jan 29 12:35:03 2011
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SelectedCard: 0 Intel HDA-Intel - HDA Intel
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [IDT ID 76c1] ALSA test tone not correctly played back
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: FG41
  dmi.board.vendor: Shuttle Inc
  dmi.board.version: V20
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Shuttle Inc
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/04/2010:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: SG41
  dmi.product.version: V20
  dmi.sys.vendor: Shuttle Inc

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

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

[Touch-packages] [Bug 1571531] Re: cupsd cause apparmor denials for /etc/ld.so.preload

After some initialization, this message only appears below in the ESET
event log.

Look:

22/02/2019 08:14:13 Media control access Can not unblock removable media
(org.freedesktop.udisks2.filesystem-mount)

The rest are gone :)

Waiting for new instructions

Thank you

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

Title:
  cupsd cause apparmor denials for /etc/ld.so.preload

Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  There is a constant flood of messages in dmesg:

  [ 4431.638163] audit: type=1400 audit(1460962510.272:60): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10559 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661208] audit: type=1400 audit(1460962510.296:61): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661390] audit: type=1400 audit(1460962510.296:62): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661759] audit: type=1400 audit(1460962510.296:63): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.661936] audit: type=1400 audit(1460962510.296:64): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661937] audit: type=1400 audit(1460962510.296:65): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.662534] audit: type=1400 audit(1460962510.296:66): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 5081.410342] audit: type=1400 audit(1460963160.033:67): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10810 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 5081.446507] audit: type=1400 audit(1460963160.069:68): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10815 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 18 10:56:37 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1003 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  Lpstat: device for Generic-PCL-5e: socket://192.168.1.100:9100
  MachineType: LENOVO 4298R86
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-PCL-5e.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-PCL-5e.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=3d4ce850-6e8a-4cf5-9b82-fb135c22fe1e ro
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2015-10-29 (171 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4298R86
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4298R86
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-03-12T15:11:15.740184

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

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

[Touch-packages] [Bug 1571531] Re: cupsd cause apparmor denials for /etc/ld.so.preload

2019-02-22 Thread Seth Arnold

Hello snapd friends, Edson has an antivirus tool that requires all
processes have write access to a unix domain socket. Adding a rule to
/etc/apparmor.d/abstractions/base addressed many profiles but not
snapd's snap-confine profile.

What's the mechanism for admins to add local rules to this file?

Thanks

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

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

Title:
  cupsd cause apparmor denials for /etc/ld.so.preload

Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  There is a constant flood of messages in dmesg:

  [ 4431.638163] audit: type=1400 audit(1460962510.272:60): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10559 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661208] audit: type=1400 audit(1460962510.296:61): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661390] audit: type=1400 audit(1460962510.296:62): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661759] audit: type=1400 audit(1460962510.296:63): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.661936] audit: type=1400 audit(1460962510.296:64): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661937] audit: type=1400 audit(1460962510.296:65): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.662534] audit: type=1400 audit(1460962510.296:66): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 5081.410342] audit: type=1400 audit(1460963160.033:67): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10810 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 5081.446507] audit: type=1400 audit(1460963160.069:68): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10815 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 18 10:56:37 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1003 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  Lpstat: device for Generic-PCL-5e: socket://192.168.1.100:9100
  MachineType: LENOVO 4298R86
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-PCL-5e.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-PCL-5e.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=3d4ce850-6e8a-4cf5-9b82-fb135c22fe1e ro
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2015-10-29 (171 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4298R86
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4298R86
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-03-12T15:11:15.740184

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

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

[Touch-packages] [Bug 1775018] Re: Fix for openssl 1.0.2 backport

2019-02-22 Thread Dimitri John Ledkov

https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750
is [18.04 FEAT] Add support for CPACF enhancements to openssl
also known as ltc-163655 and is only present in bionic.

In xenial:
we have src:openssl, 1.0.2 which does not have CPACF backport, and therefore 
the attached patch does not apply at all, and also there are no issues to fix 
there either. Unless, you mean openssl-ibmca is also affected in xenial? in 
that case do you have a patch for openssl-ibmca?

In bionic:
we have src:openssl, 1.1.0 which is not affected as you say, as the default 
openssl version.
we also have src:openssl1.0 which does have CPACF backport and the attached 
patch applies to. Please note, that openssl1.0 is only used by a small amount 
of packages in bionic. We are preparing the update for that package.


** Description changed:

- This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and
- upstream code are not affected ).
+ [Impact]
  
- Original LP ticket : 
+  * Fix hw accelerated performance impact on s390x with non-default
+ openssl1.0.
+ 
+ [Test Case]
+ 
+  * Test that performance of hw accelerated crypto is improved / i.e. ssl
+ speed test
+ 
+  * Test that openssh still works, just in case.
+ 
+ [Regression Potential]
+ 
+  * This only changes accelerated codepath on s390x, for specific algos when 
CPACF is enabled on the system cpu, which is usually on.
+  * Same fix is already in use by 1.1.0 default openssl package, and well 
excercised on bionic and up.
+ 
+ [Other Info]
+  
+  * original bug report.
+ 
+ 
+ This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and 
upstream code are not affected ).
+ 
+ Original LP ticket :
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750

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

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

** Also affects: openssl1.0 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Changed in: openssl (Ubuntu Bionic)
   Status: New => Fix Released

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

** Also affects: openssl1.0 (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: openssl (Ubuntu Cosmic)
   Status: New => Fix Released

** Changed in: openssl1.0 (Ubuntu)
   Status: New => Confirmed

** Changed in: openssl1.0 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: openssl1.0 (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: openssl1.0 (Ubuntu Cosmic)
   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/1775018

Title:
  Fix for openssl 1.0.2 backport

Status in Ubuntu on IBM z Systems:
  Triaged
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl1.0 package in Ubuntu:
  Confirmed
Status in openssl source package in Xenial:
  Invalid
Status in openssl1.0 source package in Xenial:
  Invalid
Status in openssl source package in Bionic:
  Fix Released
Status in openssl1.0 source package in Bionic:
  Confirmed
Status in openssl source package in Cosmic:
  Fix Released
Status in openssl1.0 source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

   * Fix hw accelerated performance impact on s390x with non-default
  openssl1.0.

  [Test Case]

   * Test that performance of hw accelerated crypto is improved / i.e.
  ssl speed test

   * Test that openssh still works, just in case.

  [Regression Potential]

   * This only changes accelerated codepath on s390x, for specific algos when 
CPACF is enabled on the system cpu, which is usually on.
   * Same fix is already in use by 1.1.0 default openssl package, and well 
excercised on bionic and up.

  [Other Info]
   
   * original bug report.

  
  This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and 
upstream code are not affected ).

  Original LP ticket :
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750

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

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

[Touch-packages] [Bug 1654448] Re: Dell XPS 13 9350, 9360 and 9370 headphone audio hiss

2019-02-22 Thread Kai-Heng Feng

Chris,

Please file a separate bug report which collects information, so I can
work on a patch and build a test kernel.

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

Title:
  Dell XPS 13 9350, 9360 and 9370 headphone  audio hiss

Status in Dell Sputnik:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions

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

[Touch-packages] [Bug 574037] Re: Lucid: pulseaudio causes many wakeups while playing music

Further to comment #6, closing as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Lucid: pulseaudio causes many wakeups while playing music

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  While playing music in rhythmbox or totem pulseaudio causes many CPU-
  wakeups as can be seen with powertop. When rhythmbox is on but not
  playing any music the CPU-wakeups are much lower.

  I will attach the output from 'powertop -d' while
  - rhythmbox playing music (playing)
  - rhythmbox not playing music but loaded (idle)

  As I can't remember ever seen such behavior in previous versions of
  Ubuntu I think this is a bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mreiche1392 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 11'
 Mixer name : 'Analog Devices AD1981B'
 Components : 'AC97a:41445374'
 Controls  : 26
 Simple ctrls  : 18
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
1QHT23WW-1.08'
 Mixer name : 'ThinkPad EC 1QHT23WW-1.08'
 Components : ''
 Controls  : 2
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
 Playback channels: Mono
 Limits: Playback 0 - 14
 Mono: Playback 8 [57%] [on]
  Date: Mon May  3 00:05:52 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
  ProcEnviron:
   LANG=de_DE.utf8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  dmi.bios.date: 09/22/2005
  dmi.bios.vendor: IBM
  dmi.bios.version: 1QET97WW (3.02 )
  dmi.board.name: 2672CXG
  dmi.board.vendor: IBM
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: IBM
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnIBM:bvr1QET97WW(3.02):bd09/22/2005:svnIBM:pn2672CXG:pvrThinkPadX31:rvnIBM:rn2672CXG:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
  dmi.product.name: 2672CXG
  dmi.product.version: ThinkPad X31
  dmi.sys.vendor: IBM

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

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

[Touch-packages] [Bug 797444] Re: No sound Ubuntu 11.04- No soundcard detected

Further to comment #3, closing as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  No sound Ubuntu 11.04- No soundcard detected

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  Hello,
  I have a problem with ALSA and it does not detect my audio card. I have tried 
to solve using ALSA update, but it does not work. I made a report for web 
ALSA (with script alsa-info.sh)
   Thanks

  !!
  !!ALSA Information Script v 0.4.60
  !!

  !!Script ran on: Tue Jun 14 22:28:09 UTC 2011

  !!Linux Distribution
  !!--

  Ubuntu 11.04 \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu
  11.04"

  !!DMI Information
  !!---

  Manufacturer:  Hewlett-Packard
  Product Name:  Compaq Presario C700 Notebook PC
  Product Version:   F.34

  !!Kernel Information
  !!--

  Kernel release:2.6.38-8-generic
  Operating System:  GNU/Linux
  Architecture:  i686
  Processor: i686
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version:
  Library version:1.0.9
  Utilities version:  1.0.24.2

  !!Loaded ALSA modules
  !!---

  !!Sound Servers on this system
  !!

  Pulseaudio:
    Installed - Yes (/usr/bin/pulseaudio)
    Running - Yes

  ESound Daemon:
    Installed - Yes (/usr/bin/esd)
    Running - No

  !!Soundcards recognised by ALSA
  !!-

  !!PCI Soundcards installed in the system
  !!--

  00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
  Controller (rev 04)

  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!

  00:1b.0 0403: 8086:284b (rev 04)
   Subsystem: 14f1:5051

  !!Modprobe options (Sound related)
  !!

  snd-atiixp-modem: index=-2
  snd-intel8x0m: index=-2
  snd-via82xx-modem: index=-2
  snd-usb-audio: index=-2
  snd-usb-caiaq: index=-2
  snd-usb-ua101: index=-2
  snd-usb-us122l: index=-2
  snd-usb-usx2y: index=-2
  snd-cmipci: mpu_port=0x330 fm_port=0x388
  snd-pcsp: index=-2
  snd-usb-audio: index=-2

  !!Loaded sound module options
  !!--

  !!ALSA Device nodes
  !!-

  !!Aplay/Arecord output
  !!

  APLAY

  aplay: device_list:240: no soundcards found...

  ARECORD

  arecord: device_list:240: no soundcards found...

  !!Amixer output
  !!-

  !!Alsactl output
  !!-

  --startcollapse--
  --endcollapse--

  !!All Loaded Modules
  !!--

  Module
  binfmt_misc
  parport_pc
  ppdev
  vboxnetadp
  vboxnetflt
  vboxdrv
  arc4
  i915
  ath5k
  uvcvideo
  ath
  mac80211
  joydev
  hp_wmi
  sparse_keymap
  usbhid
  videodev
  decnet
  drm_kms_helper
  hid
  drm
  ipt_REJECT
  ipt_LOG
  xt_limit
  xt_tcpudp
  ipt_addrtype
  cfg80211
  xt_state
  psmouse
  serio_raw
  ip6table_filter
  ip6_tables
  nf_nat_irc
  nf_conntrack_irc
  nf_nat_ftp
  nf_nat
  nf_conntrack_ipv4
  nf_defrag_ipv4
  nf_conntrack_ftp
  nf_conntrack
  i2c_algo_bit
  iptable_filter
  ip_tables
  x_tables
  video
  lp
  parport
  usb_storage
  uas
  ahci
  8139too
  8139cp
  libahci

  !!ALSA/HDA dmesg
  !!--

  [   22.193179] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on 
minor 0
  [   22.229939] HDA Intel :00:1b.0: PCI INT A -> GSI 22 (level, low) -> 
IRQ 22
  [   22.230026] HDA Intel :00:1b.0: irq 43 for MSI/MSI-X
  [   22.230060] HDA Intel :00:1b.0: setting latency timer to 64
  [   22.230066] ALSA hda_intel.c:2590: chipset global capabilities = 0x4401
  [   22.280050] ALSA hda_intel.c:915: codec_mask = 0x1
  [   22.282377] ALSA hda_intel.c:1364: codec #0 probed OK
  [   22.367224] ALSA hda_codec.c:3796: hda_codec: model 'hp' is selected for 
config 14f1:5051 (HP Spartan 1.1)
  [   22.367424] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input11
  [   22.369317] input: HDA Intel Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input12
  [   22.369576] input: HDA Intel Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input13
  [   22.376160] input: HDA Intel Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input14
  [   22.593466] ppdev: user-space parallel port driver
  --
  [  444.590791] [UFW BLOCK] IN=eth0 OUT= 
MAC=01:00:5e:00:00:01:00:26:44:bd:ed:3e:08:00 SRC=192.168.1.254 DST=224.0.0.1 
LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=40350 DF PROTO=2
  [  559.772183] HDA Intel :00:1b.0: PCI INT A disabled
  [  559.882991] HDA Intel :00:1b.0: PCI INT A -> GSI 22 (level, low) -> 
IRQ 22
  [  559.883078] HDA Intel :00:1b.0:

[Touch-packages] [Bug 685471] Re: Dell Precision M4500 internal mic does not work

Further to comment #3, closing as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Dell Precision M4500 internal mic does not work

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  The internal mic of my Dell Precision M4500 does not work in Ubuntu
  10.10 64bit (2.6.35-23-generic #41-Ubuntu SMP Wed Nov 24 11:55:36 UTC
  2010 x86_64 GNU/Linux).n souns

  In Sound Preferences / Hadrware I have:
  High Definition Audio Controller
  Internal Audio

  In Input/Controller there are:
  Microphone2 / Line in
  Microphone2 / Microphone
  Microphone1 / Line in
  Microphone1 / Microphone

  If I use external mic, it works with this configuration:
  Internal Audio -> Microphone1 / Microphone
  but sound quality is very bad.

  Internal mic does not work with any configuration.

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

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

[Touch-packages] [Bug 540906] Re: external sound not working right on hp 5102

Further to comment #3, closing as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  external sound not working right on hp 5102

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  The external speakers do not work on the hp 5102.  Sound does come
  through the headphones though.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 3116 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0x9450 irq 19'
 Mixer name : 'IDT 92HD75B2X5'
 Components : 'HDA:111d7608,103c3653,00100202'
 Controls  : 28
 Simple ctrls  : 18
  CheckboxCommand: cat /proc/asound/cards
  CheckboxDescription:
   Detecting your sound device(s):
   
   $output
   
   Is this correct?
  CheckboxTest: list_audio_devices
  Date: Thu Mar 18 12:49:10 2010
  DistroRelease: Ubuntu 9.10
  LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: alsa-base 1.0.20+dfsg-1ubuntu5
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: alsa-driver
  Tags: checkbox-bug
  Uname: Linux 2.6.31-14-generic i686

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

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

[Touch-packages] [Bug 518969] Re: Extigy Sound level of AC3 optical input muted after karmic boot

Further to comment #11, closing as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Extigy Sound level of AC3 optical input muted after karmic boot

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to Karmic, the input level on the optical and digital
  cinch input (or DolbyDigital decoder) of the extigy card is muted.

  This is very annoying since i'm using the card to decode DD to the 5.1
  cinch output and send it to my Amp.

  (The PC driver also seems to have problems with the 5.1 output => Bug
  518966 )

  I did not succeed to enable the DD sound output with any mixer (Pulseaudio / 
Alsa) on ubuntu.
  Once i started windows with the Extigy mixer App, the card was working 
correctly.

  Best regards.

  ProblemType: Bug
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: Extigy [Sound Blaster Extigy], device 0: USB Audio [USB Audio]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jean-luc   2681 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'HDMI'/'HDA ATI HDMI at 0xfe9fc000 irq 29'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100100'
 Controls  : 4
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'Extigy'/'Creative Technology Ltd. Sound Blaster Extigy at 
usb-:00:1a.0-2, full speed'
 Mixer name : 'USB Mixer'
 Components : 'USB041e:3000'
 Controls  : 23
 Simple ctrls  : 17
  Date: Mon Feb  8 19:58:00 2010
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: fglrx
  Package: alsa-base 1.0.20+dfsg-1ubuntu5
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
  SourcePackage: alsa-driver
  Uname: Linux 2.6.31-19-generic x86_64
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: Extigy [Sound Blaster Extigy], device 0: USB Audio [USB Audio]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 3381 F pulseaudio
   /dev/snd/pcmC0D3p:   ubuntu 3381 F...m pulseaudio
   /dev/snd/controlC1:  ubuntu 3381 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'HDMI'/'HDA ATI HDMI at 0xfe9fc000 irq 17'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100100'
 Controls  : 4
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'Extigy'/'Creative Technology Ltd. Sound Blaster Extigy at 
usb-:00:1a.0-2, full speed'
 Mixer name : 'USB Mixer'
 Components : 'USB041e:3000'
 Controls  : 23
 Simple ctrls  : 17
  DistroRelease: Ubuntu 10.04
  LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  Package: alsa-driver (not installed)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
  Tags: lucid
  Uname: Linux 2.6.32-16-generic x86_64
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Touch-packages] [Bug 1654448] Re: Dell XPS 13 9350, 9360 and 9370 headphone audio hiss

2019-02-22 Thread Chris

Hi Kai-Heng Feng, I experience a hissing noise on Ubuntu Ubuntu 18.04.2
LTS with Dell XPS 9370. Is there some patch I can apply to prevent this
from happening?

The hissing begins as soon as I plug headphones or speakers in and it
goes away when I mute the system.

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

Title:
  Dell XPS 13 9350, 9360 and 9370 headphone  audio hiss

Status in Dell Sputnik:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions

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

[Touch-packages] [Bug 703677] Re: headphones don't work

Further to comment #7, closing as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  headphones don't work

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: software-center

  The headphone jack used to work in Windows 7, but after installing
  Ubuntu 10.10 the headphones don't work.  When I use the headphones the
  sound still comes out of the laptop as usual.  I tried to edit this
  file /etc/modprobe.d/alsa-base.conf  I added this line to the very end
  of it:

  options snd-hda-intel model=toshiba position_fix=0

  That appears to do nothing.  My laptop is a Toshiba Satellite
  L645D-S4030.

  This is what I get when I run $ sudo lshw -c sound
*-multimedia
 description: Audio device
 product: SBx00 Azalia (Intel HDA)
 vendor: ATI Technologies Inc
 physical id: 14.2
 bus info: pci@:00:14.2
 version: 40
 width: 64 bits
 clock: 33MHz
 capabilities: pm bus_master cap_list
 configuration: driver=HDA Intel latency=64
 resources: irq:16 memory:f430-f4303fff

  Running $ alsamixer
  tells me:

  Card: HDA ATI SB
  Chip: Conexant CX20585

  How do I get my headphones to work?

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: software-center 3.0.7
  ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
  Uname: Linux 2.6.35-24-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  Date: Sun Jan 16 14:58:38 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: software-center

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

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

[Touch-packages] [Bug 1034403] Re: VIA VT2020 no front audio

Further to comment #5, closing as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  VIA VT2020 no front audio

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  When headphones are connected to the front panel audio socket, the
  rear audio sound is correctly muted but no audio is outputted through
  the headphones. The front microphone (which connects to the
  motherboard using the same cable) works correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  Uname: Linux 3.3.7-030307-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: VT2020 Analog [VT2020 Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  ian2011 F xfce4-volumed
ian2017 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf7c1 irq 48'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:11060441,1458a014,00100100 
HDA:80862806,80860101,0010'
 Controls  : 63
 Simple ctrls  : 26
  Date: Wed Aug  8 15:14:08 2012
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   2011  2017  2017  ian   F xfce4-volumed
ian   F pulseaudio
   /dev/snd/pcmC0D0p:   ian   F...m pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., VIA VT2020, Green Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd03/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 425196] Re: no sound after resuming from hibernate

Further to comments #10 and #11 closing as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  no sound after resuming from hibernate

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  Audio works fine after a reboot or when my computer is turned on after
  being shut down normally. However, when I hibernate (choosing
  "Hibernate" from the "System>Shut Down" menu) and start up my computer
  there's no audio.

  rune@runescomp:~$ lsb_release -rd
  Description:  Ubuntu karmic (development branch)
  Release:  9.10

  The following command fixes the problem:

  sudo alsa force-reload

  It seems this is a duplicate of bug #11149, but I'm not sure. I use a
  different sound module than that of bug #11149.

  ProblemType: Bug
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rune   3488 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'T71Space'/'Terratec Aureon 7.1-Space at 0xbf00, irq 22'
 Mixer name : 'ICE1724 - multitrack'
 Components : ''
 Controls  : 56
 Simple ctrls  : 33
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdcfc000 irq 17'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,0010'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined
 Playback channels: Mono
 Mono: Playback [off]
  Date: Sun Sep  6 15:32:43 2009
  DistroRelease: Ubuntu 9.10
  Package: alsa-base 1.0.20+dfsg-1ubuntu4
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_DK.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
  SourcePackage: alsa-driver
  Uname: Linux 2.6.31-9-generic i686
  UserAsoundrc:
   # ALSA library configuration file
   
   # Include settings that are under the control of asoundconf(1).
   # (To disable these settings, comment out this line.)
   

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

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

[Touch-packages] [Bug 554781] Re: No sound at all.

Further to comment #3 by reporter closing as fixed.

** Changed in: alsa-driver (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  No sound at all.

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: pulseaudio

  I am using Ubuntu 9.10 - the Karmic Koala and I have no sound at all.
  I the pulse audio control is shows that sound is playing but nothing
  is coming out of my speakers.  I have a HP dv3, and according to all
  the test I've ran, my card is recognised and loaded.

  ProblemType: Bug
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jordan 1677 F pulseaudio
   /dev/snd/pcmC0D0p:   jordan 1677 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 22'
 Mixer name : 'Intel G45 DEVCTG'
 Components : 'HDA:111d7608,103c306e,00100202 
HDA:80862802,80860101,0010'
 Controls  : 32
 Simple ctrls  : 19
  Date: Sat Apr  3 15:38:18 2010
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: wl
  Package: pulseaudio 1:0.9.19-0ubuntu4.1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-20-generic i686
  XsessionErrors:
   (gnome-settings-daemon:1747): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:1747): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (nautilus:1839): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
   (polkit-gnome-authentication-agent-1:1876): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (firefox:2063): GLib-WARNING **: g_set_prgname() called multiple times

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

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

[Touch-packages] [Bug 1571531] Re: cupsd cause apparmor denials for /etc/ld.so.preload

I restarted and rephased the procedure and says that the apparmor can
not recharge.

Look:

edson@edson-p6540br:~$ sudo su
[sudo] senha para edson: 
root@edson-p6540br:/home/edson# gedit
malloc_consolidate(): invalid chunk size
Abortado (imagem do núcleo gravada)
root@edson-p6540br:/home/edson# sudo /etc/init.d/apparmor reload
[] Reloading apparmor configuration (via systemctl): 
apparmor.serviceapparmor.service is not active, cannot reload.
 failed!
root@edson-p6540br:/home/edson# 

See too:

22/02/2019 07:31:50Media control accessCannot unblock removable media 
(org.freedesktop.udisks2.filesystem-mount)   
22/02/2019 07:30:33 Preload library access control  Cannot connect to 
/tmp/esets.sock: Permission denied
22/02/2019 07:30:33 Preload library access control  Cannot connect to 
/tmp/esets.sock: Permission denied

See too:

root@edson-p6540br:/home/edson# dmesg | grep DENIED
[   38.206971] audit: type=1400 audit(1550831497.819:22): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1204 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   38.206975] audit: type=1400 audit(1550831497.819:23): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1204 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   38.206978] audit: type=1400 audit(1550831497.819:24): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1204 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   46.486291] audit: type=1400 audit(1550831506.095:25): apparmor="DENIED" 
operation="change_onexec" info="label not found" error=-2 
profile="/usr/lib/snapd/snap-confine" 
name="snap.canonical-livepatch.canonical-livepatchd" pid=1204 
comm="snap-confine"
[   46.723239] audit: type=1400 audit(1550831506.335:26): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1363 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   46.723261] audit: type=1400 audit(1550831506.335:27): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1363 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   46.723289] audit: type=1400 audit(1550831506.335:28): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1363 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   46.746999] audit: type=1400 audit(1550831506.359:29): apparmor="DENIED" 
operation="change_onexec" info="label not found" error=-2 
profile="/usr/lib/snapd/snap-confine" 
name="snap.canonical-livepatch.canonical-livepatchd" pid=1363 
comm="snap-confine"
[   46.914262] audit: type=1400 audit(1550831506.523:30): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1399 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   46.914283] audit: type=1400 audit(1550831506.523:31): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1399 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   46.914313] audit: type=1400 audit(1550831506.523:32): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1399 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   46.946874] audit: type=1400 audit(1550831506.559:33): apparmor="DENIED" 
operation="change_onexec" info="label not found" error=-2 
profile="/usr/lib/snapd/snap-confine" 
name="snap.canonical-livepatch.canonical-livepatchd" pid=1399 
comm="snap-confine"
[   47.244230] audit: type=1400 audit(1550831506.855:34): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1432 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
root@edson-p6540br:/home/edson# 


I am waiting for new instructions as messages continue to appear on Eset.

Thank You

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

Title:
  cupsd cause apparmor denials for /etc/ld.so.preload

Status in apparmor package in Ubuntu:
  New

Bug description:
  There is a constant flood of messages in dmesg:

  [ 4431.638163] audit: type=1400 audit(1460962510.272:60): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10559 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661208] audit: type=1400

[Touch-packages] [Bug 1571531] Re: cupsd cause apparmor denials for /etc/ld.so.preload

Hi, Arnold

It includes the comma in the line after the unix as requested, but
appeared error message at the time of applying sudo /etc/init.d/apparmor
reload

unix, (connect, send, receive) peer =
(addr="@2F746D702F65736574732E736F636B00*"),

edson@edson-p6540br:~$ sudo su
[sudo] senha para edson: 
root@edson-p6540br:/home/edson# gedit
malloc_consolidate(): invalid chunk size
Abortado (imagem do núcleo gravada)
root@edson-p6540br:/home/edson# sudo /etc/init.d/apparmor reload
[] Reloading apparmor configuration (via systemctl): apparmor.serviceJob 
for apparmor.service failed because the control process exited with error code.
See "systemctl status apparmor.service" and "journalctl -xe" for details.
 failed!
root@edson-p6540br:/home/edson# sudo /etc/init.d/apparmor reload
[] Reloading apparmor configuration (via systemctl): 
apparmor.serviceapparmor.service is not active, cannot reload.
 failed!
root@edson-p6540br:/home/edson#

I will restart and then I will return again


Obrigado

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

Title:
  cupsd cause apparmor denials for /etc/ld.so.preload

Status in apparmor package in Ubuntu:
  New

Bug description:
  There is a constant flood of messages in dmesg:

  [ 4431.638163] audit: type=1400 audit(1460962510.272:60): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10559 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661208] audit: type=1400 audit(1460962510.296:61): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661390] audit: type=1400 audit(1460962510.296:62): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661759] audit: type=1400 audit(1460962510.296:63): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.661936] audit: type=1400 audit(1460962510.296:64): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661937] audit: type=1400 audit(1460962510.296:65): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.662534] audit: type=1400 audit(1460962510.296:66): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 5081.410342] audit: type=1400 audit(1460963160.033:67): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10810 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 5081.446507] audit: type=1400 audit(1460963160.069:68): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10815 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 18 10:56:37 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1003 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  Lpstat: device for Generic-PCL-5e: socket://192.168.1.100:9100
  MachineType: LENOVO 4298R86
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-PCL-5e.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-PCL-5e.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=3d4ce850-6e8a-4cf5-9b82-fb135c22fe1e ro
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2015-10-29 (171 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4298R86
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4298R86
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.cups:

[Touch-packages] [Bug 1599646] Re: E-mail report contains repeated "Reading database ... NN%" lines

Verified with unattended-upgrades/1.1ubuntu1.18.04.9 on Bionic:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic/bionic/amd64/u/unattended-
upgrades/20190221_190835_4cafb@/log.gz :

...
From: root 
Message-Id: 
Date: Thu, 21 Feb 2019 18:10:59 +

Unattended upgrade returned: True

Packages that were upgraded:
 apparmor apport apt apt-utils base-files dirmngr distro-info-data 
 file gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client 
 gpg-wks-server gpgconf gpgsm gpgv gvfs gvfs-common gvfs-daemons 
 gvfs-libs initramfs-tools initramfs-tools-bin initramfs-tools-core 
 krb5-locales libapparmor1 libapt-inst2.0 libapt-pkg5.0 
 libavahi-client3 libavahi-common-data libavahi-common3 
 libavahi-glib1 libcaca0 libcups2 libdns-export1100 libgcrypt20 
 libglib2.0-0 libglib2.0-data libgssapi-krb5-2 libisc-export169 
 libjavascriptcoregtk-4.0-18 libjpeg-turbo-progs libjpeg-turbo8 
 libk5crypto3 libkrb5-3 libkrb5support0 liblcms2-2 libmagic-mgc 
 libmagic1 libmysqlclient20 libnss-systemd libnss3 libpam-systemd 
 libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libperl5.26 
 libpng16-16 libpolkit-agent-1-0 libpolkit-backend-1-0 
 libpolkit-gobject-1-0 libpoppler-glib8 libpoppler73 libprocps6 
 libpython2.7 libpython2.7-minimal libpython2.7-stdlib 
 libsoup-gnome2.4-1 libsoup2.4-1 libssl1.1 libsystemd0 libtiff5 
 libudev1 libudisks2-0 libwavpack1 libwebkit2gtk-4.0-37 libx11-6 
 libx11-data libx11-xcb1 libxkbcommon0 libxml2 netplan.io nplan 
 openssl perl perl-base perl-modules-5.26 policykit-1 procps 
 python3-apport python3-problem-report python3-requests systemd 
 systemd-sysv tzdata udev udisks2 xserver-common xserver-xorg-core 
 xserver-xorg-legacy 


Package installation log:
Log started: 2019-02-21  18:09:19
Preconfiguring packages ...
Preparing to unpack .../apparmor_2.12-4ubuntu5.1_amd64.deb ...
Unpacking apparmor (2.12-4ubuntu5.1) over (2.12-4ubuntu5) ...
Setting up apparmor (2.12-4ubuntu5.1) ...
Installing new version of config file 
/etc/apparmor.d/abstractions/private-files ...
Installing new version of config file 
/etc/apparmor.d/abstractions/private-files-strict ...
Installing new version of config file 
/etc/apparmor.d/abstractions/ubuntu-browsers.d/user-files ...
Processing triggers for systemd (237-3ubuntu10) ...
Processing triggers for man-db (2.8.3-2) ...
Log ended: 2019-02-21  18:09:20
...

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

Title:
  E-mail report contains repeated "Reading database ... NN%" lines

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Cosmic:
  Fix Committed
Status in apt package in Debian:
  New

Bug description:
  [Impact]

   * Unattended-upgrades sends the following repeating dpkg progress lines with 
almost no informational value in the email report:
  ...
   (Reading database ...
   (Reading database ... 5%
   (Reading database ... 10%
   (Reading database ... 15%
   (Reading database ... 20%
   (Reading database ... 25%
   (Reading database ... 30%
   (Reading database ... 35%
   (Reading database ... 40%
   (Reading database ... 45%
   (Reading database ... 50%
   (Reading database ... 55%
   (Reading database ... 60%
   (Reading database ... 65%
   (Reading database ... 70%
   (Reading database ... 75%
   (Reading database ... 80%
   (Reading database ... 85%
   (Reading database ... 90%
   (Reading database ... 95%
  (Reading database ... 60486 files and directories currently installed.)
  ...

   * This makes the report email too verbose and makes harder to spot
  real problems.

  [Test Case]

   * Run package autopkgtest and observe no such lines in the echoed
  email in upgrade-all-security and upgrade-between-snapshots tests.

  [Regression Potential]

   * The fix filters dpkg's output only and in the worst case other
  lines could be missing or u-u could crash. Since the applied hard-
  coded regex pattern is fairly simple and we observed no crashes in the
  tests those regressions are unlikey to occur.

  [Originial Bug Text]

  This concerns unattended-upgrades 0.90 in Xenial.

  Here is an excerpt from an e-mail report sent out by u-u after the
  upgrade process is completed:

   Package installation log:
   Log started: 2016-07-06  17:24:21
   Preconfiguring packages ...
   (Reading database ...
   (Reading database ... 5%
   (Reading database ... 10%
   (Reading database ... 15%
   (Reading database ... 20%
   (Reading database ... 25%
   (Reading database ... 30%
   (Reading database ... 35%
   (Reading database ... 40%
   (Reading database ... 45%
   (Reading database ... 50%
   (Reading database ... 55%
   (Reading database ... 60%
   (Reading database ... 65%
   (Reading database ... 70%
   (Reading

[Touch-packages] [Bug 1815494] Re: May remove autoremovable non-kernel packages matching pattern from APT::VersionedKernelPackages

Verified with unattended-upgrades/1.1ubuntu1.18.04.9 on Bionic:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic/bionic/amd64/u/unattended-
upgrades/20190221_190835_4cafb@/log.gz :

...

Running ./test_remove_unused.py with python3
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=lucid-security
APT::VersionedKernelPackages is not set
Checking: test-package ([])
pkgs that look like they should be upgraded: test-package

Fetched 0 B in 0s (0 B/s)   
fetch.run() result: 0
http://archive.ubuntu.com/ubuntu/test-package_2.0_all.deb' ID:0 
ErrorText: ''>
check_conffile_prompt(/tmp/autopkgtest.SPDe54/build.D9P/src/test/root.unused-deps/var/cache/apt/archives/test-package_2.0_all.deb)
found pkg: test-package
blacklist: []
whitelist: []
Packages that will be upgraded: test-package
Writing dpkg log to 
./root.unused-deps/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
applying set ['test-package']
left to upgrade set()
All upgrades installed
marking old-unused-dependency for removal
marking test-package-dependency for removal
marking linux-image-4.05.0-1021-kvm for removal
marking any-old-unused-modules for removal
Packages that were successfully auto-removed: any-old-unused-modules 
linux-image-4.05.0-1021-kvm old-unused-dependency test-package-dependency
Packages that are kept back: 
InstCount=0 DelCount=0 BrokenCount=0
Extracting content from 
./root.unused-deps/var/log/unattended-upgrades/unattended-upgrades-dpkg.log 
since 2019-02-21 18:01:34
/tmp/autopkgtest.SPDe54/build.D9P/src/test/unattended_upgrade.py:1129: 
ResourceWarning: unclosed file <_io.TextIOWrapper name=13 mode='w' 
encoding='UTF-8'>
  options.verbose or options.debug)
/tmp/autopkgtest.SPDe54/build.D9P/src/test/unattended_upgrade.py:1129: 
ResourceWarning: unclosed file <_io.TextIOWrapper name=12 mode='r' 
encoding='UTF-8'>
  options.verbose or options.debug)
/tmp/autopkgtest.SPDe54/build.D9P/src/test/unattended_upgrade.py:1474: 
ResourceWarning: unclosed file <_io.TextIOWrapper name=10 mode='w' 
encoding='UTF-8'>
  res, error = cache_commit(cache, logfile_dpkg, verbose)
/tmp/autopkgtest.SPDe54/build.D9P/src/test/unattended_upgrade.py:1474: 
ResourceWarning: unclosed file <_io.TextIOWrapper name=9 mode='r' 
encoding='UTF-8'>
  res, error = cache_commit(cache, logfile_dpkg, verbose)
.Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=lucid-security
Using 
(^linux-image-[0-9]+\.[0-9\.]+-.*|^.*-modules-[0-9]+\.[0-9\.]+-.*|^linux-headers-[0-9]+\.[0-9\.]+-.*)
 regexp to find kernel packages
Using 
(^linux-image-4\.15\.0\-45\-generic$|^.*-modules-4\.15\.0\-45\-generic$|^linux-headers-4\.15\.0\-45\-generic$)
 regexp to find running kernel packages
Checking: test-package ([])
pkgs that look like they should be upgraded: test-package

Fetched 0 B in 0s (0 B/s)   
fetch.run() result: 0
http://archive.ubuntu.com/ubuntu/test-package_2.0_all.deb' ID:0 
ErrorText: ''>
check_conffile_prompt(/tmp/autopkgtest.SPDe54/build.D9P/src/test/root.unused-deps/var/cache/apt/archives/test-package_2.0_all.deb)
found pkg: test-package
blacklist: []
whitelist: []
Removing unused kernel packages: linux-image-4.05.0-1021-kvm
marking linux-image-4.05.0-1021-kvm for removal
Keeping auto-removable linux-image-4.05.0-1021-kvm package(s) because it would 
also remove the following packages which should be kept in this step: 
test-package
Packages that were successfully auto-removed: 
Packages that are kept back: linux-image-4.05.0-1021-kvm
Packages that will be upgraded: test-package
Writing dpkg log to 
./root.unused-deps/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
applying set ['test-package']
left to upgrade set()
All upgrades installed
marking test-package-dependency for removal
Packages that were successfully auto-removed: test-package-dependency
Packages that are kept back: 
InstCount=0 DelCount=0 BrokenCount=0
Extracting content from 
./root.unused-deps/var/log/unattended-upgrades/unattended-upgrades-dpkg.log 
since 2019-02-21 18:01:35
/tmp/autopkgtest.SPDe54/build.D9P/src/test/unattended_upgrade.py:1129: 
ResourceWarning: unclosed file <_io.TextIOWrapper name=16 mode='w' 
encoding='UTF-8'>
  options.verbose or options.debug)
/tmp/autopkgtest.SPDe54/build.D9P/src/test/unattended_upgrade.py:1129: 
ResourceWarning: unclosed file <_io.TextIOWrapper name=15 mode='r' 
encoding='UTF-8'>
  options.verbose or options.debug)
/tmp/autopkgtest.SPDe54/build.D9P/src/test/unattended_upgrade.py:1474: 
ResourceWarning: unclosed file <_io.TextIOWrapper name=16 mode='w' 
encoding='UTF-8'>
  res, error = cache_commit(cache, logfile_dpkg, verbose)
/tmp/autopkgtest.SPDe54/build.D9P/src/test/unattended_upgrade.py:1474: 
ResourceWarning: unclosed file

[Touch-packages] [Bug 1817097] Comment bridged from LTC Bugzilla

2019-02-22 Thread bugproxy

--- Comment From christian.r...@de.ibm.com 2019-02-22 05:23 EDT---
Further investigations revealed that no dm-crypt mapper device is needed at all 
to reproduce the behaviour but just two block devices with different physical 
block sizes, e.g.

# blockdev --getpbsz /dev/mapper/mpatha-part1
512
# blockdev --getpbsz /dev/dasdc1
4096

Mind to first add the SCSI device/the device with the smaller phys. block size 
to the volume group when running the 'vgcreate' command.
# blockdev --getpbsz /dev/mapper/TEST_VG-LV1
512

Use one SCSI disk partition (multipath devices are recommended but not 
required) and one DASD partition to recreate the pvmove problem. Run pvs after 
the move completed, and unmount, mount the fs again.
The fsck.ext4 does not detect any problems on the fs which is unexpected.

Pertaining syslog entries:
Feb 22 11:09:23 system kernel: print_req_error: I/O error, dev dasdc, sector 
280770
Feb 22 11:09:23 system kernel: Buffer I/O error on dev dm-3, logical block 
139265, lost sync page write
Feb 22 11:09:23 system kernel: JBD2: Error -5 detected when updating journal 
superblock for dm-3-8.
Feb 22 11:09:23 system kernel: Aborting journal on device dm-3-8.
Feb 22 11:09:23 system kernel: print_req_error: I/O error, dev dasdc, sector 
280770
Feb 22 11:09:23 system kernel: Buffer I/O error on dev dm-3, logical block 
139265, lost sync page write
Feb 22 11:09:23 system kernel: JBD2: Error -5 detected when updating journal 
superblock for dm-3-8.
Feb 22 11:09:23 system kernel: print_req_error: I/O error, dev dasdc, sector 
2242
Feb 22 11:09:23 system kernel: Buffer I/O error on dev dm-3, logical block 1, 
lost sync page write
Feb 22 11:09:23 system kernel: EXT4-fs (dm-3): I/O error while writing 
superblock
Feb 22 11:09:23 system kernel: EXT4-fs error (device dm-3): ext4_put_super:938: 
Couldn't clean up the journal
Feb 22 11:09:23 system kernel: EXT4-fs (dm-3): Remounting filesystem read-only
Feb 22 11:09:23 system kernel: print_req_error: I/O error, dev dasdc, sector 
2242
Feb 22 11:09:23 system kernel: Buffer I/O error on dev dm-3, logical block 1, 
lost sync page write
Feb 22 11:09:23 system kernel: EXT4-fs (dm-3): I/O error while writing 
superblock
Feb 22 11:09:32 system kernel: EXT4-fs (dm-3): bad block size 1024

The very last syslog line repeats upon 'mount /dev/mapper/TEST_VG-LV1 /mnt ' 
attempts, the 1024 block size is related to
# blockdev --getbsz /dev/mapper/TEST_VG-LV1
1024

After the pvmove the physical blocksize is also changed to
# blockdev --getpbsz /dev/mapper/TEST_VG-LV1
4096

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

Title:
  pvmove causes file system corruption without notice upon move from 512
  -> 4096 logical block size devices

Status in Ubuntu on IBM z Systems:
  New
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Problem Description---
  Summary
  ===
  Environment: IBM Z13 LPAR and z/VM Guest
   IBM Type: 2964 Model: 701 NC9
  OS:  Ubuntu 18.10 (GNU/Linux 4.18.0-13-generic s390x)
   Package: lvm2 version 2.02.176-4.1ubuntu3
  LVM: pvmove operation corrupts file system when using 4096 (4k) logical block 
size
   and default block size being 512 bytes in the underlying devices
  The problem is immediately reproducible.

  We see a real usability issue with data destruction as consequence - which is 
not acceptable.
  We expect 'pvmove' to fail with error in such situations to prevent fs 
destruction,
  which might possibly be overridden by a force flag.

  
  Details
  ===
  After a 'pvmove' operation is run to move a physical volume onto an ecrypted
  device with 4096 bytes logical block size we experience a file system 
corruption.
  There is no need for the file system to be mounted, but the problem surfaces
  differently if so.

  Either, the 'pvs' command after the pvmove shows
/dev/LOOP_VG/LV: read failed after 0 of 1024 at 0: Invalid argument
/dev/LOOP_VG/LV: read failed after 0 of 1024 at 314507264: Invalid argument
/dev/LOOP_VG/LV: read failed after 0 of 1024 at 314564608: Invalid argument
/dev/LOOP_VG/LV: read failed after 0 of 1024 at 4096: Invalid argument

  or

  a subsequent mount shows (after umount if the fs had previously been mounted 
as in our
  setup)
  mount: /mnt: wrong fs type, bad option, bad superblock on 
/dev/mapper/LOOP_VG-LV, missing codepage or helper program, or other error.

  A minimal setup of LVM using one volume group with one logical volume defined,
  based on one physical volume is sufficient to raise the problem. One more 
physical
  volume of the same size is needed to run the pvmove operation to. 

LV
 |
  VG: LOOP_VG [ ]
 |
  PV: /dev/loop0   -->   /dev/mapper/enc-loop
  ( backed by /dev/mapper/enc-loop )

  The physical volumes are backed by loopback devices

[Touch-packages] [Bug 1599646] Re: E-mail report contains repeated "Reading database ... NN%" lines

Verified on unattended-upgrades/1.5ubuntu3.18.10.2 for Cosmic:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/u/unattended-upgrades/20190221_173137_1ecf7@/log.gz
 :
...
>From root@autopkgtest Thu Feb 21 17:09:54 2019
Return-path: 
Envelope-to: root@autopkgtest
Delivery-date: Thu, 21 Feb 2019 17:09:54 +
Received: from root by autopkgtest with local (Exim 4.91)
(envelope-from )
id 1gwrr8-0001k8-Ag
for root@autopkgtest; Thu, 21 Feb 2019 17:09:54 +
Subject: [package on hold] unattended-upgrades result for 
adt-cosmic-amd64-unattended-upgrades-20190221-165334.novalocal: SUCCESS
To: root@autopkgtest
Auto-Submitted: auto-generated
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: root 
Message-Id: 
Date: Thu, 21 Feb 2019 17:09:54 +

Unattended upgrade result: All upgrades installed

Packages that were upgraded:
 apt apt-utils dirmngr distro-info-data gnupg gnupg-l10n gnupg-utils 
 gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm gpgv gvfs 
 gvfs-common gvfs-daemons gvfs-libs initramfs-tools 
 initramfs-tools-bin initramfs-tools-core krb5-locales libapt-inst2.0 
 libapt-pkg5.0 libavahi-client3 libavahi-common-data libavahi-common3 
 libavahi-glib1 libcaca0 libcups2 libgssapi-krb5-2 
 libjavascriptcoregtk-4.0-18 libk5crypto3 libkrb5-3 libkrb5support0 
 libmysqlclient20 libnss-systemd libnss3 libpam-systemd libperl5.26 
 libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 
 libpoppler-glib8 libpoppler79 libssl1.0.0 libssl1.1 libsystemd0 
 libtiff5 libudev1 libwavpack1 libwebkit2gtk-4.0-37 openssh-client 
 openssl perl perl-base perl-modules-5.26 policykit-1 
 python3-requests snapd systemd systemd-sysv tzdata udev 
 xserver-common xserver-xorg-core xserver-xorg-legacy 
Packages with upgradable origin but kept back:
 libpython3.6-minimal libpython3.6-stdlib python3.6 python3.6-minimal 

Packages that were auto-removed:
 libncursesw5 libtinfo5 


Package installation log:
Log started: 2019-02-21  17:08:07
Preparing to unpack .../distro-info-data_0.38ubuntu0.1_all.deb ...
Unpacking distro-info-data (0.38ubuntu0.1) over (0.38) ...
Setting up distro-info-data (0.38ubuntu0.1) ...
Log ended: 2019-02-21  17:08:09
...


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

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

Title:
  E-mail report contains repeated "Reading database ... NN%" lines

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Cosmic:
  Fix Committed
Status in apt package in Debian:
  New

Bug description:
  [Impact]

   * Unattended-upgrades sends the following repeating dpkg progress lines with 
almost no informational value in the email report:
  ...
   (Reading database ...
   (Reading database ... 5%
   (Reading database ... 10%
   (Reading database ... 15%
   (Reading database ... 20%
   (Reading database ... 25%
   (Reading database ... 30%
   (Reading database ... 35%
   (Reading database ... 40%
   (Reading database ... 45%
   (Reading database ... 50%
   (Reading database ... 55%
   (Reading database ... 60%
   (Reading database ... 65%
   (Reading database ... 70%
   (Reading database ... 75%
   (Reading database ... 80%
   (Reading database ... 85%
   (Reading database ... 90%
   (Reading database ... 95%
  (Reading database ... 60486 files and directories currently installed.)
  ...

   * This makes the report email too verbose and makes harder to spot
  real problems.

  [Test Case]

   * Run package autopkgtest and observe no such lines in the echoed
  email in upgrade-all-security and upgrade-between-snapshots tests.

  [Regression Potential]

   * The fix filters dpkg's output only and in the worst case other
  lines could be missing or u-u could crash. Since the applied hard-
  coded regex pattern is fairly simple and we observed no crashes in the
  tests those regressions are unlikey to occur.

  [Originial Bug Text]

  This concerns unattended-upgrades 0.90 in Xenial.

  Here is an excerpt from an e-mail report sent out by u-u after the
  upgrade process is completed:

   Package installation log:
   Log started: 2016-07-06  17:24:21
   Preconfiguring packages ...
   (Reading database ...
   (Reading database ... 5%
   (Reading database ... 10%
   (Reading database ... 15%
   (Reading database ... 20%
   (Reading database ... 25%
   (Reading database ... 30%
   (Reading database ... 35%
   (Reading database ... 40%
   (Reading database ... 45%
   (Reading database ... 50%
   (Reading database ... 55%
   (Reading database ... 60%
   (Reading database ... 65%
   (Reading database ... 70%

[Touch-packages] [Bug 1815494] Re: May remove autoremovable non-kernel packages matching pattern from APT::VersionedKernelPackages

Verified on unattended-upgrades/1.5ubuntu3.18.10.2 for Cosmic:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/u/unattended-upgrades/20190221_173137_1ecf7@/log.gz
 :
...
Running ./test_remove_unused.py with python3
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=lucid-security
APT::VersionedKernelPackages is not set
Checking: test-package ([])
pkgs that look like they should be upgraded: test-package

Fetched 0 B in 0s (0 B/s)   
fetch.run() result: 0
http://archive.ubuntu.com/ubuntu/test-package_2.0_all.deb' ID:0 
ErrorText: ''>
check_conffile_prompt(/tmp/autopkgtest.5oXOHy/build.r1N/src/test/root.unused-deps/var/cache/apt/archives/test-package_2.0_all.deb)
found pkg: test-package
blacklist: []
whitelist: []
Packages that will be upgraded: test-package
Writing dpkg log to 
./root.unused-deps/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
applying set ['test-package']
left to upgrade set()
All upgrades installed
marking linux-image-4.05.0-1021-kvm for removal
marking old-unused-dependency for removal
marking any-old-unused-modules for removal
marking test-package-dependency for removal
Packages that were successfully auto-removed: any-old-unused-modules 
linux-image-4.05.0-1021-kvm old-unused-dependency test-package-dependency
Packages that are kept back: 
InstCount=0 DelCount=0 BrokenCount=0
...
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=lucid-security
Using 
(^linux-image-[0-9]+\.[0-9\.]+-.*|^.*-modules-[0-9]+\.[0-9\.]+-.*|^linux-headers-[0-9]+\.[0-9\.]+-.*)
 regexp to find kernel packages
Using 
(^linux-image-4\.18\.0\-15\-generic$|^.*-modules-4\.18\.0\-15\-generic$|^linux-headers-4\.18\.0\-15\-generic$)
 regexp to find running kernel packages
Checking: test-package ([])
pkgs that look like they should be upgraded: test-package

Fetched 0 B in 0s (0 B/s)   
fetch.run() result: 0
http://archive.ubuntu.com/ubuntu/test-package_2.0_all.deb' ID:0 
ErrorText: ''>
check_conffile_prompt(/tmp/autopkgtest.5oXOHy/build.r1N/src/test/root.unused-deps/var/cache/apt/archives/test-package_2.0_all.deb)
found pkg: test-package
blacklist: []
whitelist: []
Removing unused kernel packages: linux-image-4.05.0-1021-kvm
marking linux-image-4.05.0-1021-kvm for removal
Keeping auto-removable linux-image-4.05.0-1021-kvm package(s) because it would 
also remove the following packages which should be kept in this step: 
test-package
Packages that were successfully auto-removed: 
Packages that are kept back: linux-image-4.05.0-1021-kvm
Packages that will be upgraded: test-package
Writing dpkg log to 
./root.unused-deps/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
applying set ['test-package']
left to upgrade set()
All upgrades installed
marking test-package-dependency for removal
Packages that were successfully auto-removed: test-package-dependency
Packages that are kept back: 
InstCount=0 DelCount=0 BrokenCount=0
Extracting content from 
./root.unused-deps/var/log/unattended-upgrades/unattended-upgrades-dpkg.log 
since 2019-02-21 17:12:00
/tmp/autopkgtest.5oXOHy/build.r1N/src/test/unattended_upgrade.py:1163: 
ResourceWarning: unclosed file <_io.TextIOWrapper name=12 mode='w' 
encoding='UTF-8'>
  options.verbose or options.debug)
/tmp/autopkgtest.5oXOHy/build.r1N/src/test/unattended_upgrade.py:1163: 
ResourceWarning: unclosed file <_io.TextIOWrapper name=11 mode='r' 
encoding='UTF-8'>
  options.verbose or options.debug)
/tmp/autopkgtest.5oXOHy/build.r1N/src/test/unattended_upgrade.py:1513: 
ResourceWarning: unclosed file <_io.TextIOWrapper name=12 mode='w' 
encoding='UTF-8'>
  res, error = cache_commit(cache, logfile_dpkg, verbose)
/tmp/autopkgtest.5oXOHy/build.r1N/src/test/unattended_upgrade.py:1513: 
ResourceWarning: unclosed file <_io.TextIOWrapper name=11 mode='r' 
encoding='UTF-8'>
  res, error = cache_commit(cache, logfile_dpkg, verbose)
.
--
Ran 2 tests in 2.761s
...

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

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

Title:
  May remove autoremovable non-kernel packages matching pattern from
  APT::VersionedKernelPackages

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  New
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  * Non-kernel related autoremovable packages may be removed by

[Touch-packages] [Bug 1801439] Re: Unable to add software sources via the software-properties-qt

2019-02-22 Thread Hans P Möller

I uploaded solution in 
https://bazaar.launchpad.net/~hmollercl/software-properties/software-properties/revision/1071
waiting for merge

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

Title:
  Unable to add software sources via the software-properties-qt

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Test
  1. Start Software-properties. E.g. sudo software-properties-qt
  2. Navigate to Other Software (Tab), Add -> Add, to add a PPA
  3. Insert the PPA string. E.g. "deb 
http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " (or even the 
example repo given in the dialog, which is not a PPA)
  4. Click Okay.

  The software sources list does not contain the new field. Executing in
  terminal results in the following error message.

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 627, in on_add_clicked
  self.add_source_from_line(line)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
752, in add_source_from_line
  enable_source_code=enable_source_code)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
769, in add_source_from_shortcut
  worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
709, in check_and_add_key_for_whitelisted_shortcut
  self.options.keyserver)})
  AttributeError: type object 'OptionParsed' has no attribute 'keyserver'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: software-properties-qt 0.96.27
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Sat Nov  3 09:59:52 2018
  InstallationDate: Installed on 2018-10-19 (14 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1817281] [NEW] /usr/bin/zeitgeist-daemon:11:magazine_chain_pop_head:magazine_chain_prepare_fields:magazine_cache_push_magazine:thread_memory_magazine2_unload:g_slice_free1

2019-02-22 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
zeitgeist.  This problem was most recently seen with package version 
1.0-0.1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/b0f0bc44a5f414003e4a8fdea7d19dd0488a224b 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful bionic cosmic precise saucy trusty vivid wily xenial zesty

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

Title:
  /usr/bin/zeitgeist-
  
daemon:11:magazine_chain_pop_head:magazine_chain_prepare_fields:magazine_cache_push_magazine:thread_memory_magazine2_unload:g_slice_free1

Status in zeitgeist package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
zeitgeist.  This problem was most recently seen with package version 
1.0-0.1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/b0f0bc44a5f414003e4a8fdea7d19dd0488a224b 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1813227] Re: lvm2-pvscan services fails to start on S390X DPM

I saw [1] by xnox popping up, so he might work on this already. I have
pinged him to clarify.

[1]: https://code.launchpad.net/~xnox/ubuntu-seeds/+git/ubuntu-
seeds/+merge/363541

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

Title:
  lvm2-pvscan services fails to start on S390X DPM

Status in lvm2 package in Ubuntu:
  New

Bug description:
  The lvm2-pvscan service fails to start in the MAAS ephemeral
  environment. The service takes ~3 minutes to fail, blocking boot until
  failure. Curtin is expereincing a similar bug(LP:1813228) due to LVM.

  Release: 18.10(18.04 does not currently boot on S390X DPM)
  Kernel: 4.18.0-13-generic
  LVM: 2.02.176-4.1ubuntu3

  root@node3:~# lvm pvscan --cache --activate ay 8:98
    WARNING: Not using lvmetad because duplicate PVs were found.
    WARNING: Autoactivation reading from disk instead of lvmetad.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdb2 was already 
found on /dev/sdfe2.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sde2 was already 
found on /dev/sdfh2.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdba2 was 
already found on /dev/sdhd2.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdfj2 was 
already found on /dev/sddi2.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdg2 was already 
found on /dev/sddi2.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdbc2 was 
already found on /dev/sdfe2.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sdbf2 was 
already found on /dev/sdfh2.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sddb2 was 
already found on /dev/sdhd2.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sddr2 was 
already found on /dev/sdbq2.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdbh2 was 
already found on /dev/sddi2.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sddd2 was 
already found on /dev/sdfe2.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sddg2 was 
already found on /dev/sdfh2.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdfc2 was 
already found on /dev/sdhd2.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdfs2 was 
already found on /dev/sdbq2.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdp2 was already 
found on /dev/sdbq2.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device 
/dev/sdfe2 because device was seen first.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device 
/dev/sdfe2 because device was seen first.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device 
/dev/sdfe2 because device was seen first.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device 
/dev/sdfh2 because device was seen first.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device 
/dev/sdfh2 because device was seen first.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device 
/dev/sdfh2 because device was seen first.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device 
/dev/sdhd2 because device was seen first.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device 
/dev/sdhd2 because device was seen first.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device 
/dev/sdhd2 because device was seen first.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device 
/dev/sddi2 because device was seen first.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device 
/dev/sddi2 because device was seen first.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device 
/dev/sddi2 because device was seen first.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device 
/dev/sdbq2 because device was seen first.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device 
/dev/sdbq2 because device was seen first.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device 
/dev/sdbq2 because device was seen first.
    Cannot activate LVs in VG zkvm4 while PVs appear on duplicate devices.
    0 logical volume(s) in volume group "zkvm4" now active
    zkvm4: autoactivation failed.
    Cannot activate LVs in VG zkvm1 while PVs appear on duplicate devices.
    0 logical volume(s) in volume group "zkvm1" now active
    zkvm1: autoactivation failed.
    Cannot activate LVs in VG Z_APPL_ROOT_lvm_473D86E3 while PVs appear on 
duplicate devices.
    0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_473D86E3" now active
    Z_APPL_ROOT_lvm_473D86E3: autoactivation failed.
    Cannot activate LVs in VG Z_APPL_ROOT_lvm_BBD0E8D4 while PVs appear on 
duplicate devices.
    0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_BBD0E8D4" now active
    Z_APPL_ROOT_lvm_BBD0E8D4:

[Touch-packages] [Bug 1813227] Re: lvm2-pvscan services fails to start on S390X DPM

I also pinged jfh to make it part of the s390x related tracking

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

Title:
  lvm2-pvscan services fails to start on S390X DPM

Status in lvm2 package in Ubuntu:
  New

Bug description:
  The lvm2-pvscan service fails to start in the MAAS ephemeral
  environment. The service takes ~3 minutes to fail, blocking boot until
  failure. Curtin is expereincing a similar bug(LP:1813228) due to LVM.

  Release: 18.10(18.04 does not currently boot on S390X DPM)
  Kernel: 4.18.0-13-generic
  LVM: 2.02.176-4.1ubuntu3

  root@node3:~# lvm pvscan --cache --activate ay 8:98
    WARNING: Not using lvmetad because duplicate PVs were found.
    WARNING: Autoactivation reading from disk instead of lvmetad.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdb2 was already 
found on /dev/sdfe2.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sde2 was already 
found on /dev/sdfh2.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdba2 was 
already found on /dev/sdhd2.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdfj2 was 
already found on /dev/sddi2.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdg2 was already 
found on /dev/sddi2.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdbc2 was 
already found on /dev/sdfe2.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sdbf2 was 
already found on /dev/sdfh2.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sddb2 was 
already found on /dev/sdhd2.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sddr2 was 
already found on /dev/sdbq2.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdbh2 was 
already found on /dev/sddi2.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sddd2 was 
already found on /dev/sdfe2.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sddg2 was 
already found on /dev/sdfh2.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdfc2 was 
already found on /dev/sdhd2.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdfs2 was 
already found on /dev/sdbq2.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdp2 was already 
found on /dev/sdbq2.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device 
/dev/sdfe2 because device was seen first.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device 
/dev/sdfe2 because device was seen first.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device 
/dev/sdfe2 because device was seen first.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device 
/dev/sdfh2 because device was seen first.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device 
/dev/sdfh2 because device was seen first.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device 
/dev/sdfh2 because device was seen first.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device 
/dev/sdhd2 because device was seen first.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device 
/dev/sdhd2 because device was seen first.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device 
/dev/sdhd2 because device was seen first.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device 
/dev/sddi2 because device was seen first.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device 
/dev/sddi2 because device was seen first.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device 
/dev/sddi2 because device was seen first.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device 
/dev/sdbq2 because device was seen first.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device 
/dev/sdbq2 because device was seen first.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device 
/dev/sdbq2 because device was seen first.
    Cannot activate LVs in VG zkvm4 while PVs appear on duplicate devices.
    0 logical volume(s) in volume group "zkvm4" now active
    zkvm4: autoactivation failed.
    Cannot activate LVs in VG zkvm1 while PVs appear on duplicate devices.
    0 logical volume(s) in volume group "zkvm1" now active
    zkvm1: autoactivation failed.
    Cannot activate LVs in VG Z_APPL_ROOT_lvm_473D86E3 while PVs appear on 
duplicate devices.
    0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_473D86E3" now active
    Z_APPL_ROOT_lvm_473D86E3: autoactivation failed.
    Cannot activate LVs in VG Z_APPL_ROOT_lvm_BBD0E8D4 while PVs appear on 
duplicate devices.
    0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_BBD0E8D4" now active
    Z_APPL_ROOT_lvm_BBD0E8D4: autoactivation failed.
    Cannot activate LVs in VG Z_APPL_ROOT_lvm_382F5B8E while PVs appear on 
duplicate devices.
    0

[Touch-packages] [Bug 1813227] Re: lvm2-pvscan services fails to start on S390X DPM

2019-02-22 Thread Frank Heimes

** Tags added: s390x

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

Title:
  lvm2-pvscan services fails to start on S390X DPM

Status in lvm2 package in Ubuntu:
  New

Bug description:
  The lvm2-pvscan service fails to start in the MAAS ephemeral
  environment. The service takes ~3 minutes to fail, blocking boot until
  failure. Curtin is expereincing a similar bug(LP:1813228) due to LVM.

  Release: 18.10(18.04 does not currently boot on S390X DPM)
  Kernel: 4.18.0-13-generic
  LVM: 2.02.176-4.1ubuntu3

  root@node3:~# lvm pvscan --cache --activate ay 8:98
    WARNING: Not using lvmetad because duplicate PVs were found.
    WARNING: Autoactivation reading from disk instead of lvmetad.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdb2 was already 
found on /dev/sdfe2.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sde2 was already 
found on /dev/sdfh2.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdba2 was 
already found on /dev/sdhd2.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdfj2 was 
already found on /dev/sddi2.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdg2 was already 
found on /dev/sddi2.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdbc2 was 
already found on /dev/sdfe2.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sdbf2 was 
already found on /dev/sdfh2.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sddb2 was 
already found on /dev/sdhd2.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sddr2 was 
already found on /dev/sdbq2.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdbh2 was 
already found on /dev/sddi2.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sddd2 was 
already found on /dev/sdfe2.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sddg2 was 
already found on /dev/sdfh2.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdfc2 was 
already found on /dev/sdhd2.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdfs2 was 
already found on /dev/sdbq2.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdp2 was already 
found on /dev/sdbq2.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device 
/dev/sdfe2 because device was seen first.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device 
/dev/sdfe2 because device was seen first.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device 
/dev/sdfe2 because device was seen first.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device 
/dev/sdfh2 because device was seen first.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device 
/dev/sdfh2 because device was seen first.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device 
/dev/sdfh2 because device was seen first.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device 
/dev/sdhd2 because device was seen first.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device 
/dev/sdhd2 because device was seen first.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device 
/dev/sdhd2 because device was seen first.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device 
/dev/sddi2 because device was seen first.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device 
/dev/sddi2 because device was seen first.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device 
/dev/sddi2 because device was seen first.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device 
/dev/sdbq2 because device was seen first.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device 
/dev/sdbq2 because device was seen first.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device 
/dev/sdbq2 because device was seen first.
    Cannot activate LVs in VG zkvm4 while PVs appear on duplicate devices.
    0 logical volume(s) in volume group "zkvm4" now active
    zkvm4: autoactivation failed.
    Cannot activate LVs in VG zkvm1 while PVs appear on duplicate devices.
    0 logical volume(s) in volume group "zkvm1" now active
    zkvm1: autoactivation failed.
    Cannot activate LVs in VG Z_APPL_ROOT_lvm_473D86E3 while PVs appear on 
duplicate devices.
    0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_473D86E3" now active
    Z_APPL_ROOT_lvm_473D86E3: autoactivation failed.
    Cannot activate LVs in VG Z_APPL_ROOT_lvm_BBD0E8D4 while PVs appear on 
duplicate devices.
    0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_BBD0E8D4" now active
    Z_APPL_ROOT_lvm_BBD0E8D4: autoactivation failed.
    Cannot activate LVs in VG Z_APPL_ROOT_lvm_382F5B8E while PVs appear on 
duplicate devices.
    0 logical volume(s) in volume group

[Touch-packages] [Bug 1813227] Re: lvm2-pvscan services fails to start on S390X DPM

If the change by xnox fixes your case then the resolution is to ship multipath 
on those images.
@Lee - waiting for your answer if the services (and thereby the pvscan) works 
after multipath is installed.

In general I think xnox might work on this then (not sure)?
I subscribed him to be aware as this is not tagged up as s390x related yet.

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

Title:
  lvm2-pvscan services fails to start on S390X DPM

Status in lvm2 package in Ubuntu:
  New

Bug description:
  The lvm2-pvscan service fails to start in the MAAS ephemeral
  environment. The service takes ~3 minutes to fail, blocking boot until
  failure. Curtin is expereincing a similar bug(LP:1813228) due to LVM.

  Release: 18.10(18.04 does not currently boot on S390X DPM)
  Kernel: 4.18.0-13-generic
  LVM: 2.02.176-4.1ubuntu3

  root@node3:~# lvm pvscan --cache --activate ay 8:98
    WARNING: Not using lvmetad because duplicate PVs were found.
    WARNING: Autoactivation reading from disk instead of lvmetad.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdb2 was already 
found on /dev/sdfe2.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sde2 was already 
found on /dev/sdfh2.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdba2 was 
already found on /dev/sdhd2.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdfj2 was 
already found on /dev/sddi2.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdg2 was already 
found on /dev/sddi2.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdbc2 was 
already found on /dev/sdfe2.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sdbf2 was 
already found on /dev/sdfh2.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sddb2 was 
already found on /dev/sdhd2.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sddr2 was 
already found on /dev/sdbq2.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdbh2 was 
already found on /dev/sddi2.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sddd2 was 
already found on /dev/sdfe2.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sddg2 was 
already found on /dev/sdfh2.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdfc2 was 
already found on /dev/sdhd2.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdfs2 was 
already found on /dev/sdbq2.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdp2 was already 
found on /dev/sdbq2.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device 
/dev/sdfe2 because device was seen first.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device 
/dev/sdfe2 because device was seen first.
    WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device 
/dev/sdfe2 because device was seen first.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device 
/dev/sdfh2 because device was seen first.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device 
/dev/sdfh2 because device was seen first.
    WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device 
/dev/sdfh2 because device was seen first.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device 
/dev/sdhd2 because device was seen first.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device 
/dev/sdhd2 because device was seen first.
    WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device 
/dev/sdhd2 because device was seen first.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device 
/dev/sddi2 because device was seen first.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device 
/dev/sddi2 because device was seen first.
    WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device 
/dev/sddi2 because device was seen first.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device 
/dev/sdbq2 because device was seen first.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device 
/dev/sdbq2 because device was seen first.
    WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device 
/dev/sdbq2 because device was seen first.
    Cannot activate LVs in VG zkvm4 while PVs appear on duplicate devices.
    0 logical volume(s) in volume group "zkvm4" now active
    zkvm4: autoactivation failed.
    Cannot activate LVs in VG zkvm1 while PVs appear on duplicate devices.
    0 logical volume(s) in volume group "zkvm1" now active
    zkvm1: autoactivation failed.
    Cannot activate LVs in VG Z_APPL_ROOT_lvm_473D86E3 while PVs appear on 
duplicate devices.
    0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_473D86E3" now active
    Z_APPL_ROOT_lvm_473D86E3: autoactivation failed.
    Cannot activate LVs in VG

[Touch-packages] [Bug 1813227] Re: lvm2-pvscan services fails to start on S390X DPM