[Touch-packages] [Bug 1805063] Re: package systemd-sysv 237-3ubuntu10.10 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1805063 Title: package systemd-sysv 237-3ubuntu10.10 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd package in Ubuntu: Confirmed Bug description: Im not sure where the bug may have come from...it came with the new update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.10 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 Date: Sat Nov 24 10:50:14 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2013-04-13 (2052 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.10 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-11-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805063/+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 1810150] Re: package systemd-sysv 237-3ubuntu10.9 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2
*** This bug is a duplicate of bug 1805063 *** https://bugs.launchpad.net/bugs/1805063 ** This bug has been marked a duplicate of bug 1805063 package systemd-sysv 237-3ubuntu10.10 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 -- 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/1810150 Title: package systemd-sysv 237-3ubuntu10.9 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: please resolve asap ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.9 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_33_36_generic_46 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Dec 31 16:16:52 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2012-12-08 (2213 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.9 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1810150/+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 1810277] [NEW] package linux-image-extra-4.4.0-141-generic 4.4.0-141.167 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
*** This bug is a security vulnerability *** Private security bug reported: Can't install packages like wireshark ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-141-generic 4.4.0-141.167 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: newkon 1962 F...m pulseaudio /dev/snd/controlC1: newkon 1962 F pulseaudio /dev/snd/controlC0: newkon 1962 F pulseaudio Date: Wed Jan 2 03:05:13 2019 DpkgHistoryLog: Start-Date: 2019-01-02 03:03:25 Commandline: apt-get install wireshark Requested-By: newkon (1000) Install: libc-ares2:i386 (1.10.0-3ubuntu0.2, automatic), libqgsttools-p1:i386 (5.5.1-4ubuntu2, automatic), libnghttp2-14:i386 (1.7.1-1, automatic), libwireshark11:i386 (2.6.4-2~ubuntu16.04.0, automatic), libwiretap8:i386 (2.6.4-2~ubuntu16.04.0, automatic), libwsutil9:i386 (2.6.4-2~ubuntu16.04.0, automatic), wireshark:i386 (2.6.4-2~ubuntu16.04.0), wireshark-gtk:i386 (2.6.4-2~ubuntu16.04.0, automatic), libqt5multimediawidgets5:i386 (5.5.1-4ubuntu2, automatic), libqt5multimedia5-plugins:i386 (5.5.1-4ubuntu2, automatic), wireshark-common:i386 (2.6.4-2~ubuntu16.04.0, automatic), libwscodecs2:i386 (2.6.4-2~ubuntu16.04.0, automatic), libspandsp2:i386 (0.0.6-2.1, automatic), libmaxminddb0:i386 (1.0.4-2.1, automatic), libwireshark-data:i386 (2.6.4-2~ubuntu16.04.0, automatic), wireshark-qt:i386 (2.6.4-2~ubuntu16.04.0, automatic), libsmi2ldbl:i386 (0.4.8+dfsg2-11, automatic) ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=24bdc8fd-bb52-4ca7-981e-53bbc1b94d1a InstallationDate: Installed on 2018-07-15 (170 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Hewlett-Packard HP ProBook 650 G1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-141-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.20 SourcePackage: initramfs-tools Title: package linux-image-extra-4.4.0-141-generic 4.4.0-141.167 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2018-10-09 (84 days ago) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L77 Ver. 01.02 dmi.board.name: 1993 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 16.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL77Ver.01.02:bd12/05/2013:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10203:rvnHewlett-Packard:rn1993:rvrKBCVersion16.36:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 650 G1 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check xenial ** Information type changed from Public to Public Security ** Information type changed from Public Security to Private Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1810277 Title: package linux-image-extra-4.4.0-141-generic 4.4.0-141.167 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Can't install packages like wireshark ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-141-generic 4.4.0-141.167 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: newkon 1962 F...m pulseaudio /dev/snd/controlC1: newkon 1962 F pulseaudio /dev/snd/controlC0: newkon 1962 F pulseaudio Date: Wed Jan 2 03:05:13 2019 DpkgHistoryLog: Start-Date: 2019-01-02 03:03:25 Commandline: apt-get install wireshark Requested-By: newkon (1000) Install: libc-ares2:i386 (1.10.0-3ubuntu0.2, automatic), libqgsttools-p1:i386 (5.5.1-4ubuntu2, automatic), libnghttp2-14:i386 (1.7.1-1, automatic), libwireshark11:i386 (2.6.4-2~ubuntu16.04.0, automatic), libwiretap8:i386 (2.6.4-2~ubuntu16.04.0, automatic), libwsutil9:i386 (2.6.4-2~ubuntu16.04.0, automatic), wireshark:i386 (2.6.4-2~ubuntu16.04.0), wireshark-gtk:i386 (2.6.4-2~ubuntu16.04.0, automatic), libqt5multimediawidgets5:i386 (5.5.1-4ubuntu2, automatic), libqt5multimedia5-pl
[Touch-packages] [Bug 1787867] Re: Ubuntu 18.04 LTS bluetooth left discoverable
I can't believe that such a basic security/privacy issue has not been fixed yet. Normally, the device should only be discoverable when the bluetooth settings are opened. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1787867 Title: Ubuntu 18.04 LTS bluetooth left discoverable Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Ubuntu 18.04 LTS, when Bluetooth is on, the computer stays discoverable which opens up unnecessary vulnerability surface. There should be a separate UI switch for discoverability with auto timeout. Leaving bluetooth on (using a Bluetooth mouse) should not leave the computer always discoverable. Current behavior does not match documentation https://help.ubuntu.com/stable/ubuntu-help/bluetooth- visibility.html.en, even without Bluetooth panel open, the computer is still discoverable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1787867/+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 1787867] Re: Ubuntu 18.04 LTS bluetooth left discoverable
Probably, lot of clues there: https://bugzilla.redhat.com/show_bug.cgi?id=1602985 Some upstream patches seem to be availabe, can they be ported to Ubuntu ? ** Bug watch added: Red Hat Bugzilla #1602985 https://bugzilla.redhat.com/show_bug.cgi?id=1602985 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1787867 Title: Ubuntu 18.04 LTS bluetooth left discoverable Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Ubuntu 18.04 LTS, when Bluetooth is on, the computer stays discoverable which opens up unnecessary vulnerability surface. There should be a separate UI switch for discoverability with auto timeout. Leaving bluetooth on (using a Bluetooth mouse) should not leave the computer always discoverable. Current behavior does not match documentation https://help.ubuntu.com/stable/ubuntu-help/bluetooth- visibility.html.en, even without Bluetooth panel open, the computer is still discoverable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1787867/+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 1810287] [NEW] [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] Underruns, dropouts or crackling sound
Public bug reported: I don,t know about packages. I am new to ubuntu. There is an irritating crackling and buzzy sound along with the audio from speakers ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giri 1966 F pulseaudio /dev/snd/controlC0: giri 1966 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 15:54:22 2019 InstallationDate: Installed on 2019-01-01 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Jan 02 15:44:58 giri-HP-Pavilion-15-Notebook-PC dbus-daemon[941]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.45' (uid=1000 pid=1966 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.56 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2281 dmi.board.vendor: Hewlett-Packard dmi.board.version: 77.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.56:bd06/29/2018:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr097610405F1610180:rvnHewlett-Packard:rn2281:rvr77.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.sku: J6M42PA#ACJ dmi.product.version: 097610405F1610180 dmi.sys.vendor: Hewlett-Packard mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-01-02T15:54:03.591051 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1810287 Title: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: I don,t know about packages. I am new to ubuntu. There is an irritating crackling and buzzy sound along with the audio from speakers ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giri 1966 F pulseaudio /dev/snd/controlC0: giri 1966 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 15:54:22 2019 InstallationDate: Installed on 2019-01-01 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Jan 02 15:44:58 giri-HP-Pavilion-15-Notebook-PC dbus-daemon[941]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.45' (uid=1000 pid=1966 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.56 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2281 dmi.board.vendor: Hewlett-Packard dmi.board.version: 77.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.56:bd06/29/2018:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr097610405F1610180:rvnHewlett-Packard:rn2281:rvr77.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.
[Touch-packages] [Bug 1808671] [NEW] Drop non working scopes
You have been subscribed to a public bug: Many online scopes and lenses are not working anymore. So drop them from recommends. And tomboy is going to be removed from debian so use gnote instead of tomboy. unity-gnote-scope: https://launchpad.net/unity-scope-gnote ** Affects: libunity (Ubuntu) Importance: Undecided Status: Confirmed -- Drop non working scopes https://bugs.launchpad.net/bugs/1808671 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. -- 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 1801148] Re: package gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before
You should try to re-install the package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1801148 Title: package gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libunity package in Ubuntu: New Bug description: Unable to open skype ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 Uname: Linux 4.4.0-94-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: gir1.2-unity-5.0: Configure upower: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Nov 1 13:11:35 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.29 SourcePackage: libunity Title: package gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1801148/+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 1808671] Re: Drop non working scopes
** Package changed: unity (Ubuntu) => libunity (Ubuntu) ** Changed in: libunity (Ubuntu) Status: New => Confirmed ** Branch linked: lp:~khurshid-alam/libunity/remove-deprecated-scopes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1808671 Title: Drop non working scopes Status in libunity package in Ubuntu: Confirmed Bug description: Many online scopes and lenses are not working anymore. So drop them from recommends. And tomboy is going to be removed from debian so use gnote instead of tomboy. unity-gnote-scope: https://launchpad.net/unity-scope-gnote To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1808671/+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 1810310] [NEW] Network-Manager - Incorrect settings during Installation
Public bug reported: Hi, Apologies for this, but I am not an Ubuntu Desktop user. I do, however, frequent a few Linux forums and try to help people out on occasion. Recently there's been a spate of people reporting Network-Manager in Ubuntu having wrong settings after an install. Examples are: https://www.reddit.com/r/linux4noobs/comments/aaq1tb/10mbs_instead_of_1000mbs_on_network_interface/ https://www.reddit.com/r/Ubuntu/comments/abtvwo/ubuntu_in_fast_ethernet_how_get_gigabit/ Just thought I'd bring this to your attention, in case it's not a known issue. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1810310 Title: Network-Manager - Incorrect settings during Installation Status in network-manager package in Ubuntu: New Bug description: Hi, Apologies for this, but I am not an Ubuntu Desktop user. I do, however, frequent a few Linux forums and try to help people out on occasion. Recently there's been a spate of people reporting Network-Manager in Ubuntu having wrong settings after an install. Examples are: https://www.reddit.com/r/linux4noobs/comments/aaq1tb/10mbs_instead_of_1000mbs_on_network_interface/ https://www.reddit.com/r/Ubuntu/comments/abtvwo/ubuntu_in_fast_ethernet_how_get_gigabit/ Just thought I'd bring this to your attention, in case it's not a known issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1810310/+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 1810310] Re: Network-Manager - Incorrect settings during Installation
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1810310 Title: Network-Manager - Incorrect settings during Installation Status in network-manager package in Ubuntu: Confirmed Bug description: Hi, Apologies for this, but I am not an Ubuntu Desktop user. I do, however, frequent a few Linux forums and try to help people out on occasion. Recently there's been a spate of people reporting Network-Manager in Ubuntu having wrong settings after an install. Examples are: https://www.reddit.com/r/linux4noobs/comments/aaq1tb/10mbs_instead_of_1000mbs_on_network_interface/ https://www.reddit.com/r/Ubuntu/comments/abtvwo/ubuntu_in_fast_ethernet_how_get_gigabit/ Just thought I'd bring this to your attention, in case it's not a known issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1810310/+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 1579580] Re: ureadahead reports relative path errors in journalctl output
@kkobashi: are you saying this is a wontfix for 18.04? Can't ureadahead operate in quiet mode? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+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 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic
so in 18.10 this is stil the case? I am running with i965-va-driver-shader and it is not offering VP9 decoding… -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1756380 Title: vaapi VP9 hardware decoding not working anymore in bionic Status in intel-vaapi-driver package in Ubuntu: Fix Released Status in libva package in Ubuntu: Invalid Bug description: Hardware: Dell XPS13 9365, i7-7Y75 System: Ubuntu Bionic Beaver (development branch) vainfo output on bionic is: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.1 (libva 2.1.0) vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice As you can see, VP9 entrypoints are missing. vainfo output on 17.10 was: libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple:VAEntrypointVLD VAProfileMPEG2Simple:VAEntrypointEncSlice VAProfileMPEG2Main :VAEntrypointVLD VAProfileMPEG2Main :VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointVLD VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP VAProfileH264Main :VAEntrypointVLD VAProfileH264Main :VAEntrypointEncSlice VAProfileH264Main :VAEntrypointEncSliceLP VAProfileH264High :VAEntrypointVLD VAProfileH264High :VAEntrypointEncSlice VAProfileH264High :VAEntrypointEncSliceLP VAProfileH264MultiviewHigh :VAEntrypointVLD VAProfileH264MultiviewHigh :VAEntrypointEncSlice VAProfileH264StereoHigh :VAEntrypointVLD VAProfileH264StereoHigh :VAEntrypointEncSlice VAProfileVC1Simple :VAEntrypointVLD VAProfileVC1Main:VAEntrypointVLD VAProfileVC1Advanced:VAEntrypointVLD VAProfileNone :VAEntrypointVideoProc VAProfileJPEGBaseline :VAEntrypointVLD VAProfileJPEGBaseline :VAEntrypointEncPicture VAProfileVP8Version0_3 :VAEntrypointVLD VAProfileVP8Version0_3 :VAEntrypointEncSlice VAProfileHEVC
[Touch-packages] [Bug 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11
I still see font distortions on ubuntu cosmic: openjdk version "11.0.1" 2018-10-16 OpenJDK Runtime Environment (build 11.0.1+13-Ubuntu-2ubuntu1) OpenJDK 64-Bit Server VM (build 11.0.1+13-Ubuntu-2ubuntu1, mixed mode, sharing) There is a matching upstream issue for this: http://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8214284 In the comments for that issue, a second (fixed) issue is referenced: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8214002 The fix for that issue was merged to the jdk 12 and jdk branches: http://hg.openjdk.java.net/jdk/jdk12/rev/7ed5edf6ba0c http://hg.openjdk.java.net/jdk/jdk/rev/7ed5edf6ba0c I build the jdk branch and found the issue fixed. I also rebuild the ubuntu package with the above mentioned patch included (only the change in freetypeScaler.c, not the new test) and also found, that this fixes my problem. I don't know the plans for java in ubuntu regarding LTS releases and patch backports, but it would be great if you could include the patch. For the record: I did not write that patch, it is the referenced changeset above, modified to be applied while building the ubuntu package. ** Patch added: "font-fix.diff" https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1799014/+attachment/5226426/+files/font-fix.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1799014 Title: bold font rendeing in Java is broken in Cosmic with OpenJDK 11 Status in freetype package in Ubuntu: Confirmed Status in openjdk-lts package in Ubuntu: Confirmed Status in openjdk-11 package in Debian: Fix Released Bug description: Since update to Cosmic, I see that bold fonts in Java have broken rendering. See attached 400% scaled PNG for illustration. The 'r' in bold rendering of "Hello World" shows basically a vertical line from the end of the hook end. I am not entirely sure this is freetype issue but some sources (https://github.com/adobe/brackets/issues/14290) suggest there is a bug in the 2.8.1 version that Cosmic seems to install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1799014/+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 1810347] [NEW] package ubuntu-web-launchers 18.04.6 failed to install/upgrade: problemas de dependência - deixando desconfigurado
Public bug reported: erro no sistema ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: linux-modules-extra-4.15.0-22-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 Date: Sun Dec 30 16:05:51 2018 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2018-03-19 (289 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ubuntu-settings Title: package ubuntu-web-launchers 18.04.6 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: Upgraded to bionic on 2018-05-06 (241 days ago) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1810347 Title: package ubuntu-web-launchers 18.04.6 failed to install/upgrade: problemas de dependência - deixando desconfigurado Status in ubuntu-settings package in Ubuntu: New Bug description: erro no sistema ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ubuntu-web-launchers 18.04.6 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: linux-modules-extra-4.15.0-22-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 Date: Sun Dec 30 16:05:51 2018 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2018-03-19 (289 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ubuntu-settings Title: package ubuntu-web-launchers 18.04.6 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: Upgraded to bionic on 2018-05-06 (241 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1810347/+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 1810351] [NEW] journalctl fails to work inside systemd service
Public bug reported: Using Ubuntu 16.04.4 LTS and Package: systemd Architecture: amd64 Version: 229-4ubuntu21.10 Multi-Arch: foreign Priority: required Section: admin Origin: Ubuntu The journalctl(1) command cannot be used in a systemd OnFailure service to get error logs. To replicate the issue 1) Create a service unit [Unit] Description=%n [Service] #ExecStart=/bin/sh -xv -c 'systemctl --user status -o cat -n 20 | mail -s "Unit failed" ' ExecStart=/bin/sh -c 'journalctl --user-unit= -o verbose -q -n 20 | mail -s "Unit failed" ' 2) enable the unit 3) start the unit You will get a failure message from journalctl and mail of sh[28225]: No journal files were opened due to insufficient permissions. sh[28225]: mail: Null message body; hope that's ok 4) switch the comment # to the journalctl ExecStart and uncomment the systemctl ExecStart line >From systemctl you will get journal output in the email. The man page for systemctl states "In addition, journalctl --unit=NAME or journalctl --user-unit=NAME use a similar filter for messages and might be more convenient." and indeed it would if it worked properly. ** 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/1810351 Title: journalctl fails to work inside systemd service Status in systemd package in Ubuntu: New Bug description: Using Ubuntu 16.04.4 LTS and Package: systemd Architecture: amd64 Version: 229-4ubuntu21.10 Multi-Arch: foreign Priority: required Section: admin Origin: Ubuntu The journalctl(1) command cannot be used in a systemd OnFailure service to get error logs. To replicate the issue 1) Create a service unit [Unit] Description=%n [Service] #ExecStart=/bin/sh -xv -c 'systemctl --user status -o cat -n 20 | mail -s "Unit failed" ' ExecStart=/bin/sh -c 'journalctl --user-unit= -o verbose -q -n 20 | mail -s "Unit failed" ' 2) enable the unit 3) start the unit You will get a failure message from journalctl and mail of sh[28225]: No journal files were opened due to insufficient permissions. sh[28225]: mail: Null message body; hope that's ok 4) switch the comment # to the journalctl ExecStart and uncomment the systemctl ExecStart line From systemctl you will get journal output in the email. The man page for systemctl states "In addition, journalctl --unit=NAME or journalctl --user-unit=NAME use a similar filter for messages and might be more convenient." and indeed it would if it worked properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1810351/+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 1309535] Re: Running without pam-kwallet installed issues a warning in auth.log
I can confirm the problem with `journalctl`: Jan 03 01:05:13 tron lightdm[12730]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or dire Jan 03 01:05:13 tron lightdm[12730]: PAM adding faulty module: pam_kwallet.so Jan 03 01:05:13 tron lightdm[12730]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or di Jan 03 01:05:13 tron lightdm[12730]: PAM adding faulty module: pam_kwallet5.so Jan 03 01:05:14 tron lightdm[12841]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or dire Jan 03 01:05:14 tron lightdm[12841]: PAM adding faulty module: pam_kwallet.so Jan 03 01:05:14 tron lightdm[12841]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or di Jan 03 01:05:14 tron lightdm[12841]: PAM adding faulty module: pam_kwallet5.so The lines were created during logins, i.e. initial logins or after locking the screen (xflock4) and unlocking it again. The workaround I used was to change /etc/pam.d/lightdm and /etc/pam.d /lightdm-greeter and comment out (#) the following lines (in both files): #authoptionalpam_kwallet.so #authoptionalpam_kwallet5.so ... #session optionalpam_kwallet.so auto_start #session optionalpam_kwallet5.so auto_start So far the systemd log is clear of those loglines. A different workaround would be to simply install the KDE component. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1309535 Title: Running without pam-kwallet installed issues a warning in auth.log Status in lightdm package in Ubuntu: Won't Fix Status in pam package in Ubuntu: Won't Fix Bug description: After upgrading to lightdm 1.10.0-0ubuntu2 I started to see this error in auth.log: Apr 10 14:34:54 simon-laptop lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Apr 10 14:34:54 simon-laptop lightdm: PAM adding faulty module: pam_kwallet.so This seems like a regression because with lightdm 1.10.0-0ubuntu1 or before I didn't have this error showing. FYI, I don't have the pam- kwallet package installed. $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 $ apt-cache policy lightdm pam-kwallet lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 18 09:12:37 2014 InstallationDate: Installed on 2014-01-26 (81 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1309535/+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 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic
should work in 18.10, but only if you *don't" install i965-va-driver- shaders... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1756380 Title: vaapi VP9 hardware decoding not working anymore in bionic Status in intel-vaapi-driver package in Ubuntu: Fix Released Status in libva package in Ubuntu: Invalid Bug description: Hardware: Dell XPS13 9365, i7-7Y75 System: Ubuntu Bionic Beaver (development branch) vainfo output on bionic is: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.1 (libva 2.1.0) vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice As you can see, VP9 entrypoints are missing. vainfo output on 17.10 was: libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple:VAEntrypointVLD VAProfileMPEG2Simple:VAEntrypointEncSlice VAProfileMPEG2Main :VAEntrypointVLD VAProfileMPEG2Main :VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointVLD VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP VAProfileH264Main :VAEntrypointVLD VAProfileH264Main :VAEntrypointEncSlice VAProfileH264Main :VAEntrypointEncSliceLP VAProfileH264High :VAEntrypointVLD VAProfileH264High :VAEntrypointEncSlice VAProfileH264High :VAEntrypointEncSliceLP VAProfileH264MultiviewHigh :VAEntrypointVLD VAProfileH264MultiviewHigh :VAEntrypointEncSlice VAProfileH264StereoHigh :VAEntrypointVLD VAProfileH264StereoHigh :VAEntrypointEncSlice VAProfileVC1Simple :VAEntrypointVLD VAProfileVC1Main:VAEntrypointVLD VAProfileVC1Advanced:VAEntrypointVLD VAProfileNone :VAEntrypointVideoProc VAProfileJPEGBaseline :VAEntrypointVLD VAProfileJPEGBaseline :VAEntrypointEncPicture VAProfileVP8Version0_3 :VAEntrypointVLD VAProfileVP8Version0_3 :VAEntrypointEncSlice VAProfileHEVCMain :VAEntry
[Touch-packages] [Bug 1808432] Re: systemctl template units not enabled per docs
This is related to https://github.com/systemd/systemd/issues/661 ** Bug watch added: github.com/systemd/systemd/issues #661 https://github.com/systemd/systemd/issues/661 -- 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/1808432 Title: systemctl template units not enabled per docs Status in systemd package in Ubuntu: New Bug description: Report is for Description: Ubuntu 16.04.4 LTS Release: 16.04 Package data is Package: systemd Architecture: amd64 Version: 229-4ubuntu21.10 Multi-Arch: foreign No log file is applicable The problem is that systemctl enable does not perform according to documentation in enabling template unit files. If a template unit file exists /full_path_to/tmpl@.service and you try to enable it with systemctl per the docs sudo systemctl enable /full_path_to/tmpl@instance.service or systemctl --user enable /full_path_to/tmpl@instance.service you get the error Failed to execute operation: No such file or directory What should happen is that systemctl fails to find /full_path_to/tmpl@instance.service so it then tries the template name /full_path_to/tmpl@.service, finds it, and creates a symlink to that template file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1808432/+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 411688]
I noticed the same bug in my system ( Ubuntu 14.04.5) while I was trying to set up pulseaudio server in Windows 10 over the local network. In my case network flooding occurs whenever I launch pavucontrol, upload traffics reaches up to 200kb/s and it reduced the local network unusable. When I close it the network attack diminishes. I added `unload-module module-rtp-send` into `/etc/pulse/default.pa` to workaround the bug. -- 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/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Unknown Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 efee 800a ee96 0x0020: 0071 b380 ed51 a42b 000
[Touch-packages] [Bug 411688]
I've also noticed this in the most up to data pulse versions from archlinux. I also cannot use a ttl of 1, as the router does not decrease the value when routing into wlan, as it has the same subnet. Neither does destination ip 24.0.0.1 help. From my side I have no chance to change the router config, because the internet is provided by someone else. What works for me though is to stream the music directly to the destination via destination_ip=192.168.178.x I could also add a menu in paprefs that'd also adress the ip directly, however this is more of a struggle because of the old gtk2 (if anyone here is following the mailing list). It would be highly appreciated to fix this bug in the module itself and reduce the payload somehow. -- 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/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Unknown Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.5
[Touch-packages] [Bug 411688]
Sending a wav file means a TCP connection between two computers. TCP connections are the most common type of traffic, and the hardware is optimized accordingly. UDP multicast is different, and apparently network hardware is not necessarily as efficient with processing that protocol. Comment #9 seems to suggest that the wifi specification itself forces multicast to be inefficient, so it's not necessarily just the hardware's fault. Starting from PA version 5.0, module-rtp-send should not generate traffic when nothing is playing (it can still be configured to play silence, but paprefs doesn't configure the module that way). If you observe different behaviour, please file a new bug and attach the output of "pactl list". -- 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/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Unknown Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos
[Touch-packages] [Bug 411688]
Sure mp3 would be way better. I just dont know how rtp works. I think its reasonable to use mp3 here. However I dont know how that works for streams and with pulse. Fixing the compression method would be the better fix, however a specific ip/hostname would not hurt neither. -- 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/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Unknown Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 efee 800a ee96 0x0020: 0071 b380 ed51 a42b 0x0030: 0x0040: 01:10:36.605081 IP (tos 0x10, ttl 1, id 2
[Touch-packages] [Bug 411688]
(In reply to freedesktop from comment #17) > Lowering the rate is possibly not a good idea as it results in worse > quality. The format is by default "s16be" about which I have no idea what a > different format would help. I do not know if the data can somehow be > compress further, because this would definitely be an idea, but I dont know > the procols internal. The data can certainly be compressed. I don't know if you've ever compared the sizes of mp3 and wav files. Typical compressed audio, when using a lossy codec, requires perhaps one tenth of the bandwidth that uncompressed audio requires, without too much effect on the audio quality. > So the only left option is to solve the routing. For my personal setup there > is no way to fix this on the router side, so the sender pulse module needs > to take care of it. Using an ip as destination works perfectly and would be > an option to use (which should be added to paprefs). However I tried that > the last days and due to dhcp my receiver always gets a new IP and using > hostnames would be a better idea. > > But the module does not seem to support hostnames. So I am wondering if this > could be fixed quite simple or needs a whole more work to do. Changing module-rtp-send to support hostnames doesn't sound terribly complicated. -- 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/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Unknown Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b
[Touch-packages] [Bug 411688]
You are right that this feature needs to be enabled first to make the bug rise. However I do not think that documentating this bug/behavior solves the problem. I do want to use music streaming, but I cannot do this as my router routes the traffic into the WLAN. Lowering the rate is possibly not a good idea as it results in worse quality. The format is by default "s16be" about which I have no idea what a different format would help. I do not know if the data can somehow be compress further, because this would definitely be an idea, but I dont know the procols internal. So the only left option is to solve the routing. For my personal setup there is no way to fix this on the router side, so the sender pulse module needs to take care of it. Using an ip as destination works perfectly and would be an option to use (which should be added to paprefs). However I tried that the last days and due to dhcp my receiver always gets a new IP and using hostnames would be a better idea. But the module does not seem to support hostnames. So I am wondering if this could be fixed quite simple or needs a whole more work to do. Another option would be to possibly create a port on the localhost and route that to the destination ip/name. And the kernel itself can do the name resolution. However I have no idea about that, but this could at least be a workaround to solve this issue. Other opinions? -- 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/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Unknown Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001
[Touch-packages] [Bug 411688]
Adding to my previous comment: it could be argued that the bug is that we transmit PCM audio instead of compressed audio. Adding support for compressed audio should help with the network stress. Does anyone volunteer to implement this? -- 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/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Unknown Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 efee 800a ee96 0x0020: 0071 b380 ed51 a42b 0x0030: 0x0040: 01:10:36.605081 IP (tos 0x10, ttl 1, id 23832, offset 0, flags [DF], proto UDP (
[Touch-packages] [Bug 411688]
I know nothing about RTP, but from a user perspective, I have two questions: 1) Transferring a WAV file over the network goes faster than real time (in terms of the audio contained within). Why should the network struggle with uncompressed RTP audio, then? 2) Why are packets generated when nothing is played? If there is no audio activity in PA, there is no need to send any packets. Apologies if this doesn't make sense, I'm talking purely as an end-user. -- 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/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Unknown Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 efee 800a ee96 0x0020:
[Touch-packages] [Bug 411688]
To my knowledge RTP can carry pretty much any format. You said on the mailing list that you want to use Kodi to receive the stream, and I don't know what Kodi supports, but I would guess that it supports many formats. Don't get too excited about compressed audio, though. I'm not volunteering to implement it, and it's probably pretty complicated to integrate to PulseAudio. In case someone is willing to take this task, the current "plan" (if you can call it a plan - it's all very fuzzy at the moment) is to use gstreamer to deal with the codecs, but in any case, please bring this topic up on the mailing list before spending too much time implementing it, so that there's an agreement about the design. -- 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/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Unknown Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23
[Touch-packages] [Bug 411688]
I read through the comments, and to me it looks like module-rtp-send doesn't have any flooding bug. The data rate of PCM audio is what it is, and the network hardware isn't always able to handle it. Multicast RTP is not enabled by default. If the user enables it, I don't know what we could possibly do to not "flood" the network. Since this is a common problem for people, there is certainly room for improvement in the UI and documentation so that users don't get so surprised when things don't work. -- 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/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Unknown Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b0 b
[Touch-packages] [Bug 411688]
*** Bug 98649 has been marked as a duplicate of this bug. *** -- 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/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Unknown Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 efee 800a ee96 0x0020: 0071 b380 ed51 a42b 0x0030: 0x0040: 01:10:36.605081 IP (tos 0x10, ttl 1, id 23832, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d18 4000 0111 2d64 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514
[Touch-packages] [Bug 411688]
All problems with RTP module flooding network, Wifi are caused by lack of IGMP support in rtp_send module. When pulseaudio with rtp_recv module is started proper IGMPv2 signalling works like it should: root@orangepione:~# tshark -i eth0 -Y "igmp" Capturing on 'eth0' 117 6.950723148 192.168.254.141 -> 239.255.1.56 IGMPv2 46 Membership Report group 239.255.1.56 177 10.430705605 192.168.254.141 -> 239.255.1.56 IGMPv2 46 Membership Report group 239.255.1.56 215 13.660683494 192.168.254.141 -> 239.255.1.56 IGMPv2 46 Membership Report group 239.255.1.56 Pulseaudio creates Multicast group (I don't use default group). As IGMP signalling is OK - IGMP capable switches enable that multicast group only on ports that need it. If pulseaudio is configured with rtp_send module - there is no IGMP signalling. Looking at code of module-rtp-recv.c we can find: mr4.imr_multiaddr = ((const struct sockaddr_in*) sa)->sin_addr; r = setsockopt(fd, IPPROTO_IP, IP_ADD_MEMBERSHIP, &mr4, sizeof(mr4)); IP_ADD_MEMBERSHIP tells kernel to join multicast group. There is no such command is module-rtp-send.c It needs fixing ASAP -- 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/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Unknown Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, i
[Touch-packages] [Bug 411688]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/505. -- 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/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Unknown Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 efee 800a ee96 0x0020: 0071 b380 ed51 a42b 0x0030: 0x0040:
[Touch-packages] [Bug 411688] Re: pulseaudio floods network with multicast packets
** Changed in: pulseaudio (Arch Linux) Status: Confirmed => Unknown ** Changed in: pulseaudio Status: Confirmed => Unknown -- 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/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Unknown Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 efee 800a ee96 0x0020: 0071 b380 ed51 a42b 0x0030: 0x0040: 01:10:36.605081 IP (tos 0x10, ttl 1, id 23832, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510
[Touch-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
** Information type changed from Private Security to Public ** Package changed: alsa-driver (Ubuntu) => ubuntu -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Ubuntu: New Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1810183/+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 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
+1 for gnome-shell 3.28.3-0ubuntu0.18.04.4 bionic-proposed - fixed for me -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in gnome-shell package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in ibus source package in Cosmic: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/391 --- tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765304/+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 1666432] Re: Internet drops every few minutes on wired and wireless connection
Same here ! Fresh Dell inspiron 5570, this bug occurs with both ubuntu 16.04 and 18.04 *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: enp2s0 version: 07 serial: 3c:2c:30:a1:25:ad size: 10Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:127 ioport:d000(size=256) memory:d2204000-d2204fff memory:d220-d2203fff *-network description: Wireless interface product: QCA9377 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:03:00.0 logical name: wlp3s0 version: 31 serial: 80:2b:f9:4b:c7:0d width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=4.15.0-43-generic firmware=WLAN.TF.1.0-2-QCATFSWPZ-5 ip=192.168.1.2 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:130 memory:d200-d21f any help ??? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1666432 Title: Internet drops every few minutes on wired and wireless connection Status in network-manager package in Ubuntu: Confirmed Bug description: Internet drops every 1-30 minutes when connected via wired or wireless (i.e., this is a problem on both wired and wireless) even though connection icon indicates the computer is still connected. Disconnecting and reconnecting via the connection icon resets internet temporarily until the next time. Dropped internet is discovered with "The site can't be reached" screens in Chromium, or error messages when downloading/updating in Terminal, or missing connection in Ubuntu Software app, or stalled syncing in Insync application (occurred even without Insync). Internet drops more frequently on wireless than on wired. It seems to disconnect more frequently with heavier internet use (e.g., downloading multiple files, opening several webpages in quick succession). This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron 15 5567 (dual boot). It occurs when running Live CD as well though. Ethernet and wifi both work without randomly disconnecting in Windows 10 on the same machine, and ethernet and wifi work on other machines running Ubuntu and Windows with the same router, so it is not a hardware or router issue. Output from sudo lshw -class network *-network description: Wireless interface product: Wireless 3165 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 79 serial: 58:fb:84:55:21:52 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:283 memory:df10-df101fff *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 07 serial: 18:db:f2:3c:d5:37 size: 10Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:279 ioport:d000(size=256) memory:df00-df000fff memory:d030-d0303fff ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 21 16:36:55 2017 IfupdownConfig:
[Touch-packages] [Bug 1810364] [NEW] package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Public bug reported: n@computer-1:~/Desktop$ sudo apt install lvm2 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5 Suggested packages: thin-provisioning-tools The following NEW packages will be installed: dmeventd libdevmapper-event1.02.1 liblvm2app2.2 liblvm2cmd2.02 libreadline5 lvm2 0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded. Need to get 2,090 kB of archives. After this operation, 8,260 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 libdevmapper-event1.02.1 amd64 2:1.02.145-4.1ubuntu3 [10.9 kB] Get:2 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 liblvm2cmd2.02 amd64 2.02.176-4.1ubuntu3 [586 kB] Get:3 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 dmeventd amd64 2:1.02.145-4.1ubuntu3 [30.4 kB] Get:4 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 liblvm2app2.2 amd64 2.02.176-4.1ubuntu3 [433 kB] Get:5 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 libreadline5 amd64 5.2+dfsg-3build2 [101 kB] Get:6 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 lvm2 amd64 2.02.176-4.1ubuntu3 [929 kB] Fetched 2,090 kB in 4s (470 kB/s) Selecting previously unselected package libdevmapper-event1.02.1:amd64. (Reading database ... 298985 files and directories currently installed.) Preparing to unpack .../0-libdevmapper-event1.02.1_2%3a1.02.145-4.1ubuntu3_amd64.deb ... Unpacking libdevmapper-event1.02.1:amd64 (2:1.02.145-4.1ubuntu3) ... Selecting previously unselected package liblvm2cmd2.02:amd64. Preparing to unpack .../1-liblvm2cmd2.02_2.02.176-4.1ubuntu3_amd64.deb ... Unpacking liblvm2cmd2.02:amd64 (2.02.176-4.1ubuntu3) ... Selecting previously unselected package dmeventd. Preparing to unpack .../2-dmeventd_2%3a1.02.145-4.1ubuntu3_amd64.deb ... Unpacking dmeventd (2:1.02.145-4.1ubuntu3) ... Selecting previously unselected package liblvm2app2.2:amd64. Preparing to unpack .../3-liblvm2app2.2_2.02.176-4.1ubuntu3_amd64.deb ... Unpacking liblvm2app2.2:amd64 (2.02.176-4.1ubuntu3) ... Selecting previously unselected package libreadline5:amd64. Preparing to unpack .../4-libreadline5_5.2+dfsg-3build2_amd64.deb ... Unpacking libreadline5:amd64 (5.2+dfsg-3build2) ... Selecting previously unselected package lvm2. Preparing to unpack .../5-lvm2_2.02.176-4.1ubuntu3_amd64.deb ... Unpacking lvm2 (2.02.176-4.1ubuntu3) ... Setting up libdevmapper-event1.02.1:amd64 (2:1.02.145-4.1ubuntu3) ... Processing triggers for libc-bin (2.28-0ubuntu1) ... Processing triggers for systemd (239-7ubuntu10.4) ... Setting up liblvm2app2.2:amd64 (2.02.176-4.1ubuntu3) ... Processing triggers for man-db (2.8.4-2) ... Setting up libreadline5:amd64 (5.2+dfsg-3build2) ... Setting up liblvm2cmd2.02:amd64 (2.02.176-4.1ubuntu3) ... Setting up dmeventd (2:1.02.145-4.1ubuntu3) ... dm-event.service is a disabled or a static unit not running, not starting it. Setting up lvm2 (2.02.176-4.1ubuntu3) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked. invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed. ● lvm2-lvmetad.service - LVM2 metadata daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor preset: enabled) Active: inactive (dead) since Wed 2019-01-02 21:42:08 CST; 27min ago Docs: man:lvmetad(8) Main PID: 320 (code=exited, status=0/SUCCESS) Jan 02 21:28:53 audiocito-1 systemd[1]: Started LVM2 metadata daemon. Jan 02 21:42:08 audiocito-1 systemd[1]: Stopping LVM2 metadata daemon... Jan 02 21:42:08 audiocito-1 systemd[1]: Stopped LVM2 metadata daemon. dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.28-0ubuntu1) ... Processing triggers for initramfs-tools (0.131ubuntu15) ... update-initramfs: Generating /boot/initrd.img-4.18.0-13-lowlatency Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.10 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.18.0-13.14-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Wed Jan 2 22:09:28 2019 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-01-02 (0 days ago) InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: lvm2 Title: pack
[Touch-packages] [Bug 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11
The attachment "font-fix.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1799014 Title: bold font rendeing in Java is broken in Cosmic with OpenJDK 11 Status in freetype package in Ubuntu: Confirmed Status in openjdk-lts package in Ubuntu: Confirmed Status in openjdk-11 package in Debian: Fix Released Bug description: Since update to Cosmic, I see that bold fonts in Java have broken rendering. See attached 400% scaled PNG for illustration. The 'r' in bold rendering of "Hello World" shows basically a vertical line from the end of the hook end. I am not entirely sure this is freetype issue but some sources (https://github.com/adobe/brackets/issues/14290) suggest there is a bug in the 2.8.1 version that Cosmic seems to install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1799014/+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 1798562] Re: After a side by side installation, resized filesystem is corrupted
Hello , I face same issue it shows busybox command line and says file system is corrupted ( tells to use fsck) and after doing that from live disk ( i saw it was asking to move nodes which repairing ) the next time system reboots the kernel panics, errors were " not syncing attempting to kill" ," bad RF code " im using windows 10 and ubuntu 18.10 alongside i have installed it like 8-9 times and after 3-4 reboots , file system corrupts we can increase the fs corruption time if we do software update after updating all updates , next reboot corrupts the filesystem ( does not take more reboots ) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1798562 Title: After a side by side installation, resized filesystem is corrupted Status in e2fsprogs package in Ubuntu: Confirmed Bug description: Test Case 1: With e2fsprogs 1.44.4-2: Download this file system image: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+attachment/5203159/+files/vda1b.qcow2.bz Run the following commands: bunzip2 vda1b.qcow2.bz qemu-img convert vda1b.qcow2 vda1b.raw e2fsck -f vda1b.raw resize2fs vda1b.raw 6200M e2fsck -f vda1b.raw e2fsck 1.44.4 (18-Aug-2018) Pass 1: Checking inodes, blocks, and sizes Inode 45746 extent block passes checks, but checksum does not match extent (logical block 1272, physical block 466167, len 776) Fix? Test Case 2 (Use case of the installer): 1. Perform a first installation of Ubuntu 2. Reboot into the freshly installed system and verify everything works as expected 3. Do a second installation and select "Install alonogside". Keep the size proposed by the installer and proceed to the end of installation 4. Reboot 5. On boot, in the list of installed systems, select the first system installed on the machine 6. Verify that it boots, you can login and it works as expected Actual Result The FS is corrupted and depending on the corruption it goes to initramfs, boots but cannot login, ... Attached is the journal of the system installed on the corrupted partition. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubiquity (not installed) 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: ubuntu:GNOME Date: Thu Oct 18 10:53:57 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- InstallationDate: Installed on 2018-10-18 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+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
