[Touch-packages] [Bug 1334329] Re: Sound input settings not saved

2019-04-22 Thread Chris E. 
It's also in Ubuntu 19.04. Tested minutes ago with two different
laptops.

Steps to reproduce:

1. Mute mic
2. Restart laptop
3. Check mic state/volume level
-> Mic ins't muted. Volume level wasn't saved. Really annoying bug, if want to 
use Ubuntu in production/telcos

** Tags added: disco

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

Title:
  Sound input settings not saved

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When attempting to set my preferred sound input device, simply leaving
  sound preferences and going back to sound preferences, and selecting
  input, causes the default SPDIF to be selected again, and not the
  internal microphone I preferred.  I made a video to demonstrate what I
  mean by this here:  http://youtu.be/9Q9EQvLl_rA

  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  14.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  I really don't know.  It's just the sound preferences.

  3) What you expected to happen
  For my selected sound input to be saved.

  4) What happened instead
  Keeps defaulting to the top sound input

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  brandon   23953 F pulseaudio
   /dev/snd/controlC0:  brandon   23953 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 25 11:20:14 2014
  InstallationDate: Installed on 2014-04-26 (60 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Caicos HDMI Audio [Radeon HD 6400 Series] - HDA ATI HDMI
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/12
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP81.88Z.0047.B27.1201241646
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245A3940C91C80
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245A3940C91C80
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80:
  dmi.product.name: MacBookPro8,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1334329/+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 1804847] [NEW] systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

2018-11-23 Thread Chris E 
Public bug reported:

The following description is taken from:

https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237


Hello everyone,
I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After a 
recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php failed: 
Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp failed: 
Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/log/journal 
failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument
Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: 
Invalid argument

To verify I tried this:

/usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create 
elasticsearch.conf
Reading config file "elasticsearch.conf".
Running create action for entry d /var/run/elasticsearch
Found existing directory "/var/run/elasticsearch".
"/run/elasticsearch" has right mode 40755
chown "/run/elasticsearch" to 120.128
fchownat() of /run/elasticsearch failed: Invalid argument

I can manually chown the directories, e.g. "chown
elasticsearch:elasticsearch /var/run/elasticsearch" and restart the
service successfully.  My suspicion is, this is related to an upgrade of
systemd to 229-4ubuntu21.8.

At this point I don't know what to do.

I'm also confused about the version I have installed, which I thought is 
systemd-229. Howver, I looked at 
https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found 
that fchownat() is only used from version 238+:
Tag v237 (and earlier, including 229):
/.../
if (chown(fn,
  i->uid_set ? i->uid : UID_INVALID,
  i->gid_set ? i->gid : GID_INVALID) < 0)
return log_error_errno(errno, "chown(%s) 
failed: %m", path);
}
/.../

Tag v238

/.../
if (fchownat(fd,
 "",
 i->uid_set ? i->uid : UID_INVALID,
 i->gid_set ? i->gid : GID_INVALID,
 AT_EMPTY_PATH) < 0)
return log_error_errno(errno, "fchownat() of %s failed: %m", path);
/.../


Any help fixing this problem would be highly appreciated. 
Many thanks,
Rafael

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

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

Title:
  systemd=229-4ubuntu21.8 use of fchownat failes on some systems
  (openvz)

Status in systemd package in Ubuntu:
  New

Bug description:
  The following description is taken from:

  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237

  
  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
  Nov 17

[Touch-packages] [Bug 1785383] Re: missing EDNS0 record confuses systemd-resolved

2018-08-16 Thread Chris E 
In my opinion the log message from system also needs to be dropped - a
number of systems will use NXDOMAIN as a means of domain blocking/ad
blocking, and this isn't thus an exceptional event that needs logging
each time.

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

Title:
  missing EDNS0 record confuses systemd-resolved

Status in dnsmasq package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty
  answer for a domain it is authoritative for. systemd-resolved seems to
  get confused by this in certain circumstances; when using the stub
  resolver and requesting an address for which there are no 
  records, there can sometimes be a five second hang in resolution.

  This is fixed by upstream commit
  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78

  Not sure if it is worth cherry picking? I imagine the most likely
  trigger will be dnsmasq on routers which are not likely to be running
  Ubuntu, but maybe just in case.

  I also think there are some logic issues in systemd-resolved, upstream
  bug filed:

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

  Simple-ish test case:

  ---
  IFACE=dummy0
  SUBNET=10.0.0

  ip link add $IFACE type dummy
  ifconfig $IFACE ${SUBNET}.1/24
  dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo 
--host-record=test.test,${SUBNET}.1 &

  dig -t a test.test @10.0.0.1 | grep EDNS
  # should return "; EDNS ..."
  dig -t  test.test @10.0.0.1 | grep EDNS
  # again, should return "; EDNS ..." but doesn't
  ---

  To reproduce the systemd-resolved side of the problem

  ---
  # as above, but
  # now configure systemd-resolved to look at only 10.0.0.1, then

  systemd-resolve --reset-server-features
  # should exhibit five second delay then connect, assuming sshd is running :)
  ssh test.test
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq-base 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sat Aug  4 11:33:56 2018
  InstallationDate: Installed on 2018-05-31 (64 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1785383/+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