[Touch-packages] [Bug 1341890] Re: [X550LA, Realtek ALC3236, Mic, Internal] No sound at all
I have a similar problem : the microphone doesn't work *when the mic- boost is on*. So with pulseaudio, you shoud try to reduce the sound until is disable mic-boost (quite annoying to do), or you can use "alsamixer" to set "Mic Boost" to 0. It gives at least sound, but it's not very high... If anyone knows how to be able to use the mic boost I would be very interested ! -- 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/1341890 Title: [X550LA, Realtek ALC3236, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've been trying to fix this myself for a while now, and just a day or two ago, the speakers stopped working, too. Neither the internal nor external speakers I've been using with my laptop have been working, with two exceptions: the bongos noise when the login screen comes up, and the tones made during a system test. I have tried the commands "alsamixer" and "gstreamer-properties" in terminal and have had success with neither of them, and have also tried using the pulse audio volume controls to no avail. My assumption is that there is an issue with the drivers, as even the microphone produced a few sporadic noises ONLY when I was playing with the mic volume controls, but at no other point in no other program has it been so responsive. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jake 1815 F pulseaudio /dev/snd/controlC0: jake 1815 F pulseaudio /dev/snd/pcmC0D3p: jake 1815 F...m pulseaudio CurrentDesktop: Unity Date: Mon Jul 14 20:25:02 2014 InstallationDate: Installed on 2014-05-23 (52 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jake 1815 F pulseaudio /dev/snd/controlC0: jake 1815 F pulseaudio /dev/snd/pcmC0D3p: jake 1815 F...m pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X550LA, Realtek ALC3236, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.403:bd11/26/2013:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1341890/+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 1354924] Re: Networkmanager does not autoconnect to wireless network
Could anyone put the priority of this bug to more than medium ? Because it has implication on everyday life... And if you have a bad wifi connection that often disconnect is just horrible to click every ten seconds to reconnect. -- 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/1354924 Title: Networkmanager does not autoconnect to wireless network Status in network-manager package in Ubuntu: Confirmed Bug description: When adding a net wireless network and enable connect automatically' networkmanager does not automatically connect to the network wenever possible. I'm running kubuntu 14.10 daily. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Aug 10 21:30:03 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-11 (29 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710) IpRoute: default via 192.168.0.2 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.213 metric 9 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /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 disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+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 1354924] Re: Networkmanager does not autoconnect to wireless network
I don't know if it's linked but I'm playing with a Wifi rooteur and I often change the name/encryption of the device, and to refresh the list of the devices the refresh button isn't enough : sometimes it detect a wrong encryption (none instead of psk), sometimes it doesn't detect the Wifi network (while sudo iwlist wlan0 scan does). I'm not sure it's linked to this problem but if it is I hope it can 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/1354924 Title: Networkmanager does not autoconnect to wireless network Status in network-manager package in Ubuntu: Confirmed Bug description: When adding a net wireless network and enable connect automatically' networkmanager does not automatically connect to the network wenever possible. I'm running kubuntu 14.10 daily. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Aug 10 21:30:03 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-11 (29 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710) IpRoute: default via 192.168.0.2 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.213 metric 9 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /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 disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+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 1354924] Re: Networkmanager does not autoconnect to wireless network
I can confirm I've the same (very annoying) bug. I don't have the file that Paul L. is talking about, but when I do sudo service network- manager restart it works (but it's dirty, even in the /etc/rc.local folder). I don't know if it can be useful but here are some logs (I aslept and awoke my laptop) : $ cat /var/log/syslog | grep -i network Dec 23 17:13:36 tblinux NetworkManager[1003]: info sleep requested (sleeping: no enabled: yes) Dec 23 17:13:36 tblinux NetworkManager[1003]: info sleeping or disabling... Dec 23 17:13:36 tblinux NetworkManager[1003]: info (eth0): device state change: unavailable - unmanaged (reason 'sleeping') [20 10 37] Dec 23 17:13:36 tblinux NetworkManager[1003]: info (eth0): cleaning up... Dec 23 17:13:36 tblinux NetworkManager[1003]: info (eth0): taking down device. Dec 23 17:13:37 tblinux NetworkManager[1003]: info NetworkManager state is now ASLEEP Dec 23 17:13:37 tblinux NetworkManager[1003]: info (wlan0): device state change: activated - unmanaged (reason 'sleeping') [100 10 37] Dec 23 17:13:37 tblinux NetworkManager[1003]: info (wlan0): deactivating device (reason 'sleeping') [37] Dec 23 17:13:37 tblinux NetworkManager[1003]: info (wlan0): canceled DHCP transaction, DHCP client pid 5018 Dec 23 17:13:37 tblinux NetworkManager[1003]: warn DNS: plugin dnsmasq update failed Dec 23 17:13:37 tblinux NetworkManager[1003]: info Removing DNS information from /sbin/resolvconf Dec 23 17:13:38 tblinux NetworkManager[1003]: info (wlan0): cleaning up... Dec 23 17:13:38 tblinux NetworkManager[1003]: info (wlan0): taking down device. Dec 23 17:13:38 tblinux NetworkManager[1003]: info (D0:C1:B1:5F:55:D9): device state change: disconnected - unmanaged (reason 'sleeping') [30 10 37] Dec 23 17:13:38 tblinux NetworkManager[1003]: info (D0:C1:B1:5F:55:D9): cleaning up... Dec 23 17:13:38 tblinux NetworkManager[1003]: info (D0:C1:B1:5F:55:D9): taking down device. Dec 23 17:13:45 tblinux NetworkManager[1003]: info BT device D0:C1:B1:5F:55:D9 removed Dec 23 17:13:46 tblinux NetworkManager[1003]: info wake requested (sleeping: yes enabled: yes) Dec 23 17:13:46 tblinux NetworkManager[1003]: info waking up and re-enabling... Dec 23 17:13:46 tblinux NetworkManager[1003]: info (eth0): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] Dec 23 17:13:46 tblinux NetworkManager[1003]: info (eth0): bringing up device. Dec 23 17:13:46 tblinux NetworkManager[1003]: info (eth0): preparing device. Dec 23 17:13:46 tblinux NetworkManager[1003]: info (eth0): deactivating device (reason 'managed') [2] Dec 23 17:13:46 tblinux NetworkManager[1003]: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Dec 23 17:13:46 tblinux NetworkManager[1003]: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Dec 23 17:13:46 tblinux NetworkManager[1003]: info NetworkManager state is now CONNECTED_GLOBAL Dec 23 17:13:46 tblinux NetworkManager[1003]: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0): bringing up device. Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0): preparing device. Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0): deactivating device (reason 'managed') [2] Dec 23 17:13:46 tblinux NetworkManager[1003]: info NetworkManager state is now DISCONNECTED Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0) supports 4 scan SSIDs Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0): supplicant interface state: starting - ready Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0): device state change: unavailable - disconnected (reason 'supplicant-available') [20 30 42] Dec 23 17:13:46 tblinux NetworkManager[1003]: warn Trying to remove a non-existant call id. Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0): supplicant interface state: ready - disconnected Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0) supports 4 scan SSIDs Dec 23 17:13:47 tblinux NetworkManager[1003]: info (wlan0): supplicant interface state: disconnected - inactive Dec 23 17:13:47 tblinux NetworkManager[1003]: info BT device tobias (D0:C1:B1:5F:55:D9) added (NAP) Dec 23 17:13:47 tblinux NetworkManager[1003]: info (D0:C1:B1:5F:55:D9): new Bluetooth device (driver: 'bluez' ifindex: 0) Dec 23 17:13:47 tblinux NetworkManager[1003]: info (D0:C1:B1:5F:55:D9): exported as /org/freedesktop/NetworkManager/Devices/5 Dec 23 17:13:47 tblinux NetworkManager[1003]: info (D0:C1:B1:5F:55:D9): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] Dec 23 17:13:47 tblinux NetworkManager[1003]: info (D0:C1:B1:5F:55:D9): deactivating device (reason 'managed') [2] Dec 23 17:13:47 tblinux NetworkManager[1003]:
[Touch-packages] [Bug 1354924] Re: Networkmanager does not autoconnect to wireless network
Is it possible that the wifi is loaded after network-manager, so that network-manager cannot reconnect ? -- 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/1354924 Title: Networkmanager does not autoconnect to wireless network Status in network-manager package in Ubuntu: Confirmed Bug description: When adding a net wireless network and enable connect automatically' networkmanager does not automatically connect to the network wenever possible. I'm running kubuntu 14.10 daily. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Aug 10 21:30:03 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-11 (29 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710) IpRoute: default via 192.168.0.2 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.213 metric 9 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /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 disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+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
Bryan Paradis : I'm sorry but using pulseaudio instead of the system configuration menu doesn't change anything for me (but I'm using KDE, so maybe there isn't the bug that affects Unity ?). But my problem is still here, even with Disable=Headset in my /etc/bluetooth/audio.conf sometimes I need a full reboot to make my bluetooth headset working (sudo services bluetooth restart isn't always enough). -- 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
[Touch-packages] [Bug 1389781] Re: A2DP works randomly
In fact even the work around doesn't work... I tried to make my computer sleeping, and then the A2DP mode doesn't work anymore... -- 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: 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
[Touch-packages] [Bug 1389781] [NEW] A2DP works randomly
Public bug reported: 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. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Attachment added: bug.log https://bugs.launchpad.net/bugs/1389781/+attachment/4253989/+files/bug.log -- 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: 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
[Touch-packages] [Bug 1389781] Re: A2DP works randomly
After some more researches I found a way to make A2DP work, to do that I need to put in /etc/bluetooth/audio.conf in [General] the line Disable=Headset (then sudo service bluetooth restart). A2DP seems to work now, but there is an other problem which appears : I can't use HSP/HFP mode which is usefull to record a sound from the headphone. So is there a solution to make both HSP and A2DP usable without a need to edit /etc/bluetooth/audio.conf and restart bluetooth ? Thank you. -- 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: 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
