[Touch-packages] [Bug 1900404] Re: pulseaudio[2032]: No UCM verb is valid for hw:0
This also happens on 20.04.1 LTS. Please fix it there also. May be same as https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1056 ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1056 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1056 -- 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/1900404 Title: pulseaudio[2032]: No UCM verb is valid for hw:0 Status in pulseaudio package in Ubuntu: Fix Released Bug description: pulseaudio[2032]: No UCM verb is valid for hw:1 pulseaudio[2032]: No UCM verb is valid for hw:0 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat2032 F pulseaudio /dev/snd/controlC0: navycat2032 F pulseaudio /dev/snd/pcmC0D0p: navycat2032 F...m pulseaudio /dev/snd/controlC1: navycat2032 F pulseaudio CasperMD5CheckResult: skip Date: Mon Oct 19 11:57:52 2020 InstallationDate: Installed on 2020-10-07 (11 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1900404/+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 1793668] Re: xargs gives "[: err: unexpected operator" on Ubuntu but not Centos
** Changed in: findutils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to findutils in Ubuntu. https://bugs.launchpad.net/bugs/1793668 Title: xargs gives "[: err: unexpected operator" on Ubuntu but not Centos Status in findutils package in Ubuntu: Confirmed Bug description: cd /tmp rm -Rf tst err echo 'if [ "$1" == "" ]; then echo "empty"; else cat $1; fi' > tst chmod +x tst echo "a" > err ls err | xargs ./tst # ./tst: 1: [: err: unexpected operator ./tst err # works fine, outputs 'a' On Ubuntu the error will be shown, on Centos it won't. The error looks to be incorrect. $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ xargs --version xargs (GNU findutils) 4.7.0-git Copyright (C) 2017 Free Software Foundation, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1793668/+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 1772315] [NEW] ulimit can be enlarged, but not reduced back to below original
Public bug reported: Last login: Sat May 19 15:50:25 2018 from 192.168.0.130 ~$ ulimit -u 5000 ~$ ulimit -u 1000 ~$ ulimit -u 1 -bash: ulimit: max user processes: cannot modify limit: Operation not permitted ~$ ulimit -u 8000 -bash: ulimit: max user processes: cannot modify limit: Operation not permitted ~$ ulimit -u 7000 -bash: ulimit: max user processes: cannot modify limit: Operation not permitted ~$ ulimit -u 6000 -bash: ulimit: max user processes: cannot modify limit: Operation not permitted ~$ ulimit -u 5000 -bash: ulimit: max user processes: cannot modify limit: Operation not permitted ~$ ulimit -u 4000 -bash: ulimit: max user processes: cannot modify limit: Operation not permitted ~$ cat /etc/security/limits.conf | grep nproc | grep -v "^#" * soft nproc 20480 * hard nproc 20480 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bash 4.4.18-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Mon May 21 07:12:11 2018 InstallationDate: Installed on 2018-04-06 (44 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1772315 Title: ulimit can be enlarged, but not reduced back to below original Status in bash package in Ubuntu: New Bug description: Last login: Sat May 19 15:50:25 2018 from 192.168.0.130 ~$ ulimit -u 5000 ~$ ulimit -u 1000 ~$ ulimit -u 1 -bash: ulimit: max user processes: cannot modify limit: Operation not permitted ~$ ulimit -u 8000 -bash: ulimit: max user processes: cannot modify limit: Operation not permitted ~$ ulimit -u 7000 -bash: ulimit: max user processes: cannot modify limit: Operation not permitted ~$ ulimit -u 6000 -bash: ulimit: max user processes: cannot modify limit: Operation not permitted ~$ ulimit -u 5000 -bash: ulimit: max user processes: cannot modify limit: Operation not permitted ~$ ulimit -u 4000 -bash: ulimit: max user processes: cannot modify limit: Operation not permitted ~$ cat /etc/security/limits.conf | grep nproc | grep -v "^#" * soft nproc 20480 * hard nproc 20480 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bash 4.4.18-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Mon May 21 07:12:11 2018 InstallationDate: Installed on 2018-04-06 (44 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1772315/+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 1767314] [NEW] Ubuntu Bionic vi/vim not working correctly
Public bug reported: The vim default configuration in Bionic does not match Ubuntu 17.10 nor Centos 7 and is hard to use. It auto-inserts tabs or spaces, and the '/' search mode command works differently (pressing enter is required before you can use cursors left/right). For some discussion, please see https://askubuntu.com/questions/1026820 /vi-vim-usage-in-ubuntu-bionic-not-normal/1028684#1028684 Setting :set nocompatbile in ~/.vimrc fixes it, but this should not be required. ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Tags: bionic vi vim -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1767314 Title: Ubuntu Bionic vi/vim not working correctly Status in vim package in Ubuntu: New Bug description: The vim default configuration in Bionic does not match Ubuntu 17.10 nor Centos 7 and is hard to use. It auto-inserts tabs or spaces, and the '/' search mode command works differently (pressing enter is required before you can use cursors left/right). For some discussion, please see https://askubuntu.com/questions/1026820/vi-vim-usage-in-ubuntu-bionic- not-normal/1028684#1028684 Setting :set nocompatbile in ~/.vimrc fixes it, but this should not be required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1767314/+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 1598759] Re: AppArmor nameservice abstraction doesn't allow communication with systemd-resolved
[175882.466186] audit: type=1400 audit(1503640503.535:62): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/evince" name="/run/systemd/journal/socket" pid=7704 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 Same here (17.04) -- 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/1598759 Title: AppArmor nameservice abstraction doesn't allow communication with systemd-resolved Status in AppArmor: Triaged Status in apparmor package in Ubuntu: Fix Released Status in ntp package in Ubuntu: Invalid Status in apparmor source package in Yakkety: Fix Released Status in ntp source package in Yakkety: Invalid Bug description: [ Impact ] Processes confined by AppArmor profiles making use of the nameservice AppArmor abstraction are unable to access the systemd-resolved network name resolution service. The nsswitch.conf file shipped in Yakkety puts the nss-resolve plugin to use which talks to systemd-resolved over D-Bus. The D-Bus communication is blocked for the confined processes described above and those processes will fallback to the traditional means of name resolution. [ Test Case ] * Use ntpd to test: $ sudo apt-get install -y ntp ... $ sudo systemctl stop ntp # in another terminal, watch for AppArmor denials $ dmesg -w # in the original terminal, start ntp $ sudo systemctl start ntp # You'll see a number of denials on the system_bus_socket file: audit: type=1400 audit(1476240762.854:35): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=3867 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=126 ouid=0 * Use tcpdump to test: # Capture traffic on whichever network interface you're currently using $ sudo tcpdump -i eth0 # Look in /var/log/syslog for denials on the system_bus_socket file: audit: type=1400 audit(1476240896.021:40): apparmor="DENIED" operation="connect" profile="/usr/sbin/tcpdump" name="/run/dbus/system_bus_socket" pid=4106 comm="tcpdump" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 In both situations, ntpd and tcpdump will seemingly work as expected due to the name resolution fallback configured in nsswitch.conf. However, neither confined process will be using systemd-resolved for name resolution. [ Regression Potential ] This fix will allow ntp, tcpdump, cupsd, dhclient, and other confined- by-default programs to start using systemd-resolved. There is some potential for regression since those applications have not been previously using systemd-resolved. [ Original bug description ] On this plain install of Xenial apparmor complains about ntpd: [ 19.379152] audit: type=1400 audit(1467623330.386:27): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 [ 20.379299] audit: type=1400 audit(1467623331.386:28): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 [ 22.426246] audit: type=1400 audit(146762.434:29): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 [ 22.771326] audit: type=1400 audit(146762.782:30): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 [ 23.568548] audit: type=1400 audit(1467623334.574:31): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 Adding the following line to /etc/apparmor.d/usr.sbin.ntpd fixes the problem: #include To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1598759/+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
