[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)
Sorry: This script https://gist.github.com/hamidzr/dd81e429dc86f4327ded7a2030e7d7d9. This activated everything so far. -- 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
[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)
Hi @hui.wang, i can also help with that. I'm currently using Mint 19.3 with the 5.3.0-40-generic kernel and used this script to activate my soundcard and mic. This works great until the -40- kernel but with -42- also the shutdown doesnt work anymore. Nevertheless here is my bios_version grabbed with cat /sys/devices/virtual/dmi/id/bios_version N2HET44W (1.27 ) - So "N2H". Let me know if i can also help otherwise. Is the procedure the same for me on Mint if i want your proposed version to run? I can use timeshift if something goes wrong and restore the last working version, so i can test almost everything. Btw. the 5.0.0-1043-oem-osp1 kernel didnt boot correctly. it stopped with blank screen and only mouse was active. -- 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
[Touch-packages] [Bug 1867885] [NEW] Suspend does not work on Thinkpad X1 Yoga
Public bug reported: After upgrading to the Kernel version 5.3.0-42-generic on Ubuntu 19.10 on my Thinkpad X1 Yoga I could not wake it up from suspend anymore. I downgraded to 5.3.0-40-generic and it works again. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: eoan ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- 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/1867885 Title: Suspend does not work on Thinkpad X1 Yoga Status in linux package in Ubuntu: Incomplete Bug description: After upgrading to the Kernel version 5.3.0-42-generic on Ubuntu 19.10 on my Thinkpad X1 Yoga I could not wake it up from suspend anymore. I downgraded to 5.3.0-40-generic and it works again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867885/+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 1737614] Re: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop
Sorry...I've missed a relevant attachment from `alsa-info`... ** Attachment added: "alsa-info.txt.LHRz4IJ4Ka" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1737614/+attachment/5338271/+files/alsa-info.txt.LHRz4IJ4Ka -- 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/1737614 Title: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop Status in alsa-driver package in Ubuntu: Won't Fix Bug description: I have a new laptop HP-15-BS576TX which has this Intel Corporation Sunrise Point-LP HD Audio. 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) The laptop sound works perfectly fine in Windows 10 with realtek drivers. However, in Ubuntu 17.10, the volume is significantly low, that I've to scroll the volume slider above 100% mark in pulseaudio to the maximum to get acceptable level of sound. I suspect the sound quality also is low (mono-like), may be not coming from all speakers (perhaps subwoofer exist for this model). Also alsamixer shows the speaker volume at the maximum. Details about the audio hardware are below: :~$ sudo lspci -vvv | grep -A 40 -i audio 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Hewlett-Packard Company Device 832b Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- /proc/asound/card0/codec#0 <== Codec: Realtek ALC3227 ==> /proc/asound/card0/codec#2 <== Codec: Intel Kabylake HDMI :~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3227 Analog [ALC3227 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 I have gone through Linux kernel sources ALSA and Snd-HDA lists and unable to find any optimizations for this laptop. Here is the relevant dmesg details: [ 15.502856] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 16.310503] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3227: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [ 16.310506] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 16.310507] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 16.310508] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 16.310509] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 16.310510] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 [ 16.310512] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 16.451397] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input9 [ 16.451451] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 16.451496] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 16.451538] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input12 [ 16.451581] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input13 [ 16.451624] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input14 [ 16.451687] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input15 Any further information needed, please let me know. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 [modified: usr/share/alsa-base/alsa-info.sh] ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: ndiswrapper ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: admin2018 1246 F pulseaudio CurrentDesktop: GNOME Date: Tue Dec 12 00:46:12 2017 InstallationDate: Installed on 2017-11-22 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2017 dmi.bios.vendor: Insyde d
[Touch-packages] [Bug 1737614] Re: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop
Seems the problem is worsened with new kernel in 18.04. Linux [...] 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 [...] x86_64 GNU/Linux After the last update, no more audio cards are detected, but `lspci` says: lspci -v -d 8086:9d71 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-LP HD Audio (rev 21) Subsystem: Acer Incorporated [ALI] Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 32, IRQ 16 Memory at b1228000 (64-bit, non-prefetchable) [size=16K] Memory at b120 (64-bit, non-prefetchable) [size=64K] Capabilities: [50] Power Management version 3 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ Kernel driver in use: snd_soc_skl Kernel modules: snd_hda_intel, snd_soc_skl -- 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/1737614 Title: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop Status in alsa-driver package in Ubuntu: Won't Fix Bug description: I have a new laptop HP-15-BS576TX which has this Intel Corporation Sunrise Point-LP HD Audio. 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) The laptop sound works perfectly fine in Windows 10 with realtek drivers. However, in Ubuntu 17.10, the volume is significantly low, that I've to scroll the volume slider above 100% mark in pulseaudio to the maximum to get acceptable level of sound. I suspect the sound quality also is low (mono-like), may be not coming from all speakers (perhaps subwoofer exist for this model). Also alsamixer shows the speaker volume at the maximum. Details about the audio hardware are below: :~$ sudo lspci -vvv | grep -A 40 -i audio 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Hewlett-Packard Company Device 832b Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- /proc/asound/card0/codec#0 <== Codec: Realtek ALC3227 ==> /proc/asound/card0/codec#2 <== Codec: Intel Kabylake HDMI :~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3227 Analog [ALC3227 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 I have gone through Linux kernel sources ALSA and Snd-HDA lists and unable to find any optimizations for this laptop. Here is the relevant dmesg details: [ 15.502856] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 16.310503] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3227: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [ 16.310506] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 16.310507] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 16.310508] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 16.310509] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 16.310510] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 [ 16.310512] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 16.451397] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input9 [ 16.451451] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 16.451496] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 16.451538] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input12 [ 16.451581] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input13 [ 16.451624] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input14 [ 16.451687] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input15 Any further information needed, please let me know. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 [modified: usr/share/alsa-base/alsa-info.sh] ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-gener
[Touch-packages] [Bug 1867898] Re: package libaudit1:amd64 1:2.4.5-1ubuntu2 [modified: lib/x86_64-linux-gnu/libaudit.so.1.0.0 usr/share/doc/libaudit1/changelog.Debian.gz] failed to install/upgrade: pa
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1867898 Title: package libaudit1:amd64 1:2.4.5-1ubuntu2 [modified: lib/x86_64-linux- gnu/libaudit.so.1.0.0 usr/share/doc/libaudit1/changelog.Debian.gz] failed to install/upgrade: package libaudit1:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in audit package in Ubuntu: New Bug description: error while updating browser ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libaudit1:amd64 1:2.4.5-1ubuntu2 [modified: lib/x86_64-linux-gnu/libaudit.so.1.0.0 usr/share/doc/libaudit1/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 AptOrdering: libaudit1: Configure firefox: Install firefox: Configure NULL: ConfigurePending Architecture: amd64 Date: Wed Mar 18 09:51:52 2020 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libaudit-common 1:2.4.5-1ubuntu2.1 libc6 2.23-0ubuntu11 libgcc1 1:6.0.1-0ubuntu1 DpkgTerminalLog: dpkg: error processing package libaudit1:amd64 (--configure): package libaudit1:amd64 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package libaudit1:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-07-18 (973 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: audit Title: package libaudit1:amd64 1:2.4.5-1ubuntu2 [modified: lib/x86_64-linux-gnu/libaudit.so.1.0.0 usr/share/doc/libaudit1/changelog.Debian.gz] failed to install/upgrade: package libaudit1:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1867898/+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 1013597] Re: No default route for stateful DHCPv6
Apparently, I've done a stupid thing and forgot my Ubuntu Server in AWS
is Server 14. I've upgraded the ubuntu to 16.04 a few months back, but
forgot that it's supposed to be still Ubuntu Server 14.
So I followed the guide https://docs.aws.amazon.com/vpc/latest/userguide
/vpc-migrate-ipv6.html and followed the steps in Ubuntu Server 16. This
got me locked out of my own server, and no matter what I tried
(rebooting, assigned new private IP, tried pinging from other servers in
the same subnet), I still can't get in. SSH ends up in Operation timed
out. I've locked myself out.
I even tried creating an AMI and launch the image into a new instance
but still it won't work, maybe because the network interfaces files are
backed up into the image as well?
What can I do to regain access to my server?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1013597
Title:
No default route for stateful DHCPv6
Status in ifupdown package in Ubuntu:
Fix Released
Status in ifupdown source package in Precise:
Won't Fix
Bug description:
The default route cannot be provided via DHCPv6, it must be obtained
from router advertisements. However, when using the dhcp method for
inet6 in /etc/network/interfaces (e.g. "iface eth0 inet6 dhcp"), ifup
will set net.ipv6.conf..accept_ra=0, resulting in no default
route for IPv6. Instead, it should explicitly set accept_ra=1.
A workaround is to set it in a post-up script. However, Linux
apparently only sends router solicitations when the interface is
brought up, so if unsolicited RA:s are infrequent the host will be
without a default route until the next RA.
Another problem is that when bringing the interface down on dual-stack
hosts, there will be a long timeout. This is because bringing down
IPv4 also brings the interface link down, and afterwards dhclient
cannot release the DHCPv6 lease due to the link being down ("RTNETLINK
answers: Cannot assign requested address"). The workaround is to bring
the link back up before bringing IPv6 down.
So the workarounds (which obviously should not be needed) for a dual-
stack dhcp client look like this:
iface eth0 inet dhcp
iface eth0 inet6 dhcp
up sysctl net.ipv6.conf.$IFACE.accept_ra=1
pre-down ip link set dev $IFACE up
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1013597/+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 Looks good here: michael@metalmachine:~$ cat /sys/devices/virtual/dmi/id/bios_version N2HET46W (1.29 ) michael@metalmachine:~$ -- 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
[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)
The kernel 5.3.0-43 and 5.0.0-1043-oem-osp1 are ready, I just booted with these kernels, no errors so far. And with these kernels, no need to blacklist snd_soc_skl and snd_hda_intel. For looking for ucm based on bios version, please test this alsa-lib 1.1.9-0ubuntu1.2+testucm in https://launchpad.net/~hui.wang/+archive/ubuntu/audio-master. sudo add-apt-repository ppa:hui.wang/audio-master sudo apt-get update sudo apt install libasound2 reboot thx. -- 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
[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)
thanks @hui.wang, where can i find the 5.3.0-43 ? is it in the upstream repos ? -- 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
[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)
@Paolo,
Enable Pre-released updates (eoan-proposed) in the Software & Updates
sudo apt-get update
sudo apt install linux-image-unsigned-5.3.0-4 {pressing tab}, it will list -43
kernel.
--
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
[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)
Ok thanks @jui.wang, it's in the pre-released updates, because i saw that -42 had been promoted upstream between yesterday and today causing several issues, i had to manually downgrade to -40. -- 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
[Touch-packages] [Bug 621430] Re: [VIA VT1708S] Playback problem "Sound Skipping"
I encounter this bug on Ubuntu 19.10, both using internal sound card and
external Behringer UM2
Fixable by changing
load-module module-udev-detect
to
load-module module-udev-detect tshed=0
in file
/etc/pulse/default.pa
** Changed in: alsa-driver (Ubuntu)
Status: Expired => Confirmed
--
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/621430
Title:
[VIA VT1708S] Playback problem "Sound Skipping"
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
I am using the kernel backport from Maverick to Lucid. The summary of
this problem is that at seemingly random times the sound skips almost
like it does not have sufficient hardware to play it, which also
results in totem and flash video skipping. It corrects itself, however
does happen again at random times. I took debug information for this
report after such an occurrence.
Symptoms:
1.) The sound card pops and crackles during log in, and the log-in noise is
delayed.
2.) After login the sound functions normally and seems to have good latency.
3.) At random times the sound skips, and takes video playback with it,
however it does sort itself out.
Steps to recreate:
None, I am assuming anyone with this sound card would have this issue. My
hardware is a stock Asus k50ij laptop.
Notes:
Fedora 13 has a lot of problems with volume and playback with this chipset,
it seems Ubuntu does not. I also plan to do upstream testing on a mainline
kernel, though I have not done so yet.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-17.23~lucid1-generic 2.6.35.2
Uname: Linux 2.6.35-17-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: VT1708S Analog [VT1708S Analog]
Subdevices: 1/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: VT1708S Analog [VT1708S Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: virgil 1404 F pulseaudio
/dev/snd/pcmC0D0p: virgil 1404 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfe9f4000 irq 45'
Mixer name : 'VIA VT1708S'
Components : 'HDA:11060397,1043,0010'
Controls : 20
Simple ctrls : 13
Date: Fri Aug 20 17:49:06 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
PackageArchitecture: all
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
SelectedCard: 0 Intel HDA-Intel - HDA Intel
SourcePackage: alsa-driver
Symptom: audio
Title: [VIA VT1708S] Playback problem
dmi.bios.date: 12/04/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 217
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K50IJ
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.:bvr217:bd12/04/2009:svnASUSTeKComputerInc.:pnK50IJ:pvr1.0:rvnASUSTeKComputerInc.:rnK50IJ:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K50IJ
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/621430/+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)
Looks good so far; with kernel 5.3.0-43 from proposed and the libasound2 from your ppa. Microphone selection seems to be a bit iffy when I have a headset plugged into the headset jack (both are available to select, and the default seems to be the built-in one) but otherwise good. -- 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
[Touch-packages] [Bug 1867944] [NEW] Bluetooth A2DP audio device disconnect automatically after long time using (almost 49mins)
Public bug reported: After upgrading Ubuuntu 18.04 LTS to 20.04 , when I watching Netflix(by Firefox) videos with my bluetooth speaker (Lasonic i931BT), I found that almost every 49mins ,the video suddenly slow down and then sound stop transmitting to my speaker. It shouldn't happen. I check the pulseaudio mixer's output device. My speaker dissappeared. Only "Dummy Output " showed. (As the screenshot ) Everytime, I need go to bluetooth manager to disconnect the speaker, and wait it automatically connects again. Sometimes it works, but sometimes does not. I need to reboot to fix it (Power off the speak won't help ). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio-module-bluetooth 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-lowlatency 5.4.24 Uname: Linux 5.4.0-18-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 18 23:13:06 2020 InstallationDate: Installed on 2020-03-10 (8 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200130) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06TCOP dmi.board.asset.tag: Tag 12345 dmi.board.name: ZX Series dmi.board.vendor: COPELION INTERNATIONAL INC. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: COPELION INTERNATIONAL INC. dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06TCOP:bd10/14/2019:svnCOPELIONINTERNATIONALINC.:pnZXSeries:pvrNotApplicable:rvnCOPELIONINTERNATIONALINC.:rnZXSeries:rvrNotApplicable:cvnCOPELIONINTERNATIONALINC.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: ZX Series dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: COPELION INTERNATIONAL INC. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug buletooth focal ** Attachment added: "螢幕快照_2020-03-18_20-54-01.png" https://bugs.launchpad.net/bugs/1867944/+attachment/5338438/+files/%E8%9E%A2%E5%B9%95%E5%BF%AB%E7%85%A7_2020-03-18_20-54-01.png ** Description changed: - After upgrading Ubuuntu 18.04 LTS to 20.04 , when I watching Netflix + After upgrading Ubuuntu 18.04 LTS to 20.04 , when I am watching Netflix videos with my bluetooth speaker (Lasonic i931BT), I found that almost every 49mins ,the video suddenly slow down and then sound stop transmitting to my speaker. It shouldn't happen. I check the pulseaudio mixer's output device. My speaker dissappeared. Only "Dummy Output " showed. (As the screenshot ) Everytime, I need go to bluetooth manager to disconnect the speaker, and wait it automatically connects again. Sometimes it works, but sometimes does not. I need to reboot to fix it (Power off the speak won't help ). My System is Ubuntustudio 20.04 pulseaudio: 1:13.99.1-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio-module-bluetooth 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-lowlatency 5.4.24 Uname: Linux 5.4.0-18-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 18 23:13:06 2020 InstallationDate: Installed on 2020-03-10 (8 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200130) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06TCOP dmi.board.asset.tag: Tag 12345 dmi.board.name: ZX Series dmi.board.vendor: COPELION INTERNATIONAL INC. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: COPELION INTERNATIONAL INC. dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06TCOP:bd10/14/2019:svnCOPELIONINTERNATIONALINC.:pnZXSeries:pvrNotApplicable:rvnCOPELIONINTERNATIONALINC.:rnZXSeries:rvrNotApplicable:cvnCOPELIONINTERNATIONALINC.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: ZX Series dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: COPELION INTERNATIONAL INC. ** Description changed: - After upgrading Ubuuntu 18.04 LTS to 20.04 , when I am watching Netflix - videos with my bluetooth speaker (Lasonic i931BT), I found that almost - every 49mins ,the video suddenly slow down and then sound stop - transmitting to my speaker. It shouldn't happen. + After upgrading Ubuuntu 18.04 LTS to 20.04 , when I watching Netflix(by + Firefox) videos with my bluetooth speaker (Lasonic i931BT), I found + that almost every 49mins ,the video suddenly slow down and then sound + stop transmitting to my speaker. It shouldn't happen. I check the pulseaudio mixer's output device. My speaker dissappeared. Only "Dummy Output "
[Touch-packages] [Bug 1867949] [NEW] It's time to increase the default pid_max from 32768 to avoid PID wraparounds/collossions
Public bug reported: The kernel.pid_max sysctl defaults to 32768. This is a very historic limit to provide compatibility with ancient binaries. Moving on to the year 2020 multicore CPU:s for desktops, laptops and servers is the standard, and together with PID randomization wraparound happens rather quickly on many-core machines with lots of activity. Wraparounds in itself is not a big issue, but there are corner cases like scripts that checks if a PID is alive etc that run into trouble if another process has started using the PID it expects, scripts (erroneously) using PIDs for work/temporary files, etc. To avoid problems within the lifetime of Ubuntu Focal, it's time to increase kernel.pid_max by default in the distribution by including tuning in a file in /etc/sysctl.d/ Our suggestion is to ship the following tuning by default: # Make PID-rollover not happen as often. # Default is 32768 kernel.pid_max = 99 with the following motivation: 1) It achieves a 30-fold increase in the available number-space, reducing the likelihood of PID wraparound/collisions. 2) It only adds one digit to the PID, so it's still possible to remember a PID 3) Output in top, ps, etc is still nicely readable 3) We have used it for years on Ubuntu 14.04 and onwards, on 1000+ machines and with a wide array of commercial and scientific software without any issues. 4) One could argue that it is a preventive security measure, there are a lot of weirdly written scripts and software out there that behaves badly upon PID reuse/collissions. ** Affects: procps (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1867949 Title: It's time to increase the default pid_max from 32768 to avoid PID wraparounds/collossions Status in procps package in Ubuntu: New Bug description: The kernel.pid_max sysctl defaults to 32768. This is a very historic limit to provide compatibility with ancient binaries. Moving on to the year 2020 multicore CPU:s for desktops, laptops and servers is the standard, and together with PID randomization wraparound happens rather quickly on many-core machines with lots of activity. Wraparounds in itself is not a big issue, but there are corner cases like scripts that checks if a PID is alive etc that run into trouble if another process has started using the PID it expects, scripts (erroneously) using PIDs for work/temporary files, etc. To avoid problems within the lifetime of Ubuntu Focal, it's time to increase kernel.pid_max by default in the distribution by including tuning in a file in /etc/sysctl.d/ Our suggestion is to ship the following tuning by default: # Make PID-rollover not happen as often. # Default is 32768 kernel.pid_max = 99 with the following motivation: 1) It achieves a 30-fold increase in the available number-space, reducing the likelihood of PID wraparound/collisions. 2) It only adds one digit to the PID, so it's still possible to remember a PID 3) Output in top, ps, etc is still nicely readable 3) We have used it for years on Ubuntu 14.04 and onwards, on 1000+ machines and with a wide array of commercial and scientific software without any issues. 4) One could argue that it is a preventive security measure, there are a lot of weirdly written scripts and software out there that behaves badly upon PID reuse/collissions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1867949/+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 1867972] [NEW] [FFe] Please accept systemd 245-2ubuntu1 to Focal
Public bug reported: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd-repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1867972 Title: [FFe] Please accept systemd 245-2ubuntu1 to Focal Status in systemd package in Ubuntu: New Bug description: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd- repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+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 1867972] Re: [FFe] Please accept systemd 245-2ubuntu1 to Focal
** Description changed: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd-repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS + + There is one notable failing test, netplan.io's which is failing in the + release pocket, too. I'd like to have this passing, too, with systemd + 245 before in migrates to the release pocket. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1867972 Title: [FFe] Please accept systemd 245-2ubuntu1 to Focal Status in systemd package in Ubuntu: New Bug description: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd- repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS There is one notable failing test, netplan.io's which is failing in the release pocket, too. I'd like to have this passing, too, with systemd 245 before in migrates to the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+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 1867972] Re: [FFe] Please accept systemd 245-2ubuntu1 to Focal
Passing gpsd test: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ci-train-ppa-service-3801/focal/amd64/g/gpsd/20200318_155140_9068e@/log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1867972 Title: [FFe] Please accept systemd 245-2ubuntu1 to Focal Status in systemd package in Ubuntu: New Bug description: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd- repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS There is one notable failing test, netplan.io's which is failing in the release pocket, too. I'd like to have this passing, too, with systemd 245 before in migrates to the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+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 1867972] Re: [FFe] Please accept systemd 245-2ubuntu1 to Focal
systemd/armhf is pending. There are two notable regression tracked upstream: https://github.com/systemd/systemd/issues/15141 Update to systemd 245-2 breaks user login for usernames starting with a number https://github.com/systemd/systemd/issues/15070 [Arch Linux | systemd 245-1 & 245-2 | ZFS on root] System no longer boots - "Caught , dumped core as pid / Freezing execution" I have a fix for the first one and if the second one is reproducible on Ubuntu I can revert the change causing it. I'm seeking a tentative decision on accepting the new upstream release, assuming that the two regressions are also fixed in the first or in a follow-up upload. ** Bug watch added: github.com/systemd/systemd/issues #15141 https://github.com/systemd/systemd/issues/15141 ** Bug watch added: github.com/systemd/systemd/issues #15070 https://github.com/systemd/systemd/issues/15070 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1867972 Title: [FFe] Please accept systemd 245-2ubuntu1 to Focal Status in systemd package in Ubuntu: New Bug description: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd- repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS There is one notable failing test, netplan.io's which is failing in the release pocket, too. I'd like to have this passing, too, with systemd 245 before in migrates to the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+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 1867982] [NEW] unable to copy and paste login and password
Public bug reported: Select eg Google account when you have your user and password in clipboard. In the new account interface, cant paste into fields. Expected is paste. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Thu Mar 19 08:37:01 2020 InstallationDate: Installed on 2020-03-15 (2 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200312) SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1867982 Title: unable to copy and paste login and password Status in gnome-online-accounts package in Ubuntu: New Bug description: Select eg Google account when you have your user and password in clipboard. In the new account interface, cant paste into fields. Expected is paste. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Thu Mar 19 08:37:01 2020 InstallationDate: Installed on 2020-03-15 (2 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200312) SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1867982/+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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
** Changed in: boot-repair Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Committed Status in Boot-Repair: Fix Released Status in GNOME Terminal: New Status in HPLIP: New Status in Settings editor for LightDM GTK+ Greeter: New Status in OS-Uninstaller: Fix Committed Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Won't Fix Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: Invalid Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: Fix Released Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: * Main upstream discussion & fixes example to deal with wayland: https://bugzilla.gnome.org/show_bug.cgi?id=776437 * Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 CurrentDesktop: GNOME Date: Sun Aug 27 14:23:14 2017 InstallationDate: Installed on 2017-08-26 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) PackageArchitecture: all SourcePackage: backintime UpgradeStatus: No upgrade log prese
[Touch-packages] [Bug 1814611] Re: turning off "Send error reports to Canonical" prevents using ubuntu-bug
** Changed in: apport (Ubuntu Disco) Status: Triaged => Won't Fix ** Changed in: apport (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: apport (Ubuntu Bionic) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu Eoan) Status: Triaged => In Progress ** Changed in: apport (Ubuntu Eoan) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: turning off "Send error reports to Canonical" prevents using ubuntu- bug Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: In Progress Status in apport source package in Disco: Won't Fix Status in apport source package in Eoan: In Progress Bug description: Impact -- apport was modified (bug 1778497) to reduce the number of times people have to respond to crash reports, however the changes introduced a check to see if whoopsie is enabled. That check is done for any type of report, not just crashes, and subsequently people can not use ubuntu-bug to report bugs if whoopsie is disabled which is wrong as whoopsie is only for uploading crashes to the Error Tracker. Test Case - 1) On a system with Gnome installed use the Privacy control panel and set "Send error reports to Canonical" to Off 2) In a terminal run 'ubuntu-bug gnome-terminal' 3) Click "Send" and observe nothing happening (if something does happen confirm that whoopsie is disabled via 'systemctl is-enabled whoopsie' - there may be a bug in the control panel) Original Description Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1814611] Re: turning off "Send error reports to Canonical" prevents using ubuntu-bug
** Description changed: Impact -- apport was modified (bug 1778497) to reduce the number of times people have to respond to crash reports, however the changes introduced a check to see if whoopsie is enabled. That check is done for any type of report, not just crashes, and subsequently people can not use ubuntu-bug to report bugs if whoopsie is disabled which is wrong as whoopsie is only for uploading crashes to the Error Tracker. Test Case - 1) On a system with Gnome installed use the Privacy control panel and set "Send error reports to Canonical" to Off 2) In a terminal run 'ubuntu-bug gnome-terminal' 3) Click "Send" and observe nothing happening (if something does happen confirm that whoopsie is disabled via 'systemctl is-enabled whoopsie' - there may be a bug in the control panel) + + Regression Potential + + The fix is just setting the value of a variable to True instead of checking to see if whoopsie is enabled so there really isn't any. However, it could cause a regression if there's a typo in the line being changed. Original Description Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: turning off "Send error reports to Canonical" prevents using ubuntu- bug Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: In Progress Status in apport source package in Disco: Won't Fix Status in apport source package in Eoan: In Progress Bug description: Impact -- apport was modified (bug 1778497) to reduce the number of times people have to respond to crash reports, however the changes introduced a check to see if whoopsie is enabled. That check is done for any type of report, not just crashes, and subsequently people can not use ubuntu-bug to report bugs if whoopsie is disabled which is wrong as whoopsie is only for uploading crashes to the Error Tracker. Test Case - 1) On a system with Gnome installed use the Privacy control panel and set "Send error reports to Canonical" to Off 2) In a terminal run 'ubuntu-bug gnome-terminal' 3) Click "Send" and observe nothing happening (if something does happen confirm that whoopsie is disabled via 'systemctl is-enabled whoopsie' - there may be a bug in the control panel) Regression Potential The fix is just setting the value of a variable to True instead of checking to see if whoopsie is enabled so there really isn't any. However, it could cause a regression if there's a typo in the line being changed. Original Description Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1856376] Re: "Dummy Output" -- built-in audio not detected
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1856376 Title: "Dummy Output" -- built-in audio not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: I no longer seem to be getting audio on my laptop, and only "Dummy Output" shows up in the sound settings dialog. This sounds similar to LP #1781294 (including the same PCI device), though that seems to have been marked expired. alex@tapada:~$ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Lenovo Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 64, IRQ 159 Memory at 2ffb028000 (64-bit, non-prefetchable) [size=16K] Memory at 2ffb00 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl alex@tapada:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 23:38:35 2019 InstallationDate: Installed on 2019-08-31 (104 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T22:15:32.867642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856376/+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 1867972] Re: [FFe] Please accept systemd 245-2ubuntu1 to Focal
Can I get a binary debdiff of the packages attached to this FFe request? Is anything upstream using the new systemd-journald namespace feature by default? (It shouldn't) I don't see anything else in here that I would consider a blocker, provided it passes all the integration tests. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1867972 Title: [FFe] Please accept systemd 245-2ubuntu1 to Focal Status in systemd package in Ubuntu: Incomplete Bug description: Focal currently has 244.3-1ubuntu1. Upstream released 245 after the Focal Feature Freeze date, but updating to v245 will allow us to carry fewer patches in Focal and have the latest upstream fixes without cherry-picking the important ones. The proposed package is tested in Bileto and there are no unfixed regressions compared to the results of the latest tests. https://bileto.ubuntu.com/#/ticket/3801 The fixed gpsd upload invalidated the default excuses page, but it is still available at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-3801-excuses/2020-03-18_14:40:01/3801_focal_excuses.html The changelog is not final in the Bileto PPA, the final one is at: https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+ref/ubuntu-focal New notable upstream features, such as systemd-homed and systemd- repart are _not_ enabled in this upload. Please find the full NEWS file at: https://github.com/systemd/systemd/blob/v245/NEWS There is one notable failing test, netplan.io's which is failing in the release pocket, too. I'd like to have this passing, too, with systemd 245 before in migrates to the release pocket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867972/+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 1867987] [NEW] Two possible sounds output, when playing movie from youtube, output is set to wrong one automatically after 5 seconds [, Realtek ALC283, Black Headphone Out, Left]
You have been subscribed to a public bug: I start playing movie in Firefox and there is no sound coming out. I open sound configuration and change "Output Device" from "HDMI / DispalyPort - Built in Audio" to "Headphones - Built in Audio" Sound starts to play and then after 5 seconds it stops again. When I open sound configuration again, I can change "Output Device" again and sound plays again for 5 seconds and then it is turned off. I play sound using my display built in device connected through HDMI cable and also using audio cable. Sound is not working through HDMI cable. It is working using audio cable or headphones. My expectation is, when I set output device to be audio cable - it will not be changed to HDMI cable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lmlich 1369 F pulseaudio /dev/snd/pcmC1D0c: lmlich 1369 F...m pulseaudio /dev/snd/pcmC1D0p: lmlich 1369 F...m pulseaudio /dev/snd/controlC0: lmlich 1369 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 21:09:40 2020 InstallationDate: Installed on 2019-12-27 (82 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulseAudioLog: bře 18 21:02:14 lmquiet dbus-daemon[770]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.42' (uid=125 pid=979 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") bře 18 21:02:31 lmquiet systemd[972]: pulseaudio.service: Succeeded. bře 18 21:02:42 lmquiet systemd[972]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [, Realtek ALC283, Black Headphone Out, Left] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2016 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0354.2016.0120.0912 dmi.board.name: NUC5i3RYB dmi.board.vendor: Intel Corporation dmi.board.version: H41000-503 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0354.2016.0120.0912:bd01/20/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5i3RYB:rvrH41000-503:cvn:ct3:cvr: ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Two possible sounds output, when playing movie from youtube, output is set to wrong one automatically after 5 seconds [, Realtek ALC283, Black Headphone Out, Left] fails after a while https://bugs.launchpad.net/bugs/1867987 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- 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 1867987] Re: Two possible sounds output, when playing movie from youtube, output is set to wrong one automatically after 5 seconds [, Realtek ALC283, Black Headphone Out, Left] f
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/1867987 Title: Two possible sounds output, when playing movie from youtube, output is set to wrong one automatically after 5 seconds [, Realtek ALC283, Black Headphone Out, Left] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: I start playing movie in Firefox and there is no sound coming out. I open sound configuration and change "Output Device" from "HDMI / DispalyPort - Built in Audio" to "Headphones - Built in Audio" Sound starts to play and then after 5 seconds it stops again. When I open sound configuration again, I can change "Output Device" again and sound plays again for 5 seconds and then it is turned off. I play sound using my display built in device connected through HDMI cable and also using audio cable. Sound is not working through HDMI cable. It is working using audio cable or headphones. My expectation is, when I set output device to be audio cable - it will not be changed to HDMI cable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lmlich 1369 F pulseaudio /dev/snd/pcmC1D0c: lmlich 1369 F...m pulseaudio /dev/snd/pcmC1D0p: lmlich 1369 F...m pulseaudio /dev/snd/controlC0: lmlich 1369 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 21:09:40 2020 InstallationDate: Installed on 2019-12-27 (82 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulseAudioLog: bře 18 21:02:14 lmquiet dbus-daemon[770]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.42' (uid=125 pid=979 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") bře 18 21:02:31 lmquiet systemd[972]: pulseaudio.service: Succeeded. bře 18 21:02:42 lmquiet systemd[972]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [, Realtek ALC283, Black Headphone Out, Left] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2016 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0354.2016.0120.0912 dmi.board.name: NUC5i3RYB dmi.board.vendor: Intel Corporation dmi.board.version: H41000-503 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0354.2016.0120.0912:bd01/20/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5i3RYB:rvrH41000-503:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867987/+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 1868009] [NEW] Xorg high CPU usage and stuttering on ubuntu 20.04
Public bug reported: Hi there! I'm experiencing some stuttering on my machine after running updates today Mar 18th. The stuttering is for all visual effects including mouse movement, videos playing, dragging windows, animations and more. The stuttering is not affecting sound (as far as I can tell). The stuttering does not seem to happen on any regular interval, but does happen every 500-1000ms lasting for 50-100ms... just enough to be annoying enough to open a bug report :P I think that this issue is related to Xorg and the nvidia drivers doing something, but I'm not sure what exactly could be the issue. Here are some related links that led me to report this bug: - https://unix.stackexchange.com/questions/568173/nvidia-drivers-390-440-stuttering-ubuntu-20-04 - This led me to start thinking that the problem could be with Xorg or nvidia - https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1867352 - I'm experiencing all of these problems reported (including the Xorg.conf message), but I'm not getting a full freeze, I'm only getting stuttering) Steps I've taken: - Updated my system to latest packages on 20.04 - Installed [kwin-lowlatency](https://github.com/tildearrow/kwin-lowlatency) when I thought it might be related to the compositor - Toggled various compositor and Xorg settings - A few reboots here and there If I'm not including enough information please let me know what else to include and how to report it. Thanks! --Harrison System Information: ``` % sudo lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ``` ``` % sudo apt-cache policy nvidia-driver-440 nvidia-driver-440: Installed: 440.64-0ubuntu2 Candidate: 440.64-0ubuntu2 Version table: *** 440.64-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages 100 /var/lib/dpkg/status 440.64-0ubuntu0~0.20.04.2 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal/main amd64 Packages ``` ``` % ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1B06sv3842sd6393bc03sc00i00 vendor : NVIDIA Corporation model : GP102 [GeForce GTX 1080 Ti] driver : nvidia-driver-440 - distro non-free recommended driver : nvidia-driver-390 - distro non-free driver : nvidia-driver-435 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-3ubuntu1) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Mar 18 20:11:20 2020 DistUpgraded: 2020-02-29 17:19:20,722 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-14-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6393] InstallationDate: Installed on 2014-12-27 (1908 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: MSI MS-7915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=83fc3053-1a71-4a02-9f50-48dbd4e1b9c3 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-02-29 (18 days ago) dmi.bios.date: 04/22/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97 MPOWER (MS-7915) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.0:bd04/22/2014:svnMSI:pnMS-7915:pvr1.0:rvnMSI:rnZ97MPOWER(MS-7915):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7915 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.100-4 v
[Touch-packages] [Bug 1689833] Re: OpenVPN server does not start properly on boot
** Changed in: openvpn (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1689833 Title: OpenVPN server does not start properly on boot Status in openvpn package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Bug description: OpenVPN intermittently fails to bind to local address during boot on Ubuntu Server 16.04.2 LTS. Sometimes it succeeds, sometimes it does not. /var/log/openvpn.log Wed May 10 15:42:02 2017 OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Feb 2 2016 Wed May 10 15:42:02 2017 library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08 Wed May 10 15:42:02 2017 Diffie-Hellman initialized with 2048 bit key Wed May 10 15:42:02 2017 Control Channel Authentication: using './easy-rsa/keys/ta.key' as a OpenVPN static key file Wed May 10 15:42:02 2017 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed May 10 15:42:02 2017 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed May 10 15:42:02 2017 Socket Buffers: R=[212992->212992] S=[212992->212992] Wed May 10 15:42:02 2017 TCP/UDP: Socket bind failed on local address [AF_INET]192.168.4.254:1194: Cannot assign requested address Wed May 10 15:42:02 2017 Exiting due to fatal error In case it does not start, running 'sudo service openvpn start' fixes that problem. /var/log/openvpn.log Wed May 10 15:42:43 2017 OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Feb 2 2016 Wed May 10 15:42:43 2017 library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08 Wed May 10 15:42:43 2017 Diffie-Hellman initialized with 2048 bit key Wed May 10 15:42:43 2017 Control Channel Authentication: using './easy-rsa/keys/ta.key' as a OpenVPN static key file Wed May 10 15:42:43 2017 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed May 10 15:42:43 2017 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed May 10 15:42:43 2017 Socket Buffers: R=[212992->212992] S=[212992->212992] Wed May 10 15:42:43 2017 ROUTE_GATEWAY 192.168.4.1/255.255.255.0 IFACE=ens4 HWADDR=52:54:00:f0:26:0c Wed May 10 15:42:43 2017 TUN/TAP device tun0 opened Wed May 10 15:42:43 2017 TUN/TAP TX queue length set to 100 Wed May 10 15:42:43 2017 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0 Wed May 10 15:42:43 2017 /sbin/ip link set dev tun0 up mtu 1500 Wed May 10 15:42:43 2017 /sbin/ip addr add dev tun0 local 172.16.1.1 peer 172.16.1.2 Wed May 10 15:42:43 2017 /sbin/ip route add 172.16.1.0/24 via 172.16.1.2 Wed May 10 15:42:43 2017 GID set to nogroup Wed May 10 15:42:43 2017 UID set to nobody Wed May 10 15:42:43 2017 UDPv4 link local (bound): [AF_INET]192.168.4.254:1194 Wed May 10 15:42:43 2017 UDPv4 link remote: [undef] Wed May 10 15:42:43 2017 MULTI: multi_init called, r=256 v=256 Wed May 10 15:42:43 2017 IFCONFIG POOL: base=172.16.1.4 size=62, ipv6=0 Wed May 10 15:42:43 2017 IFCONFIG POOL LIST Wed May 10 15:42:43 2017 Initialization Sequence Completed My guess is that systemd starts OpenVPN too early before the network is brought up sufficiently. Running 'sudo systemctl edit --full openvpn' and adding 'Wants=network-online.target' does not change that behaviour. user@server:~$ sudo systemd-analyze critical-chain graphical.target @2.160s └─multi-user.target @2.159s └─ntp.service @2.054s +104ms └─remote-fs.target @2.052s └─remote-fs-pre.target @2.052s └─open-iscsi.service @1.993s +57ms └─iscsid.service @1.942s +47ms └─network-online.target @1.941s └─network.target @1.929s └─networking.service @1.793s +134ms └─apparmor.service @1.140s +395ms └─local-fs.target @1.140s └─local-fs-pre.target @1.139s └─lvm2-monitor.service @602ms +536ms └─lvm2-lvmetad.service @773ms └─systemd-journald.socket @574ms └─-.slice @500ms The boot time is quite short. Clean install with the additional packages ntp and openssh-server. This happens both on bare metal and as a Virtual Machine (KVM) as well. /etc/openvpn/server.conf local 192.168.4.254 port 1194 proto udp dev tun ca ./easy-rsa/keys/ca.crt cert ./easy-rsa/keys/crt.crt key ./easy-rsa/keys/key.key dh ./easy-rsa/keys/dh2048.pem tls-auth ./easy-rsa/keys/ta.key 0 server 172.16.1.0 255.255.255.0 ifconfig-pool-persist ipp.txt push "route 192.168.0.0 255.255.255.0" push "route 192.168.4.0 255.255
[Touch-packages] [Bug 1866303] Re: slapd crash with pwdAccountLockedTime and stacked overlays
We're no longer looking at backporting fixes for disco. This looks suitable for SRU so the other proposed series tasks are valid, and this is already in the server-next queue. ** Changed in: openldap (Ubuntu Disco) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1866303 Title: slapd crash with pwdAccountLockedTime and stacked overlays Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: New Status in openldap source package in Bionic: New Status in openldap source package in Disco: Won't Fix Status in openldap source package in Eoan: New Status in openldap package in Debian: Unknown Bug description: Hello, Please merge openldap 2.4.49+dfsg-2 from Debian unstable to fix an issue in the ppolicy overlay that can crash slapd. Please also consider SRUing the patch after it has had some testing time. Upstream: https://openldap.org/its/?findid=9171 Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953150 The ingredients for the crash are: 1: ppolicy overlay configured with pwdLockout: TRUE 2. smbk5pwd overlay stacked after ppolicy 3. an account locked out via pwdAccountLockedTime 4. a client binding to the locked-out account and also requesting the ppolicy control The buggy code is not as specific as the above steps, so I suspect there are probably other configurations or steps that can trigger the same crash. I will attach my test script and data for reproducing the crash. Expected output (last lines): [ ok ] Starting OpenLDAP: slapd. slapd running ldap_bind: Invalid credentials (49) slapd running Actual output (last lines): [ ok ] Starting OpenLDAP: slapd. slapd running ldap_bind: Invalid credentials (49) slapd dead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1866303/+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 1867944] Re: Bluetooth A2DP audio device disconnect automatically after long time using (almost 49mins)
Please run these commands before and again after the bug occurs: dmesg > dmesg.txt lsusb > lsusb.txt rfkill > rfkill.txt and attach both sets of text files. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1867944 Title: Bluetooth A2DP audio device disconnect automatically after long time using (almost 49mins) Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading Ubuuntu 18.04 LTS to 20.04 , when I watching Netflix(by Firefox) videos with my bluetooth speaker (Lasonic i931BT), I found that almost every 49mins ,the video suddenly slow down and then sound stop transmitting to my speaker. It shouldn't happen. I check the pulseaudio mixer's output device. My speaker dissappeared. Only "Dummy Output " showed. (As the screenshot ) Everytime, I need go to bluetooth manager to disconnect the speaker, and wait it automatically connects again. Sometimes it works, but sometimes does not. I need to reboot to fix it (Power off the speak won't help ). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio-module-bluetooth 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-lowlatency 5.4.24 Uname: Linux 5.4.0-18-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 18 23:13:06 2020 InstallationDate: Installed on 2020-03-10 (8 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200130) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06TCOP dmi.board.asset.tag: Tag 12345 dmi.board.name: ZX Series dmi.board.vendor: COPELION INTERNATIONAL INC. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: COPELION INTERNATIONAL INC. dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06TCOP:bd10/14/2019:svnCOPELIONINTERNATIONALINC.:pnZXSeries:pvrNotApplicable:rvnCOPELIONINTERNATIONALINC.:rnZXSeries:rvrNotApplicable:cvnCOPELIONINTERNATIONALINC.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: ZX Series dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: COPELION INTERNATIONAL INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1867944/+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 1868009] Re: Xorg high CPU usage and stuttering on ubuntu 20.04
The nvidia driver lives inside the Xorg process so I don't think this is Xorg's fault but is Nvidia's. Particularly since you've said "Disabling the nvidia driver (going back to an opensource driver) removed this spiking". ** Tags added: nvidia ** Tags added: performance ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440 (Ubuntu) ** Summary changed: - Xorg high CPU usage and stuttering on ubuntu 20.04 + Xorg high CPU usage and stuttering with the Nvidia driver -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1868009 Title: Xorg high CPU usage and stuttering with the Nvidia driver Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: Hi there! I'm experiencing some stuttering on my machine after running updates today Mar 18th. The stuttering is for all visual effects including mouse movement, videos playing, dragging windows, animations and more. The stuttering is not affecting sound (as far as I can tell). The stuttering does not seem to happen on any regular interval, but does happen every 500-1000ms lasting for 50-100ms... just enough to be annoying enough to open a bug report :P I think that this issue is related to Xorg and the nvidia drivers doing something, but I'm not sure what exactly could be the issue. Here are some related links that led me to report this bug: - https://unix.stackexchange.com/questions/568173/nvidia-drivers-390-440-stuttering-ubuntu-20-04 - This led me to start thinking that the problem could be with Xorg or nvidia - https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1867352 - I'm experiencing all of these problems reported (including the Xorg.conf message), but I'm not getting a full freeze, I'm only getting stuttering) Steps I've taken: - Updated my system to latest packages on 20.04 - Installed [kwin-lowlatency](https://github.com/tildearrow/kwin-lowlatency) when I thought it might be related to the compositor - Toggled various compositor and Xorg settings - A few reboots here and there If I'm not including enough information please let me know what else to include and how to report it. Thanks! --Harrison System Information: ``` % sudo lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ``` ``` % sudo apt-cache policy nvidia-driver-440 nvidia-driver-440: Installed: 440.64-0ubuntu2 Candidate: 440.64-0ubuntu2 Version table: *** 440.64-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages 100 /var/lib/dpkg/status 440.64-0ubuntu0~0.20.04.2 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal/main amd64 Packages ``` ``` % ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1B06sv3842sd6393bc03sc00i00 vendor : NVIDIA Corporation model : GP102 [GeForce GTX 1080 Ti] driver : nvidia-driver-440 - distro non-free recommended driver : nvidia-driver-390 - distro non-free driver : nvidia-driver-435 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-3ubuntu1) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Mar 18 20:11:20 2020 DistUpgraded: 2020-02-29 17:19:20,722 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-14-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6393] InstallationDate: Installed on 2014-12-27 (1908 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (
[Touch-packages] [Bug 1746582] Re: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Thanks to Yevhen (yevhen.b) I fixed it by sudo apt purge lvm2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1746582 Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: Confirmed Bug description: I *think* this was from trying to install python-guestfs ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 Date: Wed Jan 31 09:56:36 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-06-28 (217 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-01-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1746582/+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 1310121] Re: headphones working while speakers not working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1310121 Title: headphones working while speakers not working Status in pulseaudio package in Ubuntu: Confirmed Bug description: to change kernel does not help, I tried 3.11 kernel, 3.8 kernel, 3.5 kernel. Testing the left and right channel work for headphones output , a minijack is connected to the ampli. Removing the jack the notebook ( system76 notebook) is like mute. I have tried to use alsamixer , all the volume are ok. application seem to output their audios... but nothing to through the speakers. thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: francesca 2074 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 20 00:23:09 2014 InstallationDate: Installed on 2012-10-18 (548 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: pulseaudio UpgradeStatus: Upgraded to trusty on 2014-04-19 (0 days ago) dmi.bios.date: 09/27/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Gazelle Professional dmi.board.vendor: System76, Inc. dmi.board.version: gazp8 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/27/2012:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp8:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp8:cvnNoEnclosure:ct9:cvrN/A: dmi.product.name: Gazelle Professional dmi.product.version: gazp8 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1310121/+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 1647285] Re: SSL trust not system-wide
nss should have everything on focal ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Changed in: nss (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in firefox package in Ubuntu: New Status in nss package in Ubuntu: Fix Released Status in p11-kit package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+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 1647285] Re: SSL trust not system-wide
p11-kit too ** Changed in: p11-kit (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in firefox package in Ubuntu: New Status in nss package in Ubuntu: Fix Released Status in p11-kit package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+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 1310121] Re: headphones working while speakers not working
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Won't Fix -- 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/1310121 Title: headphones working while speakers not working Status in pulseaudio package in Ubuntu: Won't Fix Bug description: to change kernel does not help, I tried 3.11 kernel, 3.8 kernel, 3.5 kernel. Testing the left and right channel work for headphones output , a minijack is connected to the ampli. Removing the jack the notebook ( system76 notebook) is like mute. I have tried to use alsamixer , all the volume are ok. application seem to output their audios... but nothing to through the speakers. thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: francesca 2074 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 20 00:23:09 2014 InstallationDate: Installed on 2012-10-18 (548 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: pulseaudio UpgradeStatus: Upgraded to trusty on 2014-04-19 (0 days ago) dmi.bios.date: 09/27/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Gazelle Professional dmi.board.vendor: System76, Inc. dmi.board.version: gazp8 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/27/2012:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp8:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp8:cvnNoEnclosure:ct9:cvrN/A: dmi.product.name: Gazelle Professional dmi.product.version: gazp8 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1310121/+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 1310121] Re: headphones working while speakers not working
Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic. Speakers are muted at boot and remains muted after plug and unplug headphones. Only can be activated from alsamixer, unmuting the headphones while the headphones are unplugged. Both speakers and headphones muting seems to be controlled in the Headphones area using alsamixer. I've "solved" it in a not very good way, keeping automute activated in alsamixer, modifiyng /usr/share/pulseaudio/alsa-mixer/paths/analog- output-headphones.conf and executing a bash script at boot (sonido.sh) with the command "amixer set -c 0 Headphone unmute 100%" in order to prevent the speakers being muted. Tomorrow I'm going to send more details and try to reproduce the same bug using Xubuntu 18.04. System: Host: ROI-TOSHIBA-NB250 Kernel: 5.3.0-42-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Xfce 4.14.1 tk: Gtk 3.22.30 wm: xfwm4 dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: TOSHIBA product: TOSHIBA NB250 v: PLL2XE-005003AS serial: Chassis: type: 10 serial: Mobo: TOSHIBA model: PAV10 DDR2 v: 1.00 serial: BIOS: TOSHIBA v: 1.60 date: 07/30/2010 CPU: Topology: Single Core model: Intel Atom N455 bits: 64 type: MT arch: Bonnell rev: A L2 cache: 512 KiB flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 6649 Speed: 997 MHz min/max: 1000/1667 MHz Core speeds (MHz): 1: 997 2: 997 Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Toshiba America Info Systems driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8 Sound Server: ALSA v: k5.3.0-42-generic Repos: No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http://mirrors.evowise.com/linuxmint/packages tricia main upstream import backport 2: deb http://es-mirrors.evowise.com/ubuntu bionic main restricted universe multiverse 3: deb http://es-mirrors.evowise.com/ubuntu bionic-updates main restricted universe multiverse 4: deb http://es-mirrors.evowise.com/ubuntu bionic-backports main restricted universe multiverse 5: deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse 6: deb http://archive.canonical.com/ubuntu/ bionic partner Info: Processes: 160 Uptime: 40m Memory: 1.93 GiB used: 927.8 MiB (46.9%) Init: systemd v: 237 runlevel: 5 Compilers: gcc: 7.5.0 alt: 7 Shell: bash v: 4.4.20 running in: xfce4-terminal inxi: 3.0.32 ** Attachment added: "analog-output-headphones.conf" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1310121/+attachment/5338626/+files/analog-output-headphones.conf -- 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/1310121 Title: headphones working while speakers not working Status in pulseaudio package in Ubuntu: Won't Fix Bug description: to change kernel does not help, I tried 3.11 kernel, 3.8 kernel, 3.5 kernel. Testing the left and right channel work for headphones output , a minijack is connected to the ampli. Removing the jack the notebook ( system76 notebook) is like mute. I have tried to use alsamixer , all the volume are ok. application seem to output their audios... but nothing to through the speakers. thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: francesca 2074 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 20 00:23:09 2014 InstallationDate: Installed on 2012-10-18 (548 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: pulseaudio UpgradeStatus: Upgraded to trusty on 2014-04-19 (0 days ago) dmi.bios.date: 09/27/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Gazelle Professional dmi.board.vendor: System76, Inc. dmi.board.version: gazp8 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/27/2012:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp8:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp8:cvnNoEnclosure:ct9:cvrN/A: dmi.product.name: Gazelle Professional dmi.product.version: gazp8 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1310121/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsu
[Touch-packages] [Bug 1863874] Re: Backport GetFB2 ioctl
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1863874 Title: Backport GetFB2 ioctl Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: We need this in order to re-enable intel CCS compression, which was originally disabled in mesa to fix this bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1753776 GetFB2 was recently added to drm-misc, and should get upstream in 5.7, but would be best to have it in focal and unstable kernel so that the userland parts can be added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1863874/+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 1310121] Re: headphones working while speakers not working
There are some issues reported to pulseaudio manteiners. Not the same but related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540 ** Bug watch added: PulseAudio #256 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256 ** Bug watch added: PulseAudio #540 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540 -- 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/1310121 Title: headphones working while speakers not working Status in pulseaudio package in Ubuntu: Won't Fix Bug description: to change kernel does not help, I tried 3.11 kernel, 3.8 kernel, 3.5 kernel. Testing the left and right channel work for headphones output , a minijack is connected to the ampli. Removing the jack the notebook ( system76 notebook) is like mute. I have tried to use alsamixer , all the volume are ok. application seem to output their audios... but nothing to through the speakers. thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: francesca 2074 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 20 00:23:09 2014 InstallationDate: Installed on 2012-10-18 (548 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: pulseaudio UpgradeStatus: Upgraded to trusty on 2014-04-19 (0 days ago) dmi.bios.date: 09/27/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Gazelle Professional dmi.board.vendor: System76, Inc. dmi.board.version: gazp8 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/27/2012:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp8:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp8:cvnNoEnclosure:ct9:cvrN/A: dmi.product.name: Gazelle Professional dmi.product.version: gazp8 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1310121/+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 1310121] Re: headphones working while speakers not working
Everyone please report your own new bugs by running: ubuntu-bug pulseaudio This bug is closed. ** Bug watch removed: PulseAudio #256 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256 ** Bug watch removed: PulseAudio #540 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540 -- 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/1310121 Title: headphones working while speakers not working Status in pulseaudio package in Ubuntu: Won't Fix Bug description: to change kernel does not help, I tried 3.11 kernel, 3.8 kernel, 3.5 kernel. Testing the left and right channel work for headphones output , a minijack is connected to the ampli. Removing the jack the notebook ( system76 notebook) is like mute. I have tried to use alsamixer , all the volume are ok. application seem to output their audios... but nothing to through the speakers. thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: francesca 2074 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 20 00:23:09 2014 InstallationDate: Installed on 2012-10-18 (548 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: pulseaudio UpgradeStatus: Upgraded to trusty on 2014-04-19 (0 days ago) dmi.bios.date: 09/27/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Gazelle Professional dmi.board.vendor: System76, Inc. dmi.board.version: gazp8 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/27/2012:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp8:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp8:cvnNoEnclosure:ct9:cvrN/A: dmi.product.name: Gazelle Professional dmi.product.version: gazp8 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1310121/+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 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px
Actually the proper solution to comment #28 would be to change to overlay scrollbars, which is already covered by bug 1451924. It's still a different bug to this one, but if implemented it would close this bug nicely. If we just wanted to work on this bug without doing bug 1451924 then that would involve replacing the white background with the actual terminal background colour. Kind of similar to scrollbar-background- theming.patch but in a way that would actually be upstreamable... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1691678 Title: Scrollbars escape the bottom and right side of the Terminal window by 1px Status in GNOME Terminal: Fix Released Status in gnome-terminal package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: New Status in yaru-theme package in Ubuntu: Fix Released Bug description: Ubuntu's orange overlay scrollbars escape the bottom of the window during resizing. To reproduce try gnome-shell on artful using the Ambiance theme. Open a Terminal window and resize it vertically, quickly. Notice the bottom of the overlay scrollbar overruns the bottom of the window. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:28:33 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1691678/+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
