[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
I can confirm that the update to 20.04 fixed the audio and microphone for me! -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Is this bug something that is actively worked on or is it ignored until 20.04 is released as stable (Regarding to https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1840725/comments/37 in 20.04 the mic works)? -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
I am on the HP 830 G6 and with 'options snd-hda-intel index=0 model =laptop-dmic' I finally see the microphone appearing in pavucontrol. However, I cannot get the microphone/input working. Currently, I have the following lines added to make at least output sound working and *see* the microphone in pavucontrol: options snd-hda-intel dmic_detect=0 options snd-hda-intel index=0 model=laptop-dmic My system is as follow: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan $ inxi -Fxz Audio: Device-1: Intel Cannon Point-LP High Definition Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Sound Server: ALSA v: k5.3.0-42-generic $ uname -a Linux hostname 5.3.0-42-generic #34-Ubuntu SMP Fri Feb 28 05:49:40 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
@Morten Clausen (morten-c): Thanks for bringing that up. Hopefully this bug will also be resolved soon... -- 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/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 Status in cryptsetup package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: In Progress Bug description: I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30). After upgrading the boot time is longer (what is negligible) but the more severe error is, that I cannot enter my passphrase when I see the crypt dialog. I just see the dialog to enter my passphrase, but when I try to enter it, nothing appears in the textfield. I tried with the builtin laptop keyboard but also with an external USB keyboard. I thought about supplying more information, but things like the syslog are not helping apparently (I was not able to boot until the syslog would capture information...). If you need anything I can provide, I gladly help. [Test case] 1. On an affected system boot into kernel 3.19.0-30 [Solution] The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a real solution). PS.: Bugs like the following are either not applicable or the solution is not working for me: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689 https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+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 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
@Morten Clausen (morten-c) Imho it's better to open a separate bug. Extending this one doesn't make sense, since the problem may lay in another package and therefore will need another responsible person to take care of. Anyway, I experience the same thing as you and @Kyle Boone (kyboone) ([drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!) -- 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/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 Status in cryptsetup package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: In Progress Bug description: I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30). After upgrading the boot time is longer (what is negligible) but the more severe error is, that I cannot enter my passphrase when I see the crypt dialog. I just see the dialog to enter my passphrase, but when I try to enter it, nothing appears in the textfield. I tried with the builtin laptop keyboard but also with an external USB keyboard. I thought about supplying more information, but things like the syslog are not helping apparently (I was not able to boot until the syslog would capture information...). If you need anything I can provide, I gladly help. [Test case] 1. On an affected system boot into kernel 3.19.0-30 [Solution] The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a real solution). PS.: Bugs like the following are either not applicable or the solution is not working for me: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689 https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+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 1507214] [NEW] Ubuntu 15.04: Not possible to activate bluetooth
Public bug reported: Hi. [Issue] When I boot up my Xubuntu 15.04 and I try to turn on bluetooth (left-click on the applet in the bar and then click on "Turn bluetooth On") nothing happens. Therefore I cannot pair any BT devices. [Installed bluetooth packages] ii blueman 1.99~alpha1-1ubuntu1 amd64Graphical bluetooth manager ii bluez 4.101-0ubuntu25 amd64Bluetooth tools and daemons ii bluez-alsa:amd644.101-0ubuntu25 amd64Bluetooth ALSA support ii bluez-cups 4.101-0ubuntu25 amd64Bluetooth printer driver for CUPS ii libbluetooth3:amd64 4.101-0ubuntu25 amd64Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth113.8.2.1-0ubuntu12 amd64GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth 1:6.0-0ubuntu6 amd64Bluetooth module for PulseAudio sound server [Log] Right after boot, these lines are in the syslog: Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: gdk_mir_display_open Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: Unable to init server: Could not connect: Connection refused Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: gdk_mir_display_open Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory Oct 17 23:27:49 kernel org.blueman.Mechanism[932]: Unable to init server: Could not connect: Connection refused Every other time, the following lines appear in the Syslog: Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: Exception AttributeError: "'NoneType' object has no attribute 'stdout'" in > ignored Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: Starting blueman-mechanism Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: loading Config Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: loading Ppp Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: loading RfKill Oct 17 23:28:19 kernel org.blueman.Mechanism[932]: loading Network Anyway, when I click on "Turn BT on" as stated above, I get the following lines in Syslog: Oct 17 23:33:22 kernel dbus[932]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper) Oct 17 23:33:22 kernel blueman-mechanism: Starting blueman-mechanism Oct 17 23:33:22 kernel dbus[932]: [system] Successfully activated service 'org.blueman.Mechanism' Oct 17 23:33:22 kernel blueman-mechanism: loading Config Oct 17 23:33:22 kernel blueman-mechanism: loading Ppp Oct 17 23:33:22 kernel blueman-mechanism: loading RfKill Oct 17 23:33:22 kernel blueman-mechanism: loading Network Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: gdk_mir_display_open Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: Unable to init server: Could not connect: Connection refused Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: gdk_mir_display_open Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: Failed to connect to Mir: Failed to connect to server socket: No such file or directory Oct 17 23:33:22 kernel org.blueman.Mechanism[932]: Unable to init server: Could not connect: Connection refused Oct 17 23:33:22 kernel bluetoothd[887]: hci0: Set Powered (0x0005) failed: Busy (0x0a) Oct 17 23:33:22 kernel bluetoothd[887]: bluetoothd[887]: hci0: Set Powered (0x0005) failed: Busy (0x0a) Oct 17 23:33:22 kernel bluetoothd[887]: Adapter /org/bluez/887/hci0 has been enabled Oct 17 23:33:22 kernel bluetoothd[887]: bluetoothd[887]: Adapter /org/bluez/887/hci0 has been enabled Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: Exception AttributeError: "'NoneType' object has no attribute 'stdout'" in > ignored Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: Starting blueman-mechanism Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: loading Config Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: loading Ppp Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: loading RfKill Oct 17 23:33:52 kernel org.blueman.Mechanism[932]: loading Network [Similar bugs] I tried, as suggested in [1], to "sudo hciconfig hci0 up", which doesn't help at all. If you need anymore information, I am happy to provide it. [1] ... https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/411481 ** Affects: blueman (Ubuntu) Importance: Undecided Status: New ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags
[Touch-packages] [Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
** Package changed: gnome-icon-theme (Ubuntu) => cryptsetup (Ubuntu) ** Description changed: I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30). After upgrading the boot time is longer (what is negligible) but the more sever error is, that I cannot enter my passphrase when I see the crypt dialog. I just see the dialog to enter my passphrase, but when I try to enter it, nothing appears in the textfield. I tried with the builtin laptop keyboard but also with an external USB keyboard. I thought about supplying more information, but things like the syslog are not helping apparently (I was not able to boot until the syslog would capture information...). If you need anything I can provide, I gladly help. - The "solution" for now is booting the older Kernel 3.19.0-28. + [Test case] + 1. On an affected system boot into kernel 3.19.0-30 + + [Solution] + The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a real solution). PS.: Bugs like the following are either not applicable or the solution is not working for me: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689 https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 Status in cryptsetup package in Ubuntu: New Bug description: I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30). After upgrading the boot time is longer (what is negligible) but the more sever error is, that I cannot enter my passphrase when I see the crypt dialog. I just see the dialog to enter my passphrase, but when I try to enter it, nothing appears in the textfield. I tried with the builtin laptop keyboard but also with an external USB keyboard. I thought about supplying more information, but things like the syslog are not helping apparently (I was not able to boot until the syslog would capture information...). If you need anything I can provide, I gladly help. [Test case] 1. On an affected system boot into kernel 3.19.0-30 [Solution] The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a real solution). PS.: Bugs like the following are either not applicable or the solution is not working for me: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689 https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1500751/+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 1500751] [NEW] Cryptsetup Keyboard not working on Xubuntu 3.19.0-30
Public bug reported: I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30). After upgrading the boot time is longer (what is negligible) but the more sever error is, that I cannot enter my passphrase when I see the crypt dialog. I just see the dialog to enter my passphrase, but when I try to enter it, nothing appears in the textfield. I tried with the builtin laptop keyboard but also with an external USB keyboard. I thought about supplying more information, but things like the syslog are not helping apparently (I was not able to boot until the syslog would capture information...). If you need anything I can provide, I gladly help. The "solution" for now is booting the older Kernel 3.19.0-28. PS.: Bugs like the following are either not applicable or the solution is not working for me: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689 https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194 ** Affects: gnome-icon-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1500751 Title: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30 Status in gnome-icon-theme package in Ubuntu: New Bug description: I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30). After upgrading the boot time is longer (what is negligible) but the more sever error is, that I cannot enter my passphrase when I see the crypt dialog. I just see the dialog to enter my passphrase, but when I try to enter it, nothing appears in the textfield. I tried with the builtin laptop keyboard but also with an external USB keyboard. I thought about supplying more information, but things like the syslog are not helping apparently (I was not able to boot until the syslog would capture information...). If you need anything I can provide, I gladly help. The "solution" for now is booting the older Kernel 3.19.0-28. PS.: Bugs like the following are either not applicable or the solution is not working for me: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689 https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1500751/+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
