[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
Ubuntu 22.04.3 LTS In an LXD VM also running Ubuntu 22.04.3 LTS I executed: $ sudo apt install -f ./webmesh_0.17.1_linux_amd64.deb and this is what displayed... Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'webmesh' instead of './webmesh_0.17.1_linux_amd64.deb' The following additional packages will be installed: wireguard-tools Suggested packages: openresolv | resolvconf The following NEW packages will be installed: webmesh wireguard-tools 0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded. Need to get 86.9 kB/28.8 MB of archives. After this operation, 56.5 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 /home/bmullan/webmesh/scripts/webmesh_0.17.1_linux_amd64.deb webmesh amd64 0.17.1 [28.8 MB] Get:2 http://archive.ubuntu.com/ubuntu jammy/main amd64 wireguard-tools amd64 1.0.20210914-1ubuntu2 [86.9 kB] Fetched 86.9 kB in 1s (72.9 kB/s) Selecting previously unselected package webmesh. (Reading database ... 56780 files and directories currently installed.) Preparing to unpack .../webmesh_0.17.1_linux_amd64.deb ... Unpacking webmesh (0.17.1) ... Selecting previously unselected package wireguard-tools. Preparing to unpack .../wireguard-tools_1.0.20210914-1ubuntu2_amd64.deb ... Unpacking wireguard-tools (1.0.20210914-1ubuntu2) ... Setting up webmesh (0.17.1) ... Setting up wireguard-tools (1.0.20210914-1ubuntu2) ... wg-quick.target is a disabled or a static unit not running, not starting it. Processing triggers for man-db (2.10.2-1) ... Scanning processes... Scanning linux images... Running kernel seems to be up-to-date. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host. N: Download is performed unsandboxed as root as file '/home/bmullan/webmesh/scripts/webmesh_0.17.1_linux_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) As with the others there seems to be a "permissions" problem? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in aptitude source package in Xenial: Confirmed Status in synaptic source package in Xenial: Confirmed Status in update-notifier source package in Xenial: Fix Released Status in apt source package in Hirsute: Fix Released Status in aptitude source package in Hirsute: Fix Released Status in synaptic source package in Hirsute: Won't Fix Status in update-notifier source package in Hirsute: Fix Released Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: READ ME FIRST = This is only a regression on a cosmetic level. Previous versions of apt did not have any sandboxing whatsoever, so this means apt reverted back to that old behavior. update-notifier SRU --- [Impact] Cosmetic. Warnings when installing packages using update-notifier downloading stuff [Test case] Install flashplugin-installer with apt and check that the output does not contain a message like this: W: Can't drop privileges for downloading as file '...' couldn't be accessed by user '_apt' [Regression Potential] It just chowns /var/lib/update-notifier/package-data- downloads/partial/ to _apt:root, there should not be any regression. Original report --- Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 roo
[Touch-packages] [Bug 1652101] Re: Can't create nested AppArmor namespaces
how does this get assigned to someone so it might get fixed? -- 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/1652101 Title: Can't create nested AppArmor namespaces Status in AppArmor: Confirmed Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: A user with CAP_MAC_ADMIN in the init namespace can create an AppArmor policy namespace and load a profile belonging to that AppArmor namespace. Once that's done, the user can confine a process with that namespaced AppArmor profile and enter into a user namespace. That process can then load additional AppArmor profiles inside of the AppArmor and user namespace. Here's an example: We need to set up the namespace, n1, and load the profile, p1. $ export rules="file, signal, unix, dbus, ptrace, mount, pivot_root, capability," $ sudo mkdir /sys/kernel/security/apparmor/policy/namespaces/n1 $ echo "profile p1 { $rules }" | sudo apparmor_parser -qrn n1 Now we enter into confinement using the AppArmor namespace and profile and then enter into an unprivileged user namespace $ aa-exec -n n1 -p p1 -- unshare -Ur We can now load profiles as the privileged user inside of the unprivileged user namespace # echo "profile test {}" | apparmor_parser -qr The reason for this bug report is that we cannot create a nested AppArmor policy namespace inside of the unprivileged user namespace # mkdir /sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1 mkdir: cannot create directory ‘/sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1’: Permission denied If that worked, we could adjust LXD to read /sys/kernel/security/apparmor/.ns_name to get the current AppArmor namespace, then create a new namespace under the current namespace, and leverage the nested namespace for its nested containers. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1652101/+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 1770429] Re: Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3
more clues related to comment #9 if I run alsamixer I can toggle AUTO-MUTE from ENABLED to DISABLED and the SOUND SETTINGS Choose a device for sound output switches between headphones output and Analog Stereo Output. I did this 4-5 rapidly and now it seems that the SOUND SETTINGS Choose a device for sound output now appears to switch back/forth between headphones and Analog Stereo Out but when I plug in Headphones I hear audio from both speakers & headphones. But as a temp workaround this is ok for me since if I use headphones I can turn off my speakers but if not using headphones (re not plugged in) my speakers work. -- 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/1770429 Title: Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3 Status in alsa-driver package in Ubuntu: Confirmed Bug description: I updated my Surface Pro 3 From Ubuntu 17.10 to Ubuntu 18.04 (did a clean install) and the only audio working was from the headphone jack. I tried all these: [troubleshooting guide](https://help.ubuntu.com/community/SoundTroubleshootingProcedure) [this answer](https://askubuntu.com/questions/117842/no-sound-from-speakers-but-headphones-work) [another answer](https://askubuntu.com/questions/829520/ubuntu-16-04-no-sound-from-speakers-only-headphones-working) I went back and tested the live CD and even the live cd has no audio through the speakers. so this must be related to 18.04. I never had sound issues before and under windows audio still works correctly. here is my alsa iformation http://www.alsa- project.org/db/?f=8bf135db52610a603014779ef24041a491c8a32d and here is how I fixed it: renaming /etc/modprobe.d/alsa-base.conf to /etc/modprobe.d/alsa- base.bk , then rebooting the computer fixed the my speaker sound issue. I then restored line by line in to /etc/modprobe.d/alsa-base.conf, rebooting between restored lines, until all lines were back and ... it still worked! so I restored the original /etc/modprobe.d/alsa-base.conf and rebooted the computer and everything was still working so I am not sure what the problem was but is now fixed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.16.7-041607-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: carlosr2267 F pulseaudio /dev/snd/controlC0: carlosr2267 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 10 10:15:29 2018 InstallationDate: Installed on 2018-04-27 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.2350 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.2350:bd01/23/2018:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.family: Surface dmi.product.name: Surface Pro 3 dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-05-09T14:04:13.313882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1770429/+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 1770429] Re: Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3
Same problem ubuntu 18.04 ran pavucontrol and saw "line-out (unplugged)" plug in my headphones and "line-out unplugged" changed to: line-out (plugged in) -- 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/1770429 Title: Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3 Status in alsa-driver package in Ubuntu: Confirmed Bug description: I updated my Surface Pro 3 From Ubuntu 17.10 to Ubuntu 18.04 (did a clean install) and the only audio working was from the headphone jack. I tried all these: [troubleshooting guide](https://help.ubuntu.com/community/SoundTroubleshootingProcedure) [this answer](https://askubuntu.com/questions/117842/no-sound-from-speakers-but-headphones-work) [another answer](https://askubuntu.com/questions/829520/ubuntu-16-04-no-sound-from-speakers-only-headphones-working) I went back and tested the live CD and even the live cd has no audio through the speakers. so this must be related to 18.04. I never had sound issues before and under windows audio still works correctly. here is my alsa iformation http://www.alsa- project.org/db/?f=8bf135db52610a603014779ef24041a491c8a32d and here is how I fixed it: renaming /etc/modprobe.d/alsa-base.conf to /etc/modprobe.d/alsa- base.bk , then rebooting the computer fixed the my speaker sound issue. I then restored line by line in to /etc/modprobe.d/alsa-base.conf, rebooting between restored lines, until all lines were back and ... it still worked! so I restored the original /etc/modprobe.d/alsa-base.conf and rebooted the computer and everything was still working so I am not sure what the problem was but is now fixed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.16.7-041607-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: carlosr2267 F pulseaudio /dev/snd/controlC0: carlosr2267 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 10 10:15:29 2018 InstallationDate: Installed on 2018-04-27 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.2350 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.2350:bd01/23/2018:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.family: Surface dmi.product.name: Surface Pro 3 dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-05-09T14:04:13.313882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1770429/+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 1813952] [NEW] Audio Playback problem - Speakers only work if Headphones are also plugged in
Public bug reported: Ubuntu 18.04 Linux dadspc 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux pulseaudio v 11.1 $ cat /proc/asound/version Advanced Linux Sound Architecture Driver Version k4.15.0-44-generic. Audio has been working fine until this morning when "some" update occurred on my Ubuntu desktop system. I found that I was NOT getting any audio out of my speakers. I also found in SOUND SETTINGS that for OUTPUT I only had listed: Digital Output (S/PDIF) - Built-in Audio" Headphones - Built-in audio Next, I plugged in my headphones to my Desktop and when I did that: I started hearing Audio out of my Speakers AND in my Headphones ! AND... in SOUND SETTINGS Line Out - Built-in Audio appeared ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmullan2599 F pulseaudio /dev/snd/pcmC0D0c: bmullan2599 F...m pulseaudio /dev/snd/pcmC0D0p: bmullan2599 F...m pulseaudio /dev/snd/controlC0: bmullan2599 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 30 09:52:10 2019 InstallationDate: Installed on 2018-11-06 (84 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: HDA NVidia - HDA NVidia Symptom_Type: None of the above Title: [HDA-Intel - HDA ATI SB, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2901:bd05/04/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: Ubuntu 18.04 Linux dadspc 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux pulseaudio v 11.1 $ cat /proc/asound/version Advanced Linux Sound Architecture Driver Version k4.15.0-44-generic. Audio has been working fine until this morning when "some" update occurred on my Ubuntu desktop system. - I found that I wasn NOT getting any audio out of my speakers. + I found that I was NOT getting any audio out of my speakers. I also found in SOUND SETTINGS that for OUTPUT I only had listed: Digital Output (S/PDIF) - Built-in Audio" Headphones - Built-in audio Next, I plugged in my headphones to my Desktop and when I did that: I started hearing Audio out of my Speakers AND in my Headphones ! AND... in SOUND SETTINGS Line Out - Built-in Audio appeared ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: bmullan2599 F pulseaudio - /dev/snd/pcmC0D0c: bmullan2599 F...m pulseaudio - /dev/snd/pcmC0D0p: bmullan2599 F...m pulseaudio - /dev/snd/controlC0: bmullan2599 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: bmullan2599 F pulseaudio + /dev/snd/pcmC0D0c: bmullan2599 F...m pulseaudio + /dev/snd/pcmC0D0p: bmullan2599 F...m pulseaudio + /dev/snd/controlC0: bmullan2599 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 30 09:52:10 2019 InstallationDate: Installed on 2018-11-06 (84 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: alsa-driver Sympto
[Touch-packages] [Bug 1652101] Re: Can't create nested AppArmor namespaces
>From what I understand, LXD is moving toward SNAP LXD as a default, so not being able to run SNAP in an LXD container configured for "nesting": re - lxc config set security.nesting true Is basically going to prevent LXD from being used for Nested Containers. -- 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/1652101 Title: Can't create nested AppArmor namespaces Status in AppArmor: Confirmed Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: A user with CAP_MAC_ADMIN in the init namespace can create an AppArmor policy namespace and load a profile belonging to that AppArmor namespace. Once that's done, the user can confine a process with that namespaced AppArmor profile and enter into a user namespace. That process can then load additional AppArmor profiles inside of the AppArmor and user namespace. Here's an example: We need to set up the namespace, n1, and load the profile, p1. $ export rules="file, signal, unix, dbus, ptrace, mount, pivot_root, capability," $ sudo mkdir /sys/kernel/security/apparmor/policy/namespaces/n1 $ echo "profile p1 { $rules }" | sudo apparmor_parser -qrn n1 Now we enter into confinement using the AppArmor namespace and profile and then enter into an unprivileged user namespace $ aa-exec -n n1 -p p1 -- unshare -Ur We can now load profiles as the privileged user inside of the unprivileged user namespace # echo "profile test {}" | apparmor_parser -qr The reason for this bug report is that we cannot create a nested AppArmor policy namespace inside of the unprivileged user namespace # mkdir /sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1 mkdir: cannot create directory ‘/sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1’: Permission denied If that worked, we could adjust LXD to read /sys/kernel/security/apparmor/.ns_name to get the current AppArmor namespace, then create a new namespace under the current namespace, and leverage the nested namespace for its nested containers. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1652101/+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 1583256] [NEW] Ubuntu 16.04 Pulseaudio does not use /etc/pulse/default.pa if ~/.config/pulse/default.pa does not exist
*** This bug is a duplicate of bug 1583255 *** https://bugs.launchpad.net/bugs/1583255 Public bug reported: System is Ubuntu 16.04 According to Ubuntu Pulseaudio MAN page: http://manpages.ubuntu.com/manpages/xenial/man5/default.pa.5.html it says... The PulseAudio sound server interprets a configuration script on startup, which is mainly used to define the set of modules to load. When PulseAudio runs in the per-usermodeand ~/.config/pulse/default.pa exists, that file is used. When PulseAudio runs in the per-user mode and that file doesn't exist, /etc/pulse/default.pa is used. On my system I have put the following into - /etc/pulse/default.pa load-module module-native-protocol-tcp auth-ip- acl=127.0.0.1;10.204.151.0/24 The contents of my ~/.config/pulse/ directory contains NO default.pa file only the cookie file: $ ls ~/.config/pulse cookie After a reload I issue the command patcl list modules and the "module- native-protocol-tcp" is NOT listed ? $ pactl list modules Module #0 Name: module-augment-properties Argument: Usage counter: n/a Properties: module.author = "Lennart Poettering" module.description = "Augment the property sets of streams with additional static information" module.version = "8.0" Module #1 Name: module-always-sink Argument: Usage counter: n/a Properties: module.author = "Colin Guthrie" module.description = "Always keeps at least one sink loaded even if it's a null one" module.version = "8.0" Module #3 Name: module-xrdp-sink Argument: Usage counter: 0 Properties: module.author = "Jay Sorg" module.description = "xrdp sink" module.version = "8.0" Module #4 Name: module-xrdp-source Argument: Usage counter: n/a Properties: module.author = "Laxmikant Rashinkar" module.description = "xrdp source" module.version = "8.0" Module #5 Name: module-native-protocol-unix Argument: Usage counter: n/a Properties: module.author = "Lennart Poettering" module.description = "Native protocol (UNIX sockets)" module.version = "8.0" Module #6 Name: module-cli-protocol-unix Argument: Usage counter: n/a Properties: module.author = "Lennart Poettering" module.description = "Command line interface protocol (UNIX sockets)" module.version = "8.0" I am filing this bug because according to the MAN page (see above)... since I do NOT have a ~/.config/pulse/default.pa Ubuntu/Pulseaudio should be executing the /etc/pulse/default.pa configuration instead... which should be loading: load-module module-native-protocol-tcp auth-ip- acl=127.0.0.1;10.204.151.0/24 but it not. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: pulseaudio ** Tags added: pulseaudio -- 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/1583256 Title: Ubuntu 16.04 Pulseaudio does not use /etc/pulse/default.pa if ~/.config/pulse/default.pa does not exist Status in pulseaudio package in Ubuntu: New Bug description: System is Ubuntu 16.04 According to Ubuntu Pulseaudio MAN page: http://manpages.ubuntu.com/manpages/xenial/man5/default.pa.5.html it says... The PulseAudio sound server interprets a configuration script on startup, which is mainly used to define the set of modules to load. When PulseAudio runs in the per-usermodeand ~/.config/pulse/default.pa exists, that file is used. When PulseAudio runs in the per-user mode and that file doesn't exist, /etc/pulse/default.pa is used. On my system I have put the following into - /etc/pulse/default.pa load-module module-native-protocol-tcp auth-ip- acl=127.0.0.1;10.204.151.0/24 The contents of my ~/.config/pulse/ directory contains NO default.pa file only the cookie file: $ ls ~/.config/pulse cookie After a reload I issue the command patcl list modules and the "module- native-protocol-tcp" is NOT listed ? $ pactl list modules Module #0 Name: module-augment-properties Argument: Usage counter: n/a Properties: module.author = "Lennart Poettering" module.description = "Augment the property sets of streams with additional static information" module.version = "8.0" Module #1
[Touch-packages] [Bug 1583255] [NEW] Ubuntu 16.04 Pulseaudio does not use /etc/pulse/default.pa if ~/.config/pulse/default.pa does not exist
Public bug reported: System is Ubuntu 16.04 According to Ubuntu Pulseaudio MAN page: http://manpages.ubuntu.com/manpages/xenial/man5/default.pa.5.html it says... The PulseAudio sound server interprets a configuration script on startup, which is mainly used to define the set of modules to load. When PulseAudio runs in the per-usermodeand ~/.config/pulse/default.pa exists, that file is used. When PulseAudio runs in the per-user mode and that file doesn't exist, /etc/pulse/default.pa is used. On my system I have put the following into - /etc/pulse/default.pa load-module module-native-protocol-tcp auth-ip- acl=127.0.0.1;10.204.151.0/24 The contents of my ~/.config/pulse/ directory contains NO default.pa file only the cookie file: $ ls ~/.config/pulse cookie After a reload I issue the command patcl list modules and the "module- native-protocol-tcp" is NOT listed ? $ pactl list modules Module #0 Name: module-augment-properties Argument: Usage counter: n/a Properties: module.author = "Lennart Poettering" module.description = "Augment the property sets of streams with additional static information" module.version = "8.0" Module #1 Name: module-always-sink Argument: Usage counter: n/a Properties: module.author = "Colin Guthrie" module.description = "Always keeps at least one sink loaded even if it's a null one" module.version = "8.0" Module #3 Name: module-xrdp-sink Argument: Usage counter: 0 Properties: module.author = "Jay Sorg" module.description = "xrdp sink" module.version = "8.0" Module #4 Name: module-xrdp-source Argument: Usage counter: n/a Properties: module.author = "Laxmikant Rashinkar" module.description = "xrdp source" module.version = "8.0" Module #5 Name: module-native-protocol-unix Argument: Usage counter: n/a Properties: module.author = "Lennart Poettering" module.description = "Native protocol (UNIX sockets)" module.version = "8.0" Module #6 Name: module-cli-protocol-unix Argument: Usage counter: n/a Properties: module.author = "Lennart Poettering" module.description = "Command line interface protocol (UNIX sockets)" module.version = "8.0" I am filing this bug because according to the MAN page (see above)... since I do NOT have a ~/.config/pulse/default.pa Ubuntu/Pulseaudio should be executing the /etc/pulse/default.pa configuration instead... which should be loading: load-module module-native-protocol-tcp auth-ip- acl=127.0.0.1;10.204.151.0/24 but it not. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1583255 Title: Ubuntu 16.04 Pulseaudio does not use /etc/pulse/default.pa if ~/.config/pulse/default.pa does not exist Status in pulseaudio package in Ubuntu: New Bug description: System is Ubuntu 16.04 According to Ubuntu Pulseaudio MAN page: http://manpages.ubuntu.com/manpages/xenial/man5/default.pa.5.html it says... The PulseAudio sound server interprets a configuration script on startup, which is mainly used to define the set of modules to load. When PulseAudio runs in the per-usermodeand ~/.config/pulse/default.pa exists, that file is used. When PulseAudio runs in the per-user mode and that file doesn't exist, /etc/pulse/default.pa is used. On my system I have put the following into - /etc/pulse/default.pa load-module module-native-protocol-tcp auth-ip- acl=127.0.0.1;10.204.151.0/24 The contents of my ~/.config/pulse/ directory contains NO default.pa file only the cookie file: $ ls ~/.config/pulse cookie After a reload I issue the command patcl list modules and the "module- native-protocol-tcp" is NOT listed ? $ pactl list modules Module #0 Name: module-augment-properties Argument: Usage counter: n/a Properties: module.author = "Lennart Poettering" module.description = "Augment the property sets of streams with additional static information" module.version = "8.0" Module #1 Name: module-always-sink Argument: Usage counter: n/a Properties: module.author = "Colin Guthr
Re: [Touch-packages] [Bug 1512749] Please test proposed package
will do... On Tue, Nov 3, 2015 at 4:20 PM, Stéphane Graber wrote: > Hello brian, or anyone else affected, > > Accepted network-manager into wily-proposed. The package will build now > and be available at https://launchpad.net/ubuntu/+source/network- > manager/1.0.4-0ubuntu5.1 in a few hours, and then in the -proposed > repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to > enable and use -proposed. Your feedback will aid us getting this update > out to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested, and change the tag > from verification-needed to verification-done. If it does not fix the > bug for you, please add a comment stating that, and change the tag to > verification-failed. In either case, details of your testing will help > us make a better decision. > > Further information regarding the verification process can be found at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in > advance! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1512749 > > Title: > lxcbr0 dissappears on Ubuntu 15.10 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1512749/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1512749 Title: lxcbr0 dissappears on Ubuntu 15.10 Status in lxc package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Fix Committed Status in lxc source package in Wily: Invalid Status in network-manager source package in Wily: Fix Committed Status in lxc source package in Xenial: Invalid Status in network-manager source package in Xenial: Fix Committed Bug description: === SRU === Rationale: Network Manager in wily triggers on newly created interfaces and resets their network configuration even though it's not supposed to manage them at all. This breaks LXC and quite possibly libvirt as those provide bridges which are then completely unconfigured by Network Manager. Test case: 1) Update (or not) network-manager 2) Restart it 3) Install lxc 4) Check that lxcbr0 exists and has an IP configured Regression potential: The change to Network Manager is related to udev handling of new devices, even though normal operation on a regular desktop machine was tested, it's not impossible that this may regress handling of some devices. The fix was cherry-picked directly from upstream, so did go through code review and has been publicly available for a while. This fixes a significant regression compared to Ubuntu 15.04 and looks less risky than the alternative workaround which was uploaded earlier. === Original report === After initial upgrade from Ubuntu 15.04 to Ubuntu 15.10 LXC worked for a couple days then failed. I found that the lxcbr0 interface no longer existed. I reported this on the lxc-user alias and about the same time several others had this happen to them also. Serge Hallyn requested I open a launchpad bug and post some info but before I could gather that info the system returned to normal (re lxcbr0 was back) the next day after the server was booted up again. note: at least one other person had this happen to them also (lxcbr0 came back by itself). Today, I booted this server again and ... again lxcbr0 was missing where it had been working last night. Below is all of the Info Serge Hallyn asked me to post. $ ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found $ journalctl -u lxc-net -- Logs begin at Tue 2015-11-03 07:25:22 EST, end at Tue 2015-11-03 10:02:08 EST Nov 03 07:25:48 server3 systemd[1]: Starting LXC network bridge setup... Nov 03 07:25:50 server3 lxc-net[913]: dnsmasq: failed to create listening socket Nov 03 07:25:50 server3 lxc-net[913]: Failed to setup lxc-net. Nov 03 07:25:50 server3 systemd[1]: Started LXC network bridge setup. root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop # note - execution just returns to command line root@server3:/home/bmullan# >> and lxcbr0 is still missing # ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net start dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign requested address Failed to setup lxc-net. root@server3:/home/bmullan# $ uname -a Linux server3 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 15.10
[Touch-packages] [Bug 1512749] [NEW] lxcbr0 dissappears on Ubuntu 15.10
Public bug reported: After initial upgrade from Ubuntu 15.04 to Ubuntu 15.10 LXC worked for a couple days then failed. I found that the lxcbr0 interface no longer existed. I reported this on the lxc-user alias and about the same time several others had this happen to them also. Serge Hallyn requested I open a launchpad bug and post some info but before I could gather that info the system returned to normal (re lxcbr0 was back) the next day after the server was booted up again. note: at least one other person had this happen to them also (lxcbr0 came back by itself). Today, I booted this server again and ... again lxcbr0 was missing where it had been working last night. Below is all of the Info Serge Hallyn asked me to post. $ ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found $ journalctl -u lxc-net -- Logs begin at Tue 2015-11-03 07:25:22 EST, end at Tue 2015-11-03 10:02:08 EST Nov 03 07:25:48 server3 systemd[1]: Starting LXC network bridge setup... Nov 03 07:25:50 server3 lxc-net[913]: dnsmasq: failed to create listening socket Nov 03 07:25:50 server3 lxc-net[913]: Failed to setup lxc-net. Nov 03 07:25:50 server3 systemd[1]: Started LXC network bridge setup. root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop # note - execution just returns to command line root@server3:/home/bmullan# >> and lxcbr0 is still missing # ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net start dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign requested address Failed to setup lxc-net. root@server3:/home/bmullan# $ uname -a Linux server3 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename:wily ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1512749 Title: lxcbr0 dissappears on Ubuntu 15.10 Status in lxc package in Ubuntu: New Bug description: After initial upgrade from Ubuntu 15.04 to Ubuntu 15.10 LXC worked for a couple days then failed. I found that the lxcbr0 interface no longer existed. I reported this on the lxc-user alias and about the same time several others had this happen to them also. Serge Hallyn requested I open a launchpad bug and post some info but before I could gather that info the system returned to normal (re lxcbr0 was back) the next day after the server was booted up again. note: at least one other person had this happen to them also (lxcbr0 came back by itself). Today, I booted this server again and ... again lxcbr0 was missing where it had been working last night. Below is all of the Info Serge Hallyn asked me to post. $ ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found $ journalctl -u lxc-net -- Logs begin at Tue 2015-11-03 07:25:22 EST, end at Tue 2015-11-03 10:02:08 EST Nov 03 07:25:48 server3 systemd[1]: Starting LXC network bridge setup... Nov 03 07:25:50 server3 lxc-net[913]: dnsmasq: failed to create listening socket Nov 03 07:25:50 server3 lxc-net[913]: Failed to setup lxc-net. Nov 03 07:25:50 server3 systemd[1]: Started LXC network bridge setup. root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop # note - execution just returns to command line root@server3:/home/bmullan# >> and lxcbr0 is still missing # ifconfig lxcbr0 lxcbr0: error fetching interface information: Device not found root@server3:/home/bmullan# /usr/lib/x86_64-linux-gnu/lxc/lxc-net start dnsmasq: failed to create listening socket for 10.0.3.1: Cannot assign requested address Failed to setup lxc-net. root@server3:/home/bmullan# $ uname -a Linux server3 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename:wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1512749/+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 1400745] [NEW] lxc-create -t download and specifying Lucid for release ends w/only IPv6 addr
Public bug reported: I don't know if this is considered an LXC bug or a bug in the "download" rootfs build process but I recently had a need to use a container with a lucid image. I created it using: $ sudo lxc-create -t download -n my_test and specified Lucid, amd64 after creating the container and starting/attaching to it I found it only has an IPv6 address on its eth0 interface instead of a 10.x.x.x. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Summary changed: - lxc-create -t download and specifying Lucid for release ends w/no IP + lxc-create -t download and specifying Lucid for release ends only IPv6 addr ** Summary changed: - lxc-create -t download and specifying Lucid for release ends only IPv6 addr + lxc-create -t download and specifying Lucid for release ends w/only IPv6 addr -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1400745 Title: lxc-create -t download and specifying Lucid for release ends w/only IPv6 addr Status in lxc package in Ubuntu: New Bug description: I don't know if this is considered an LXC bug or a bug in the "download" rootfs build process but I recently had a need to use a container with a lucid image. I created it using: $ sudo lxc-create -t download -n my_test and specified Lucid, amd64 after creating the container and starting/attaching to it I found it only has an IPv6 address on its eth0 interface instead of a 10.x.x.x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1400745/+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] [Bug 1373981] Re: ubuntu 14.10 server, amd64 - lxc-start fails to start container
Serge I don't have the problem now. But there was a round of sw upgrades during that time and I suspect whatever had caused it was fixed somewhere. The original AMI though should still exhibit the problem I guess. *ubuntu-utopic-14.10-beta1-amd64-server-20140826 (ami-3021fb58)* Brian On Tue, Sep 30, 2014 at 3:39 PM, Serge Hallyn <1373...@bugs.launchpad.net> wrote: > Thanks for submitting this bug. > > To be clear, > > 'sudo ip link add type veth' > > also returns an error? > > Could you tell us which ami and which machine type you used to start the > amazon instance? > > ** Changed in: lxc (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1373981 > > Title: > ubuntu 14.10 server, amd64 - lxc-start fails to start container > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1373981/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1373981 Title: ubuntu 14.10 server, amd64 - lxc-start fails to start container Status in “lxc” package in Ubuntu: Incomplete Bug description: I had previously created an lxc container successfully using either: $ sudo lxc-create -t download -n test_cn -or- $ sudo lxc-create -t ubuntu -n test_cn However... when trying to start it fails with the following? $ sudo lxc-start -n test_cn lxc-start: failed to create vethBQ6TPB-vethV9VF9A : Operation not supported lxc-start: failed to create netdev lxc-start: failed to create the network lxc-start: failed to spawn 'test_cn' lxc-start: The container failed to start. lxc-start: Additional information can be obtained by setting the --logfile and --log-priority options. To check if the "veth" kernel module is loaded I updated the server and rebooted I ran "sudo modprobe veth" and it shows an error also? $ sudo modprobe veth modprobe: ERROR: could not insert 'veth': Cannot allocate memory This server is running on AWS EC2. $ uname -a Linux ip-10-69-148-9 3.16.0-10-generic #15-Ubuntu SMP Thu Aug 21 16:26:44 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1373981/+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