[Touch-packages] [Bug 1704297] Re: Bluetooth audio stuck in A2DP profile ([pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected)
I have a similar issue. I'm trying to get the mic working on Beats X headset. These series of patches helped me to solve the issue: https://patchwork.freedesktop.org/patch/178198/ https://patchwork.freedesktop.org/patch/178199/ https://patchwork.freedesktop.org/patch/178200/ https://patchwork.freedesktop.org/patch/178201/ Can we get them upstream? I'm on Ubuntu 18.04. -- 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/1704297 Title: Bluetooth audio stuck in A2DP profile ([pulseaudio] module- bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected) Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've got a pair of Parot Zik bluetooth headphones, with inbuilt microphones and such. The Sound control panel offers a “Profile” dropdown, with choice of A2DP and HSP profiles, but selecting the HSP profile (a) doesn't add an input source to the “Inputs” tab, and (b) doesn't stop the headphones playing stereo sound, indicating that it hasn't actually been switched to HSP profile (which is, AFAIK, mono). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: chris 7755 F pulseaudio /dev/snd/controlC1: chris 7755 F pulseaudio /dev/snd/pcmC0D0c: chris 7755 F...m pulseaudio /dev/snd/controlC0: chris 7755 F pulseaudio CurrentDesktop: GNOME Date: Fri Jul 14 16:27:09 2017 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1704297/+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 1533631] [NEW] Failed to renew DHCPv6 lease after suspend
Public bug reported: After fixing IPv6 address assignment (#1469346), IPv6 works fine until sleep. On wake up ubuntu fails to renew its IPv6 lease: Jan 13 10:47:47 ubuntu dhclient: PRC: Renewing lease on wlp3s0. Jan 13 10:47:47 ubuntu dhclient: PRC: Rebinding lease on wlp3s0. Jan 13 10:47:47 ubuntu dhclient: XMT: Rebind on wlp3s0, interval 9890ms. Jan 13 10:47:47 ubuntu NetworkManager[796]: (wlp3s0): DHCPv6 state changed bound -> unknown Jan 13 10:47:47 ubuntu dhclient: PRC: Address 2a02:::::b44 depreferred. Jan 13 10:47:47 ubuntu NetworkManager[796]: (wlp3s0): DHCPv6 state changed unknown -> expire Jan 13 10:47:47 ubuntu NetworkManager[796]: (wlp3s0): canceled DHCP transaction, DHCP client pid 1170 Jan 13 10:47:47 ubuntu NetworkManager[796]: (wlp3s0): DHCPv6 state changed expire -> done I'm not sure that it's solely NetworkManager issue (dhclient could also be affected). ** 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/1533631 Title: Failed to renew DHCPv6 lease after suspend Status in network-manager package in Ubuntu: New Bug description: After fixing IPv6 address assignment (#1469346), IPv6 works fine until sleep. On wake up ubuntu fails to renew its IPv6 lease: Jan 13 10:47:47 ubuntu dhclient: PRC: Renewing lease on wlp3s0. Jan 13 10:47:47 ubuntu dhclient: PRC: Rebinding lease on wlp3s0. Jan 13 10:47:47 ubuntu dhclient: XMT: Rebind on wlp3s0, interval 9890ms. Jan 13 10:47:47 ubuntu NetworkManager[796]: (wlp3s0): DHCPv6 state changed bound -> unknown Jan 13 10:47:47 ubuntu dhclient: PRC: Address 2a02:::::b44 depreferred. Jan 13 10:47:47 ubuntu NetworkManager[796]: (wlp3s0): DHCPv6 state changed unknown -> expire Jan 13 10:47:47 ubuntu NetworkManager[796]: (wlp3s0): canceled DHCP transaction, DHCP client pid 1170 Jan 13 10:47:47 ubuntu NetworkManager[796]: (wlp3s0): DHCPv6 state changed expire -> done I'm not sure that it's solely NetworkManager issue (dhclient could also be affected). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1533631/+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 1469346] Re: DHCPv6 responses with multiple addresses applied incorrectly to interface
There is a patch exists that fixes this problem, but against more recent version of NetworkManager: https://bugzilla.gnome.org/show_bug.cgi?id=681764#c20 I tried to adapt it to 1.0.4 currently present in Ubuntu (and it works for me). However, further testing needed. ** Bug watch added: GNOME Bug Tracker #681764 https://bugzilla.gnome.org/show_bug.cgi?id=681764 ** Patch added: "nm.patch" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1469346/+attachment/4541727/+files/nm.patch -- 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/1469346 Title: DHCPv6 responses with multiple addresses applied incorrectly to interface Status in network-manager package in Ubuntu: Confirmed Bug description: A DHCPv6 server may respond with multiple addresses, and is not an unusual case as you may wish to provide both a ULA and a global prefix to a common suffix. Recent versions of OpenWRT behave in this manner for DHCPv6. Network Manager is handling this *almost* correctly. Both addresses get applied, just not simultaneously as would be expected. The dhclient process is seeing both addresses, and both get processed by the handler, but is handled as though there were two seperate requests, applies the first address, promptly removes it, and replaces it with the second address, resulting in only the latter address persisting after interface setup. After adding the following to the upstart config for network manager, you can easily follow the mishandling of the response: --log-level=debug --log-domains=DEVICE,IP6,DHCP6 The following are key lines from the debug logging: Jun 20 23:21:16 pinky-linux NetworkManager[6244]: [1434856876.790352] [nm-system.c:280] sync_addresses(): (wlan0): adding address '2607:::ad10::61/128' ... Jun 20 23:21:17 pinky-linux NetworkManager[6244]: [1434856877.837130] [nm-system.c:247] sync_addresses(): (wlan0): removing address '2607:::ad10::61/128' Jun 20 23:21:17 pinky-linux NetworkManager[6244]: [1434856877.837526] [nm-system.c:280] sync_addresses(): (wlan0): adding address 'fd5b:::10::61/128' In this case the global prefixed address was applied, then immediately replaced by the ULA prefixed one. So it's correctly parsing both addresses of the response as supplied by dhclient, but the end result is not what is expected for the given configuration sent from the server. The correct behaviour is to add/replace all addresses in the response as a set. This negates much of the usefulness of supporting DHCPv6, and is an impediment to integration with IPv6 networks requiring it's use. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 26 22:19:20 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-05-21 (36 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) IpRoute: default via 192.168.169.1 dev wlan0 proto static 192.168.169.0/24 dev wlan0 proto kernel scope link src 192.168.169.61 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-06-17T17:39:57.347300 mtime.conffile..etc.init.network.manager.conf: 2015-06-20T23:20:39.172713 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH somewhere 1bc6a70d-cf1a-4109-8a21-71656d34685c 802-11-wireless 1435371500 Fri 26 Jun 2015 10:18:20 PM EDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled To manage notifications about
[Touch-packages] [Bug 1273907] Re: multiple cups daemons running
Also had this issue. The problem here is that one or some of the configuration utilities (could be hplip tools also) restarts cups at some point by calling /etc/init.d/cups restart. Since cups startup scripts were converted to upstart jobs, at the moment of restart upstart will notice that there is no more daemon running and will start it. So does old Sys V script. You could easy reproduce the problem by issuing /etc/init.d/cups restart from command line. The result will be two instances of cupsd running. The solution is simple: get rid of old init scripts and create symlinks to /lib/init/upstart-job in init.d. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1273907 Title: multiple cups daemons running Status in “cups” package in Ubuntu: Expired Bug description: On 13.10, after using system-config-printer, there will be multiple cups daemons running: root 10159 1 0 17:06 ?00:00:00 /usr/sbin/cupsd -C /etc/cups/cupsd.conf root 10163 1 0 17:06 ?00:00:01 /usr/sbin/cupsd -F Upstart only knows about the one with -F: # service cups stop cups stop/waiting root@terra:~# ps -ef | grep cups root 10159 1 0 17:06 ?00:00:00 /usr/sbin/cupsd -C /etc/cups/cupsd.conf This seems to cause all kinds of problems, mostly with them fighting over the printers.conf file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1273907/+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
