[Touch-packages] [Bug 1894172] [NEW] isc-dhcp-server using wrong env variable for INTERFACES
Public bug reported: When checking isc-dhcp-server unit file I saw isc-dhcp-server is being started by: ConditionPathExists=/etc/default/isc-dhcp-server ConditionPathExists=|/etc/ltsp/dhcpd.conf ConditionPathExists=|/etc/dhcp/dhcpd.conf [Service] EnvironmentFile=/etc/default/isc-dhcp-server RuntimeDirectory=dhcp-server # The leases files need to be root:dhcpd even when dropping privileges ExecStart=/bin/sh -ec '\ CONFIG_FILE=/etc/dhcp/dhcpd.conf; \ if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; fi; \ [ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \ chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \ chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \ exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACES' But the /etc/default/isc-dhcp-server file sets $INTERFACESv4 and $INTERFACESv6. This has only been working because cmdline sets -4 and subnet declaration in dhcpd.conf file makes dhcp-server to bind to the correct interfaces, as it looks like. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: Triaged ** Affects: isc-dhcp (Ubuntu Bionic) Importance: Undecided Status: Triaged ** Affects: isc-dhcp (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Tags: bitesize server-next ** Changed in: isc-dhcp (Ubuntu) Status: New => Triaged ** Also affects: isc-dhcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: isc-dhcp (Ubuntu Groovy) Importance: Undecided Status: Triaged ** Also affects: isc-dhcp (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: isc-dhcp (Ubuntu Focal) Status: New => Confirmed ** Changed in: isc-dhcp (Ubuntu Bionic) Status: New => Triaged ** No longer affects: isc-dhcp (Ubuntu Groovy) ** Tags added: server-next ** Tags added: bitesize -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1894172 Title: isc-dhcp-server using wrong env variable for INTERFACES Status in isc-dhcp package in Ubuntu: Triaged Status in isc-dhcp source package in Bionic: Triaged Status in isc-dhcp source package in Focal: Confirmed Bug description: When checking isc-dhcp-server unit file I saw isc-dhcp-server is being started by: ConditionPathExists=/etc/default/isc-dhcp-server ConditionPathExists=|/etc/ltsp/dhcpd.conf ConditionPathExists=|/etc/dhcp/dhcpd.conf [Service] EnvironmentFile=/etc/default/isc-dhcp-server RuntimeDirectory=dhcp-server # The leases files need to be root:dhcpd even when dropping privileges ExecStart=/bin/sh -ec '\ CONFIG_FILE=/etc/dhcp/dhcpd.conf; \ if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; fi; \ [ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \ chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \ chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \ exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf $CONFIG_FILE $INTERFACES' But the /etc/default/isc-dhcp-server file sets $INTERFACESv4 and $INTERFACESv6. This has only been working because cmdline sets -4 and subnet declaration in dhcpd.conf file makes dhcp-server to bind to the correct interfaces, as it looks like. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1894172/+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 1894155] Re: libpam-moudles update failure
Since your debconf database was locked but dpkg and apt were not, this is not a bug in the pam package; and since you say you've killed the process that held the lock, there's not much more debugging we can do. Therefore, closing this bug report as invalid. ** Changed in: pam (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1894155 Title: libpam-moudles update failure Status in pam package in Ubuntu: Invalid Bug description: today ubuntu software updater pushed a update, but it failed when update libpam-modules from 1.3.1-5ubuntu4.1 to 1.3.1-5ubuntu4.1. after that i tried to update this package manually, here is the error reported. debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable (Reading database ... 187403 files and directories currently installed.) Preparing to unpack .../libpam-modules_1.3.1-5ubuntu4.1_amd64.deb ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another p rocess: Resource temporarily unavailable dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.3.1-5ubu ntu4.1_amd64.deb (--unpack): new libpam-modules:amd64 package pre-installation script subprocess returned er ror exit status 1 Errors were encountered while processing: /var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) seems caused by debconf, similar to the bug below: https://bugs.launchpad.net/ubuntu/+source/libgtk3-perl/+bug/1871960 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 17:34:21 2020 InstallationDate: Installed on 2020-08-18 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1894155/+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 1894075] Re: sound is absent ubuntu 20.04
Try resetting pulseaudio's user settings and restarting pulseaudio: rm -r ~/.config/pulse* pulseaudio -k -- 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/1894075 Title: sound is absent ubuntu 20.04 Status in pulseaudio package in Ubuntu: New Bug description: Could You help me with sound restore in Ubuntu 20.04 LTS after upgrade from Ubuntu 19.10? Sincerely N.E. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsystemd0:amd64 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.1 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:123:2243292:2020-09-02 17:38:34.836466312 +0300:2020-09-02 17:38:35.836466312 +0300:/var/crash/_usr_lib_firefox_crashreporter.1000.crash 640:0:123:81354:2020-09-02 14:42:34.015875816 +0300:2020-09-02 14:42:35.015875816 +0300:/var/crash/systemd.0.crash 640:0:123:81374:2020-09-02 14:42:33.987879276 +0300:2020-09-02 14:42:34.987879276 +0300:/var/crash/libsystemd0:amd64.0.crash 640:0:123:81374:2020-09-02 14:42:35.003877338 +0300:2020-09-02 14:42:34.991878838 +0300:/var/crash/systemd-timesyncd.0.crash Date: Wed Sep 2 14:42:34 2020 DpkgTerminalLog: dpkg: error processing package libsystemd0:amd64 (--configure): package libsystemd0:amd64 is already installed and configured ErrorMessage: package libsystemd0:amd64 is already installed and configured InstallationDate: Installed on 2019-09-27 (341 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: dpkg Title: package libsystemd0:amd64 245.4-4ubuntu3.2 failed to install/upgrade: package libsystemd0:amd64 is already installed and configured UpgradeStatus: Upgraded to focal on 2020-06-19 (75 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolae1554 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-01 (368 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190709) Package: pulseaudio 1:13.99.1-1ubuntu3.5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal wayland-session Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 6SCN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6SCN35WW:bd06/21/2018:svnLENOVO:pn81AX:pvrLenovoV330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV330-15IKB: dmi.product.family: V330-15IKB dmi.product.name: 81AX dmi.product.sku: LENOVO_MT_81AX_BU_idea_FM_V330-15IKB dmi.product.version: Lenovo V330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894075/+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 1894155] Re: libpam-moudles update failure
$ sudo lsof /var/cache/debconf/config.dat $ sudo kill [pid listed above] then update is successful. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1894155 Title: libpam-moudles update failure Status in pam package in Ubuntu: New Bug description: today ubuntu software updater pushed a update, but it failed when update libpam-modules from 1.3.1-5ubuntu4.1 to 1.3.1-5ubuntu4.1. after that i tried to update this package manually, here is the error reported. debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable (Reading database ... 187403 files and directories currently installed.) Preparing to unpack .../libpam-modules_1.3.1-5ubuntu4.1_amd64.deb ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another p rocess: Resource temporarily unavailable dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.3.1-5ubu ntu4.1_amd64.deb (--unpack): new libpam-modules:amd64 package pre-installation script subprocess returned er ror exit status 1 Errors were encountered while processing: /var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) seems caused by debconf, similar to the bug below: https://bugs.launchpad.net/ubuntu/+source/libgtk3-perl/+bug/1871960 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 17:34:21 2020 InstallationDate: Installed on 2020-08-18 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1894155/+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 1894075] Re: sound is absent ubuntu 20.04
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- 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/1894075 Title: sound is absent ubuntu 20.04 Status in pulseaudio package in Ubuntu: New Bug description: Could You help me with sound restore in Ubuntu 20.04 LTS after upgrade from Ubuntu 19.10? Sincerely N.E. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsystemd0:amd64 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.1 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:123:2243292:2020-09-02 17:38:34.836466312 +0300:2020-09-02 17:38:35.836466312 +0300:/var/crash/_usr_lib_firefox_crashreporter.1000.crash 640:0:123:81354:2020-09-02 14:42:34.015875816 +0300:2020-09-02 14:42:35.015875816 +0300:/var/crash/systemd.0.crash 640:0:123:81374:2020-09-02 14:42:33.987879276 +0300:2020-09-02 14:42:34.987879276 +0300:/var/crash/libsystemd0:amd64.0.crash 640:0:123:81374:2020-09-02 14:42:35.003877338 +0300:2020-09-02 14:42:34.991878838 +0300:/var/crash/systemd-timesyncd.0.crash Date: Wed Sep 2 14:42:34 2020 DpkgTerminalLog: dpkg: error processing package libsystemd0:amd64 (--configure): package libsystemd0:amd64 is already installed and configured ErrorMessage: package libsystemd0:amd64 is already installed and configured InstallationDate: Installed on 2019-09-27 (341 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: dpkg Title: package libsystemd0:amd64 245.4-4ubuntu3.2 failed to install/upgrade: package libsystemd0:amd64 is already installed and configured UpgradeStatus: Upgraded to focal on 2020-06-19 (75 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolae1554 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-01 (368 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190709) Package: pulseaudio 1:13.99.1-1ubuntu3.5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal wayland-session Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 6SCN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6SCN35WW:bd06/21/2018:svnLENOVO:pn81AX:pvrLenovoV330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV330-15IKB: dmi.product.family: V330-15IKB dmi.product.name: 81AX dmi.product.sku: LENOVO_MT_81AX_BU_idea_FM_V330-15IKB dmi.product.version: Lenovo V330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894075/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
This bug was fixed in the package linux - 5.8.0-18.19
---
linux (5.8.0-18.19) groovy; urgency=medium
* groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)
* Packaging resync (LP: #1786013)
- update dkms package versions
* Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr:
[Touch-packages] [Bug 1891224] Re: [Hyper-V] VSS and File Copy daemons intermittently fails to start
This bug was fixed in the package linux - 5.8.0-18.19
---
linux (5.8.0-18.19) groovy; urgency=medium
* groovy/linux: 5.8.0-18.19 -proposed tracker (LP: #1893047)
* Packaging resync (LP: #1786013)
- update dkms package versions
* Groovy update: v5.8.4 upstream stable release (LP: #1893048)
- drm/vgem: Replace opencoded version of drm_gem_dumb_map_offset()
- drm/panel-simple: Fix inverted V/H SYNC for Frida FRD350H54004 panel
- drm/ast: Remove unused code paths for AST 1180
- drm/ast: Initialize DRAM type before posting GPU
- khugepaged: adjust VM_BUG_ON_MM() in __khugepaged_enter()
- ALSA: hda: avoid reset of sdo_limit
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Flex Book
- ALSA: hda/realtek: Add quirk for Samsung Galaxy Book Ion
- can: j1939: transport: j1939_session_tx_dat(): fix use-after-free read in
j1939_tp_txtimer()
- can: j1939: socket: j1939_sk_bind(): make sure ml_priv is allocated
- spi: Prevent adding devices below an unregistering controller
- io_uring: find and cancel head link async work on files exit
- mm/vunmap: add cond_resched() in vunmap_pmd_range
- romfs: fix uninitialized memory leak in romfs_dev_read()
- kernel/relay.c: fix memleak on destroy relay channel
- uprobes: __replace_page() avoid BUG in munlock_vma_page()
- squashfs: avoid bio_alloc() failure with 1Mbyte blocks
- mm: include CMA pages in lowmem_reserve at boot
- mm, page_alloc: fix core hung in free_pcppages_bulk()
- ASoC: amd: renoir: restore two more registers during resume
- RDMA/hfi1: Correct an interlock issue for TID RDMA WRITE request
- opp: Enable resources again if they were disabled earlier
- opp: Put opp table in dev_pm_opp_set_rate() for empty tables
- opp: Put opp table in dev_pm_opp_set_rate() if _set_opp_bw() fails
- ext4: do not block RWF_NOWAIT dio write on unallocated space
- ext4: fix checking of directory entry validity for inline directories
- jbd2: add the missing unlock_buffer() in the error path of
jbd2_write_superblock()
- scsi: zfcp: Fix use-after-free in request timeout handlers
- selftests: kvm: Use a shorter encoding to clear RAX
- s390/pci: fix zpci_bus_link_virtfn()
- s390/pci: re-introduce zpci_remove_device()
- s390/pci: fix PF/VF linking on hot plug
- s390/pci: ignore stale configuration request event
- mm/memory.c: skip spurious TLB flush for retried page fault
- drm: amdgpu: Use the correct size when allocating memory
- drm/amdgpu/display: use GFP_ATOMIC in dcn20_validate_bandwidth_internal
- drm/amd/display: Fix incorrect backlight register offset for DCN
- drm/amd/display: Fix EDID parsing after resume from suspend
- drm/amd/display: Blank stream before destroying HDCP session
- drm/amd/display: Fix DFPstate hang due to view port changed
- drm/amd/display: fix pow() crashing when given base 0
- drm/i915/pmu: Prefer drm_WARN_ON over WARN_ON
- drm/i915: Provide the perf pmu.module
- scsi: ufs: Add DELAY_BEFORE_LPM quirk for Micron devices
- scsi: target: tcmu: Fix crash in tcmu_flush_dcache_range on ARM
- media: budget-core: Improve exception handling in budget_register()
- media: coda: jpeg: add NULL check after kmalloc
- f2fs: fix to check page dirty status before writeback
- rtc: goldfish: Enable interrupt in set_alarm() when necessary
- media: vpss: clean up resources in init
- f2fs: should avoid inode eviction in synchronous path
- Input: psmouse - add a newline when printing 'proto' by sysfs
- MIPS: Fix unable to reserve memory for Crash kernel
- m68knommu: fix overwriting of bits in ColdFire V3 cache control
- svcrdma: Fix another Receive buffer leak
- xfs: fix inode quota reservation checks
- drm/ttm: fix offset in VMAs with a pg_offs in ttm_bo_vm_access
- riscv: Fixup static_obj() fail
- jffs2: fix UAF problem
- ceph: fix use-after-free for fsc->mdsc
- swiotlb-xen: use vmalloc_to_page on vmalloc virt addresses
- cpufreq: intel_pstate: Fix cpuinfo_max_freq when MSR_TURBO_RATIO_LIMIT is 0
- scsi: libfc: Free skb in fc_disc_gpn_id_resp() for valid cases
- virtio_ring: Avoid loop when vq is broken in virtqueue_poll
- media: camss: fix memory leaks on error handling paths in probe
- tools/testing/selftests/cgroup/cgroup_util.c: cg_read_strcmp: fix null
pointer dereference
- xfs: Fix UBSAN null-ptr-deref in xfs_sysfs_init
- alpha: fix annotation of io{read,write}{16,32}be()
- fat: fix fat_ra_init() for data clusters == 0
- fs/signalfd.c: fix inconsistent return codes for signalfd4
- ext4: fix potential negative array index in do_split()
- drm/virtio: fix missing dma_fence_put() in virtio_gpu_execbuffer_ioctl()
- ext4: don't allow overlapping system zones
- ext4: check journal inode extents more carefully
- netfilter: nf_tables: nft_exthdr:
[Touch-packages] [Bug 1894155] [NEW] libpam-moudles update failure
Public bug reported: today ubuntu software updater pushed a update, but it failed when update libpam-modules from 1.3.1-5ubuntu4.1 to 1.3.1-5ubuntu4.1. after that i tried to update this package manually, here is the error reported. debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable (Reading database ... 187403 files and directories currently installed.) Preparing to unpack .../libpam-modules_1.3.1-5ubuntu4.1_amd64.deb ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another p rocess: Resource temporarily unavailable dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.3.1-5ubu ntu4.1_amd64.deb (--unpack): new libpam-modules:amd64 package pre-installation script subprocess returned er ror exit status 1 Errors were encountered while processing: /var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) seems caused by debconf, similar to the bug below: https://bugs.launchpad.net/ubuntu/+source/libgtk3-perl/+bug/1871960 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 17:34:21 2020 InstallationDate: Installed on 2020-08-18 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pam (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 pam in Ubuntu. https://bugs.launchpad.net/bugs/1894155 Title: libpam-moudles update failure Status in pam package in Ubuntu: New Bug description: today ubuntu software updater pushed a update, but it failed when update libpam-modules from 1.3.1-5ubuntu4.1 to 1.3.1-5ubuntu4.1. after that i tried to update this package manually, here is the error reported. debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable (Reading database ... 187403 files and directories currently installed.) Preparing to unpack .../libpam-modules_1.3.1-5ubuntu4.1_amd64.deb ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another p rocess: Resource temporarily unavailable dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.3.1-5ubu ntu4.1_amd64.deb (--unpack): new libpam-modules:amd64 package pre-installation script subprocess returned er ror exit status 1 Errors were encountered while processing: /var/cache/apt/archives/libpam-modules_1.3.1-5ubuntu4.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) seems caused by debconf, similar to the bug below: https://bugs.launchpad.net/ubuntu/+source/libgtk3-perl/+bug/1871960 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libpam-modules 1.3.1-5ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 17:34:21 2020 InstallationDate: Installed on 2020-08-18 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1894155/+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 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
also, I looked for the error you described, and it's not present, but I do see this: 2539:D: [pulseaudio] alsa-util.c: snd_pcm_hw_params_set_channels(8) failed: Invalid argument 2542:D: [pulseaudio] alsa-util.c: snd_pcm_hw_params_set_channels(8) failed: Invalid argument 2545:D: [pulseaudio] alsa-util.c: snd_pcm_hw_params_set_channels(8) failed: Invalid argument 2548:D: [pulseaudio] alsa-util.c: snd_pcm_hw_params_set_channels(8) failed: Invalid argument 2549:I: [pulseaudio] alsa-util.c: Failed to set hardware parameters on plug:surround71:0: Invalid argument I imagine this is because my output device is a 7.1 device, not a 5.1 device, but it is still strange that it's even attempting to set a mode that isn't what I configured, but instead the highest-channel mode. -- 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/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
the before and after outputs of catting this card are identical according to diff, so I've just included the before output here. ** Attachment added: "before.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+attachment/5407463/+files/before.txt -- 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/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 774071] Re: Indicator-datetime-service renders 100% CPU usage
I confirm the bad behavior on my side with google account enabled.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/774071 Title: Indicator-datetime-service renders 100% CPU usage Status in Indicator Date and Time: Fix Released Status in Unity Foundations: Fix Released Status in indicator-datetime package in Ubuntu: Fix Released Bug description: Binary package hint: indicator-datetime On my laptop "indicator-datetime-service" occasionally make my CPU to use 100% of its resources. It does not happen every time I log in to Ubuntu, but when it happens, it stays hogging 100% of CPU until I kill the process. If it helps, I've noticed in "System Monitor" that there are two instances of "indicator-datetime-service" running, but only one of them is hogging recourses. So far I was unable to determine after what actions/events this bug pups up. I'm using Ubuntu 11.04 64-bit. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: indicator-datetime 0.2.3-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Apr 30 15:27:58 2011 ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: indicator-datetime UpgradeStatus: Upgraded to natty on 2011-04-28 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/774071/+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 1894075] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1894075/+attachment/5407459/+files/Dependencies.txt -- 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/1894075 Title: sound is absent ubuntu 20.04 Status in pulseaudio package in Ubuntu: Incomplete Bug description: Could You help me with sound restore in Ubuntu 20.04 LTS after upgrade from Ubuntu 19.10? Sincerely N.E. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsystemd0:amd64 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.1 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:123:2243292:2020-09-02 17:38:34.836466312 +0300:2020-09-02 17:38:35.836466312 +0300:/var/crash/_usr_lib_firefox_crashreporter.1000.crash 640:0:123:81354:2020-09-02 14:42:34.015875816 +0300:2020-09-02 14:42:35.015875816 +0300:/var/crash/systemd.0.crash 640:0:123:81374:2020-09-02 14:42:33.987879276 +0300:2020-09-02 14:42:34.987879276 +0300:/var/crash/libsystemd0:amd64.0.crash 640:0:123:81374:2020-09-02 14:42:35.003877338 +0300:2020-09-02 14:42:34.991878838 +0300:/var/crash/systemd-timesyncd.0.crash Date: Wed Sep 2 14:42:34 2020 DpkgTerminalLog: dpkg: error processing package libsystemd0:amd64 (--configure): package libsystemd0:amd64 is already installed and configured ErrorMessage: package libsystemd0:amd64 is already installed and configured InstallationDate: Installed on 2019-09-27 (341 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: dpkg Title: package libsystemd0:amd64 245.4-4ubuntu3.2 failed to install/upgrade: package libsystemd0:amd64 is already installed and configured UpgradeStatus: Upgraded to focal on 2020-06-19 (75 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolae1554 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-01 (368 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190709) Package: pulseaudio 1:13.99.1-1ubuntu3.5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal wayland-session Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 6SCN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6SCN35WW:bd06/21/2018:svnLENOVO:pn81AX:pvrLenovoV330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV330-15IKB: dmi.product.family: V330-15IKB dmi.product.name: 81AX dmi.product.sku: LENOVO_MT_81AX_BU_idea_FM_V330-15IKB dmi.product.version: Lenovo V330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894075/+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 1894075] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1894075/+attachment/5407460/+files/ProcCpuinfoMinimal.txt -- 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/1894075 Title: sound is absent ubuntu 20.04 Status in pulseaudio package in Ubuntu: Incomplete Bug description: Could You help me with sound restore in Ubuntu 20.04 LTS after upgrade from Ubuntu 19.10? Sincerely N.E. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsystemd0:amd64 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.1 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:123:2243292:2020-09-02 17:38:34.836466312 +0300:2020-09-02 17:38:35.836466312 +0300:/var/crash/_usr_lib_firefox_crashreporter.1000.crash 640:0:123:81354:2020-09-02 14:42:34.015875816 +0300:2020-09-02 14:42:35.015875816 +0300:/var/crash/systemd.0.crash 640:0:123:81374:2020-09-02 14:42:33.987879276 +0300:2020-09-02 14:42:34.987879276 +0300:/var/crash/libsystemd0:amd64.0.crash 640:0:123:81374:2020-09-02 14:42:35.003877338 +0300:2020-09-02 14:42:34.991878838 +0300:/var/crash/systemd-timesyncd.0.crash Date: Wed Sep 2 14:42:34 2020 DpkgTerminalLog: dpkg: error processing package libsystemd0:amd64 (--configure): package libsystemd0:amd64 is already installed and configured ErrorMessage: package libsystemd0:amd64 is already installed and configured InstallationDate: Installed on 2019-09-27 (341 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: dpkg Title: package libsystemd0:amd64 245.4-4ubuntu3.2 failed to install/upgrade: package libsystemd0:amd64 is already installed and configured UpgradeStatus: Upgraded to focal on 2020-06-19 (75 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolae1554 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-01 (368 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190709) Package: pulseaudio 1:13.99.1-1ubuntu3.5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal wayland-session Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 6SCN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6SCN35WW:bd06/21/2018:svnLENOVO:pn81AX:pvrLenovoV330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV330-15IKB: dmi.product.family: V330-15IKB dmi.product.name: 81AX dmi.product.sku: LENOVO_MT_81AX_BU_idea_FM_V330-15IKB dmi.product.version: Lenovo V330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894075/+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 1894075] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1894075/+attachment/5407461/+files/ProcEnviron.txt -- 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/1894075 Title: sound is absent ubuntu 20.04 Status in pulseaudio package in Ubuntu: Incomplete Bug description: Could You help me with sound restore in Ubuntu 20.04 LTS after upgrade from Ubuntu 19.10? Sincerely N.E. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsystemd0:amd64 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.1 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:123:2243292:2020-09-02 17:38:34.836466312 +0300:2020-09-02 17:38:35.836466312 +0300:/var/crash/_usr_lib_firefox_crashreporter.1000.crash 640:0:123:81354:2020-09-02 14:42:34.015875816 +0300:2020-09-02 14:42:35.015875816 +0300:/var/crash/systemd.0.crash 640:0:123:81374:2020-09-02 14:42:33.987879276 +0300:2020-09-02 14:42:34.987879276 +0300:/var/crash/libsystemd0:amd64.0.crash 640:0:123:81374:2020-09-02 14:42:35.003877338 +0300:2020-09-02 14:42:34.991878838 +0300:/var/crash/systemd-timesyncd.0.crash Date: Wed Sep 2 14:42:34 2020 DpkgTerminalLog: dpkg: error processing package libsystemd0:amd64 (--configure): package libsystemd0:amd64 is already installed and configured ErrorMessage: package libsystemd0:amd64 is already installed and configured InstallationDate: Installed on 2019-09-27 (341 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: dpkg Title: package libsystemd0:amd64 245.4-4ubuntu3.2 failed to install/upgrade: package libsystemd0:amd64 is already installed and configured UpgradeStatus: Upgraded to focal on 2020-06-19 (75 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolae1554 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-01 (368 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190709) Package: pulseaudio 1:13.99.1-1ubuntu3.5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal wayland-session Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 6SCN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6SCN35WW:bd06/21/2018:svnLENOVO:pn81AX:pvrLenovoV330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV330-15IKB: dmi.product.family: V330-15IKB dmi.product.name: 81AX dmi.product.sku: LENOVO_MT_81AX_BU_idea_FM_V330-15IKB dmi.product.version: Lenovo V330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894075/+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 1894075] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1894075/+attachment/5407462/+files/PulseList.txt -- 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/1894075 Title: sound is absent ubuntu 20.04 Status in pulseaudio package in Ubuntu: Incomplete Bug description: Could You help me with sound restore in Ubuntu 20.04 LTS after upgrade from Ubuntu 19.10? Sincerely N.E. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsystemd0:amd64 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.1 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:123:2243292:2020-09-02 17:38:34.836466312 +0300:2020-09-02 17:38:35.836466312 +0300:/var/crash/_usr_lib_firefox_crashreporter.1000.crash 640:0:123:81354:2020-09-02 14:42:34.015875816 +0300:2020-09-02 14:42:35.015875816 +0300:/var/crash/systemd.0.crash 640:0:123:81374:2020-09-02 14:42:33.987879276 +0300:2020-09-02 14:42:34.987879276 +0300:/var/crash/libsystemd0:amd64.0.crash 640:0:123:81374:2020-09-02 14:42:35.003877338 +0300:2020-09-02 14:42:34.991878838 +0300:/var/crash/systemd-timesyncd.0.crash Date: Wed Sep 2 14:42:34 2020 DpkgTerminalLog: dpkg: error processing package libsystemd0:amd64 (--configure): package libsystemd0:amd64 is already installed and configured ErrorMessage: package libsystemd0:amd64 is already installed and configured InstallationDate: Installed on 2019-09-27 (341 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: dpkg Title: package libsystemd0:amd64 245.4-4ubuntu3.2 failed to install/upgrade: package libsystemd0:amd64 is already installed and configured UpgradeStatus: Upgraded to focal on 2020-06-19 (75 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolae1554 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-01 (368 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190709) Package: pulseaudio 1:13.99.1-1ubuntu3.5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal wayland-session Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 6SCN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6SCN35WW:bd06/21/2018:svnLENOVO:pn81AX:pvrLenovoV330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV330-15IKB: dmi.product.family: V330-15IKB dmi.product.name: 81AX dmi.product.sku: LENOVO_MT_81AX_BU_idea_FM_V330-15IKB dmi.product.version: Lenovo V330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894075/+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 1894075] Re: sound is absent ubuntu 20.04
apport information ** Tags added: apport-collected wayland-session ** Description changed: Could You help me with sound restore in Ubuntu 20.04 LTS after upgrade from Ubuntu 19.10? Sincerely N.E. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsystemd0:amd64 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.1 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:123:2243292:2020-09-02 17:38:34.836466312 +0300:2020-09-02 17:38:35.836466312 +0300:/var/crash/_usr_lib_firefox_crashreporter.1000.crash 640:0:123:81354:2020-09-02 14:42:34.015875816 +0300:2020-09-02 14:42:35.015875816 +0300:/var/crash/systemd.0.crash 640:0:123:81374:2020-09-02 14:42:33.987879276 +0300:2020-09-02 14:42:34.987879276 +0300:/var/crash/libsystemd0:amd64.0.crash 640:0:123:81374:2020-09-02 14:42:35.003877338 +0300:2020-09-02 14:42:34.991878838 +0300:/var/crash/systemd-timesyncd.0.crash Date: Wed Sep 2 14:42:34 2020 DpkgTerminalLog: dpkg: error processing package libsystemd0:amd64 (--configure): package libsystemd0:amd64 is already installed and configured ErrorMessage: package libsystemd0:amd64 is already installed and configured InstallationDate: Installed on 2019-09-27 (341 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: dpkg Title: package libsystemd0:amd64 245.4-4ubuntu3.2 failed to install/upgrade: package libsystemd0:amd64 is already installed and configured UpgradeStatus: Upgraded to focal on 2020-06-19 (75 days ago) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: nicolae1554 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-09-01 (368 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190709) + Package: pulseaudio 1:13.99.1-1ubuntu3.5 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 + Tags: focal wayland-session + Uname: Linux 5.4.0-42-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 06/21/2018 + dmi.bios.vendor: LENOVO + dmi.bios.version: 6SCN35WW + dmi.board.asset.tag: No Asset Tag + dmi.board.name: LNVNB161216 + dmi.board.vendor: LENOVO + dmi.board.version: NO DPK + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Lenovo V330-15IKB + dmi.modalias: dmi:bvnLENOVO:bvr6SCN35WW:bd06/21/2018:svnLENOVO:pn81AX:pvrLenovoV330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV330-15IKB: + dmi.product.family: V330-15IKB + dmi.product.name: 81AX + dmi.product.sku: LENOVO_MT_81AX_BU_idea_FM_V330-15IKB + dmi.product.version: Lenovo V330-15IKB + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1894075/+attachment/5407457/+files/AlsaInfo.txt -- 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/1894075 Title: sound is absent ubuntu 20.04 Status in pulseaudio package in Ubuntu: Incomplete Bug description: Could You help me with sound restore in Ubuntu 20.04 LTS after upgrade from Ubuntu 19.10? Sincerely N.E. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsystemd0:amd64 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.1 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:123:2243292:2020-09-02 17:38:34.836466312 +0300:2020-09-02 17:38:35.836466312 +0300:/var/crash/_usr_lib_firefox_crashreporter.1000.crash 640:0:123:81354:2020-09-02 14:42:34.015875816 +0300:2020-09-02 14:42:35.015875816 +0300:/var/crash/systemd.0.crash 640:0:123:81374:2020-09-02 14:42:33.987879276 +0300:2020-09-02 14:42:34.987879276 +0300:/var/crash/libsystemd0:amd64.0.crash 640:0:123:81374:2020-09-02 14:42:35.003877338 +0300:2020-09-02 14:42:34.991878838 +0300:/var/crash/systemd-timesyncd.0.crash Date: Wed Sep 2 14:42:34 2020 DpkgTerminalLog: dpkg: error processing package libsystemd0:amd64 (--configure): package libsystemd0:amd64 is already installed and configured ErrorMessage: package
[Touch-packages] [Bug 1894075] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1894075/+attachment/5407458/+files/CurrentDmesg.txt -- 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/1894075 Title: sound is absent ubuntu 20.04 Status in pulseaudio package in Ubuntu: Incomplete Bug description: Could You help me with sound restore in Ubuntu 20.04 LTS after upgrade from Ubuntu 19.10? Sincerely N.E. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsystemd0:amd64 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.1 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:123:2243292:2020-09-02 17:38:34.836466312 +0300:2020-09-02 17:38:35.836466312 +0300:/var/crash/_usr_lib_firefox_crashreporter.1000.crash 640:0:123:81354:2020-09-02 14:42:34.015875816 +0300:2020-09-02 14:42:35.015875816 +0300:/var/crash/systemd.0.crash 640:0:123:81374:2020-09-02 14:42:33.987879276 +0300:2020-09-02 14:42:34.987879276 +0300:/var/crash/libsystemd0:amd64.0.crash 640:0:123:81374:2020-09-02 14:42:35.003877338 +0300:2020-09-02 14:42:34.991878838 +0300:/var/crash/systemd-timesyncd.0.crash Date: Wed Sep 2 14:42:34 2020 DpkgTerminalLog: dpkg: error processing package libsystemd0:amd64 (--configure): package libsystemd0:amd64 is already installed and configured ErrorMessage: package libsystemd0:amd64 is already installed and configured InstallationDate: Installed on 2019-09-27 (341 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: dpkg Title: package libsystemd0:amd64 245.4-4ubuntu3.2 failed to install/upgrade: package libsystemd0:amd64 is already installed and configured UpgradeStatus: Upgraded to focal on 2020-06-19 (75 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolae1554 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-01 (368 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190709) Package: pulseaudio 1:13.99.1-1ubuntu3.5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal wayland-session Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 6SCN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6SCN35WW:bd06/21/2018:svnLENOVO:pn81AX:pvrLenovoV330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV330-15IKB: dmi.product.family: V330-15IKB dmi.product.name: 81AX dmi.product.sku: LENOVO_MT_81AX_BU_idea_FM_V330-15IKB dmi.product.version: Lenovo V330-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894075/+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 1894142] Re: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit sta
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1894142 Title: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 137 Status in unattended-upgrades package in Ubuntu: New Bug description: After updating ubuntu's 20.04.1 packages, lots of error reports started to pop up, and one of those is this one. I dont know what it could be ProblemType: Package DistroRelease: Ubuntu 20.04 Package: unattended-upgrades 2.3ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 3 16:35:32 2020 DuplicateSignature: package:unattended-upgrades:2.3ubuntu0.1 Setting up unattended-upgrades (2.3ubuntu0.1) ... dpkg: error processing package unattended-upgrades (--configure): installed unattended-upgrades package post-installation script subprocess returned error exit status 137 ErrorMessage: installed unattended-upgrades package post-installation script subprocess returned error exit status 137 InstallationDate: Installed on 2020-09-02 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 137 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1894142/+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 1894142] [NEW] package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit s
Public bug reported: After updating ubuntu's 20.04.1 packages, lots of error reports started to pop up, and one of those is this one. I dont know what it could be ProblemType: Package DistroRelease: Ubuntu 20.04 Package: unattended-upgrades 2.3ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 3 16:35:32 2020 DuplicateSignature: package:unattended-upgrades:2.3ubuntu0.1 Setting up unattended-upgrades (2.3ubuntu0.1) ... dpkg: error processing package unattended-upgrades (--configure): installed unattended-upgrades package post-installation script subprocess returned error exit status 137 ErrorMessage: installed unattended-upgrades package post-installation script subprocess returned error exit status 137 InstallationDate: Installed on 2020-09-02 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 137 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1894142 Title: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 137 Status in unattended-upgrades package in Ubuntu: New Bug description: After updating ubuntu's 20.04.1 packages, lots of error reports started to pop up, and one of those is this one. I dont know what it could be ProblemType: Package DistroRelease: Ubuntu 20.04 Package: unattended-upgrades 2.3ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 3 16:35:32 2020 DuplicateSignature: package:unattended-upgrades:2.3ubuntu0.1 Setting up unattended-upgrades (2.3ubuntu0.1) ... dpkg: error processing package unattended-upgrades (--configure): installed unattended-upgrades package post-installation script subprocess returned error exit status 137 ErrorMessage: installed unattended-upgrades package post-installation script subprocess returned error exit status 137 InstallationDate: Installed on 2020-09-02 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 137 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1894142/+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 1890609] Re: improved resolved configuration
** Tags added: resolved-resolvconf -- 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/1890609 Title: improved resolved configuration Status in systemd package in Ubuntu: Fix Released Bug description: improved resolved configuration * isc-dhcp-client pushes DNS data to resolved via a hook it ships * ifupdown pushes DNS data to resolved via a hook it ships * resolvconf skips pulling DNS data that is pushed to resolved * systemd doesn't have enter hook anymore This way with or without resolvconf, resolved has all the information it needs and /etc/resolv.conf can be static, point at resolvconf managed file, or at resolved managed file as desired. isc-dhcp 4.4.1-2.1ubuntu7 ifupdown 0.8.35ubuntu2 resolvconf 1.82ubuntu1 systemd TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890609/+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 1892798] Re: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf
** Tags added: resolved-resolvconf -- 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/1892798 Title: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf Status in systemd package in Ubuntu: Won't Fix Status in wireguard package in Ubuntu: Confirmed Status in systemd package in Debian: Incomplete Bug description: By default Ubuntu now uses systemd to manage the nameservers in resolv.conf, so resolvconf and openresolv seem to be redundant. However, it appears that systemd's resolvectl is compatable with resolvconf style commands if symlinked as resolvconf. I'm not really sure how deb packaging works, but if it possible to check for the resolvconf command, and if not found just symlink /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work without additional packages. See https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8) for more info. Apologies if there is a better place to direct this info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+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 1889068] Re: Improve resolved integration
** Tags added: resolved-resolvconf -- 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/1889068 Title: Improve resolved integration Status in ifupdown package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Fix Released Status in resolvconf package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Insure that ifupdown & dhcp DNS information is always added to resolved. Move the resolved hooks from systemd package to isc-dhcp-client and ifupdown themselves. Figure out how to integrate "eth0" resolver => Manager resolver. Blog / document how to control this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1889068/+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 1894075] Re: sound is absent ubuntu 20.04
Please run the following command to gather audio information: apport-collect 1894075 ** Package changed: dpkg (Ubuntu) => pulseaudio (Ubuntu) ** 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/1894075 Title: sound is absent ubuntu 20.04 Status in pulseaudio package in Ubuntu: Incomplete Bug description: Could You help me with sound restore in Ubuntu 20.04 LTS after upgrade from Ubuntu 19.10? Sincerely N.E. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsystemd0:amd64 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.1 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:123:2243292:2020-09-02 17:38:34.836466312 +0300:2020-09-02 17:38:35.836466312 +0300:/var/crash/_usr_lib_firefox_crashreporter.1000.crash 640:0:123:81354:2020-09-02 14:42:34.015875816 +0300:2020-09-02 14:42:35.015875816 +0300:/var/crash/systemd.0.crash 640:0:123:81374:2020-09-02 14:42:33.987879276 +0300:2020-09-02 14:42:34.987879276 +0300:/var/crash/libsystemd0:amd64.0.crash 640:0:123:81374:2020-09-02 14:42:35.003877338 +0300:2020-09-02 14:42:34.991878838 +0300:/var/crash/systemd-timesyncd.0.crash Date: Wed Sep 2 14:42:34 2020 DpkgTerminalLog: dpkg: error processing package libsystemd0:amd64 (--configure): package libsystemd0:amd64 is already installed and configured ErrorMessage: package libsystemd0:amd64 is already installed and configured InstallationDate: Installed on 2019-09-27 (341 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: dpkg Title: package libsystemd0:amd64 245.4-4ubuntu3.2 failed to install/upgrade: package libsystemd0:amd64 is already installed and configured UpgradeStatus: Upgraded to focal on 2020-06-19 (75 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894075/+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 1894075] [NEW] sound is absent ubuntu 20.04
You have been subscribed to a public bug: Could You help me with sound restore in Ubuntu 20.04 LTS after upgrade from Ubuntu 19.10? Sincerely N.E. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsystemd0:amd64 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.1 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:123:2243292:2020-09-02 17:38:34.836466312 +0300:2020-09-02 17:38:35.836466312 +0300:/var/crash/_usr_lib_firefox_crashreporter.1000.crash 640:0:123:81354:2020-09-02 14:42:34.015875816 +0300:2020-09-02 14:42:35.015875816 +0300:/var/crash/systemd.0.crash 640:0:123:81374:2020-09-02 14:42:33.987879276 +0300:2020-09-02 14:42:34.987879276 +0300:/var/crash/libsystemd0:amd64.0.crash 640:0:123:81374:2020-09-02 14:42:35.003877338 +0300:2020-09-02 14:42:34.991878838 +0300:/var/crash/systemd-timesyncd.0.crash Date: Wed Sep 2 14:42:34 2020 DpkgTerminalLog: dpkg: error processing package libsystemd0:amd64 (--configure): package libsystemd0:amd64 is already installed and configured ErrorMessage: package libsystemd0:amd64 is already installed and configured InstallationDate: Installed on 2019-09-27 (341 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: dpkg Title: package libsystemd0:amd64 245.4-4ubuntu3.2 failed to install/upgrade: package libsystemd0:amd64 is already installed and configured UpgradeStatus: Upgraded to focal on 2020-06-19 (75 days ago) ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: already-installed amd64 apport-package focal -- sound is absent ubuntu 20.04 https://bugs.launchpad.net/bugs/1894075 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio 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 1882098] Re: Packagekit lets user install untrusted local packages in Bionic and Focal
It asks apt if the package is trusted, and from apt's POV it is. which might or might not be good, UX wise, for apt (maybe it should also tell you that local debs are not verified), but not much of an issue there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1882098 Title: Packagekit lets user install untrusted local packages in Bionic and Focal Status in packagekit package in Ubuntu: Triaged Bug description: We have packagekit configured to allow users to install trusted packages from preconfigured repositories, but disallowed them to install any untrusted packages. The policykit configuration we use is following: [tld.univ.packagekit] Identity=unix-group:adm; Action=org.freedesktop.packagekit.package-install;org.freedesktop.packagekit.package-reinstall;org.freedesktop.packagekit.package-remove;org.freedesktop.packagekit.system-sources-refresh;org.freedesktop.packagekit.system-update;org.freedesktop.packagekit.repair-system; ResultAny=auth_self ResultActive=auth_self ResultInactive=auth_self [tld.univ.packagekit-deny] Identity=unix-user:*; Action=org.freedesktop.packagekit.package-install-untrusted; ResultAny=no We would expect this to prevent users from installing local packages downloaded from random repositories, however this does not seem to be the case. pkcon install-local random_package.deb will happily prompt for the user to authenticate and will install the package, while pkcon --allow-untrusted install-local random_package.deb will prompt for root password, which the user does not have. Our initial toughts was that the issue would be in packagekitd, but after further investigations it looks like the issue could be in aptcc backend. We are more than happy to provide you with further details, but the above should be enough to reproduce the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1882098/+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 1894124] [NEW] Merge gtk 3.24.22 from Debian
Public bug reported: Please merge gtk 3.24.22 from Debian. It supposedly fixes bug #1891761 and improves frame clock smoothness and fixes frame clock monotonicity. https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS Overview of Changes in GTK+ 3.24.22 === * GtkTextView: - Fix some corner cases of pixelcache invalidation - Make select-all work on touch * Fix print portal support * Adwaita: - Tweak title style class - Add a public color for text view background * Windows: - Limit the size of the corner mask cache - Use native API for keycode conversion - Use GLES on arm64 * Wayland: Add a way to change the application id (LP: #1891761) * Quartz: Add axes to master devices * Add --enable-tracker3 option to configure * Translation updates: Catalan German Indonesian Italian Kazakh Spanish Turkish Overview of Changes in GTK+ 3.24.21 === * Wayland: - Prevent crashes with offscreen windows - Handle disorderly tablet/pad disconnects * GtkFileChooser: - Translate the type column - Add a tracker3 search engine - Rate-limit trash monitoring - Make get_filter work for native chooser * GtkGLArea: - Fix a redraw problem * GtkScrolledWindow: - Fix kinetic scrolling * Add a gtk-cursor-aspect-ratio setting * GDK: - Improve frame clock smoothness - Fix frame clock monotonicity * OS X: - Support Pen / Eraser input - Support openfiles in GtkApplication * Adwaita: - Improve notebook tab legibility * Translation updates: Basque Brazilian Portuguese Catalan Chinese (Taiwan) German Indonesian Italian Japanese Kazakh Lithuanian Polish Romanian Slovak Slovenian Swedish Ukrainian ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: groovy upgrade-software-version -- 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/1894124 Title: Merge gtk 3.24.22 from Debian Status in gtk+3.0 package in Ubuntu: New Bug description: Please merge gtk 3.24.22 from Debian. It supposedly fixes bug #1891761 and improves frame clock smoothness and fixes frame clock monotonicity. https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS Overview of Changes in GTK+ 3.24.22 === * GtkTextView: - Fix some corner cases of pixelcache invalidation - Make select-all work on touch * Fix print portal support * Adwaita: - Tweak title style class - Add a public color for text view background * Windows: - Limit the size of the corner mask cache - Use native API for keycode conversion - Use GLES on arm64 * Wayland: Add a way to change the application id (LP: #1891761) * Quartz: Add axes to master devices * Add --enable-tracker3 option to configure * Translation updates: Catalan German Indonesian Italian Kazakh Spanish Turkish Overview of Changes in GTK+ 3.24.21 === * Wayland: - Prevent crashes with offscreen windows - Handle disorderly tablet/pad disconnects * GtkFileChooser: - Translate the type column - Add a tracker3 search engine - Rate-limit trash monitoring - Make get_filter work for native chooser * GtkGLArea: - Fix a redraw problem * GtkScrolledWindow: - Fix kinetic scrolling * Add a gtk-cursor-aspect-ratio setting * GDK: - Improve frame clock smoothness - Fix frame clock monotonicity * OS X: - Support Pen / Eraser input - Support openfiles in GtkApplication * Adwaita: - Improve notebook tab legibility * Translation updates: Basque Brazilian Portuguese Catalan Chinese (Taiwan) German Indonesian Italian Japanese Kazakh Lithuanian Polish Romanian Slovak Slovenian Swedish Ukrainian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1894124/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Same problem here, Sone WH-1000MX2, ubuntu 20.04.1 LTS, Linux 5.4.0-45-generic. Tried proposed solutions with no luck. -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Same problem here, Sone WH-1000MX2, ubuntu 20.04.1 LTS, Linux 5.4.0-45-generic. AD2P works, however as soon as i switch to HSP/HFP then i loose bluetooth audio. Worked in Ubuntu 18 LTS. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871794/+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 1893899] Re: update alsa/audio related infomation collection code in apport
** Summary changed: - update alsa/audio realted infomation collection code in apport + update alsa/audio related infomation collection code in 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/1893899 Title: update alsa/audio related infomation collection code in apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: New Bug description: what need to change 1. try to use /usr/sbin/alsa-info before try /usr/share/alsa-base/alsa-info.sh (weird for me that two copy of alsa-info co-exists, but anyway) 2. add pa-info (exist after focal) 3. add ucm2 directory. (exist after focal) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893899/+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 1893728] Re: Ubuntu CVE Tracker krb5 1.17-6ubuntu4 CVE-2018-20217 false positive
** Also affects: krb5 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: krb5 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: krb5 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1893728 Title: Ubuntu CVE Tracker krb5 1.17-6ubuntu4 CVE-2018-20217 false positive Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Bionic: New Status in krb5 source package in Focal: New Bug description: Information in shows that krb5 versions before 1.17 are vulnerable to CVE-2018-20217. https://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-20217.html Based on Debian bug report, this is already fixed in 1.16.2 version: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917387 Ubuntu 20.04 LTS (Focal Fossa) includes version krb5 1.17.6: https://launchpad.net/ubuntu/focal/+source/krb5 Ubuntu CVE Tracker page shows that Ubuntu 20.04 LTS (Focal Fossa) doesn't have a package where CVE-2018-20217 is fixed. https://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-20217.html Steps to reproduce: This was found when examining AWS Elastic Container Registry Vulnerability scanning results for a Docker image based on latest Ubuntu 20.04: Here is the complete line from the report: krb5:1.17-6ubuntu4 MEDIUM A Reachable Assertion issue was discovered in the KDC in MIT Kerberos 5 (aka krb5) before 1.17. If an attacker can obtain a krbtgt ticket using an older encryption type (single-DES, triple-DES, or RC4), the attacker can crash the KDC by making an S4U2Self request. It can be seen from the scan that the Docker image included krb5 bversion 1.17-6. Expected: No vulnerability finding. Actual: krb5 bversion 1.17-6ubuntu4 is reported as vulnerable to CVE-2018-20217. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1893728/+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 1893695] Re: package libx264-155:amd64 2:0.155.2917+git0a84d98-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin
Problem solved thanks ** Changed in: x264 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to x264 in Ubuntu. https://bugs.launchpad.net/bugs/1893695 Title: package libx264-155:amd64 2:0.155.2917+git0a84d98-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in x264 package in Ubuntu: Fix Released Bug description: All I know is that it states that I must install libx264-155:amd64 before proceeding with any further installation. This is a new installations, but I have completed to date five other upgrades without too much issue. Not sure why it is causing problems this time as things seem to be installing fine. One observation is that i noted the software centre is short of packages to start. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libx264-155:amd64 2:0.155.2917+git0a84d98-2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 31 21:38:05 2020 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-08-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: x264 Title: package libx264-155:amd64 2:0.155.2917+git0a84d98-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x264/+bug/1893695/+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 1893958] Re: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend
** Changed in: iptables (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1893958 Title: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend Status in iptables package in Ubuntu: Confirmed Bug description: The change is a planned change for this development cycle and the fix has been tested as described in LP: #1887186 and https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041142.html . Changes: iptables (1.8.4-3ubuntu3) groovy; urgency=medium . * Swap alternative priority and prefer nftables backend over legacy (LP: #1887186) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1893958/+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 1893958] Re: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend
LXD depends on the nft tool when iptables-legacy rules are not in use (as the iptables-nft tools do not provide all the functionality it depends on). However the nft tool is bundled in the snap package so this should be fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1893958 Title: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend Status in iptables package in Ubuntu: New Bug description: The change is a planned change for this development cycle and the fix has been tested as described in LP: #1887186 and https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041142.html . Changes: iptables (1.8.4-3ubuntu3) groovy; urgency=medium . * Swap alternative priority and prefer nftables backend over legacy (LP: #1887186) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1893958/+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 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions
Hello Thomas, Thanks for reporting this and making Ubuntu better. about your statement on lsb-release, in 00-header: [ -r /etc/lsb-release ] && . /etc/lsb-release if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then # Fall back to using the very slow lsb_release utility DISTRIB_DESCRIPTION=$(lsb_release -s -d) fi # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS" the slowpath is only executed if the DISTRIB_DESCRIPTION variable is not set, at least in my tests. In regards to your statement: """ The content of /etc/update-motd.d/* really, really, really shouldn't be executed if the session in question is not interactive, as it provides no value at all. Unfortunately, to disable it for these non-interactive sessions, we also have to disable it for the interactive ones as well where it has some value (though not enough to make spiking the load on this server through the roof an acceptable tradeoff). """ Considering there IS a way of disabling the dynamic motd contents currently by commenting only the line containing the /run/motd.dynamic wording: # Print the message of the day upon successful login. # This includes a dynamically generated part from /run/motd.dynamic # and a static (admin-editable) part from /etc/motd. # sessionoptional pam_motd.so motd=/run/motd.dynamic sessionoptional pam_motd.so noupdate I'm flagging this bug as a whishlist priority. ** Also affects: update-motd (Ubuntu) Importance: Undecided Status: New ** No longer affects: openssh (Ubuntu) ** No longer affects: base-files (Ubuntu) ** Changed in: update-motd (Ubuntu) Status: New => Triaged ** Changed in: update-motd (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1893716 Title: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions Status in update-motd package in Ubuntu: Triaged Bug description: My client has 200+ devices automatically uploading information via sftp and scp to a server every few minutes. After a recent update, I noticed the load on their server spiking through the roof. Upon investigation, I discovered a horde of landscape-sysinfo and /usr/bin/lsb_release processes running that correlated with login session notifications in /var/log/syslog and the load spikes. It appears that even in non-interactive sessions where this information will never be seen, the configuration options below in /etc/pam.d/sshd cause these items to be launched (in fact, probably everything in /etc/update-motd.d). This only started on the system in question after a recent set of system updates were installed. The content of /etc/update-motd.d/* really, really, really shouldn't be executed if the session in question is not interactive, as it provides no value at all. Unfortunately, to disable it for these non- interactive sessions, we also have to disable it for the interactive ones as well where it has some value (though not enough to make spiking the load on this server through the roof an acceptable tradeoff). # Print the message of the day upon successful login. # This includes a dynamically generated part from /run/motd.dynamic # and a static (admin-editable) part from /etc/motd. #sessionoptional pam_motd.so motd=/run/motd.dynamic #sessionoptional pam_motd.so noupdate Also, looking at the script 00-header in /etc/update-motd.d/, /usr/bin/lsb_release is being improperly launched, as /etc/lsb_release does include the necessary information: [ -r /etc/lsb-release ] && . /etc/lsb-release if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then # Fall back to using the very slow lsb_release utility DISTRIB_DESCRIPTION=$(lsb_release -s -d) fi # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1893716/+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 1893958] Re: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend
@laney I've sent the email to ubuntu-devel@ a week ago and it also made it to https://www.phoronix.com/scan.php?page=news_item=Ubuntu-20.10-Nftables so I believe every interested party must be aware of that, but I've now pinged stgraber on #ubuntu-release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1893958 Title: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend Status in iptables package in Ubuntu: New Bug description: The change is a planned change for this development cycle and the fix has been tested as described in LP: #1887186 and https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041142.html . Changes: iptables (1.8.4-3ubuntu3) groovy; urgency=medium . * Swap alternative priority and prefer nftables backend over legacy (LP: #1887186) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1893958/+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 1843468] Re: nftables based iptables wrapper break userspace
switching to nftables (again) is tracked in LP: #1887186 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1843468 Title: nftables based iptables wrapper break userspace Status in iptables package in Ubuntu: Fix Released Bug description: iptables just got replaced by the nftables wrappers, effectively changing all Ubuntu systems to using nftables rather than regular iptables/ip6tables/ebtables. Unfortunately those wrappers aren't perfect and don't convert every option properly, nor know about some of the available plugins for those commands. This means that unless the software using those commands are aware that those are wrappers and adapt their use, they may break at some random point in time. While nftables is clearly the way forward, just silently switching the existing native tools with the compat wrappers will lead to widespread breakage both from packages in the archive, snaps and a variety of scripts our users may be running. So far, looking around, known breakages post-nft are expected with at least Docker, Kubernetes and LXD but the same may be true with the many other packages we have that call iptables, ip6tables, ebtables or arptables today. A migration should include a proper audit of all in-archive users, see if they have a plan/patch for native nft interaction and if not, validate their use of the tools is compatible with the wrappers. We should also extend that to popular snaps / those we ship by default. Snaps make things worse as they use the tools from their base snap, which in LXD's case is currently 16.04 (soon to switch to 18.04). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1843468/+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 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
This bug was fixed in the package rpcbind - 0.2.3-0.2ubuntu0.16.04.1 --- rpcbind (0.2.3-0.2ubuntu0.16.04.1) xenial; urgency=medium * d/rules, d/control: - Add dh-autoreconf build-dep and force dh_autoreconf to fix FTBFS (LP: #1885389) * d/p/lp304393/0001-rpcbind-Disable-remote-calls-by-default.patch, d/p/lp304393/0002-rmt-calls.patch, d/p/lp304393/0003-change-rmtcalls-default-to-enabled.patch: - Allow disabling rmtcalls port binding (LP: #304393) -- Dan Streetman Mon, 10 Aug 2020 11:05:43 -0400 ** Changed in: rpcbind (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: Fix Released Status in rpcbind source package in Bionic: Fix Released Status in rpcbind package in Debian: Fix Released Status in Fedora: Confirmed Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, and also adds a check for the existence of an environment variable "RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. This allows 1) retaining the existing default behavior of rpcbind in x and b, while also 2) providing a mechanism to change that default for anyone who does *not* want remote calls to be enabled, and 3) allowing the mechanism to change the default to remain in place after an upgrade to Focal. Using the environment variable allows anyone to disable the remote calls in x and/or b, and then upgrade to Focal without breaking rpcbind or needing to remove the env var. After the upgrade to Focal, the environment variable (defined in /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored without any change needed to the rpcbind package in Focal or later. [original description] Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/304393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1893958] Re: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend
Have you checked with the LXD team that they are happy with this? If so, ack from me. If 1.8.5 fixes bugs then we should take that for sure - please could you make sure to do that (can be later, but not much later)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1893958 Title: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend Status in iptables package in Ubuntu: New Bug description: The change is a planned change for this development cycle and the fix has been tested as described in LP: #1887186 and https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041142.html . Changes: iptables (1.8.4-3ubuntu3) groovy; urgency=medium . * Swap alternative priority and prefer nftables backend over legacy (LP: #1887186) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1893958/+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 1554455] Re: "update-initramfs" is executed several times when you remove old kernels
It's been 4 years and nothing has been changed, this still happening. executing "update-initramfs" several times is wasting of processing power and time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1554455 Title: "update-initramfs" is executed several times when you remove old kernels Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Here is an example. I had several old kernels: linux-image-3.19.0-49-generic linux-image-4.2.0-25-generic linux-signed-image-3.19.0-49-generic linux-signed-image-4.2.0-25-generic I used apt-get autoremove and here is the result: apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: grub-pc-bin linux-headers-3.19.0-49 linux-headers-3.19.0-49-generic linux-image-3.19.0-49-generic linux-image-4.2.0-25-generic linux-image-extra-3.19.0-49-generic linux-image-extra-4.2.0-25-generic linux-signed-image-3.19.0-49-generic linux-signed-image-4.2.0-25-generic 0 upgraded, 0 newly installed, 9 to remove and 0 not upgraded. After this operation, 502 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 211099 files and directories currently installed.) Removing grub-pc-bin (2.02~beta2-9ubuntu1.7) ... Removing linux-headers-3.19.0-49-generic (3.19.0-49.55~14.04.1) ... Removing linux-headers-3.19.0-49 (3.19.0-49.55~14.04.1) ... Removing linux-signed-image-3.19.0-49-generic (3.19.0-49.55~14.04.1) ... Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-generic Found initrd image: /boot/initrd.img-3.19.0-51-generic Found linux image: /boot/vmlinuz-3.19.0-49-generic Found initrd image: /boot/initrd.img-3.19.0-49-generic Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-generic Found initrd image: /boot/initrd.img-3.19.0-51-generic Found linux image: /boot/vmlinuz-3.19.0-49-generic Found initrd image: /boot/initrd.img-3.19.0-49-generic Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi Found Ubuntu Xenial Xerus (development branch) (16.04) on /dev/mapper/VG-root Adding boot menu entry for EFI firmware configuration done Removing linux-image-extra-3.19.0-49-generic (3.19.0-49.55~14.04.1) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic update-initramfs: Generating /boot/initrd.img-3.19.0-49-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-generic Found initrd image: /boot/initrd.img-3.19.0-51-generic Found linux image: /boot/vmlinuz-3.19.0-49-generic Found initrd image: /boot/initrd.img-3.19.0-49-generic Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-generic Found initrd image: /boot/initrd.img-3.19.0-51-generic Found linux image: /boot/vmlinuz-3.19.0-49-generic Found initrd image: /boot/initrd.img-3.19.0-49-generic Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi Found Ubuntu Xenial Xerus (development branch) (16.04) on /dev/mapper/VG-root Adding boot menu entry for EFI firmware configuration done Removing linux-image-3.19.0-49-generic (3.19.0-49.55~14.04.1) ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic update-initramfs: Deleting /boot/initrd.img-3.19.0-49-generic run-parts: executing
[Touch-packages] [Bug 1893958] Re: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend
@oibaf Please open a separate bug for the merge, this one is only for the switch. I agree that the bug fixes would be better to be merged. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1893958 Title: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend Status in iptables package in Ubuntu: New Bug description: The change is a planned change for this development cycle and the fix has been tested as described in LP: #1887186 and https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041142.html . Changes: iptables (1.8.4-3ubuntu3) groovy; urgency=medium . * Swap alternative priority and prefer nftables backend over legacy (LP: #1887186) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1893958/+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 1882098] Re: Packagekit lets user install untrusted local packages in Bionic and Focal
Thanks for triaging and investigating this, Julian!
A fix for at least the aptcc backend would be highly appreciated -- I'd
hope the other backends will fix this on their own if they care about
it.
The point of packagekit+policykit is to enable people to do (at least
somewhat limited) stuff without explicit root access -- otherwise you'd
just give them sudo rights and be done with it. In the current
situation, granting a user the right to install ("trusted") packages
actually grants them rights to place arbitrary files in the filesystem
and execute arbitrary code (package scripts) as root, which is at the
very very least highly misleading.
I took a cursory look at the earlier apt backend written in python
(which is now deleted from the packagekit tree) and it at least looked
like it had some logic to decide whether a package can be trusted or not
so it didn't seem like checking where the package is coming from would
be unprecedented.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1882098
Title:
Packagekit lets user install untrusted local packages in Bionic and
Focal
Status in packagekit package in Ubuntu:
Triaged
Bug description:
We have packagekit configured to allow users to install trusted
packages from preconfigured repositories, but disallowed them to
install any untrusted packages.
The policykit configuration we use is following:
[tld.univ.packagekit]
Identity=unix-group:adm;
Action=org.freedesktop.packagekit.package-install;org.freedesktop.packagekit.package-reinstall;org.freedesktop.packagekit.package-remove;org.freedesktop.packagekit.system-sources-refresh;org.freedesktop.packagekit.system-update;org.freedesktop.packagekit.repair-system;
ResultAny=auth_self
ResultActive=auth_self
ResultInactive=auth_self
[tld.univ.packagekit-deny]
Identity=unix-user:*;
Action=org.freedesktop.packagekit.package-install-untrusted;
ResultAny=no
We would expect this to prevent users from installing local packages
downloaded from random repositories, however this does not seem to be
the case.
pkcon install-local random_package.deb will happily prompt for the
user to authenticate and will install the package, while pkcon
--allow-untrusted install-local random_package.deb will prompt for
root password, which the user does not have.
Our initial toughts was that the issue would be in packagekitd, but
after further investigations it looks like the issue could be in aptcc
backend.
We are more than happy to provide you with further details, but the
above should be enough to reproduce the issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1882098/+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 431166] Re: karmic gdm restarts X infinitely when video driver fails to load
** Changed in: gdm (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/431166 Title: karmic gdm restarts X infinitely when video driver fails to load Status in gdm: Invalid Status in gdm package in Ubuntu: Won't Fix Status in upstart package in Ubuntu: Invalid Status in gdm source package in Karmic: Won't Fix Status in upstart source package in Karmic: Invalid Bug description: Binary package hint: gdm If Xorg is misconfigured in a way that prevents the video driver from loading, such as this /etc/X11/xorg.conf: Section "Device" Identifier "Default Device" Driver "drunk" EndSection (or, more realistically, if you’re using a proprietary driver that failed to compile for the current kernel), then gdm will respawn X repeatedly, many times per second, forever. When this happens, it is nearly impossible to log into the console to stop gdm, because you cannot tell which characters of your password made it into the password prompt while the screen was flickering wildly. So if you want to test this, make sure you have an open console root shell with ‘stop gdm’ ready to execute. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/431166/+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 677067] Re: No subwoofer and frontcenter with 5.1 soundblaster x-fi
Moved to bug 1894047.
--
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/677067
Title:
No subwoofer and frontcenter with 5.1 soundblaster x-fi
Status in pulseaudio package in Ubuntu:
Expired
Bug description:
Binary package hint: pulseaudio
When I select 5.1 analog output I get no sound whatsoever out of the
subwoofer and front center speakers. These to speakers never emit sound in
linux (they do in windows), no matter what setting I try.
Also the input (for microphone) does not work... no sound is registering. I
do not even get (static) noise when inserting the mini-jack...
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: XFi [Creative X-Fi], device 0: ctxfi [Front/WaveIn]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: wouterd1818 F pulseaudio
/dev/snd/seq:timidity 1638 F timidity
Card0.Amixer.info:
Card hw:0 'XFi'/'Creative X-Fi 20K1 SB073x'
Mixer name : '20K1'
Components : ''
Controls : 29
Simple ctrls : 10
Date: Thu Nov 18 17:15:45 2010
EcryptfsInUse: Yes
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: pulseaudio
dmi.bios.date: 03/09/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2104
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5B
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd03/09/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/677067/+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 431166] Re: karmic gdm restarts X infinitely when video driver fails to load
** Changed in: gdm (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/431166 Title: karmic gdm restarts X infinitely when video driver fails to load Status in gdm: Invalid Status in gdm package in Ubuntu: Incomplete Status in upstart package in Ubuntu: Invalid Status in gdm source package in Karmic: Won't Fix Status in upstart source package in Karmic: Invalid Bug description: Binary package hint: gdm If Xorg is misconfigured in a way that prevents the video driver from loading, such as this /etc/X11/xorg.conf: Section "Device" Identifier "Default Device" Driver "drunk" EndSection (or, more realistically, if you’re using a proprietary driver that failed to compile for the current kernel), then gdm will respawn X repeatedly, many times per second, forever. When this happens, it is nearly impossible to log into the console to stop gdm, because you cannot tell which characters of your password made it into the password prompt while the screen was flickering wildly. So if you want to test this, make sure you have an open console root shell with ‘stop gdm’ ready to execute. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/431166/+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 1894047] Re: No audio for middle/center/subwoofer, muted by default for Auzentech Auzen X-Fi Prelude 7.1 (Creative X-Fi 20k1 chip)
** Summary changed: - No audio for middle/center/subwoofer, muted by default for Creative X-Fi 20k1 chip + No audio for middle/center/subwoofer, muted by default for Auzentech Auzen X-Fi Prelude 7.1 (Creative X-Fi 20k1 chip) -- 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/1894047 Title: No audio for middle/center/subwoofer, muted by default for Auzentech Auzen X-Fi Prelude 7.1 (Creative X-Fi 20k1 chip) Status in pulseaudio package in Ubuntu: New Bug description: With X.1 surround configurations only middle/center/subwoofer channel is muted by default. All other channels are ok. I need unmute with alsamixer. For Ubuntu 20.04 or any distro: I confirm that Middle/center/Subwoofer is working, when add this(Because for my card, center channel is not called Center, LFE or CLFE like other cards, but it's Center/LFE instead): [Element Center/LFE] switch = mute volume = merge override-map.1 = center,lfe To the /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf The card is Auzentech Auzen X-Fi Prelude 7.1 with Creative X-Fi 20k1 chip With this solution, there is no need to unmute middle channel. All channels have sound without edit alsamixer in terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf] Uname: Linux 5.8.5-xanmod1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: death 1194 F pulseaudio /dev/snd/controlC1: death 1194 F pulseaudio /dev/snd/controlC0: death 1194 F pulseaudio CasperMD5CheckResult: skip Date: Thu Sep 3 09:41:58 2020 InstallationDate: Installed on 2020-08-20 (13 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=bg_BG TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F21f dmi.board.asset.tag: Default string dmi.board.name: Z170-HD3 DDR3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF21f:bd03/09/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ170-HD3DDR3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170-HD3DDR3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170-HD3 DDR3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894047/+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 1894047] Re: No audio for middle/center/subwoofer, muted by default for Creative X-Fi 20k1 chip
** This bug is no longer a duplicate of bug 1894049 No audio for middle/center/subwoofer, muted by default for Creative X-Fi 20k1 chip -- 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/1894047 Title: No audio for middle/center/subwoofer, muted by default for Auzentech Auzen X-Fi Prelude 7.1 (Creative X-Fi 20k1 chip) Status in pulseaudio package in Ubuntu: New Bug description: With X.1 surround configurations only middle/center/subwoofer channel is muted by default. All other channels are ok. I need unmute with alsamixer. For Ubuntu 20.04 or any distro: I confirm that Middle/center/Subwoofer is working, when add this(Because for my card, center channel is not called Center, LFE or CLFE like other cards, but it's Center/LFE instead): [Element Center/LFE] switch = mute volume = merge override-map.1 = center,lfe To the /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf The card is Auzentech Auzen X-Fi Prelude 7.1 with Creative X-Fi 20k1 chip With this solution, there is no need to unmute middle channel. All channels have sound without edit alsamixer in terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf] Uname: Linux 5.8.5-xanmod1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: death 1194 F pulseaudio /dev/snd/controlC1: death 1194 F pulseaudio /dev/snd/controlC0: death 1194 F pulseaudio CasperMD5CheckResult: skip Date: Thu Sep 3 09:41:58 2020 InstallationDate: Installed on 2020-08-20 (13 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=bg_BG TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F21f dmi.board.asset.tag: Default string dmi.board.name: Z170-HD3 DDR3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF21f:bd03/09/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ170-HD3DDR3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170-HD3DDR3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170-HD3 DDR3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894047/+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 1894049] Re: No audio for middle/center/subwoofer, muted by default for Creative X-Fi 20k1 chip
*** This bug is a duplicate of bug 1894047 *** https://bugs.launchpad.net/bugs/1894047 ** This bug has been marked a duplicate of bug 1894047 No audio for middle/center/subwoofer, muted by default for Creative X-Fi 20k1 chip -- 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/1894049 Title: No audio for middle/center/subwoofer, muted by default for Creative X-Fi 20k1 chip Status in pulseaudio package in Ubuntu: New Bug description: With X.1 surround configurations only middle/center/subwoofer channel is muted by default. All other channels are ok. I need unmute with alsamixer. For Ubuntu 20.04 or any distro: I confirm that Middle/center/Subwoofer is working, when add this(Because for my card, center channel is not called Center, LFE or CLFE like other cards, but it's Center/LFE instead): [Element Center/LFE] switch = mute volume = merge override-map.1 = center,lfe To the /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf The card is Auzentech Auzen X-Fi Prelude 7.1 with Creative X-Fi 20k1 chip With this solution, there is no need to unmute middle channel. All channels have sound without edit alsamixer in terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf] Uname: Linux 5.8.5-xanmod1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: death 129309 F pulseaudio /dev/snd/controlC1: death 129309 F pulseaudio /dev/snd/controlC0: death 129309 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 3 10:07:53 2020 InstallationDate: Installed on 2020-08-20 (13 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F21f dmi.board.asset.tag: Default string dmi.board.name: Z170-HD3 DDR3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF21f:bd03/09/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ170-HD3DDR3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170-HD3DDR3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170-HD3 DDR3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894049/+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 1894047] Re: No audio for middle/center/subwoofer, muted by default for Creative X-Fi 20k1 chip
** This bug has been marked a duplicate of bug 1894049 No audio for middle/center/subwoofer, muted by default for Creative X-Fi 20k1 chip -- 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/1894047 Title: No audio for middle/center/subwoofer, muted by default for Auzentech Auzen X-Fi Prelude 7.1 (Creative X-Fi 20k1 chip) Status in pulseaudio package in Ubuntu: New Bug description: With X.1 surround configurations only middle/center/subwoofer channel is muted by default. All other channels are ok. I need unmute with alsamixer. For Ubuntu 20.04 or any distro: I confirm that Middle/center/Subwoofer is working, when add this(Because for my card, center channel is not called Center, LFE or CLFE like other cards, but it's Center/LFE instead): [Element Center/LFE] switch = mute volume = merge override-map.1 = center,lfe To the /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf The card is Auzentech Auzen X-Fi Prelude 7.1 with Creative X-Fi 20k1 chip With this solution, there is no need to unmute middle channel. All channels have sound without edit alsamixer in terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf] Uname: Linux 5.8.5-xanmod1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: death 1194 F pulseaudio /dev/snd/controlC1: death 1194 F pulseaudio /dev/snd/controlC0: death 1194 F pulseaudio CasperMD5CheckResult: skip Date: Thu Sep 3 09:41:58 2020 InstallationDate: Installed on 2020-08-20 (13 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=bg_BG TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F21f dmi.board.asset.tag: Default string dmi.board.name: Z170-HD3 DDR3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF21f:bd03/09/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ170-HD3DDR3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170-HD3DDR3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170-HD3 DDR3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894047/+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 1894047] Re: No audio for middle/center/subwoofer, muted by default for Creative X-Fi 20k1 chip
*** This bug is a duplicate of bug 1894049 *** https://bugs.launchpad.net/bugs/1894049 The pacmd list have output, but there is showing: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. -- 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/1894047 Title: No audio for middle/center/subwoofer, muted by default for Creative X-Fi 20k1 chip Status in pulseaudio package in Ubuntu: New Bug description: With X.1 surround configurations only middle/center/subwoofer channel is muted by default. All other channels are ok. I need unmute with alsamixer. For Ubuntu 20.04 or any distro: I confirm that Middle/center/Subwoofer is working, when add this(Because for my card, center channel is not called Center, LFE or CLFE like other cards, but it's Center/LFE instead): [Element Center/LFE] switch = mute volume = merge override-map.1 = center,lfe To the /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf The card is Auzentech Auzen X-Fi Prelude 7.1 with Creative X-Fi 20k1 chip With this solution, there is no need to unmute middle channel. All channels have sound without edit alsamixer in terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf] Uname: Linux 5.8.5-xanmod1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: death 1194 F pulseaudio /dev/snd/controlC1: death 1194 F pulseaudio /dev/snd/controlC0: death 1194 F pulseaudio CasperMD5CheckResult: skip Date: Thu Sep 3 09:41:58 2020 InstallationDate: Installed on 2020-08-20 (13 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=bg_BG TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F21f dmi.board.asset.tag: Default string dmi.board.name: Z170-HD3 DDR3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF21f:bd03/09/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ170-HD3DDR3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170-HD3DDR3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170-HD3 DDR3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1894047/+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 1894049] [NEW] No audio for middle/center/subwoofer, muted by default for Creative X-Fi 20k1 chip
Public bug reported: With X.1 surround configurations only middle/center/subwoofer channel is muted by default. All other channels are ok. I need unmute with alsamixer. For Ubuntu 20.04 or any distro: I confirm that Middle/center/Subwoofer is working, when add this(Because for my card, center channel is not called Center, LFE or CLFE like other cards, but it's Center/LFE instead): [Element Center/LFE] switch = mute volume = merge override-map.1 = center,lfe To the /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf The card is Auzentech Auzen X-Fi Prelude 7.1 with Creative X-Fi 20k1 chip With this solution, there is no need to unmute middle channel. All channels have sound without edit alsamixer in terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf] Uname: Linux 5.8.5-xanmod1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: death 129309 F pulseaudio /dev/snd/controlC1: death 129309 F pulseaudio /dev/snd/controlC0: death 129309 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 3 10:07:53 2020 InstallationDate: Installed on 2020-08-20 (13 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F21f dmi.board.asset.tag: Default string dmi.board.name: Z170-HD3 DDR3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF21f:bd03/09/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ170-HD3DDR3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170-HD3DDR3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170-HD3 DDR3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "this is showing how center channel is mutted by default with 2.1, 4.1, 5.1, 7.1 configuration" https://bugs.launchpad.net/bugs/1894049/+attachment/5407295/+files/alsamixer.png -- 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/1894049 Title: No audio for middle/center/subwoofer, muted by default for Creative X-Fi 20k1 chip Status in pulseaudio package in Ubuntu: New Bug description: With X.1 surround configurations only middle/center/subwoofer channel is muted by default. All other channels are ok. I need unmute with alsamixer. For Ubuntu 20.04 or any distro: I confirm that Middle/center/Subwoofer is working, when add this(Because for my card, center channel is not called Center, LFE or CLFE like other cards, but it's Center/LFE instead): [Element Center/LFE] switch = mute volume = merge override-map.1 = center,lfe To the /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf The card is Auzentech Auzen X-Fi Prelude 7.1 with Creative X-Fi 20k1 chip With this solution, there is no need to unmute middle channel. All channels have sound without edit alsamixer in terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf] Uname: Linux 5.8.5-xanmod1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: death 129309 F pulseaudio /dev/snd/controlC1: death 129309 F pulseaudio /dev/snd/controlC0: death 129309 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 3 10:07:53 2020 InstallationDate: Installed on 2020-08-20 (13 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F21f
[Touch-packages] [Bug 1894047] [NEW] No audio for middle/center/subwoofer, muted by default for Creative X-Fi 20k1 chip
Public bug reported: With X.1 surround configurations only middle/center/subwoofer channel is muted by default. All other channels are ok. I need unmute with alsamixer. For Ubuntu 20.04 or any distro: I confirm that Middle/center/Subwoofer is working, when add this(Because for my card, center channel is not called Center, LFE or CLFE like other cards, but it's Center/LFE instead): [Element Center/LFE] switch = mute volume = merge override-map.1 = center,lfe To the /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf The card is Auzentech Auzen X-Fi Prelude 7.1 with Creative X-Fi 20k1 chip With this solution, there is no need to unmute middle channel. All channels have sound without edit alsamixer in terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf] Uname: Linux 5.8.5-xanmod1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: death 1194 F pulseaudio /dev/snd/controlC1: death 1194 F pulseaudio /dev/snd/controlC0: death 1194 F pulseaudio CasperMD5CheckResult: skip Date: Thu Sep 3 09:41:58 2020 InstallationDate: Installed on 2020-08-20 (13 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=bg_BG TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F21f dmi.board.asset.tag: Default string dmi.board.name: Z170-HD3 DDR3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF21f:bd03/09/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ170-HD3DDR3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170-HD3DDR3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z170-HD3 DDR3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "this is showing how center channel is mutted by default with 2.1, 4.1, 5.1, 7.1 configuration" https://bugs.launchpad.net/bugs/1894047/+attachment/5407289/+files/alsamixer.png -- 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/1894047 Title: No audio for middle/center/subwoofer, muted by default for Creative X-Fi 20k1 chip Status in pulseaudio package in Ubuntu: New Bug description: With X.1 surround configurations only middle/center/subwoofer channel is muted by default. All other channels are ok. I need unmute with alsamixer. For Ubuntu 20.04 or any distro: I confirm that Middle/center/Subwoofer is working, when add this(Because for my card, center channel is not called Center, LFE or CLFE like other cards, but it's Center/LFE instead): [Element Center/LFE] switch = mute volume = merge override-map.1 = center,lfe To the /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf The card is Auzentech Auzen X-Fi Prelude 7.1 with Creative X-Fi 20k1 chip With this solution, there is no need to unmute middle channel. All channels have sound without edit alsamixer in terminal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf] Uname: Linux 5.8.5-xanmod1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: death 1194 F pulseaudio /dev/snd/controlC1: death 1194 F pulseaudio /dev/snd/controlC0: death 1194 F pulseaudio CasperMD5CheckResult: skip Date: Thu Sep 3 09:41:58 2020 InstallationDate: Installed on 2020-08-20 (13 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=bg_BG TERM=xterm-256color PATH=(custom, no user) LANG=bg_BG.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio
[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones
** Changed in: alsa-driver (Ubuntu) Status: Confirmed => New -- 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/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: New Status in alsa-driver package in Arch Linux: New Status in Fedora: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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
