[Touch-packages] [Bug 828895] Re: Bash loses track of background children sometimes

2017-04-06 Thread Ben Harris 
Just a quick note: having moved some affected systems back to Ubuntu,
this bug has just manifested in production on Ubuntu 16.04 LTS:

/opt/dump/bin/dump_multi: line 11: wait: pid 56652 is not a child of
this shell

My test script above no longer demonstrates it though.  I'll see if I
can come up with one that does.

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

Title:
  Bash loses track of background children sometimes

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Under some circumstances (I've not worked out precisely what), bash
  can forget about background child processes.  For instance, if the
  file "simpletest" contains:

  #! /bin/bash

  count=0

  while [ $count -lt 51 ]; do
  count=$((count+1))
  /nonexist
  true &
  bgpids="$bgpids $!"
  done

  for pid in $bgpids; do
  wait $pid
  done

  then running "bash simpletest", seems to reliably report "simpletest:
  line 13: wait: pid 28850 is not a child of this shell" (with different
  PIDs each time, obviously).  Increasing the "51" in the script
  increases the number of errors.  Curiously, removing the call to a
  nonexistent program causes the problem to stop manifesting.

  "getconf CHILD_MAX" returns "undefined", which I think means that Bash
  should support an unlimited number of unwaited children.

  I've observed this on two different amd64 boxes running Ubuntu 10.04
  LTS, and it persisted after I upgraded the bash package to
  4.2-0ubuntu4.  I couldn't reproduce it on an i386 box running Ubuntu
  11.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: bash 4.1-2ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-33.72-server 2.6.32.41+drm33.18
  Uname: Linux 2.6.32-33-server x86_64
  Architecture: amd64
  Date: Thu Aug 18 17:04:23 2011
  InstallationMedia: Ubuntu-Server 10.04.3 LTS "Lucid Lynx" - Release amd64 
(20110719.2)
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: bash

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

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

[Touch-packages] [Bug 1865088] [NEW] setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP: Invalid argument"

2020-02-27 Thread Ben Harris 
Public bug reported:

When I specify a large font file using the FONT variable in .console-
setup, setupcon fails to load the font, reporting "putfont: KDFONTOP:
Invalid argument".  If I specify the same font by setting CODESET,
FONTFACE, and FONTSIZE, the setupcon loads it fine.

For instance, if I have the following files:

bjh21@sole:~$ tail .console-setup.test*
==> .console-setup.test1 <==
VERBOSE_OUTPUT="no"
ACTIVE_CONSOLES="/dev/tty[1-6]"
CHARMAP="UTF-8"
CODESET="Uni2"
FONTFACE="Terminus"
FONTSIZE="32x16"

==> .console-setup.test2 <==
VERBOSE_OUTPUT="no"
ACTIVE_CONSOLES="/dev/tty[1-6]"
CHARMAP="UTF-8"
FONT=Uni2-Terminus32x16.psf.gz

==> .console-setup.test3 <==
VERBOSE_OUTPUT="no"
ACTIVE_CONSOLES="/dev/tty[1-6]"
CHARMAP="UTF-8"
FONT=Uni2-Terminus16.psf.gz

Running "setupcon test1" correctly loads Uni2-Terminus32x16, but
"setupcon test2" does not, reporting "putfont: KDFONTOP: Invalid
argument".  "setupcon test3" works, demonstrating that not all uses of
FONT are broken.

I've attached the verbose output from "setupcon -v test2".

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: console-setup 1.178ubuntu2.9
ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
Uname: Linux 4.15.0-88-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: i386
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Feb 27 20:40:08 2020
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-motts-20100121-3
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-06-09 (3550 days ago)
InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 
20100121-21:52
PackageArchitecture: all
SourcePackage: console-setup
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug bionic i386

** Attachment added: "Output from "setupcon -v test2""
   
https://bugs.launchpad.net/bugs/1865088/+attachment/5331723/+files/setupcon.out

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

Title:
  setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP:
  Invalid argument"

Status in console-setup package in Ubuntu:
  New

Bug description:
  When I specify a large font file using the FONT variable in .console-
  setup, setupcon fails to load the font, reporting "putfont: KDFONTOP:
  Invalid argument".  If I specify the same font by setting CODESET,
  FONTFACE, and FONTSIZE, the setupcon loads it fine.

  For instance, if I have the following files:

  bjh21@sole:~$ tail .console-setup.test*
  ==> .console-setup.test1 <==
  VERBOSE_OUTPUT="no"
  ACTIVE_CONSOLES="/dev/tty[1-6]"
  CHARMAP="UTF-8"
  CODESET="Uni2"
  FONTFACE="Terminus"
  FONTSIZE="32x16"

  ==> .console-setup.test2 <==
  VERBOSE_OUTPUT="no"
  ACTIVE_CONSOLES="/dev/tty[1-6]"
  CHARMAP="UTF-8"
  FONT=Uni2-Terminus32x16.psf.gz

  ==> .console-setup.test3 <==
  VERBOSE_OUTPUT="no"
  ACTIVE_CONSOLES="/dev/tty[1-6]"
  CHARMAP="UTF-8"
  FONT=Uni2-Terminus16.psf.gz

  Running "setupcon test1" correctly loads Uni2-Terminus32x16, but
  "setupcon test2" does not, reporting "putfont: KDFONTOP: Invalid
  argument".  "setupcon test3" works, demonstrating that not all uses of
  FONT are broken.

  I've attached the verbose output from "setupcon -v test2".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: console-setup 1.178ubuntu2.9
  ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
  Uname: Linux 4.15.0-88-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: i386
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Feb 27 20:40:08 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-motts-20100121-3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-09 (3550 days ago)
  InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 
20100121-21:52
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1865088/+subscriptions

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

[Touch-packages] [Bug 1865088] Re: setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP: Invalid argument"

2020-02-27 Thread Ben Harris 
I notice that the output from setupcon mentions loading the font twice.
That seems to correspond to this fragment of code in setupcon:

# FONTFILES
FONTFILES=''
if [ "$FONT" ]; then
for f in $FONT; do
FONTFILES="$FONTFILES `findfile $fontdir $f`"
RES=`findfile $fontdir $f`
if [ -z "$RES" ]; then
fdec="${f%.gz}"
RES=`findfile $fontdir $fdec`
fi
FONTFILES="$FONTFILES $RES"
done
fi

It looks to me like this will add each font file to FONTFILES twice,
once in the first line of the loop body, and once in the last.

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

Title:
  setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP:
  Invalid argument"

Status in console-setup package in Ubuntu:
  New

Bug description:
  When I specify a large font file using the FONT variable in .console-
  setup, setupcon fails to load the font, reporting "putfont: KDFONTOP:
  Invalid argument".  If I specify the same font by setting CODESET,
  FONTFACE, and FONTSIZE, the setupcon loads it fine.

  For instance, if I have the following files:

  bjh21@sole:~$ tail .console-setup.test*
  ==> .console-setup.test1 <==
  VERBOSE_OUTPUT="no"
  ACTIVE_CONSOLES="/dev/tty[1-6]"
  CHARMAP="UTF-8"
  CODESET="Uni2"
  FONTFACE="Terminus"
  FONTSIZE="32x16"

  ==> .console-setup.test2 <==
  VERBOSE_OUTPUT="no"
  ACTIVE_CONSOLES="/dev/tty[1-6]"
  CHARMAP="UTF-8"
  FONT=Uni2-Terminus32x16.psf.gz

  ==> .console-setup.test3 <==
  VERBOSE_OUTPUT="no"
  ACTIVE_CONSOLES="/dev/tty[1-6]"
  CHARMAP="UTF-8"
  FONT=Uni2-Terminus16.psf.gz

  Running "setupcon test1" correctly loads Uni2-Terminus32x16, but
  "setupcon test2" does not, reporting "putfont: KDFONTOP: Invalid
  argument".  "setupcon test3" works, demonstrating that not all uses of
  FONT are broken.

  I've attached the verbose output from "setupcon -v test2".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: console-setup 1.178ubuntu2.9
  ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
  Uname: Linux 4.15.0-88-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: i386
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Feb 27 20:40:08 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-motts-20100121-3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-09 (3550 days ago)
  InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 
20100121-21:52
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1865088/+subscriptions

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

[Touch-packages] [Bug 1397587] [NEW] Volume display does not update when changing default sink

2014-11-29 Thread Ben Harris 
Public bug reported:

On my laptop I often have two PulseAudio sinks, the on-board audio
(alsa_output.pci-_00_1b.0.analog-stereo) and a Bluetooth speaker
(bluez_sink.8C_DE_52_2F_AF_F3).  I can choose the default destination
for sound output using the "Sound" pane of System Settings, and I can
separately change the volume setting of each sink using the "paman"
application.  When I adjust the volume using the sound menu, it affects
the default sink.  However, when I change to a different default sink,
the sound menu does not update and continues displaying the volume for
the previously-selected sink.  Only if I change the volume setting for
one of the sinks (e.g. using paman) does the sound menu update to show
the new volume level.

To reproduce:

Find a system with more than one sound sink.

Launch paman and open the Properties window for each sink.

Also open the Sound pane of System Settings.

Set one sink to maximum volume and one to minumum.

Switch between outputs using Systems Settings, and note that the sound
menu does not update to match the different volume settings of the two
sinks.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
Uname: Linux 3.16.0-25-generic i686
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: i386
CurrentDesktop: Unity
Date: Sat Nov 29 19:10:52 2014
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-motts-20100121-3
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-06-09 (1634 days ago)
InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 
20100121-21:52
SourcePackage: indicator-sound
UpgradeStatus: Upgraded to trusty on 2014-08-15 (105 days ago)

** Affects: indicator-sound (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 trusty

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

Title:
  Volume display does not update when changing default sink

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  On my laptop I often have two PulseAudio sinks, the on-board audio
  (alsa_output.pci-_00_1b.0.analog-stereo) and a Bluetooth speaker
  (bluez_sink.8C_DE_52_2F_AF_F3).  I can choose the default destination
  for sound output using the "Sound" pane of System Settings, and I can
  separately change the volume setting of each sink using the "paman"
  application.  When I adjust the volume using the sound menu, it
  affects the default sink.  However, when I change to a different
  default sink, the sound menu does not update and continues displaying
  the volume for the previously-selected sink.  Only if I change the
  volume setting for one of the sinks (e.g. using paman) does the sound
  menu update to show the new volume level.

  To reproduce:

  Find a system with more than one sound sink.

  Launch paman and open the Properties window for each sink.

  Also open the Sound pane of System Settings.

  Set one sink to maximum volume and one to minumum.

  Switch between outputs using Systems Settings, and note that the sound
  menu does not update to match the different volume settings of the two
  sinks.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7
  Uname: Linux 3.16.0-25-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Nov 29 19:10:52 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-motts-20100121-3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-06-09 (1634 days ago)
  InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 
20100121-21:52
  SourcePackage: indicator-sound
  UpgradeStatus: Upgraded to trusty on 2014-08-15 (105 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1397587/+subscriptions

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