[Touch-packages] [Bug 1581567] Re: SRU regression, can't change own data
I had just created a bug for problems switching languages: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1582517 I managed to end up getting to this bug here. I have marked mine as a duplicate. I can also confirm that installing the proposed packages below in XenialXerus has fixed my problems. I can now switch languages again. https://launchpad.net/ubuntu/xenial/amd64/accountsservice/0.6.40-2ubuntu11.1 https://launchpad.net/ubuntu/xenial/amd64/libaccountsservice0/0.6.40-2ubuntu11.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1581567 Title: SRU regression, can't change own data Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Xenial: Fix Committed Bug description: * Impact Seems like https://launchpad.net/ubuntu/+source/accountsservice/0.6.40-2ubuntu11 created issues, the allow_active/inactive rules they are needed otherwise users can't change their name/icon/etc from the user panel in unity-control-center... * Test Case - open unity-control-center - go to the user panel - try to change your user icon it should work * Regression potential it's granting back rights that were given before, shouldn't create new issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1581567/+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 1422143] Re: No wifi connection after suspend with systemd due to missing "wpa_cli suspend"
Says fix released for xenial. What was it actually released in? wpa_supplicant? I still have the problem intermittently. May 16 22:58:18 bryan-Latitude-E6410 kernel: iwlwifi :03:00.0: Radio type=0x0-0x3-0x1 May 16 22:58:19 bryan-Latitude-E6410 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready May 16 22:58:19 bryan-Latitude-E6410 NetworkManager[690]: [1463453899.0483] device (eno1): state change: unmanaged -> unavailable (reason 'managed') [1 May 16 22:58:19 bryan-Latitude-E6410 kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready May 16 22:58:19 bryan-Latitude-E6410 NetworkManager[690]: [1463453899.2606] manager: NetworkManager state is now DISCONNECTED May 16 22:58:19 bryan-Latitude-E6410 kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready May 16 22:58:19 bryan-Latitude-E6410 wpa_supplicant[858]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none May 16 22:58:19 bryan-Latitude-E6410 wpa_supplicant[858]: dbus: Failed to construct signal May 16 22:58:19 bryan-Latitude-E6410 NetworkManager[690]: [1463453899.3049] device (wlp3s0): supplicant interface state: starting -> ready May 16 22:58:19 bryan-Latitude-E6410 NetworkManager[690]: [1463453899.3050] device (wlp3s0): state change: unavailable -> disconnected (reason 'supplic May 16 22:58:19 bryan-Latitude-E6410 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready May 16 22:58:20 bryan-Latitude-E6410 acpid[617]: client connected from 8954[0:0] May 16 22:58:20 bryan-Latitude-E6410 acpid[617]: 1 client rule loaded May 16 22:58:20 bryan-Latitude-E6410 kernel: dell_wmi: Unknown WMI event type 0x11: 0xffd1 sudo service network-manager restart seems to fix the problem as suggested above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1422143 Title: No wifi connection after suspend with systemd due to missing "wpa_cli suspend" Status in One Hundred Papercuts: Confirmed Status in NetworkManager: Unknown Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Wily: Fix Committed Status in wpa source package in Xenial: Fix Released Bug description: Using systemd as my default init system if I resume from suspend my laptop, it doesn't automatically reconnect to the wireless network and it doesn't list the available network connections. The only way to get a wireless connection is to restart the network- manager daemon or going to the gnome-control-center, disable wireless and enable it again. SRU INFORMATION === In some of these cases this bug can be worked around by calling "wpa_cli suspend/resume" before/after suspend, like we used to do with the old pm-utils quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects particular hardware, and thus this needs to be tested by affected reporters, there is no general reproducer for arbitrary systems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu6 Uname: Linux 3.19.0-031900-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Sun Feb 15 18:27:39 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-10-22 (116 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) IpRoute: default via 10.0.0.1 dev wlan0 proto static metric 1024 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.36 169.254.0.0/16 dev wlan0 scope link metric 1000 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0wifi connected/org/freedesktop/NetworkManager/Devices/2 openhost_caldas 09d1f69d-d3da-4978-a69c-d94455db7ecf /org/freedesktop/NetworkManager/ActiveConnection/0 docker0 bridgeunavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1422143/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help
[Touch-packages] [Bug 1389781] Re: A2DP works randomly
I have similar problems. Sometimes it works. Sometimes it doesn't. Have used multiple different bluetooth devices. Blueman doesn't work either seems like maybe a permission problem with pulseaudio? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1389781 Title: A2DP works randomly Status in “bluez” package in Ubuntu: Confirmed Bug description: Hello, There is a problem with the bluetooth mode A2DP. When I connect my bluetooth headphone, sometimes I can activate the A2DP mode (which gives a good sound quality) and sometimes I can't (nothing happened when I change it in the configuration window), and I need to switch to HFS/HFP (bad sound quality). Note that some logs are attached. I found on the internet a work around which is to put in /etc/bluetooth/audio.conf a line Disable=Socket It seems to work (well it's hard to say for the moment because I didn't have the time to do much tests), but I would like to know what Socket is supposed to do. Would it be possible to solve this bug when Socket is activated too ? Thank you, Tobias. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1389781/+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 1389781] Re: A2DP works randomly
Try this!
1) Pair the headset and run pavucontrol the pulse audio volume control panel.
2) Go to configuration
3) Change to off
4) Change to a2dp
or
pacmd set-card-profile cardnumber off
pacmd set-card-profile cardnumber a2dp
Opening unity-control-center sound will switch it back to hsp
Here is some output from unity-control-center when I open it with the
bluetooth playing and when I try to switch it to a2dp
{code}
bparadis@bparadis-x79:/usr/bin$ unity-control-center 21
(unity-control-center:23002): sound-cc-panel-WARNING **: Unable to find stream
for bar '(null)'
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug
(unity-control-center:23002): sound-cc-panel-WARNING **: active_output_update -
couldn't find a stream from the supposed active output
(unity-control-center:23002): sound-cc-panel-WARNING **:
active_input_update - couldn't find a stream from the supposed active
input
(unity-control-center:23002): sound-cc-panel-WARNING **:
pa_stream_disconnect failed, res = -15
(unity-control-center:23002): GLib-GObject-WARNING **: invalid unclassed
pointer in cast to 'GObject'
(unity-control-center:23002): GLib-GObject-CRITICAL **: g_object_set_data:
assertion 'G_IS_OBJECT (object)' failed
{code}
** Also affects: unity-control-center (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1389781
Title:
A2DP works randomly
Status in “bluez” package in Ubuntu:
Confirmed
Status in “unity-control-center” package in Ubuntu:
New
Bug description:
Hello,
There is a problem with the bluetooth mode A2DP. When I connect my
bluetooth headphone, sometimes I can activate the A2DP mode (which
gives a good sound quality) and sometimes I can't (nothing happened
when I change it in the configuration window), and I need to switch to
HFS/HFP (bad sound quality). Note that some logs are attached.
I found on the internet a work around which is to put in
/etc/bluetooth/audio.conf a line
Disable=Socket
It seems to work (well it's hard to say for the moment because I
didn't have the time to do much tests), but I would like to know what
Socket is supposed to do.
Would it be possible to solve this bug when Socket is activated too ?
Thank you,
Tobias.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1389781/+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
