[Touch-packages] [Bug 665932] Re: boot stops at resume: libgcrypt 1.4.5 for over 20 seconds
I booted a Live CD and split my swap partition into two, leading to the old UUID being invalid. Doing this makes boot hang at resume: libgrypt x.x.x forever. Some googling lead me here, but I could not find the file /usr/share /initramfs-tools/hooks/resume, and could not try the solution suggested in #11. I eventually fixed the problem by assigning the correct UUID for my new swap partition in the files /etc/fstab and /etc/uswsusp.conf, chrooting into the Ubuntu root, and running `update-initramfs -u`, and everything is up and running fine now, so no harm done. However, I would suggest that a more informative error message be printed, such as UUID 29581fa0-3814-11e4-a7d0-0002a5d5c51b not found, instead of hanging indefinitely at boot, to prevent other people from encountering the same problem in the future. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgcrypt11 in Ubuntu. https://bugs.launchpad.net/bugs/665932 Title: boot stops at resume: libgcrypt 1.4.5 for over 20 seconds Status in “libgcrypt11” package in Ubuntu: Confirmed Bug description: Binary package hint: libgcrypt11 Ubuntu 10.10 Maverick Not using any encryption unless something has been set without my knowledge by default. 20 seconds to boot has seriously increased my boot time since Ubuntu 10.04, not sure that it is libgcrypts fault but it is a place to start. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libgcrypt11 1.4.5-2ubuntu1 ProcVersionSignature: Ubuntu 2.6.36-1.7-generic 2.6.36 Uname: Linux 2.6.36-1-generic x86_64 Architecture: amd64 Date: Sun Oct 24 17:33:03 2010 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100224.1) ProcEnviron: LANG=sv_SE.utf8 SHELL=/bin/bash SourcePackage: libgcrypt11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/665932/+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 1348668] Re: Unity lockscreen lets applications capture keyboard input
Good to know. From the back of my mind, I can confirm that running Firefox, vim, Terminator, or Gedit in the foreground does not affect the lock screen. In other words the bug lies with the interaction between Unity Lockscreen and Google Chrome. Also, related to my previous comment, forget what I wrote there. I think `workaround-screen-lock-malfunction_1_all.deb` is meant to fix something else, and so is totally unrelated to this bug. I have had the issue after installing it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1348668 Title: Unity lockscreen lets applications capture keyboard input Status in “unity” package in Ubuntu: New Bug description: I noticed that with the Vimium extension activated in Google Chrome, I cannot unlock Unity's lockscreen because keyboard input is hijacked by Vimium. The lockscreen really should not let this happen, and it can even be considered a potential security vulnerability as it might allow applications to capture a user's password. I have noticed this before as well when using another application, though I can't remember which one it was at the moment. The workaround is to use the mouse to choose the Switch user-option, but this is really not obvious to anyone who might encounter this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1348668/+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 1290847] Re: pyvenv fails due to mising ensurepip module
Pierre, this seemed to work for me: $ sudo apt-get install python-virtualenv $ virtualenv /desired/path/to/env $ which pip /desired/path/to/env/bin/pip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1290847 Title: pyvenv fails due to mising ensurepip module Status in “python3-defaults” package in Ubuntu: Fix Released Status in “python3.4” package in Ubuntu: Fix Released Status in “python3.4” package in Debian: Fix Released Bug description: Hello, I noticed the following # fails python3.4 -m venv --clear python-venv Error: Command '['.../external/python-venv/bin/python3.4', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1 # works, but no pip python3.4 -m venv --clear --without-pip python-venv Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+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 1585084] Re: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)
My log. Contrary to what the log reports, I did not plug anything into the front headphone jack. ** Attachment added: "pulseverbose.log" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+attachment/4743173/+files/pulseverbose.log -- 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/1585084 Title: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner) Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 16.04 yesterday, I did a clean install while preserving the home directory which is mounted in a separate partition. Even during the installation I had constant volume notification bubble appearing on the top-right corner of my screen, it would come and go about twice every minute. I just thought it was due to installing hardware drivers or something but the problem persisted even when I booted into the freshly installed system. I did some searching and two users reported the exact problem. And one more suggested this happens because constant disconnect and reconnect of the sound card which makes sense as the sound settings flashes briefly during every popup. Someone on IRC suggested to kill pulseaudio and thus restart it, that does not fix the issue. I also tried the Live environment thinking it might be due to some old config files in home partition (which was preserved during upgrade), but this problem happens in the live environment as well, which makes sense because it was present during installation as well. Users with the same issue: http://ubuntuforums.org/showthread.php?t=2323815 http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04 http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sidd 1651 F pulseaudio /dev/snd/controlC0: sidd 1651 F pulseaudio /dev/snd/controlC1: sidd 1651 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 12:31:12 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@hui.wang My USB headset no longer works. I installed kernel 5.3.0-43 from proposed and libasound2 from your ppa. $ uname -a Linux eddie-minut 5.3.0-43-generic #36-Ubuntu SMP Mon Mar 16 13:29:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ cat /sys/devices/virtual/dmi/id/bios_version N2HET46W (1.29 ) $ dpkg -l libasound2 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++--=-- ii libasound2:amd64 1.1.9-0ubuntu1.2++testucm amd64shared library for ALSA applications $ dmesg ... [ 464.139786] usb 1-3: Manufacturer: Kingston [ 464.378226] input: Kingston HyperX Cloud Flight Wireless Headset Consumer Control as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0951:16C4.0005/input/input33 [ 464.437214] input: Kingston HyperX Cloud Flight Wireless Headset as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0951:16C4.0005/input/input34 [ 464.437594] input: Kingston HyperX Cloud Flight Wireless Headset as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0951:16C4.0005/input/input35 [ 464.437943] input: Kingston HyperX Cloud Flight Wireless Headset as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0951:16C4.0005/input/input36 [ 464.438711] hid-generic 0003:0951:16C4.0005: input,hiddev0,hidraw1: USB HID v1.11 Device [Kingston HyperX Cloud Flight Wireless Headset] on usb-:00:14.0-3/input3 [ 465.169150] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 465.264582] sof-audio-pci :00:1f.3: firmware boot complete [ 465.578000] debugfs: File 'Analog Playback and Capture' in directory 'HDA Analog' already present! [ 465.703404] debugfs: File 'Analog Playback and Capture' in directory 'HDA Analog' already present! [ 532.954965] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 533.052406] sof-audio-pci :00:1f.3: firmware boot complete [ 543.902184] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 When I plug in a headset with a mic in the 3.5mm port, it still seems to use the internal mic instead of that of the headset. I also get a lot of popping sounds in the 3.5mm headset when playing audio, but that might not be related to this issue as I had that on kernel 5.3.0-41 as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@hui.wang I'm not sure that I should file a bug against the Linux kernel; My USB headset works fine on 5.3.0-43-generic if I *don't* install libasound2 from your PPA. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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
