[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

2021-05-20 Thread Tambellini 
Tks @Daniel, 
Apparently the bug fix has been merged 2 months ago in the PulseAudio master 
branch:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/491
so about 5 years after the 1st bug reports.
To be fair, it was not a bug in ubuntu but in PulseAudio.

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1802718] Re: Allow people to do sudo apt-get build-dep without any further configuration

2020-07-24 Thread Tambellini 
Just confirming the annoyance/source of bugs/misunderstanding of doing such:
sudo cp /etc/apt/sources.list /etc/apt/sources.list~
sudo sed -Ei 's/^# deb-src /deb-src /' /etc/apt/sources.list
sudo apt-get update

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

Title:
  Allow people to do sudo apt-get build-dep without any further
  configuration

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Or provide a reliable CLI method, a direct sed on
  /etc/atp/sources.list does not feel clean.

  Motivation: https://askubuntu.com/questions/496549/error-you-must-put-
  some-source-uris-in-your-sources-list

  This is specially important for Docker, but also a big annoyance on
  desktop, as there is no clean CLI way of enabling it.

  Why not just enable by default and save people the trouble?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1802718/+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 1576747] Re: Network manager applet unable to control wifi after suspend in 16.04

2016-12-28 Thread Tambellini 
*** This bug is a duplicate of bug 1589401 ***
https://bugs.launchpad.net/bugs/1589401

Same bug on Alienware 17 R4 running ubuntu 16.04 LTS kernel 4.4.0-31-generic 
#50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux.
sudo service network-manager restart
does fix it.
Still no official fix though ?

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

Title:
  Network manager applet unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: