[Touch-packages] [Bug 1872902] Re: Upgrade to Focal now removes chrony
Testing on an Ubuntu 18.04 LTS system with ubuntu-desktop and chrony installed. bdmurray@clean-bionic-amd64:/tmp/u-r-u-proposed$ apt-cache policy chrony chrony: Installed: 3.5-6ubuntu6 Candidate: 3.5-6ubuntu6 Version table: *** 3.5-6ubuntu6 500 500 http://192.168.10.7/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status bdmurray@clean-bionic-amd64:/tmp/u-r-u-proposed$ apt-cache policy systemd-timesyncd systemd-timesyncd: Installed: (none) Candidate: 245.4-4ubuntu3 Version table: 245.4-4ubuntu3 500 500 http://192.168.10.7/ubuntu focal/main amd64 Packages bdmurray@clean-bionic-amd64:/tmp/u-r-u-proposed$ head /var/log/dist-upgrade/main.log 2020-05-06 12:26:14,373 INFO Using config files '['./DistUpgrade.cfg.bionic']' 2020-05-06 12:26:14,373 INFO uname information: 'Linux clean-bionic-amd64 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64' 2020-05-06 12:26:14,733 INFO apt version: '1.6.12' 2020-05-06 12:26:14,733 INFO python version: '3.6.9 (default, Apr 18 2020, 01:56:04) [GCC 8.4.0]' 2020-05-06 12:26:14,737 INFO release-upgrader version '20.04.19' started 2020-05-06 12:26:14,740 INFO locale: 'en_US' 'UTF-8' 2020-05-06 12:26:14,805 DEBUG Using 'DistUpgradeViewText' view 2020-05-06 12:26:14,843 DEBUG enable dpkg --force-overwrite 2020-05-06 12:26:14,870 DEBUG creating statefile: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' I had the same results with tasksel as I did with the lxc container upgrade. -- 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/1872902 Title: Upgrade to Focal now removes chrony Status in Release Notes for Ubuntu: New Status in apt package in Ubuntu: Invalid Status in chrony package in Ubuntu: Invalid Status in germinate package in Ubuntu: New Status in ntp package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Focal: Invalid Status in chrony source package in Focal: Invalid Status in germinate source package in Focal: New Status in ntp source package in Focal: Invalid Status in systemd source package in Focal: Invalid Status in ubuntu-release-upgrader source package in Focal: Fix Committed Bug description: Due to changes in systemd for bug 1849156 this issue now happens. On an upgrade for people that had chrony installed on a do-release upgrade it now will: Calculating the changes MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > FU=1 Removing: chrony MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0 That isn't what users want, those who had chrony installed would want to get chrony upgraded and systemd-timesyncd (which now is a separate pacakge) not installed. Test Case - 1) On a system running Ubuntu 19.10 or Ubuntu 18.04 LTS install the package chrony 2) Run do-release-upgrade with the appropriate switches 3) Observe that chrony is marked for deletion With the version of dist-upgrader from -proposed (accessed with the -p switch) chrony is no longer marked for deletion. Regression Potential Given that Dimitri's change is now ignoring the tasks minimal and standard (which are handled by _keepBaseMetaPkgsInstalled) we should still be cautious and test desktop upgrades and ensure that packages in those tasks are not marked for removal. Regression Test --- 1) Run do-release-upgrade on an Ubuntu 19.10 or Ubuntu 18.04 LTS system 2) Record the list of packages marked for removal Compare the list of packages marked for removal with the release- upgrader from -proposed from Focal. Original Description I'd ask you to revise the dependencies that got changes in systemd 245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays installed as that was an opt-in chances are quite high people would want to keep it that way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
Attached is the output from journalctl -b 0, where the error occurs. Apologies - no vagrant skills here, but I can confirm Kai's replication method - kvm qemu clean 20.04 server install, then add pulseaudio, docker.io, reboot and the issue occurs. ** Attachment added: "20.04 boot log showing rtkit-daemon failing to enable RT scheduling." https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+attachment/5367552/+files/ubuntu-20.04-server-rtkit-failing-bootlog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in rtkit package in Ubuntu: Confirmed Bug description: These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+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 1877194] Re: Selected audio output device not persistent between reboots (Resets to USB-device)
** Description changed: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 - Only difference is that it does not reset to and HDMI output, but to one - of my USB-outputs. It does not respect the change I made after reboot. + Only difference is that it does not reset to HDMI output, but to one of + my USB-outputs. It does not respect the change I made after reboot. (Notice that I swapped out my username with $USER in the text below) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: $USER 1604 F pulseaudio /dev/snd/controlC0: $USER 1604 F pulseaudio /dev/snd/controlC1: $USER 1604 F pulseaudio /dev/snd/pcmC1D0c: $USER 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 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: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- 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/1877194 Title: Selected audio output device not persistent between reboots (Resets to USB-device) Status in pulseaudio package in Ubuntu: New Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. (Notice that I swapped out my username with $USER in the text below) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: $USER 1604 F pulseaudio /dev/snd/controlC0: $USER 1604 F pulseaudio /dev/snd/controlC1: $USER 1604 F pulseaudio /dev/snd/pcmC1D0c: $USER 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 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: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1877194/+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 1872564] Re: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice
The missing rule for boot_id was added to Apparmor 2.13 (https://gitlab.com/apparmor/apparmor/-/blob/apparmor-2.13/profiles/apparmor.d/abstractions/nameservice#L35) and was later refined in the master branch. As such, marking as fix committed. ** Changed in: apparmor (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1872564 Title: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice Status in apparmor package in Ubuntu: Fix Committed Bug description: # Description On a default Focal install, systemd is used when looking up passwd and group information: # grep systemd /etc/nsswitch.conf passwd: files systemd group: files systemd Daemons confined by Apparmor that also query those "databases" will cause this Apparmor denial: audit: type=1400 audit(1586825456.411:247): apparmor="DENIED" operation="open" namespace="root//lxd-fb1_" profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=7370 comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 Many daemons confined by Apparmor also happen to downgrade their privileges so they always end up looking up user/group information. # Steps to reproduce 1) launch a Focal container (named fb1 here) $ lxc launch images:ubuntu/focal fb1 2) setup apparmor inside the container (already done on official Ubuntu images) $ lxc exec fb1 -- apt update && lxc exec fb1 -- apt install apparmor -y 3) install bind9 $ lxc exec fb1 -- apt install bind9 -y 4) check kernel logs for DENIED $ journalctl -o cat -b0 -k | grep 'apparmor="DENIED"' | grep -F 'profile="/usr/sbin/named"' Step 4, should not return anything. Because systemd is involved in the user/group lookups, it currently returns the following: audit: type=1400 audit(1586826072.115:266): apparmor="DENIED" operation="open" namespace="root//lxd-fb1_" profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 audit: type=1400 audit(1586826072.115:267): apparmor="DENIED" operation="open" namespace="root//lxd-fb1_" profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 audit: type=1400 audit(1586826072.115:268): apparmor="DENIED" operation="open" namespace="root//lxd-fb1_" profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 audit: type=1400 audit(1586826072.115:269): apparmor="DENIED" operation="open" namespace="root//lxd-fb1_" profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 audit: type=1400 audit(1586826072.115:270): apparmor="DENIED" operation="open" namespace="root//lxd-fb1_" profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id" pid=13756 comm="named" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 # Workaround 1) remove systemd from nsswitch.conf $ lxc exec fb1 -- sed -i 's/ systemd$/ # systemd/' /etc/nsswitch.conf 2) restart named $ lxc exec fb1 -- service named restart 3) notice no more denials in kernel logs # Additional information root@fb1:~# apt-cache policy apparmor apparmor: Installed: 2.13.3-7ubuntu4 Candidate: 2.13.3-7ubuntu4 Version table: *** 2.13.3-7ubuntu4 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@fb1:~# uname -a Linux fb1 5.3.0-46-generic #38~18.04.1-Ubuntu SMP Tue Mar 31 04:17:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@fb1:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1872564/+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 1862232] Re: Long hostname causes networking setup to fail
on xenial, additional fix is needed for bug 1877176 for complete fix for this bug, but this patch introduces no regressions and allows networkd to continue requesting the lease for invalid hostnames. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- 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/1862232 Title: Long hostname causes networking setup to fail Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Bionic: Fix Committed Bug description: [impact] networkd fails to bring up networking on systems with long hostname [test case] setting the hostname: $ sudo hostnamectl set-hostname asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf then reboot and check the networking. [regression potential] as this adjusts logging and certain error handling while performing dhcp, any regression would likely cause dhcp failure. [scope] this is fixed by upstream commit a8494759b4f14af5337391727ba295ab708b92f9 (along with some associated commits around it), which is included starting in v240, so this is included already in Eoan and later. This is needed in Bionic and Xenial. [other info] the problem around this is that Linux sets HOST_NAME_MAX to 64, but RFC 1035 limits DNS labels to 63 characters, so any host with a max- length single-label hostname (i.e. a 64 character hostname with no dots) will be "valid" from Linux's perspective, but will violate RFC 1035 and thus systemd will consider it invalid and won't pass it to the dhcp server. Also note that a 64-character hostname that is *not* single-label (i.e. a hostname with at least 1 dot) will not cause this problem. The systemd patches continue to reject sending the invalid hostname to the dhcp server, but do not prevent networkd from finishing setting up networking. [original description] 1) ubuntu version # lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 2) package version # apt-cache policy systemd systemd: Installed: 237-3ubuntu10.31 Candidate: 237-3ubuntu10.31 Version table: *** 237-3ubuntu10.31 500 500 http://mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 Packag es 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://mirrors.digitalocean.com/ubuntu bionic/main amd64 Packages 3) I expect the network to come online correctly regardless of how long the hostname is. This is what happens with both 14.0 and 19.0 (I tested the same behavior with both of them). 4) the external network interface fails to be configured and is stuck in a (pending) state as reported by networkctl status -a setting the hostname: # hostnamectl set-hostname asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf after rebooting the machine, it no longer has network access. # journalctl Feb 06 19:29:41 asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd[1]: Starting Wait for Network to be Configured... Feb 06 19:29:41 asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd-networkd[605]: eth0: Link state is up-to-date Feb 06 19:29:41 asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd-networkd[605]: eth0: found matching network '/run/systemd/network/10-netplan-eth0.network' Feb 06 19:29:41 asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd-networkd[605]: sd-netlink: callback failed: Invalid argument Feb 06 19:29:41 asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd-networkd[605]: lo: Link state is up-to-date # networkctl status -a: ● 1: lo Link File: /lib/systemd/network/99-default.link Network File: n/a Type: loopback State: carrier (unmanaged) Address: 127.0.0.1 ::1 ● 2: eth0 Link File: /run/systemd/network/10-netplan-eth0.link Network File: /run/systemd/network/10-netplan-eth0.network Type: ether State: off (pending) Path: pci-:00:03.0 Driver: virtio_net Vendor: Red Hat, Inc. Model: Virtio network device HW Address: ae:4d:91:1c:e8:86 DNS: 67.207.67.3 67.207.67.2 and to bring up the network correctly, set the hostname to something shorter # hostnamectl set-hostname asdf # systemctl restart systemd-networkd # networkctl status -a ● 1: lo Link File:
[Touch-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
seems like from the other bug that it got turn off again in -26.30 which is the revision in use by the report here according to the apport report? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in rtkit package in Ubuntu: Confirmed Bug description: These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+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 1776654] Re: systemd upstream sysusers tests fails
This was fixed in Debian at version 244.2-1, which is earlier than the version in focal, so this is fix released for focal. ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1776654 Title: systemd upstream sysusers tests fails Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Fix Committed Status in linux source package in Focal: Invalid Status in systemd source package in Focal: Fix Released Bug description: [impact] TEST-21-SYSUSERS autopkgtest fails [test case] see original description [regression potential] any regression would be limited to incorrect pass/fail of TEST-21-SYSUSERS [scope] TEST-21-SYSUSERS does not exist in Xenial, it is first contained in Bionic. This is needed for B, E, and F. [original description] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-cosmic-canonical-kernel-team- bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz == TEST-21-SYSUSERS == make: Entering directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' TEST CLEANUP: Sysuser-related tests TEST SETUP: Sysuser-related tests TEST RUN: Sysuser-related tests *** Running test-1.input *** Running test-2.input *** Running test-3.input *** Running test-4.input *** Running test unhappy-1.input --- /var/tmp/systemd-test.TjNA7s/tmp/err 2018-06-13 00:22:12.805061468 + +++ unhappy-1.expected-err2018-01-28 15:58:17.0 + @@ -1 +1 @@ -Creating user xxx (n/a) with uid 312 and gid 310. +Failed to parse UID: '99': Numerical result out of range Unexpected error output for unhappy-1.input Creating user xxx (n/a) with uid 312 and gid 310. make: *** [run] Error 1 Makefile:4: recipe for target 'run' failed make: Leaving directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' FAILED TESTS: test/TEST-21-SYSUSERS autopkgtest [00:22:13]: test upstream: ---] upstream FAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776654/+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 1877181] Re: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1877181 Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Happening while trying to upgrade from 18.04 to 20.04. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 6 14:26:11 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-03-10 (2249 days ago) InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) PackageArchitecture: all 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.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1877181/+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 1877181] [NEW] package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: Happening while trying to upgrade from 18.04 to 20.04. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 6 14:26:11 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-03-10 (2249 days ago) InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) PackageArchitecture: all 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.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-06 (0 days ago) ** Affects: initramfs-tools (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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1877181 Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Happening while trying to upgrade from 18.04 to 20.04. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 6 14:26:11 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-03-10 (2249 days ago) InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) PackageArchitecture: all 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.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1877181/+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 1870811] Re: compile auto test failure, and root-unittest failure, is extremely noisy
no build failures to verify this bug with, but manually adding build test failure shows both bionic and eoan correctly display the build test failure summary: bionic: OK: 233 FAIL: 1 SKIP: 20 TIMEOUT:0 The output from the failed tests: 50/254 test-networkFAIL 0.79 s --- command --- SYSTEMD_KBD_MODEL_MAP='/build/lp1870811/systemd-237/src/locale/kbd-model-map' SYSTEMD_LANGUAGE_FALLBACK_MAP='/build/lp1870811/systemd-237/src/locale/language-fallback-map' PATH='/build/lp1870811/systemd-237/build-deb:/home/ubuntu/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin' /build/lp1870811/systemd-237/build-deb/test-network --- stderr --- Assertion '1 == 0' failed at ../src/network/test-network.c:65, function test_deserialize_dhcp_routes(). Aborting. --- eoan: Ok: 505 Expected Fail: 0 Fail: 1 Unexpected Pass: 0 Skipped: 13 Timeout: 0 The output from the failed tests: 284/519 test-networkFAIL 0.62 s (killed by signal 6 SIGABRT) --- command --- SYSTEMD_KBD_MODEL_MAP='/build/lp1870811/systemd-242/src/locale/kbd-model-map' SYSTEMD_LANGUAGE_FALLBACK_MAP='/build/lp1870811/systemd-242/src/locale/language-fallback-map' PATH='/build/lp1870811/systemd-242/build-deb:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin' /build/lp1870811/systemd-242/build-deb/test-network --- stderr --- Assertion '1 == 0' failed at ../src/network/test-network.c:49, function test_deserialize_dhcp_routes(). Aborting. --- ** Tags removed: verification-needed verification-needed-bionic verification-needed-eoan ** Tags added: verification-done verification-done-bionic verification-done-eoan -- 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/1870811 Title: compile auto test failure, and root-unittest failure, is extremely noisy Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Won't Fix Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Eoan: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [impact] failure in the compile-time tests (also run from the root-unittest autopkgtest) prints out the entire meson testlog.txt, which shows the output of all tests, including passed ones, not just the failed test output. This makes it extremely difficult to find the output of the failed test(s) and creates a massive log to download. [test case] see any failed build, e.g. https://launchpadlibrarian.net/471257226/buildlog_ubuntu-eoan-amd64.systemd_245.218-g69d06b7acf+19.10.20200328163536_BUILDING.txt.gz [regression potential] any regression would likely occur during test failure, likely resulting in lack of details of the test failure; or, a regression caused by the additional meson parameter could cause build failure. [scope] Xenial does not use meson, so can not be adjusted. This is needed in Bionic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870811/+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 1872902] Re: Upgrade to Focal now removes chrony
I also tested upgrading an 19.10 Ubuntu desktop install with chrony installed to 20.04 LTS and chrony remained installed. bdmurray@clean-eoan-amd64:/tmp/u-r-u-proposed$ apt-cache policy chrony chrony: Installed: 3.5-6ubuntu6 Candidate: 3.5-6ubuntu6 Version table: *** 3.5-6ubuntu6 500 500 http://192.168.10.7/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status bdmurray@clean-eoan-amd64:/tmp/u-r-u-proposed$ apt-cache policy systemd-timesyncd systemd-timesyncd: Installed: (none) Candidate: 245.4-4ubuntu3 Version table: 245.4-4ubuntu3 500 500 http://192.168.10.7/ubuntu focal/main amd64 Packages bdmurray@clean-eoan-amd64:/tmp/u-r-u-proposed$ head /var/log/dist-upgrade/main.log 2020-05-06 11:12:55,719 INFO Using config files '['./DistUpgrade.cfg']' 2020-05-06 11:12:55,719 INFO uname information: 'Linux clean-eoan-amd64 5.3.0-51-generic #44-Ubuntu SMP Wed Apr 22 21:09:44 UTC 2020 x86_64' 2020-05-06 11:12:56,050 INFO apt version: '1.9.4' 2020-05-06 11:12:56,051 INFO python version: '3.7.5 (default, Apr 19 2020, 20:18:17) [GCC 9.2.1 20191008]' 2020-05-06 11:12:56,053 INFO release-upgrader version '20.04.19' started 2020-05-06 11:12:56,056 INFO locale: 'en_US' 'UTF-8' 2020-05-06 11:12:56,118 DEBUG Using 'DistUpgradeViewText' view 2020-05-06 11:12:56,151 DEBUG enable dpkg --force-overwrite 2020-05-06 11:12:56,182 DEBUG creating statefile: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1872902 Title: Upgrade to Focal now removes chrony Status in Release Notes for Ubuntu: New Status in apt package in Ubuntu: Invalid Status in chrony package in Ubuntu: Invalid Status in germinate package in Ubuntu: New Status in ntp package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Focal: Invalid Status in chrony source package in Focal: Invalid Status in germinate source package in Focal: New Status in ntp source package in Focal: Invalid Status in systemd source package in Focal: Invalid Status in ubuntu-release-upgrader source package in Focal: Fix Committed Bug description: Due to changes in systemd for bug 1849156 this issue now happens. On an upgrade for people that had chrony installed on a do-release upgrade it now will: Calculating the changes MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > FU=1 Removing: chrony MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0 That isn't what users want, those who had chrony installed would want to get chrony upgraded and systemd-timesyncd (which now is a separate pacakge) not installed. Test Case - 1) On a system running Ubuntu 19.10 or Ubuntu 18.04 LTS install the package chrony 2) Run do-release-upgrade with the appropriate switches 3) Observe that chrony is marked for deletion With the version of dist-upgrader from -proposed (accessed with the -p switch) chrony is no longer marked for deletion. Regression Potential Given that Dimitri's change is now ignoring the tasks minimal and standard (which are handled by _keepBaseMetaPkgsInstalled) we should still be cautious and test desktop upgrades and ensure that packages in those tasks are not marked for removal. Regression Test --- 1) Run do-release-upgrade on an Ubuntu 19.10 or Ubuntu 18.04 LTS system 2) Record the list of packages marked for removal Compare the list of packages marked for removal with the release- upgrader from -proposed from Focal. Original Description I'd ask you to revise the dependencies that got changes in systemd 245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays installed as that was an opt-in chances are quite high people would want to keep it that way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1803601] Re: motd-news.service scheduled even when /etc/update-motd.d/50-motd-news is not executable
There are many alternatives here. What you describe is one, and you could then also add a systemd override with that exec check. A bit cumbersome, though. Another one is specific to this service, and that is to set ENABLED=0 in /etc/default/motd-news. I think fixing this doesn't warrant an SRU, but should be considered for the devel release of ubuntu (groovy at the moment). ** Changed in: base-files (Ubuntu) Status: New => Triaged -- 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/1803601 Title: motd-news.service scheduled even when /etc/update-motd.d/50-motd-news is not executable Status in base-files package in Ubuntu: Triaged Bug description: update-motd(5) says: Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as the root user at each login, and this information is concatenated in /run/motd.dynamic. The order of script execu‐ tion is determined by the run-parts(8) --lsbsysinit option (basically alphabetical order, with a few caveats). So sysadmins are used to "chmod -x" motd fragments from /etc/update- motd.d/ to prevent their execution. When doing so for /etc/update- motd.d/50-motd-news, I noticed that motd-news.timer was still trying to execute the motd-news.service unit which then logged a failure: systemd[3704]: motd-news.service: Failed to execute command: Permission denied systemd[3704]: motd-news.service: Failed at step EXEC spawning /etc/update-motd.d/50-motd-news: Permission denied systemd[1]: motd-news.service: Main process exited, code=exited, status=203/EXEC systemd[1]: motd-news.service: Failed with result 'exit-code'. systemd[1]: Failed to start Message of the Day. The motd-news.service unit looks like this: $ systemctl cat motd-news.service # /lib/systemd/system/motd-news.service [Unit] Description=Message of the Day After=network-online.target Documentation=man:update-motd(8) [Service] Type=oneshot ExecStart=/etc/update-motd.d/50-motd-news --force This problem was observed on a Bionic system: $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy base-files base-files: Installed: 10.1ubuntu2.3 Candidate: 10.1ubuntu2.3 Version table: *** 10.1ubuntu2.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 10.1ubuntu2.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 10.1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages But the problem also exist in Disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1803601/+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 1872902] Re: Upgrade to Focal now removes chrony
Testing in an Ubuntu 18.04 LTS lxc container. root@bionic:/tmp/u-r-u-proposed# apt-cache policy chrony chrony: Installed: 3.5-6ubuntu6 Candidate: 3.5-6ubuntu6 Version table: *** 3.5-6ubuntu6 500 500 http://192.168.10.7/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@bionic:/tmp/u-r-u-proposed# apt-cache policy systemd-timesyncd systemd-timesyncd: Installed: (none) Candidate: 245.4-4ubuntu3 Version table: 245.4-4ubuntu3 500 500 http://192.168.10.7/ubuntu focal/main amd64 Packages root@bionic:/tmp/u-r-u-proposed# head /var/log/dist-upgrade/main.log 2020-05-06 18:53:45,805 INFO Using config files '['./DistUpgrade.cfg.bionic']' 2020-05-06 18:53:45,805 INFO uname information: 'Linux bionic 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64' 2020-05-06 18:53:46,054 INFO apt version: '1.6.12' 2020-05-06 18:53:46,054 INFO python version: '3.6.9 (default, Apr 18 2020, 01:56:04) [GCC 8.4.0]' 2020-05-06 18:53:46,058 INFO release-upgrader version '20.04.19' started 2020-05-06 18:53:46,063 WARNING can't import view 'DistUpgradeViewGtk3' (Namespace Vte not available) 2020-05-06 18:53:46,104 WARNING can't import view 'DistUpgradeViewKDE' (No module named 'PyQt4') Additionally, I ran 'tasksel install standard' and 'tasksel install minimal' to ensure that no packages in either task were removed and none were. (Although doing that installed systemd-timesyncd.) -- 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/1872902 Title: Upgrade to Focal now removes chrony Status in Release Notes for Ubuntu: New Status in apt package in Ubuntu: Invalid Status in chrony package in Ubuntu: Invalid Status in germinate package in Ubuntu: New Status in ntp package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Focal: Invalid Status in chrony source package in Focal: Invalid Status in germinate source package in Focal: New Status in ntp source package in Focal: Invalid Status in systemd source package in Focal: Invalid Status in ubuntu-release-upgrader source package in Focal: Fix Committed Bug description: Due to changes in systemd for bug 1849156 this issue now happens. On an upgrade for people that had chrony installed on a do-release upgrade it now will: Calculating the changes MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > FU=1 Removing: chrony MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0 That isn't what users want, those who had chrony installed would want to get chrony upgraded and systemd-timesyncd (which now is a separate pacakge) not installed. Test Case - 1) On a system running Ubuntu 19.10 or Ubuntu 18.04 LTS install the package chrony 2) Run do-release-upgrade with the appropriate switches 3) Observe that chrony is marked for deletion With the version of dist-upgrader from -proposed (accessed with the -p switch) chrony is no longer marked for deletion. Regression Potential Given that Dimitri's change is now ignoring the tasks minimal and standard (which are handled by _keepBaseMetaPkgsInstalled) we should still be cautious and test desktop upgrades and ensure that packages in those tasks are not marked for removal. Regression Test --- 1) Run do-release-upgrade on an Ubuntu 19.10 or Ubuntu 18.04 LTS system 2) Record the list of packages marked for removal Compare the list of packages marked for removal with the release- upgrader from -proposed from Focal. Original Description I'd ask you to revise the dependencies that got changes in systemd 245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays installed as that was an opt-in chances are quite high people would want to keep it that way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1818548] Re: namei -l incorrect error message
Yay, this appears to have been fixed in focal: $ namei -l /etc/ssl/private/ssl-cert-snakeoil.key f: /etc/ssl/private/ssl-cert-snakeoil.key drwxr-xr-x root root / drwxr-xr-x root root etc drwxr-xr-x root root ssl drwx--x--- root ssl-cert private ssl-cert-snakeoil.key - Permission denied -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1818548 Title: namei -l incorrect error message Status in util-linux package in Ubuntu: New Bug description: Hello, namei -l gives incorrect error messages if a directory is not readable: $ namei -l /etc/ssl/private/ssl-cert-snakeoil.key f: /etc/ssl/private/ssl-cert-snakeoil.key drwxr-xr-x root root / drwxr-xr-x root root etc drwxr-xr-x root root ssl drwx--x--- root ssl-cert private ssl-cert-snakeoil.key - No such file or directory $ cat /etc/ssl/private/ssl-cert-snakeoil.key cat: /etc/ssl/private/ssl-cert-snakeoil.key: Permission denied $ ls -l /etc/ssl/private/ ls: cannot open directory '/etc/ssl/private/': Permission denied "No such file or directory" is a poor error message for this case. The correct error message (as shown by cat) is "Permission denied". Incorrect error messages make this tool much less useful. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: util-linux 2.31.1-0.4ubuntu3.3 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Mar 4 09:00:12 2019 InstallationDate: Installed on 2012-10-18 (2328 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: Upgraded to bionic on 2018-05-02 (306 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1818548/+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 1877176] [NEW] 64-char hostname causes dhcp server to reject lease
Public bug reported: [impact] a systemd with a 64-character hostname (the maximum hostname length for Linux) will cause a dhcp server to reject its dhcp lease due to passing the invalid hostname in the dhcp lease request. [test case] $ cat /etc/systemd/network/10-ens3.network [Match] Name=ens3 [Network] DHCP=yes set hostname to 64-char name, e.g.: $ sudo hostnamectl set-hostname a123456789b123456789c123456789d123456789e123456789f123456789g123 restart networkd: $ sudo systemctl restart systemd-networkd check logs: root@a123456789b123456789c123456789d123456789e123456789f123456789g123:~# journalctl -b -u systemd-networkd --no-pager | grep 'DHCP error' May 06 19:01:30 a123456789b123456789c123456789d123456789e123456789f123456789g123 systemd-networkd[737]: ens3: DHCP error: Client failed: Invalid argument [scope] this is fixed by commit 9740eae694e93b06658ff3b3045b22b591561e7c which is included in Bionic and later. This is needed only for Xenial. [other info] this is a follow on to bug 1862232, which corrected sd-dhcp-client.c to continue networkd dhcp even if the hostname is invalid, however the older code in Xenial doesn't correctly detect the invalid hostname, so this additional patch is needed. ** Affects: systemd (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: systemd (Ubuntu Xenial) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress -- 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/1877176 Title: 64-char hostname causes dhcp server to reject lease Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Bug description: [impact] a systemd with a 64-character hostname (the maximum hostname length for Linux) will cause a dhcp server to reject its dhcp lease due to passing the invalid hostname in the dhcp lease request. [test case] $ cat /etc/systemd/network/10-ens3.network [Match] Name=ens3 [Network] DHCP=yes set hostname to 64-char name, e.g.: $ sudo hostnamectl set-hostname a123456789b123456789c123456789d123456789e123456789f123456789g123 restart networkd: $ sudo systemctl restart systemd-networkd check logs: root@a123456789b123456789c123456789d123456789e123456789f123456789g123:~# journalctl -b -u systemd-networkd --no-pager | grep 'DHCP error' May 06 19:01:30 a123456789b123456789c123456789d123456789e123456789f123456789g123 systemd-networkd[737]: ens3: DHCP error: Client failed: Invalid argument [scope] this is fixed by commit 9740eae694e93b06658ff3b3045b22b591561e7c which is included in Bionic and later. This is needed only for Xenial. [other info] this is a follow on to bug 1862232, which corrected sd-dhcp-client.c to continue networkd dhcp even if the hostname is invalid, however the older code in Xenial doesn't correctly detect the invalid hostname, so this additional patch is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877176/+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 1877182] [NEW] Blank screen timer does not work
Public bug reported: It just does not work if I set it to never or to 15 MIN it does not work it is stuck at one min ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 6 22:43:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1d3d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1d3d] InstallationDate: Installed on 2020-05-02 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b3fd Chicony Electronics Co., Ltd HD WebCam (Asus N-series) Bus 001 Device 005: ID 0b05:17ac ASUSTek Computer, Inc. ASUS Laser GAMING MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. G551VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7fb860e1-6845-4a22-9fde-4c8435d52aba ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G551VW.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G551VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG551VW.209:bd02/19/2016:svnASUSTeKCOMPUTERINC.:pnG551VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG551VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: G dmi.product.name: G551VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877182 Title: Blank screen timer does not work Status in xorg package in Ubuntu: New Bug description: It just does not work if I set it to never or to 15 MIN it does not work it is stuck at one min ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 6 22:43:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel
[Touch-packages] [Bug 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable
*** This bug is a duplicate of bug 1872778 *** https://bugs.launchpad.net/bugs/1872778 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-online-accounts (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1866974 Title: The Diffie-Hellman prime sent by the server is not acceptable Status in evolution package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: I can no longer connect to my ISP mail server. Works in previous version 19.10 "The reported error was “Failed to get capabilities: Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough).”." I've tried finding a workaround but so far no luck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evolution 3.35.92-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 11:07:01 2020 InstallationDate: Installed on 2020-03-03 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+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 1877183] [NEW] segfault in mysql_server_end() from libmysqlclient.so.21
Public bug reported: libmysqlclient.so.21 causes a segfault on shutdown. Test case attached ==> "Removed database" will not be reported. Backtrace: #0 0x714c330f in ?? () from /lib/x86_64-linux-gnu/libmysqlclient.so.21 #1 0x714c8823 in ?? () from /lib/x86_64-linux-gnu/libmysqlclient.so.21 #2 0x71466243 in mysql_server_end () from /lib/x86_64-linux-gnu/libmysqlclient.so.21 #3 0x71b4d0ee in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/sqldrivers/libqsqlmysql.so #4 0x71b4d10d in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/sqldrivers/libqsqlmysql.so #5 0x778e55fb in ?? () from /lib/x86_64-linux-gnu/libQt5Sql.so.5 #6 0x778e588e in QSqlDatabase::~QSqlDatabase() () from /lib/x86_64-linux-gnu/libQt5Sql.so.5 #7 0x778e5d9c in ?? () from /lib/x86_64-linux-gnu/libQt5Sql.so.5 #8 0x5579 in cause_segfault () at main.cpp:16 #9 0x5729 in main (argc=1, argv=0x7fffeb18) at main.cpp:23 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libqt5sql5-mysql 5.12.8+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed May 6 21:40:58 2020 InstallationDate: Installed on 2020-04-27 (9 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Test case" https://bugs.launchpad.net/bugs/1877183/+attachment/5367528/+files/main.cpp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1877183 Title: segfault in mysql_server_end() from libmysqlclient.so.21 Status in qtbase-opensource-src package in Ubuntu: New Bug description: libmysqlclient.so.21 causes a segfault on shutdown. Test case attached ==> "Removed database" will not be reported. Backtrace: #0 0x714c330f in ?? () from /lib/x86_64-linux-gnu/libmysqlclient.so.21 #1 0x714c8823 in ?? () from /lib/x86_64-linux-gnu/libmysqlclient.so.21 #2 0x71466243 in mysql_server_end () from /lib/x86_64-linux-gnu/libmysqlclient.so.21 #3 0x71b4d0ee in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/sqldrivers/libqsqlmysql.so #4 0x71b4d10d in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/sqldrivers/libqsqlmysql.so #5 0x778e55fb in ?? () from /lib/x86_64-linux-gnu/libQt5Sql.so.5 #6 0x778e588e in QSqlDatabase::~QSqlDatabase() () from /lib/x86_64-linux-gnu/libQt5Sql.so.5 #7 0x778e5d9c in ?? () from /lib/x86_64-linux-gnu/libQt5Sql.so.5 #8 0x5579 in cause_segfault () at main.cpp:16 #9 0x5729 in main (argc=1, argv=0x7fffeb18) at main.cpp:23 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libqt5sql5-mysql 5.12.8+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed May 6 21:40:58 2020 InstallationDate: Installed on 2020-04-27 (9 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1877183/+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 1873920] Re: default vi on focal emits escape sequences unrecognized by bionic's terminal?
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: vim (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1873920 Title: default vi on focal emits escape sequences unrecognized by bionic's terminal? Status in vim package in Ubuntu: Confirmed Bug description: On ubuntu 18.04, opening the default terminal (gnome-terminal 3.28.2-1ubuntu1~18.04.1), ssh'ing to an up-to-date ubuntu 20.04 system, running 'vi', and pressing 'i' shows the unwelcome garbage ESC [>4;m. Pressing ESC emits more garbage: ESC [>4;2m Focal's default vi is provided by vim.tiny via alternatives. Oddly, when running vim.tiny by itself, or if you install vim and let it provide vi, the garbage does not appear. Evidently focal's vim.tiny is confused about what escape sequences ubu1804's Terminal accepts. TERM is xterm-256color. The problem also occurs if TERM is xterm. There is no .vimrc. If I use xterm on ubuntu 18.04, all is well. Evidently xterm accepts ESC[>4;m and gnome-terminal doesn't? I captured a session using 'script' and dumped typescript via hexdump -C. In this session, I typed i, Q, and escape. Here's an excerpt showing the end of vi's welcome message, followed by five escape sequences and then the Q I typed. The unrecognized ESC > 4;m is visible in the dump, followed by ESC[?25l (CURSOR OFF) 1070 66 61 75 6c 74 1b 5b 33 34 6d 3c 45 6e 74 65 72 |fault.[34m.[m for info on| 1090 20 74 68 69 73 1b 5b 31 3b 31 48 1b 5b 3f 32 35 | this.[1;1H.[?25| 10a0 68 1b 5b 3f 32 30 30 34 6c 1b 5b 3e 34 3b 6d 1b |h.[?2004l.[>4;m.| 10b0 5b 3f 32 35 6c 51 1b 5b 38 3b 34 37 48 1b 5b 31 |[?25lQ.[8;47H.[1| The mystery sequence ESC [ > 4;m appears to be "Set/reset key modifier options, xterm", per https://invisible-island.net/xterm/ctlseqs/ctlseqs.html. So it's trying to modify function keys, or something. ssh'ing in from a mac worked fine (TERM there was also xterm-256color), as did ssh'ing from an ubuntu 19.04 system with gnome-terminal. ssh'ing from another ubuntu 18.04 system exhibited the same problem. So it's a little family squabble between focal's vim.tiny and ubuntu 18.04/bionic's gnome-terminal...? Given how long 18.04's going to be supported, this seems worth resolving somehow. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: vim-tiny 2:8.1.2269-1ubuntu5 [modified: usr/share/vim/vim81/doc/help.txt usr/share/vim/vim81/doc/tags] ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 20 09:27:50 2020 InstallationDate: Installed on 2020-01-27 (83 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1873920/+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 1877129] Re: jackd won't run in realtime
*** This bug is a duplicate of bug 1875665 *** https://bugs.launchpad.net/bugs/1875665 ** This bug has been marked a duplicate of bug 1875665 rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1877129 Title: jackd won't run in realtime Status in jackd2 package in Ubuntu: Incomplete Bug description: Was using jackd2 for ages, never had this issue. The usual limits.conf tweaks are present. Jackd won't run in realtime even as root. It's very easy to reproduce in Focal. Before upgrade, was working: Ubuntu 18.04.4 LTS uname -r kernel 5.3.0-51-generic jackd --version jackdmp version 1.9.12 tmpdir /dev/shm protocol 8 After upgrade: Ubuntu 20.04 LTS uname -r 5.4.0-29-generic jackd --version jackdmp version 1.9.12 tmpdir /dev/shm protocol 8 Simple test: jackd -R -d dummy -r192000 -p2048 jackdmp 1.9.12 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2016 Grame. Copyright 2016-2017 Filipe Coelho. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details Cannot create RT messagebuffer thread: Operation not permitted (1) Retrying messagebuffer thread without RT scheduling Messagebuffer not realtime; consider enabling RT scheduling for user no message buffer overruns Cannot create RT messagebuffer thread: Operation not permitted (1) Retrying messagebuffer thread without RT scheduling Messagebuffer not realtime; consider enabling RT scheduling for user no message buffer overruns Cannot create RT messagebuffer thread: Operation not permitted (1) Retrying messagebuffer thread without RT scheduling Messagebuffer not realtime; consider enabling RT scheduling for user no message buffer overruns JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" Cannot use real-time scheduling (RR/10)(1: Operation not permitted) AcquireSelfRealTime error I'm guessing that it's not jack itself (package ver. seems to be the same as bionic, without new feats), smth is missing in the kernel config. I would try RT kernel, but it usually does not boot at all thanks to Nvidia blob on that system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1877129/+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 1776654] Re: systemd upstream sysusers tests fails
TEST-21 did not fail for any arch for autopkgtests on bionic and eoan. ** Tags removed: verification-needed verification-needed-bionic verification-needed-eoan ** Tags added: verification-done verification-done-bionic verification-done-eoan -- 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/1776654 Title: systemd upstream sysusers tests fails Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Fix Committed Status in linux source package in Focal: Invalid Status in systemd source package in Focal: Fix Released Bug description: [impact] TEST-21-SYSUSERS autopkgtest fails [test case] see original description [regression potential] any regression would be limited to incorrect pass/fail of TEST-21-SYSUSERS [scope] TEST-21-SYSUSERS does not exist in Xenial, it is first contained in Bionic. This is needed for B, E, and F. [original description] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-cosmic-canonical-kernel-team- bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz == TEST-21-SYSUSERS == make: Entering directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' TEST CLEANUP: Sysuser-related tests TEST SETUP: Sysuser-related tests TEST RUN: Sysuser-related tests *** Running test-1.input *** Running test-2.input *** Running test-3.input *** Running test-4.input *** Running test unhappy-1.input --- /var/tmp/systemd-test.TjNA7s/tmp/err 2018-06-13 00:22:12.805061468 + +++ unhappy-1.expected-err2018-01-28 15:58:17.0 + @@ -1 +1 @@ -Creating user xxx (n/a) with uid 312 and gid 310. +Failed to parse UID: '99': Numerical result out of range Unexpected error output for unhappy-1.input Creating user xxx (n/a) with uid 312 and gid 310. make: *** [run] Error 1 Makefile:4: recipe for target 'run' failed make: Leaving directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' FAILED TESTS: test/TEST-21-SYSUSERS autopkgtest [00:22:13]: test upstream: ---] upstream FAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776654/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant
FYI, there is a pending update that will go out either tomorrow or early next week. Please base your next upload on this update. -- 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/1869819 Title: [SRU] System can't detect external headset in the codec of Conexant Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: In Progress Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] In some hp's devices, there are two audio jacks(one headset and one headphone) in the audio interface which is using the codec of Conexant, and apparently it's not working, the system can't detect the headset in current codec. [Test Case] 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon) 2. Check System Setting->Sound->Output [Expected result] Can detect external headset [Actual result] Only shows internal speaker. External headset microphone was detected. Another front audio port (earphone icon) works fine. [Regression Potential] Low. [Failure rate] 100% [Additional information] system-product-name: HP EliteDesk 800 G5 SFF CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e98] (rev 02) OS-version: 18.04 kernel-version: 4.15.0-1065-oem pulseaudio-version: 1:11.1-1ubuntu7.2 Upstream issue: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272 Ubuntu-Focal-Source: https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
I"ve had this problem on a clean install of 20.04 on a new laptop, with two headsets that support both profiles. ``` Name: Soundcore Life 2 Alias: Soundcore Life 2 Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) ``` Name: OnePlus Bullets Wireless 2 Alias: OnePlus Bullets Wireless 2 Class: 0x00240418 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Serial Port (1101--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) Modalias: bluetooth:v000Apd ``` -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1877194] [NEW] Selected audio output device not persistent between reboots (Resets to USB-device)
Public bug reported: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. (Notice that I swapped out my username with $USER in the text below) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: $USER 1604 F pulseaudio /dev/snd/controlC0: $USER 1604 F pulseaudio /dev/snd/controlC1: $USER 1604 F pulseaudio /dev/snd/pcmC1D0c: $USER 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 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: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to and HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: marcus 1604 F pulseaudio - /dev/snd/controlC0: marcus 1604 F pulseaudio - /dev/snd/controlC1: marcus 1604 F pulseaudio - /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: $USER 1604 F pulseaudio + /dev/snd/controlC0: $USER 1604 F pulseaudio + /dev/snd/controlC1: $USER 1604 F pulseaudio + /dev/snd/pcmC1D0c: $USER 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 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: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Description changed: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to and HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. + + (Notice that I swapped out my username with $USER in the text below) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: $USER 1604 F pulseaudio /dev/snd/controlC0: $USER 1604
[Touch-packages] [Bug 1870589] Re: test-seccomp fails test_restrict_suid_sgid on arm64 on Bionic
autopkgtest now passes on arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/s/systemd/20200428_033750_621b2@/log.gz
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
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/1870589
Title:
test-seccomp fails test_restrict_suid_sgid on arm64 on Bionic
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
Fix Committed
Bug description:
[impact]
RestrictSUIDSGID (backported to Bionic in security CVE) fails 100% of
the time on arm64, and testcase failure indicates this as well.
[test case]
check autopkgtest logs, e.g.
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/s/systemd/20200401_09_34f60@/log.gz
/* test_restrict_suid_sgid */
Failed to add suid/sgid rule for architecture arm64, skipping: Numerical
argument out of domain
Assertion 'chmod(path, 0775 | S_ISUID) < 0 && errno == EPERM' failed at
../src/test/test-seccomp.c:823, function test_restrict_suid_sgid(). Aborting.
suidsgidseccomp terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("suidsgidseccomp", pid, WAIT_LOG) ==
EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:889, function
test_restrict_suid_sgid(). Aborting.
FAIL: test-seccomp (code: 134)
Aborted (core dumped)
[regression potential]
this improves the function that (tries to) install seccomp suid/sgid
filters, so and regression would involve failure to restrict suid/sgid
with seccomp filters; however on arm64, the this functionality already
fails 100% of the time (which is what the failed test case was
pointing out).
[scope]
this fails only in Bionic, and this specific feature and testcase was
backported in patches for CVE-2019-384x. It does not appear that the
backported feature, or its testcase, ever passed in Bionic on arm64.
[other info]
systemd bionic arm64 autopkgtests have failed forever, but we should
fix that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870589/+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
Re: [Touch-packages] [Bug 1803601] Re: motd-news.service scheduled even when /etc/update-motd.d/50-motd-news is not executable
On 2020-05-06 2:49 p.m., Andreas Hasenack wrote: > There are many alternatives here. IIRC, `chmod -x` snippets from /etc/update-motd.d/ was the way to go a few releases ago when it was consumed by run-parts. > I think fixing this doesn't warrant an SRU, but should be considered for > the devel release of ubuntu (groovy at the moment). It's merely to avoid harmless surprise and keep the old sysadmins happy, certainly not worth a SRU. Thanks, Simon -- 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/1803601 Title: motd-news.service scheduled even when /etc/update-motd.d/50-motd-news is not executable Status in base-files package in Ubuntu: Triaged Bug description: update-motd(5) says: Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as the root user at each login, and this information is concatenated in /run/motd.dynamic. The order of script execu‐ tion is determined by the run-parts(8) --lsbsysinit option (basically alphabetical order, with a few caveats). So sysadmins are used to "chmod -x" motd fragments from /etc/update- motd.d/ to prevent their execution. When doing so for /etc/update- motd.d/50-motd-news, I noticed that motd-news.timer was still trying to execute the motd-news.service unit which then logged a failure: systemd[3704]: motd-news.service: Failed to execute command: Permission denied systemd[3704]: motd-news.service: Failed at step EXEC spawning /etc/update-motd.d/50-motd-news: Permission denied systemd[1]: motd-news.service: Main process exited, code=exited, status=203/EXEC systemd[1]: motd-news.service: Failed with result 'exit-code'. systemd[1]: Failed to start Message of the Day. The motd-news.service unit looks like this: $ systemctl cat motd-news.service # /lib/systemd/system/motd-news.service [Unit] Description=Message of the Day After=network-online.target Documentation=man:update-motd(8) [Service] Type=oneshot ExecStart=/etc/update-motd.d/50-motd-news --force This problem was observed on a Bionic system: $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy base-files base-files: Installed: 10.1ubuntu2.3 Candidate: 10.1ubuntu2.3 Version table: *** 10.1ubuntu2.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 10.1ubuntu2.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 10.1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages But the problem also exist in Disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1803601/+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 1877182] Re: Blank screen timer does not work
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1877182 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877182 Title: Blank screen timer does not work Status in gnome-shell package in Ubuntu: Incomplete Bug description: It just does not work if I set it to never or to 15 MIN it does not work it is stuck at one min ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 6 22:43:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1d3d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1d3d] InstallationDate: Installed on 2020-05-02 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b3fd Chicony Electronics Co., Ltd HD WebCam (Asus N-series) Bus 001 Device 005: ID 0b05:17ac ASUSTek Computer, Inc. ASUS Laser GAMING MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. G551VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7fb860e1-6845-4a22-9fde-4c8435d52aba ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G551VW.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G551VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG551VW.209:bd02/19/2016:svnASUSTeKCOMPUTERINC.:pnG551VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG551VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: G dmi.product.name: G551VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877182/+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 1872902] Re: Upgrade to Focal now removes chrony
I retested the armhf autopkgtest failures and update-manager and update- notifier have now both passed. -- 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/1872902 Title: Upgrade to Focal now removes chrony Status in Release Notes for Ubuntu: New Status in apt package in Ubuntu: Invalid Status in chrony package in Ubuntu: Invalid Status in germinate package in Ubuntu: New Status in ntp package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Focal: Invalid Status in chrony source package in Focal: Invalid Status in germinate source package in Focal: New Status in ntp source package in Focal: Invalid Status in systemd source package in Focal: Invalid Status in ubuntu-release-upgrader source package in Focal: Fix Committed Bug description: Due to changes in systemd for bug 1849156 this issue now happens. On an upgrade for people that had chrony installed on a do-release upgrade it now will: Calculating the changes MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > FU=1 Removing: chrony MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0 That isn't what users want, those who had chrony installed would want to get chrony upgraded and systemd-timesyncd (which now is a separate pacakge) not installed. Test Case - 1) On a system running Ubuntu 19.10 or Ubuntu 18.04 LTS install the package chrony 2) Run do-release-upgrade with the appropriate switches 3) Observe that chrony is marked for deletion With the version of dist-upgrader from -proposed (accessed with the -p switch) chrony is no longer marked for deletion. Regression Potential Given that Dimitri's change is now ignoring the tasks minimal and standard (which are handled by _keepBaseMetaPkgsInstalled) we should still be cautious and test desktop upgrades and ensure that packages in those tasks are not marked for removal. Regression Test --- 1) Run do-release-upgrade on an Ubuntu 19.10 or Ubuntu 18.04 LTS system 2) Record the list of packages marked for removal Compare the list of packages marked for removal with the release- upgrader from -proposed from Focal. Original Description I'd ask you to revise the dependencies that got changes in systemd 245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays installed as that was an opt-in chances are quite high people would want to keep it that way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
In the generic kernel CONFIG_RT_GROUP_SCHED is still enabled. It was only disabled for the lowlatency kernel. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in rtkit package in Ubuntu: Confirmed Bug description: These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+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 1877194] Re: Selected audio output device not persistent between reboots (Resets to USB-device)
We configure PulseAudio by default to automatically choose hotplugged devices so it might be thinking booting with USB counts as hotplugging. To avoid this you should just be able to comment out: load-module module-switch-on-connect from /etc/pulse/default.pa ** 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/1877194 Title: Selected audio output device not persistent between reboots (Resets to USB-device) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 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: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1877194/+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 1877216] [NEW] [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all
Public bug reported: Problem keeps appearing when video is played. video keeps playing but no sound is heard thru headphones. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ernest 1095 F pulseaudio /dev/snd/controlC1: ernest 1095 F pulseaudio /dev/snd/controlC0: ernest 1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 7 09:55:52 2020 InstallationDate: Installed on 2020-04-25 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ernest 1095 F pulseaudio /dev/snd/controlC1: ernest 1095 F pulseaudio /dev/snd/controlC0: ernest 1095 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M PRO-VDH MAX (MS-7A38) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 8.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 8.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB.10:bd08/28/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr8.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-VDHMAX(MS-7A38):rvr8.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr8.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A38 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 8.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1877216 Title: [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Problem keeps appearing when video is played. video keeps playing but no sound is heard thru headphones. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ernest 1095 F pulseaudio /dev/snd/controlC1: ernest 1095 F pulseaudio /dev/snd/controlC0: ernest 1095 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 7 09:55:52 2020 InstallationDate: Installed on 2020-04-25 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ernest 1095 F pulseaudio /dev/snd/controlC1: ernest 1095 F pulseaudio /dev/snd/controlC0: ernest 1095 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M PRO-VDH MAX (MS-7A38) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 8.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 8.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB.10:bd08/28/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr8.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-VDHMAX(MS-7A38):rvr8.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr8.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A38 dmi.product.sku: To be filled by O.E.M.
[Touch-packages] [Bug 1877194] Re: Selected audio output device not persistent between reboots (Resets to USB-device)
** Description changed: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. - - (Notice that I swapped out my username with $USER in the text below) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND - /dev/snd/controlC2: $USER 1604 F pulseaudio - /dev/snd/controlC0: $USER 1604 F pulseaudio - /dev/snd/controlC1: $USER 1604 F pulseaudio - /dev/snd/pcmC1D0c: $USER 1604 F...m pulseaudio + /dev/snd/controlC2: marcus 1604 F pulseaudio + /dev/snd/controlC0: marcus 1604 F pulseaudio + /dev/snd/controlC1: marcus 1604 F pulseaudio + /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 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: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- 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/1877194 Title: Selected audio output device not persistent between reboots (Resets to USB-device) Status in pulseaudio package in Ubuntu: New Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 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: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1877194/+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 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade
This is something to do with linux 5 kernel api You need to manually downgrade systemd - well - that's what I did. when you boot with grub or refind - edit default entry and change the init=/bin/init to init=/bin/bash That will bypass systemd starting up and drop you straight into a shell. mount -o remount / mount /usr mount /var mount /dev/sdc1 /mnt dpkg -i /mnt/systemd_241-7~deb10u3_amd64.deb On a system that works or download a previous version somehow. dpkg -l systemd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii systemd245.5-2 amd64system and service manager root@leet:/home/wozza# apt-cache policy systemd systemd: Installed: 245.5-2 Candidate: 245.5-2 Version table: *** 245.5-2 500 500 http://ftp.iinet.net.au/debian/debian bullseye/main amd64 Packages 100 /var/lib/dpkg/status 241-7~deb10u3 500 500 http://ftp.iinet.net.au/debian/debian stable/main amd64 Packages root@leet:/home/wozza# apt-get download systemd=241-7~deb10u3 Get:1 http://ftp.iinet.net.au/debian/debian stable/main amd64 systemd amd64 241-7~deb10u3 [3,495 kB] Fetched 3,495 kB in 11s (321 kB/s) W: Download is performed unsandboxed as root as file '/home/wozza/systemd_241-7~deb10u3_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) root@leet:/home/wozza# ll systemd_241-7~deb10u3_amd64.deb -rw-r--r-- 1 root root 3495428 Jan 31 15:11 systemd_241-7~deb10u3_amd64.deb root@leet:/home/wozza# mount /dev/sdc1 /mnt root@leet:/home/wozza# cp systemd_241-7~deb10u3_amd64.deb /mnt/ root@leet:/home/wozza# cd /mnt/ root@leet:/mnt# mkdir unpack root@leet:/mnt# cd unpack/ root@leet:/mnt/unpack# dpkg-deb -R ../systemd_241-7~deb10u3_amd64.deb . worst comes to worse can copy the files across from unpack directory - good luck. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade Status in libseccomp package in Ubuntu: New Bug description: Upgraded Ubuntu 18.04 to 20.04. Following the upgrade, booting was not possible. The error messages is: /sbin/init: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: seccomp_api_get [4.608900] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 See also attached photograph of screen during boot. Upgrade followed steps from here: https://help.ubuntu.com/community/FocalUpgrades/Kubuntu With the excpetion that The -d flag was used for the do-release-upgrade: sudo do-release-upgrade -d -m desktop 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Prior to upgrade: Ubuntu 18.04.4 After upgrade (but never booted): Ubuntu (Kubuntu) 20.04 Note that Ubuntu had originally be installed, but kubuntu-desktop was recently installed to change to Kubuntu, but no booting problems were experienced before updating to 20.04. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Unknown -- Package version may have changed when upgrading to 20.04. 3) What you expected to happen Boot without kernel panic. 4) What happened instead Could not boot. Even selecting safe mode from grub could not boot. Had to restore system from backups. Will not attempt upgrade again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+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 1877219] [NEW] dozens of empty grilo-plugin-cache folders polluting /tmp
Public bug reported: My /tmp folder has dozens of empty folders with names like grilo-plugin- cache-ABCDEF. I don't know anything about grilo-plugins, but surely they can do their job without leaving endless garbage directories behind when they're done? $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan $ dpkg-query --show grilo-plugins-0.3-base grilo-plugins-0.3-base:amd640.3.9-1ubuntu1 ** Affects: grilo-plugins (Ubuntu) Importance: Undecided Status: New ** Description changed: My /tmp folder has dozens of empty folders with names like grilo-plugin- cache-ABCDEF. I don't know anything about grilo-plugins, but surely they can do their job without leaving endless garbage directories behind when they're done? + + $ lsb_release -a + No LSB modules are available. + Distributor ID: Ubuntu + Description: Ubuntu 19.10 + Release: 19.10 + Codename: eoan + + $ dpkg-query --show grilo-plugins-0.3-base + grilo-plugins-0.3-base:amd64 0.3.9-1ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1877219 Title: dozens of empty grilo-plugin-cache folders polluting /tmp Status in grilo-plugins package in Ubuntu: New Bug description: My /tmp folder has dozens of empty folders with names like grilo- plugin-cache-ABCDEF. I don't know anything about grilo-plugins, but surely they can do their job without leaving endless garbage directories behind when they're done? $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan $ dpkg-query --show grilo-plugins-0.3-base grilo-plugins-0.3-base:amd64 0.3.9-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1877219/+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 1876125] Autopkgtest regression report (evolution-data-server/3.36.2-0ubuntu1)
All autopkgtests for the newly accepted evolution-data-server (3.36.2-0ubuntu1) for focal have finished running. The following regressions have been reported in tests triggered by the package: libreoffice/1:6.4.3-0ubuntu0.20.04.1 (ppc64el, armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#evolution-data-server [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1876125 Title: SRU the current 3.36.2 stable update Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1876125/+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 1872560] Re: integer overflow in whoopsie 0.2.69
Sure. This issue is also reproducible with pre-compiled version of
0.2.62ubuntu0.4.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1872560
Title:
integer overflow in whoopsie 0.2.69
Status in whoopsie package in Ubuntu:
Confirmed
Bug description:
Hi,
I have found a security issue on whoopsie 0.2.69 and earlier.
## Vulnerability in whoopsie
- whoopsie 0.2.69 and earlier have a heap-based buffer overflow
vulnerability.
- An attacker can cause a denial of service (memory corruption and
application crash) via a crafted .crash file.
## Basic
When a program has been crashed, Linux system tries to create a '.crash' file
on '/var/crash/' directory with python script located in
'/usr/share/apport/apport'.
The file contains a series of system crash information including core dump,
syslog, stack trace, memory map info, etc.
After the creation of '.crash' file, whoopsie extracts the above information
from the '.crash' file and encodes it into binary json (bson) format.
Lastly, whoopsie forwards the data to a remotely connected Ubuntu Error
Report system.
## Vulnerability
Unfortunately, we have found a heap-based buffer overflow vulnerability
during the encoding, when whoopsie attempts to bsonify with crafted crash file.
The data in '.crash' file is stored in key-value form and the whoopsie
separately measures the length of 'key' and 'value' to allocate memory region
during the encoding.
A heap-based buffer overflow can occur when an integer overflow happens on a
variable that contains length of 'key'.
FYI, a issue to that raised by 'value' is well covered by performing
exception handling.
@[bson.c:663][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n663]
const uint32_t len = strlen( name ) + 1;
- Integer overflow occurs when length of ‘name’ exceeds INT32_MAX value.
- Here, ‘name’ indicates the ‘key’ data in ‘.crash’ file.
@[bson.c:627][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n627]
b->data = bson_realloc( b->data, new_size );
- Unexpected small memory region is allocated due to above integer
overflow.
@[bson.c:680][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n680]
bson_append( b, name, len );
- Memory corruption happens when unexpected small memory region is
allocated.
## Attack Scenario
1) Create a fake.crash file
- '.crash' file is composed of the following format: 'key : value'.
- To cause the overflow attack, the size of 'key' should be in double amount
of INT32_MAX.
- The size of 'value' doesn’t matter, but not zero length.
$ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash
$ cat fake.crash
AAA … AA : B
2) Trigger the whoopsie to read the fake.crash file
- Just create 'fake.upload' file by touch command.
- Or launch apport-gtk gui or apport-bug cli application.
3) Check out the result
- After a while, the whoopsie has been killed by segmentation fault.
Sincerely,
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1872560/+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 1872560] Re: integer overflow in whoopsie 0.2.69
Sorry, I meant "Are you able to reproduce the issue with the pre-
compiled version of Whoopsie that comes with it?"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1872560
Title:
integer overflow in whoopsie 0.2.69
Status in whoopsie package in Ubuntu:
Confirmed
Bug description:
Hi,
I have found a security issue on whoopsie 0.2.69 and earlier.
## Vulnerability in whoopsie
- whoopsie 0.2.69 and earlier have a heap-based buffer overflow
vulnerability.
- An attacker can cause a denial of service (memory corruption and
application crash) via a crafted .crash file.
## Basic
When a program has been crashed, Linux system tries to create a '.crash' file
on '/var/crash/' directory with python script located in
'/usr/share/apport/apport'.
The file contains a series of system crash information including core dump,
syslog, stack trace, memory map info, etc.
After the creation of '.crash' file, whoopsie extracts the above information
from the '.crash' file and encodes it into binary json (bson) format.
Lastly, whoopsie forwards the data to a remotely connected Ubuntu Error
Report system.
## Vulnerability
Unfortunately, we have found a heap-based buffer overflow vulnerability
during the encoding, when whoopsie attempts to bsonify with crafted crash file.
The data in '.crash' file is stored in key-value form and the whoopsie
separately measures the length of 'key' and 'value' to allocate memory region
during the encoding.
A heap-based buffer overflow can occur when an integer overflow happens on a
variable that contains length of 'key'.
FYI, a issue to that raised by 'value' is well covered by performing
exception handling.
@[bson.c:663][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n663]
const uint32_t len = strlen( name ) + 1;
- Integer overflow occurs when length of ‘name’ exceeds INT32_MAX value.
- Here, ‘name’ indicates the ‘key’ data in ‘.crash’ file.
@[bson.c:627][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n627]
b->data = bson_realloc( b->data, new_size );
- Unexpected small memory region is allocated due to above integer
overflow.
@[bson.c:680][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n680]
bson_append( b, name, len );
- Memory corruption happens when unexpected small memory region is
allocated.
## Attack Scenario
1) Create a fake.crash file
- '.crash' file is composed of the following format: 'key : value'.
- To cause the overflow attack, the size of 'key' should be in double amount
of INT32_MAX.
- The size of 'value' doesn’t matter, but not zero length.
$ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash
$ cat fake.crash
AAA … AA : B
2) Trigger the whoopsie to read the fake.crash file
- Just create 'fake.upload' file by touch command.
- Or launch apport-gtk gui or apport-bug cli application.
3) Check out the result
- After a while, the whoopsie has been killed by segmentation fault.
Sincerely,
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1872560/+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 1877194] Re: Selected audio output device not persistent between reboots (Resets to USB-device)
** Description changed: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. + + In short: + 1. Boot system + 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. + 3. Reboot. + 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 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: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- 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/1877194 Title: Selected audio output device not persistent between reboots (Resets to USB-device) Status in pulseaudio package in Ubuntu: New Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 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: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1877194/+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 1877115] Re: Corruption of default wallpaper
*** This bug is a duplicate of bug 1867668 *** https://bugs.launchpad.net/bugs/1867668 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1867668, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1867668 Visual artifacts in Gnome Shell when using the 'intel' Xorg driver -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877115 Title: Corruption of default wallpaper Status in xorg package in Ubuntu: New Bug description: If the "Tearfree" Xorg option for Intel graphics is turned on, painting the default wallpaper is corrupted. See attached screenshot. My X11 change from default for the "Tearfree" option is: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree""true" EndSection as /etc/X11/xorg.conf.d/20-intel.conf Copying the wallpaper to My Pictures and setting as wallpaper doesn't show the corruption. Using other wallpapers including included wallpapers shows no corruption. Removing the "tearfree" option then logoff/logon doesn't show the wallpaper corruption (but gives me screen tearing when playing videos, which I don't like. Using the Wayland option shows no wallpaper corruption. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 6 14:06:30 2020 DistUpgraded: 2020-05-02 16:18:39,153 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-08-09 (636 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 9370 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=ff06b612-9a9b-4692-bd35-9dc3a5e65fef ro mem_sleep_default=deep quiet splash drm_kms_helper.edid_firmware=edid/1920x1080_50.00.bin vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-02 (3 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1877115/+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 1876065] Re: After unplug headphones and plug them again no sound can be heard
** Tags added: regression-release -- 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/1876065 Title: After unplug headphones and plug them again no sound can be heard Status in pulseaudio package in Ubuntu: Fix Committed Bug description: * Impact Sound isn't automatically redirected to headphones when those are connected to a jack interface * Test case Disconnect the headsets Start your webbrowser/music player/video player and play some sound Connect the headsets to the jack interface -> the sound should be directly redirected to the plugged headsets * Regression potential Check that audio routing when connecting/disconnecting devices to the hack entry is working correctly After startup with headset plugged in they play sound nicely - no issue. When they are unplugged, the sound is switched to the speaker (laptop) - all good. However, when I plug the headset back there is no sound. I see the app on pavucontrol, the volume is fine - everything looks fine except there is no sound. I dumped output of "pactl list" command on startup (headset plugged), after unplugging the headset, and when it is plugged back. From the comparison of these outputs, it looks like the source has got muted after the headset is plugged. Source #1 State: RUNNING Name: alsa_input.pci-_00_1f.3.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: yes Attached three outputs: headset-in.txt - after startup with headset plugged - all fine. headset-out.txt - after unplugged headset - sound through the speaker - all fine. headset-back.txt - after plugged headset back - no sound. Any help greatly appreciated. Regards, Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+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 1876886] Re: chrony autopkgtest fails on armhf (groovy)
It was flaky and now resolved in proposed migration. But I'd want to understand why we fail 4/5 times. So the debugging tests in the bileto ticket [1] will go on for a bit. [1]: https://bileto.ubuntu.com/#/ticket/4049 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1876886 Title: chrony autopkgtest fails on armhf (groovy) Status in chrony package in Ubuntu: New Status in libcap2 package in Ubuntu: Confirmed Bug description: Test fails on armhf only: running chronyc makestepERROR checking chronyc output OK running chronyc trimrtc ERROR checking chronyc output OK running chronyc writertcERROR This might be a new twist on https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1863590 as it is libcap2 again. This reproduces through a bunch of retries http://autopkgtest.ubuntu.com/packages/c/chrony/groovy/armhf But as I said is armfh only: http://autopkgtest.ubuntu.com/packages/chrony Flagging update-excuse, but I won't be able to get to it immediately ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1876886/+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 1026725] Re: [945GCM-S2C, Realtek ALC662 rev1, Green Line Out, Rear] Underruns, dropouts or crackling sound
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1026725 Title: [945GCM-S2C, Realtek ALC662 rev1, Green Line Out, Rear] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Expired Bug description: Audio skips when trying to play ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19 Uname: Linux 3.2.0-26-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sean 1519 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xe21c irq 43' Mixer name : 'Realtek ALC662 rev1' Components : 'HDA:10ec0662,1458a002,00100101' Controls : 39 Simple ctrls : 21 CurrentDmesg: [ 18.255982] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 18.795542] init: plymouth-stop pre-start process (1104) terminated with status 1 [ 28.370432] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. [ 28.512060] eth0: no IPv6 routers present Date: Thu Jul 19 13:09:50 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Green Line Out, Rear Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [945GCM-S2C, Realtek ALC662 rev1, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: 945GCM-S2C dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd11/08/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GCM-S2C:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GCM-S2C:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: 945GCM-S2C dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1026725/+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 1017095] Re: [Audigy2 - SB Audigy 2 Platinum [SB0240P], playback] fails after a while
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1017095 Title: [Audigy2 - SB Audigy 2 Platinum [SB0240P], playback] fails after a while Status in alsa-driver package in Ubuntu: Expired Bug description: I get sound the correct way when booting Ubuntu. Problem is every time another application tries to use the sound system (that seems to be Pulse Audio and not alsa as mentioned in the auto-compiled report). The problem usually happens when I use Amarok and any other application tries to initialize/use audio. For example today just installing Audacity while listening to music and running it as soon as it was installed broke the audio. The synthoms are a harsh noise coming from the output instead of any sound at all. I am using analog audio and nothing more out of SB Audigy 2 card (not platinum, as far as I know, it's the standard card with nothing else). I tried many things like restarting pulse, alsa, changing card, taking up all the volumes, installing a pulse audio volume controller app, using alsamixer to raise volumes and unmute/mute something. Tried all I can. The only differences I notice that stops the noise (but does not start any playback) is if I either check the output digital S/PDIF in the standard Ubuntu audio settings from the bar, OR if I use alsamixer and I UNmute the output "Audigy Analog/Digital Output Jack". I tried many sound troubleshooting guides on the wiki/website/forum but none work. I also should have added some svn repo and upgraded some audio packages, reset their settings and so on. Unfortunately only a reboot gives the audio back. Forgot to mention this is Precise x64 just installed, but I think it's in the extra debug info attached by the utility. lsb_release -rd Description: Ubuntu-Secure-Remix 12.04 LTS Release: 12.04 ** alsa packages installed: apt-cache policy alsa* mpg123-alsa: Installato: (nessuno) Candidato: 1.12.1-3.2ubuntu1 Tabella versione: 1.12.1-3.2ubuntu1 0 500 http://it.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages libalsa-ocaml: Installato: (nessuno) Candidato: 0.2.1-1build3 Tabella versione: 0.2.1-1build3 0 500 http://it.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages snd-dmotif-alsa: Installato: (nessuno) Candidato: (nessuno) Tabella versione: bluez-alsa: Installato: 4.98-2ubuntu7 Candidato: 4.98-2ubuntu7 Tabella versione: *** 4.98-2ubuntu7 0 500 http://it.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status liboss4-salsa2: Installato: (nessuno) Candidato: 4.2-build2005-2ubuntu1 Tabella versione: 4.2-build2005-2ubuntu1 0 500 http://it.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages alsa-tools: Installato: (nessuno) Candidato: 1.0.25-1ubuntu1 Tabella versione: 1.0.25-1ubuntu1 0 500 http://it.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages yate-alsa: Installato: (nessuno) Candidato: 2.2.0-1~dfsg-1.1ubuntu2 Tabella versione: 2.2.0-1~dfsg-1.1ubuntu2 0 500 http://it.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages alsaplayer-output: Installato: (nessuno) Candidato: (nessuno) Tabella versione: libpt-1.10.10-plugins-alsa: Installato: (nessuno) Candidato: 1.10.10-3.1ubuntu1 Tabella versione: 1.10.10-3.1ubuntu1 0 500 http://it.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages balsa-dbg: Installato: (nessuno) Candidato: 2.4.11-1 Tabella versione: 2.4.11-1 0 500 http://it.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages libpt-plugins-alsa: Installato: (nessuno) Candidato: (nessuno) Tabella versione: skysentials: Installato: (nessuno) Candidato: (nessuno) Tabella versione: alsa-source: Installato: (nessuno) Candidato: 1.0.25+dfsg-0ubuntu1 Tabella versione: 1.0.25+dfsg-0ubuntu1 0 500 http://it.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages 1.0.25+dfsg-0ubuntu1~precise1 0 500 http://ppa.launchpad.net/ubuntu-audio-dev/ppa/ubuntu/ precise/main amd64 Packages snd-gtk-alsa: Installato: (nessuno) Candidato: (nessuno) Tabella versione: libktpcommoninternalsprivate0: Installato: (nessuno) Candidato: 0.3.1-0ubuntu1 Tabella versione: 0.3.1-0ubuntu1 0 500 http://it.archive.ubuntu.com/ubuntu/ precise/universe
[Touch-packages] [Bug 1036221] Re: [USB-Audio - Bose USB Audio, playback] No sound at all
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1036221 Title: [USB-Audio - Bose USB Audio, playback] No sound at all Status in alsa-driver package in Ubuntu: Expired Bug description: This is a very irritating problem. Symptoms : - Audio does not work on booting. I usually have to reboot to get it to work. - I have to fiddle with the audio volume to get it to work. Does not work everytime. If it does not work, i reboot again. - Audio starts to work and if I am playing music/ watching a movie/etc, it continues to work. However, if I pause for a few minutes - e.g. taking a lunch/dinner break, and come back, the audio does not work again. This is not an issue with the Bose hardware because: 1. I have a dual boot system, and I do not ever get this problem on windows. 2. If audio is not working, i can pull the usb out and put it in again to get it to work. I suspect - there is some usb keep awake issue. if there is no signal on the usb cable for sometime, it just dies and stops listening. I think other people are having the same problem. I had blogged about it a while back and got comments from other readers. You can read about it at http://vibhurishi.blogspot.in/2012/03/ubuntu-no-sound-fix- for-usb-audio.html . Its worse in Ubuntu 12.04 as I need to reboot or unplug/plug the usb cable. This is driving me nuts. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic-pae 3.2.21 Uname: Linux 3.2.0-27-generic-pae i686 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: vibhu 2170 F pulseaudio /dev/snd/controlC1: vibhu 2170 F pulseaudio /dev/snd/controlC0: vibhu 2170 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe72 irq 47' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,80860036,00100202' Controls : 42 Simple ctrls : 23 Card1.Amixer.info: Card hw:1 'Generic'/'HD-Audio Generic at 0xfe64 irq 48' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 6 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Card2.Amixer.info: Card hw:2 'Audio'/'Bose Corporation Bose USB Audio at usb-:00:1a.0-1.1, full speed' Mixer name : 'USB Mixer' Components : 'USB05a7:1020' Controls : 2 Simple ctrls : 1 Card2.Amixer.values: Simple mixer control 'PCM',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum Playback channels: Mono Limits: Playback 0 - 100 Mono: Playback 100 [100%] [0.00dB] [on] Date: Mon Aug 13 20:00:37 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio failed Symptom_Card: Bose USB Audio - Bose USB Audio Symptom_DevicesInUse: 2170 2170 2170 2170 vibhu F pulseaudio /dev/snd/pcmC2D0p: vibhu F...m pulseaudio /dev/snd/controlC1: vibhu F pulseaudio /dev/snd/controlC0: vibhu F pulseaudio Symptom_Type: No sound at all Title: [USB-Audio - Bose USB Audio, playback] No sound at all UpgradeStatus: Upgraded to precise on 2012-06-09 (65 days ago) dmi.bios.date: 12/06/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: TCIBX10H.86A.0048.2011.1206.1342 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH55PJ dmi.board.vendor: Intel Corporation dmi.board.version: AAE93812-303 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0048.2011.1206.1342:bd12/06/2011:svn:pn:pvr:rvnIntelCorporation:rnDH55PJ:rvrAAE93812-303:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1036221/+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 756928] Re: no opportunity to cancel when using ubuntu-bug -w
Ah ok, that’s really helpful Alex. I think let’s close this as wontfix then as you suggested. Thanks for looking into this! ** Changed in: apport (Ubuntu) Status: New => Won't Fix -- 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/756928 Title: no opportunity to cancel when using ubuntu-bug -w Status in apport package in Ubuntu: Won't Fix Bug description: Binary package hint: apport I would expect that right-click would cancel the selection of "ubuntu- bug -w", as it does with programs such as xkill. Esc should also work. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: apport 1.20-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 NonfreeKernelModules: wl Architecture: amd64 Date: Sun Apr 10 18:21:17 2011 LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/756928/+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 998322] Re: [Inspiron N5010, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Expired
--
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/998322
Title:
[Inspiron N5010, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
Status in alsa-driver package in Ubuntu:
Expired
Bug description:
Suddenly the sound stopped coming out!
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic i686
NonfreeKernelModules: fglrx wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: shankhs2053 F pulseaudio
/dev/snd/controlC0: shankhs2053 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfbf0 irq 48'
Mixer name : 'IDT 92HD81B1X5'
Components : 'HDA:111d7605,10280447,00100105'
Controls : 16
Simple ctrls : 9
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbe3 irq 49'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100100'
Controls : 6
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Sat May 12 09:49:05 2012
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_IN
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
Symptom_Card: RV710/730 HDMI Audio [Radeon HD 4000 series] - HDA ATI HDMI
Symptom_DevicesInUse:
2053 2053 shankhs F pulseaudio
/dev/snd/controlC0: shankhs F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [Inspiron N5010, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: Upgraded to precise on 2012-05-10 (1 days ago)
dmi.bios.date: 07/19/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0FCVWR
dmi.board.vendor: Dell Inc.
dmi.board.version: A15
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A15
dmi.modalias:
dmi:bvnDellInc.:bvrA15:bd07/19/2011:svnDellInc.:pnInspironN5010:pvrA15:rvnDellInc.:rn0FCVWR:rvrA15:cvnDellInc.:ct8:cvrA15:
dmi.product.name: Inspiron N5010
dmi.product.version: A15
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/998322/+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 1005227] Re: I replaced my video card now I have no sound [GN573AAR-ABA SR5223WM, Nvidia GPU 0b HDMI/DP, Digital Out, HDMI] No sound at all
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1005227 Title: I replaced my video card now I have no sound [GN573AAR-ABA SR5223WM, Nvidia GPU 0b HDMI/DP, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: Expired Bug description: I also installed a new monitor which is a tv and I can't get my screen to the right size ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cletis 1686 F pulseaudio Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16' Mixer name : 'Nvidia GPU 0b HDMI/DP' Components : 'HDA:10de000b,10de0101,00100200' Controls : 24 Simple ctrls : 4 Date: Sun May 27 10:23:17 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: 1686/dev/snd/controlC0: cletisF pulseaudio AND Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [GN573AAR-ABA SR5223WM, Nvidia GPU 0b HDMI/DP, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to precise on 2012-04-28 (28 days ago) dmi.bios.date: 05/15/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.09 dmi.board.name: IVY8 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 2.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.09:bd05/15/2007:svnCompaq-Presario:pnGN573AAR-ABASR5223WM:pvr:rvnASUSTekComputerINC.:rnIVY8:rvr2.00:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: GN573AAR-ABA SR5223WM dmi.sys.vendor: Compaq-Presario To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1005227/+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 998315] Re: [Acer Aspire 5930, Realtek ALC888] Jack sensing broken, sounds to both headphones and speakers at same time
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/998315 Title: [Acer Aspire 5930, Realtek ALC888] Jack sensing broken, sounds to both headphones and speakers at same time Status in alsa-driver package in Ubuntu: Expired Bug description: It worked fine in 11.10. I expect sound to speakers when there are no headphones plugged ad sound to headphones else. if headphones was plugged in on startup, they works, but if I unplug it, speakers don't work. If headphones wasn't plugged before startup, sound is in speakers and in headphones at the same time. riad@riad-laptop:~$ lsb_release -rd Description: Ubuntu quantal (development branch) Release: 12.10 but Ubuntu help shows "Welcome to Ubuntu 12.04" ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: riad 2814 F pulseaudio /dev/snd/pcmC0D0c: riad 2814 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf650 irq 49' Mixer name : 'Nvidia MCP77/78 HDMI' Components : 'HDA:10ec0888,1025013f,00100202 HDA:11c11040,11c10001,00100200 HDA:10de0006,10de0101,0010' Controls : 38 Simple ctrls : 20 Date: Sat May 12 07:28:16 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Aspire 5930, Realtek ALC888, Black Headphone Out, Front] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.17 dmi.board.name: Eiger dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.17:bd07/07/2008:svnAcer:pnAspire5930:pvr0100:rvnAcer:rnEiger:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5930 dmi.product.version: 0100 dmi.sys.vendor: Acer modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-05-12T07:18:13.471922 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/998315/+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 997674] Re: [Lenovo G470, Conexant CX20590, Mic, Internal] No sound at all
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Expired
--
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/997674
Title:
[Lenovo G470, Conexant CX20590, Mic, Internal] No sound at all
Status in alsa-driver package in Ubuntu:
Expired
Bug description:
Its an internal mic, after installing 12.04, I couldn't be able to use
the mic. It doesnt respond at all.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rahman 2206 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xd060 irq 43'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:14f1506e,17aac011,0012
HDA:80862805,80860101,0010'
Controls : 14
Simple ctrls : 6
Date: Thu May 10 20:25:34 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120317)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
2206 rahmanF pulseaudio
PID ACCESS COMMAND
Symptom_Jack: Mic, Internal
Symptom_Type: No sound at all
Title: [20078, Conexant CX20590, Mic, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/13/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 40CN26WW(V2.12)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: LENOVO
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnLENOVO:bvr40CN26WW(V2.12):bd09/13/2011:svnLENOVO:pn20078:pvrLenovoG470:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: 20078
dmi.product.version: Lenovo G470
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/997674/+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 1877030] [NEW] ping is missing IDN support
Public bug reported: The ping util is missing IDN support (at least in 19.10). For other packages (e.g. bind9) this was enabled a long time ago: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/175316 ** Affects: iputils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1877030 Title: ping is missing IDN support Status in iputils package in Ubuntu: New Bug description: The ping util is missing IDN support (at least in 19.10). For other packages (e.g. bind9) this was enabled a long time ago: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/175316 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1877030/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
** Changed in: rtkit (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in rtkit package in Ubuntu: Confirmed Bug description: These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+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 1854588] Re: Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened from Chrome/Firefox
** Changed in: firefox (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1854588 Title: Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened from Chrome/Firefox Status in Ubuntu MATE: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu with gdebi-gtk installed 2. Open Firefox 3. Visit some site with deb-package download link or use direct link like https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb 4. Proceed with file downloading 5. In Firefox select Library → Downloads, click on downloaded deb-file Expected results: * gdebi-gtk is opened, the package installs normally after users clicks Install button Actual results: * gdebi-gtk is opened, the package is not installed because of vanishing of gdebi-gtk window just after clicking Install button Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1854588/+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 1877030] Re: ping is missing IDN support
** Changed in: iputils (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1877030 Title: ping is missing IDN support Status in iputils package in Ubuntu: New Bug description: The ping util is missing IDN support (at least in 19.10). For other packages (e.g. bind9) this was enabled a long time ago: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/175316 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1877030/+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 1877030] Re: ping is missing IDN support
Thank you for your bug report, could you give an example of how to test that IDN support is working if it was enabled? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1877030 Title: ping is missing IDN support Status in iputils package in Ubuntu: New Bug description: The ping util is missing IDN support (at least in 19.10). For other packages (e.g. bind9) this was enabled a long time ago: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/175316 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1877030/+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 1877030] Re: ping is missing IDN support
With idn: $ ping öbb.at PING öbb.at (195.69.192.140) 56(84) bytes of data. Without idn: $ ping öbb.at ping: öbb.at: Name or service not known -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1877030 Title: ping is missing IDN support Status in iputils package in Ubuntu: New Bug description: The ping util is missing IDN support (at least in 19.10). For other packages (e.g. bind9) this was enabled a long time ago: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/175316 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1877030/+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 1876915] Re: package cups-daemon 2.2.12-2ubuntu1.1 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1
Thank you for your bug report, the log has Failed to restart cups.service: Unit -.mount is masked. Did you do any change to the cups system service? ** Changed in: cups (Ubuntu) Status: New => Incomplete -- 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/1876915 Title: package cups-daemon 2.2.12-2ubuntu1.1 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1 Status in cups package in Ubuntu: Incomplete Bug description: Im not sure what caused this problem ProblemType: Package DistroRelease: Ubuntu 19.10 Package: cups-daemon 2.2.12-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat May 2 11:27:39 2020 DpkgHistoryLog: Start-Date: 2020-05-02 11:27:19 Commandline: /usr/bin/unattended-upgrade Upgrade: libcups2:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), libcups2:i386 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-server-common:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-common:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-bsd:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-core-drivers:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-daemon:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), libcupsimage2:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-client:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-ipp-utils:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1) ErrorMessage: installed cups-daemon package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-30 (35 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUSTeK COMPUTER INC. Q500A Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=d1314bd9-a342-4a79-ba05-fd27f747bc14 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=d1314bd9-a342-4a79-ba05-fd27f747bc14 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: cups Title: package cups-daemon 2.2.12-2ubuntu1.1 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2020-04-02 (32 days ago) dmi.bios.date: 08/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q500A.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q500A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ500A.205:bd08/17/2012:svnASUSTeKCOMPUTERINC.:pnQ500A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ500A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Q dmi.product.name: Q500A dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1876915/+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 1875927] Re: add support for phys_port_name attribute in Xenial/16.04LTS
Centos had to revert the patch in their systemd package via: commit 83b94d10951d79445f7975bff835a88261c11a4e SOURCES/0499-Revert-udev-net_id-add-support-for-phys_port_name-at.patch They workaround (differing from upstream) the regression installing script and udev rule to add phys_port_name for mlxsw and rocker drivers and put them in dracut. -- 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/1875927 Title: add support for phys_port_name attribute in Xenial/16.04LTS Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Bug description: [Impact] In Xenial/16.04LTS, one can't generate network interface name from "phys_port_name" attribute. "phys_port_name" indicates the interface physical port name within the NIC. [Test Case] Check that udev (systemd-udevd) provides the phys_port_name property Tests should be done on both kernel versions: v4.4 and v4.15 [Regression Potential] Risk: Low * This piece of code is already in place in Bionic (systemd) and late. AFAICT, nothing has been reported since then with regards to this feature. * phys_port_name kernel support has been introduced in v4.1. Xenial supported kernel are : v4.4 and v4.15 (HWE). * If a regression arise, it will most likely be limited to the "Ethernet switch device driver model (switchdev)" reported by: rocker, mlxsw, broadcom, ... [Other informations] https://github.com/systemd/systemd/commit/4887b656c22af059d4e833de7b56544f24951184 https://github.com/systemd/systemd/pull/4506 [Original Description] It has been brought to my attention that systemd in Xenial/16.04LTS doesn't have support for phys_port_name[0] attribute. The support has been first introduced in systemd version "232" via: https://github.com/systemd/systemd/commit/4887b656c22af059d4e833de7b56544f24951184 https://github.com/systemd/systemd/pull/4506 Bionic and late have the necessary bits ( systemd >232), but not Xenial (229)[1] Support for "phys_port_name" has been first introduced in the kernel with v4.1[2] [0] - https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net - https://www.freedesktop.org/software/systemd/man/systemd.net-naming-scheme.html - https://www.kernel.org/doc/Documentation/networking/switchdev.txt [1] # git systemd/systemd git describe --contains 4887b656c22af059d4e833de7b56544f24951184 v232~15 # rmadison => systemd | 229-4ubuntu21.27 | xenial-updates systemd | 237-3ubuntu10.39 | bionic-updates systemd | 240-6ubuntu5.8 | disco-updates systemd | 242-7ubuntu3.7 | eoan-updates systemd | 245.4-4ubuntu3 | focal systemd | 245.4-4ubuntu3 | groovy [2] https://github.com/torvalds/linux/commit/db24a9044ee1 $ git describe --contains db24a9044ee1 v4.1-rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1875927/+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 1875927] Re: add support for phys_port_name attribute in Xenial/16.04LTS
https://git.centos.org/rpms/systemd/c/83b94d10951d79445f7975bff835a88261c11a4e?branch=83b94d10951d79445f7975bff835a88261c11a4e -- 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/1875927 Title: add support for phys_port_name attribute in Xenial/16.04LTS Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Bug description: [Impact] In Xenial/16.04LTS, one can't generate network interface name from "phys_port_name" attribute. "phys_port_name" indicates the interface physical port name within the NIC. [Test Case] Check that udev (systemd-udevd) provides the phys_port_name property Tests should be done on both kernel versions: v4.4 and v4.15 [Regression Potential] Risk: Low * This piece of code is already in place in Bionic (systemd) and late. AFAICT, nothing has been reported since then with regards to this feature. * phys_port_name kernel support has been introduced in v4.1. Xenial supported kernel are : v4.4 and v4.15 (HWE). * If a regression arise, it will most likely be limited to the "Ethernet switch device driver model (switchdev)" reported by: rocker, mlxsw, broadcom, ... [Other informations] https://github.com/systemd/systemd/commit/4887b656c22af059d4e833de7b56544f24951184 https://github.com/systemd/systemd/pull/4506 [Original Description] It has been brought to my attention that systemd in Xenial/16.04LTS doesn't have support for phys_port_name[0] attribute. The support has been first introduced in systemd version "232" via: https://github.com/systemd/systemd/commit/4887b656c22af059d4e833de7b56544f24951184 https://github.com/systemd/systemd/pull/4506 Bionic and late have the necessary bits ( systemd >232), but not Xenial (229)[1] Support for "phys_port_name" has been first introduced in the kernel with v4.1[2] [0] - https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net - https://www.freedesktop.org/software/systemd/man/systemd.net-naming-scheme.html - https://www.kernel.org/doc/Documentation/networking/switchdev.txt [1] # git systemd/systemd git describe --contains 4887b656c22af059d4e833de7b56544f24951184 v232~15 # rmadison => systemd | 229-4ubuntu21.27 | xenial-updates systemd | 237-3ubuntu10.39 | bionic-updates systemd | 240-6ubuntu5.8 | disco-updates systemd | 242-7ubuntu3.7 | eoan-updates systemd | 245.4-4ubuntu3 | focal systemd | 245.4-4ubuntu3 | groovy [2] https://github.com/torvalds/linux/commit/db24a9044ee1 $ git describe --contains db24a9044ee1 v4.1-rc1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1875927/+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 1839290] Re: systemd doesn't restart a service after crashes
bionic: ubuntu@lp1839290-b:~$ dpkg -l systemd|grep systemd ii systemd237-3ubuntu10.39 amd64system and service manager ubuntu@lp1839290-b:~$ systemctl cat foo # /etc/systemd/system/foo.service [Unit] PartOf=bar.service [Service] ExecStart=/bin/sleep infinity RestartSec=0s Restart=always ubuntu@lp1839290-b:~$ systemctl cat bar # /etc/systemd/system/bar.service [Unit] BindsTo=foo.service #Same with or without After=, the window is very small to make a difference. After=foo.service [Service] ExecStart=/bin/sleep infinity ubuntu@lp1839290-b:~$ sudo systemctl start foo ubuntu@lp1839290-b:~$ sudo systemctl start bar ubuntu@lp1839290-b:~$ systemctl status foo bar ● foo.service Loaded: loaded (/etc/systemd/system/foo.service; static; vendor preset: enabled) Active: active (running) since Wed 2020-05-06 11:20:31 UTC; 4s ago Main PID: 8560 (sleep) Tasks: 1 (limit: 4702) CGroup: /system.slice/foo.service └─8560 /bin/sleep infinity May 06 11:20:31 lp1839290-b systemd[1]: Started foo.service. ● bar.service Loaded: loaded (/etc/systemd/system/bar.service; static; vendor preset: enabled) Active: active (running) since Wed 2020-05-06 11:20:33 UTC; 3s ago Main PID: 8570 (sleep) Tasks: 1 (limit: 4702) CGroup: /system.slice/bar.service └─8570 /bin/sleep infinity May 06 11:20:33 lp1839290-b systemd[1]: Started bar.service. ubuntu@lp1839290-b:~$ sudo kill -6 8560 ubuntu@lp1839290-b:~$ systemctl status foo bar ● foo.service Loaded: loaded (/etc/systemd/system/foo.service; static; vendor preset: enabled) Active: failed (Result: core-dump) since Wed 2020-05-06 11:21:08 UTC; 1s ago Process: 8560 ExecStart=/bin/sleep infinity (code=dumped, signal=ABRT) Main PID: 8560 (code=dumped, signal=ABRT) May 06 11:21:08 lp1839290-b systemd[1]: foo.service: Service has no hold-off time, scheduling restart. May 06 11:21:08 lp1839290-b systemd[1]: foo.service: Failed to schedule restart job: Transaction is destructive. May 06 11:21:08 lp1839290-b systemd[1]: foo.service: Failed with result 'core-dump'. ● bar.service Loaded: loaded (/etc/systemd/system/bar.service; static; vendor preset: enabled) Active: inactive (dead) since Wed 2020-05-06 11:21:08 UTC; 1s ago Process: 8570 ExecStart=/bin/sleep infinity (code=killed, signal=TERM) Main PID: 8570 (code=killed, signal=TERM) May 06 11:20:33 lp1839290-b systemd[1]: Started bar.service. May 06 11:21:08 lp1839290-b systemd[1]: Stopping bar.service... May 06 11:21:08 lp1839290-b systemd[1]: Stopped bar.service. ubuntu@lp1839290-b:~$ dpkg -l systemd|grep systemd ii systemd237-3ubuntu10.40 amd64system and service manager ubuntu@lp1839290-b:~$ sudo systemctl start bar ubuntu@lp1839290-b:~$ sudo systemctl start foo ubuntu@lp1839290-b:~$ sudo systemctl status foo bar ● foo.service Loaded: loaded (/etc/systemd/system/foo.service; static; vendor preset: enabled) Active: active (running) since Wed 2020-05-06 11:24:57 UTC; 10s ago Main PID: 1256 (sleep) Tasks: 1 (limit: 4702) CGroup: /system.slice/foo.service └─1256 /bin/sleep infinity May 06 11:24:57 lp1839290-b systemd[1]: Started foo.service. ● bar.service Loaded: loaded (/etc/systemd/system/bar.service; static; vendor preset: enabled) Active: active (running) since Wed 2020-05-06 11:24:57 UTC; 10s ago Main PID: 1258 (sleep) Tasks: 1 (limit: 4702) CGroup: /system.slice/bar.service └─1258 /bin/sleep infinity May 06 11:24:57 lp1839290-b systemd[1]: Started bar.service. ubuntu@lp1839290-b:~$ sudo kill -6 1256 ubuntu@lp1839290-b:~$ sudo systemctl status foo bar ● foo.service Loaded: loaded (/etc/systemd/system/foo.service; static; vendor preset: enabled) Active: active (running) since Wed 2020-05-06 11:25:19 UTC; 2s ago Main PID: 1276 (sleep) Tasks: 1 (limit: 4702) CGroup: /system.slice/foo.service └─1276 /bin/sleep infinity May 06 11:25:19 lp1839290-b systemd[1]: Started foo.service. ● bar.service Loaded: loaded (/etc/systemd/system/bar.service; static; vendor preset: enabled) Active: active (running) since Wed 2020-05-06 11:25:19 UTC; 2s ago Main PID: 1277 (sleep) Tasks: 1 (limit: 4702) CGroup: /system.slice/bar.service └─1277 /bin/sleep infinity May 06 11:25:19 lp1839290-b systemd[1]: Started bar.service. ubuntu@lp1839290-b:~$ journalctl -b -u foo -- Logs begin at Wed 2020-05-06 11:11:19 UTC, end at Wed 2020-05-06 11:25:22 UTC. -- May 06 11:24:57 lp1839290-b systemd[1]: Started foo.service. May 06 11:25:19 lp1839290-b systemd[1]: foo.service: Main process exited, code=dumped, status=6/ABRT May 06 11:25:19 lp1839290-b systemd[1]: foo.service: Failed with result 'core-dump'. May 06 11:25:19 lp1839290-b systemd[1]: foo.service: Service has no hold-off time, scheduling restart. May 06 11:25:19 lp1839290-b systemd[1]: foo.service: Scheduled restart job, restart counter is at 1. May 06 11:25:19 lp1839290-b systemd[1]: Stopped
[Touch-packages] [Bug 1877030] Re: ping is missing IDN support
Thanks for the detail, indeed it has the wrong bug depends on libidn, I reported that to Debian now https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959868 I've also tested a build in a ppa, https://launchpad.net/~ubuntu- desktop/+archive/ubuntu/ppa/+build/19267763 and indeed your testcase works now ** Bug watch added: Debian Bug tracker #959868 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959868 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1877030 Title: ping is missing IDN support Status in iputils package in Ubuntu: New Bug description: The ping util is missing IDN support (at least in 19.10). For other packages (e.g. bind9) this was enabled a long time ago: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/175316 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1877030/+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 1877093] [NEW] [SRU] New stable release 2.34.2
Public bug reported: [ Description ] GNOME upstream have released a new stable version of at-spi2-atk. Changes: What's new in at-spi2-atk 2.34.2: * Meson: don't hard-code shared_library (!19). * Mitigate missing window events at startup. * Set C standard to gnu99 (#10). * Tests: include sys/time.h (#14). [ QA ] GNOME has a micro release exception that covers this package. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME So we don't need to verify the fixes explicitly. Install the desktop and exercise the screen reader in a variety of situations. Optionally, but ideally, test the installer too. [ Regression potential ] If this update is busted the screen reader might not work. This changes the C standard too, which should be fine, but make sure to do some QA. ** Affects: at-spi2-atk (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: at-spi2-atk (Ubuntu Focal) Importance: Undecided Assignee: Iain Lane (laney) Status: In Progress ** Also affects: at-spi2-atk (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: at-spi2-atk (Ubuntu Focal) Status: New => In Progress ** Changed in: at-spi2-atk (Ubuntu Focal) Assignee: (unassigned) => Iain Lane (laney) ** Changed in: at-spi2-atk (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1877093 Title: [SRU] New stable release 2.34.2 Status in at-spi2-atk package in Ubuntu: Fix Released Status in at-spi2-atk source package in Focal: In Progress Bug description: [ Description ] GNOME upstream have released a new stable version of at-spi2-atk. Changes: What's new in at-spi2-atk 2.34.2: * Meson: don't hard-code shared_library (!19). * Mitigate missing window events at startup. * Set C standard to gnu99 (#10). * Tests: include sys/time.h (#14). [ QA ] GNOME has a micro release exception that covers this package. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME So we don't need to verify the fixes explicitly. Install the desktop and exercise the screen reader in a variety of situations. Optionally, but ideally, test the installer too. [ Regression potential ] If this update is busted the screen reader might not work. This changes the C standard too, which should be fine, but make sure to do some QA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1877093/+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 1877096] [NEW] package linux-image-4.15.0-96-generic 4.15.0-96.97~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: every time I run apt ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-96-generic 4.15.0-96.97~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-91.92~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Wed May 6 08:57:52 2020 DpkgHistoryLog: Start-Date: 2020-05-06 08:57:27 Commandline: /usr/bin/unattended-upgrade Upgrade: mysql-client-5.7:amd64 (5.7.29-0ubuntu0.16.04.1, 5.7.30-0ubuntu0.16.04.1), mysql-server-5.7:amd64 (5.7.29-0ubuntu0.16.04.1, 5.7.30-0ubuntu0.16.04.1), mysql-server:amd64 (5.7.29-0ubuntu0.16.04.1, 5.7.30-0ubuntu0.16.04.1), mysql-client-core-5.7:amd64 (5.7.29-0ubuntu0.16.04.1, 5.7.30-0ubuntu0.16.04.1), mysql-common:amd64 (5.7.29-0ubuntu0.16.04.1, 5.7.30-0ubuntu0.16.04.1), libmysqlclient20:amd64 (5.7.29-0ubuntu0.16.04.1, 5.7.30-0ubuntu0.16.04.1), mysql-server-core-5.7:amd64 (5.7.29-0ubuntu0.16.04.1, 5.7.30-0ubuntu0.16.04.1) ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-02-06 (89 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.29ubuntu0.1 SourcePackage: initramfs-tools Title: package linux-image-4.15.0-96-generic 4.15.0-96.97~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1877096 Title: package linux-image-4.15.0-96-generic 4.15.0-96.97~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: every time I run apt ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-96-generic 4.15.0-96.97~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-91.92~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Wed May 6 08:57:52 2020 DpkgHistoryLog: Start-Date: 2020-05-06 08:57:27 Commandline: /usr/bin/unattended-upgrade Upgrade: mysql-client-5.7:amd64 (5.7.29-0ubuntu0.16.04.1, 5.7.30-0ubuntu0.16.04.1), mysql-server-5.7:amd64 (5.7.29-0ubuntu0.16.04.1, 5.7.30-0ubuntu0.16.04.1), mysql-server:amd64 (5.7.29-0ubuntu0.16.04.1, 5.7.30-0ubuntu0.16.04.1), mysql-client-core-5.7:amd64 (5.7.29-0ubuntu0.16.04.1, 5.7.30-0ubuntu0.16.04.1), mysql-common:amd64 (5.7.29-0ubuntu0.16.04.1, 5.7.30-0ubuntu0.16.04.1), libmysqlclient20:amd64 (5.7.29-0ubuntu0.16.04.1, 5.7.30-0ubuntu0.16.04.1), mysql-server-core-5.7:amd64 (5.7.29-0ubuntu0.16.04.1, 5.7.30-0ubuntu0.16.04.1) ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-02-06 (89 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.29ubuntu0.1 SourcePackage: initramfs-tools Title: package linux-image-4.15.0-96-generic 4.15.0-96.97~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1877096/+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 1839290] Re: systemd doesn't restart a service after crashes
xenial: ubuntu@lp1839290-x:~$ dpkg -l systemd|grep systemd ii systemd229-4ubuntu21.27 amd64system and service manager ubuntu@lp1839290-x:~$ systemctl cat foo # /etc/systemd/system/foo.service # /etc/systemd/system/foo.service [Unit] PartOf=bar.service [Service] ExecStart=/bin/sleep infinity RestartSec=0s Restart=always ubuntu@lp1839290-x:~$ systemctl cat bar # /etc/systemd/system/bar.service # /etc/systemd/system/bar.service [Unit] BindsTo=foo.service #Same with or without After=, the window is very small to make a difference. After=foo.service [Service] ExecStart=/bin/sleep infinity ubuntu@lp1839290-x:~$ sudo systemctl start foo ubuntu@lp1839290-x:~$ sudo systemctl start bar ubuntu@lp1839290-x:~$ systemctl status foo bar ● foo.service Loaded: loaded (/etc/systemd/system/foo.service; static; vendor preset: enabled) Active: active (running) since Wed 2020-05-06 11:28:14 UTC; 5s ago Main PID: 1268 (sleep) Tasks: 1 Memory: 80.0K CPU: 1ms CGroup: /system.slice/foo.service └─1268 /bin/sleep infinity May 06 11:28:14 lp1839290-x systemd[1]: Started foo.service. ● bar.service Loaded: loaded (/etc/systemd/system/bar.service; static; vendor preset: enabled) Active: active (running) since Wed 2020-05-06 11:28:17 UTC; 3s ago Main PID: 1273 (sleep) Tasks: 1 Memory: 84.0K CPU: 1ms CGroup: /system.slice/bar.service └─1273 /bin/sleep infinity May 06 11:28:17 lp1839290-x systemd[1]: Started bar.service. ubuntu@lp1839290-x:~$ sudo kill -6 1268 ubuntu@lp1839290-x:~$ systemctl status foo bar ● foo.service Loaded: loaded (/etc/systemd/system/foo.service; static; vendor preset: enabled) Active: failed (Result: resources) since Wed 2020-05-06 11:28:29 UTC; 929ms ago Process: 1268 ExecStart=/bin/sleep infinity (code=dumped, signal=ABRT) Main PID: 1268 (code=dumped, signal=ABRT) May 06 11:28:29 lp1839290-x systemd[1]: foo.service: Unit entered failed state. May 06 11:28:29 lp1839290-x systemd[1]: foo.service: Failed with result 'core-dump'. May 06 11:28:29 lp1839290-x systemd[1]: foo.service: Service has no hold-off time, scheduling restart. May 06 11:28:29 lp1839290-x systemd[1]: foo.service: Failed to schedule restart job: Transaction is destructive. May 06 11:28:29 lp1839290-x systemd[1]: foo.service: Unit entered failed state. May 06 11:28:29 lp1839290-x systemd[1]: foo.service: Failed with result 'resources'. ● bar.service Loaded: loaded (/etc/systemd/system/bar.service; static; vendor preset: enabled) Active: inactive (dead) since Wed 2020-05-06 11:28:29 UTC; 931ms ago Process: 1273 ExecStart=/bin/sleep infinity (code=killed, signal=TERM) Main PID: 1273 (code=killed, signal=TERM) May 06 11:28:17 lp1839290-x systemd[1]: Started bar.service. May 06 11:28:29 lp1839290-x systemd[1]: Stopping bar.service... May 06 11:28:29 lp1839290-x systemd[1]: Stopped bar.service. ubuntu@lp1839290-x:~$ dpkg -l systemd|grep systemd ii systemd229-4ubuntu21.28 amd64system and service manager ubuntu@lp1839290-x:~$ sudo systemctl start foo ubuntu@lp1839290-x:~$ sudo systemctl start bar ubuntu@lp1839290-x:~$ systemctl status foo bar ● foo.service Loaded: loaded (/etc/systemd/system/foo.service; static; vendor preset: enabl Active: active (running) since Wed 2020-05-06 11:31:03 UTC; 6s ago Main PID: 1238 (sleep) Tasks: 1 Memory: 84.0K CPU: 1ms CGroup: /system.slice/foo.service └─1238 /bin/sleep infinity May 06 11:31:03 lp1839290-x systemd[1]: Started foo.service. ● bar.service Loaded: loaded (/etc/systemd/system/bar.service; static; vendor preset: enabl Active: active (running) since Wed 2020-05-06 11:31:05 UTC; 3s ago Main PID: 1243 (sleep) Tasks: 1 Memory: 84.0K CPU: 1ms CGroup: /system.slice/bar.service └─1243 /bin/sleep infinity May 06 11:31:05 lp1839290-x systemd[1]: Started bar.service. ubuntu@lp1839290-x:~$ sudo kill -6 1238 ubuntu@lp1839290-x:~$ systemctl status foo bar ● foo.service Loaded: loaded (/etc/systemd/system/foo.service; static; vendor preset: enabled) Active: active (running) since Wed 2020-05-06 11:31:32 UTC; 1s ago Main PID: 1257 (sleep) Tasks: 1 Memory: 80.0K CPU: 1ms CGroup: /system.slice/foo.service └─1257 /bin/sleep infinity May 06 11:31:32 lp1839290-x systemd[1]: Started foo.service. ● bar.service Loaded: loaded (/etc/systemd/system/bar.service; static; vendor preset: enabled) Active: active (running) since Wed 2020-05-06 11:31:32 UTC; 1s ago Main PID: 1258 (sleep) Tasks: 1 Memory: 80.0K CPU: 1ms CGroup: /system.slice/bar.service └─1258 /bin/sleep infinity May 06 11:31:32 lp1839290-x systemd[1]: Started bar.service. ubuntu@lp1839290-x:~$ journalctl -b -u foo -- Logs begin at Wed 2020-05-06 11:30:16 UTC, end at Wed 2020-05-06 11:31:35 UTC. -- May 06 11:31:03 lp1839290-x systemd[1]: Started foo.service. May 06 11:31:32 lp1839290-x
[Touch-packages] [Bug 572146] Re: lpib position_fix ssid quirk addition breaks existing hardware
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Invalid -- 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/572146 Title: lpib position_fix ssid quirk addition breaks existing hardware Status in alsa-driver package in Ubuntu: Invalid Bug description: Description: Ubuntu 10.04 LTS Release: 10.04 yesterday i upgraded to 10.04 and now my microphone records together with my voice a constant crackling. this only happens if i used the shipped kernel 2.6.32-21. if i boot the latest 9.10 kernel (2.6.31-21) the recording works in normal quality. the microphone is connected to an onboard hda intel card. i also have an audigy 2 in my system. also my webcam has a mono usb soundcard. lspci: 00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller (rev 02) 00:01.0 PCI bridge: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port (rev 02) 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02) 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02) 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02) 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 02) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92) 00:1f.0 ISA bridge: Intel Corporation 82801IR (ICH9R) LPC Interface Controller (rev 02) 00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA AHCI Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation GT200 [GeForce GTX 260] (rev a1) 03:00.0 SATA controller: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 02) 03:00.1 IDE interface: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller (rev 02) 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01) 05:00.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04) 05:00.1 Input device controller: Creative Labs SB Audigy Game Port (rev 04) 05:00.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04) 05:06.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/572146/+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 662299] Re: Soundcard not detected (workaround: add "pci=use_crs" to GRUB)
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Invalid -- 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/662299 Title: Soundcard not detected (workaround: add "pci=use_crs" to GRUB) Status in ALSA driver: Fix Released Status in alsa-driver package in Ubuntu: Invalid Status in grub2 package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: I was using Ubuntu 10.04 64 bit with sound enabled. After I updated to Ubuntu 10.10 64 bit its saying no sound cards detected. Report generated by alsa-info.sh : http://www.alsa- project.org/db/?f=6fd7c2b5363fb860fbfdf2fcbce5af440562f0a1 Name of my Sound Card (onboard) anish@logika:~/Downloads$ sudo lshw -c sound [sudo] password for anish: *-multimedia description: Audio device product: VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) vendor: VIA Technologies, Inc. physical id: 1 bus info: pci@:80:01.0 version: 10 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=HDA Intel latency=0 resources: iomemory:fd0-fcf irq:17 memory:fd-fd3fff anish@logika:~/Downloads$ lspci | grep -i audio 80:01.0 Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10) ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: alsa-base 1.0.23+dfsg-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 3 2010-10-17 23:01 seq crw-rw+ 1 root audio 116, 2 2010-10-17 23:01 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. AplayDevices: aplay: device_list:235: no soundcards found... Architecture: amd64 ArecordDevices: arecord: device_list:235: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sun Oct 17 23:36:06 2010 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Soundcard not detected dmi.bios.date: 05/10/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: V1.11 dmi.board.name: 0A88h dmi.board.vendor: Board Manufacturer dmi.chassis.asset.tag: INA74206SB dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.11:bd05/10/2007:svnHewlett-Packard:pnHPdx2255MT(RL028AV):pvr:rvnBoardManufacturer:rn0A88h:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP dx2255 MT(RL028AV) dmi.sys.vendor: Hewlett-Packard --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 3 2010-10-19 22:29 seq crw-rw+ 1 root audio 116, 2 2010-10-19 22:29 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Compiled on Oct 17 2010 for kernel 2.6.35-22-generic (SMP). AplayDevices: aplay: device_list:235: no soundcards found... Architecture: amd64 ArecordDevices: arecord: device_list:235: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 10.10 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) Package: alsa-driver (not installed) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Tags: maverick Uname: Linux 2.6.35-22-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/10/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: V1.11 dmi.board.name: 0A88h dmi.board.vendor: Board Manufacturer dmi.chassis.asset.tag: INA74206SB dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.11:bd05/10/2007:svnHewlett-Packard:pnHPdx2255MT(RL028AV):pvr:rvnBoardManufacturer:rn0A88h:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP dx2255 MT(RL028AV) dmi.sys.vendor: Hewlett-Packard --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 3 2010-10-20 22:10 seq crw-rw+ 1 root audio 116, 2 2010-10-20 22:10 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Compiled on Oct 20 2010 for kernel 2.6.35-22-generic (SMP). AplayDevices: aplay: device_list:235: no soundcards found...
[Touch-packages] [Bug 1264609] Re: No AC3 paththrough with hda intel ALC887-VD Saucy
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Invalid -- 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/1264609 Title: No AC3 paththrough with hda intel ALC887-VD Saucy Status in alsa-driver package in Ubuntu: Invalid Bug description: Ubuntu 13.10 linux-image-extra-3.11.0-14-generic: 3.11.0-14.21 The original problem is that I have not managed to play AC3 sound bit perfect from a DVD to the AMP. I think I have tracked down the problem to an Alsa issue: I expect: aplay -vv -D iec958:CARD=PCH,DEV=0 Norrlanda.wav to play the file with all 6 channels via fiber optic to my amplifier like outlined at http://alsa.opensrc.org/DigitalOut Instead, there is only silence. This is the output: $ pasuspender -- aplay -v -v -D iec958:CARD=PCH,DEV=0 /home/daniel/workspace/Testsounds/Norrlanda.wav Wiedergabe: WAVE '/home/daniel/workspace/Testsounds/Norrlanda.wav' : Signed 16 bit Little Endian, Rate: 44100 Hz, stereo Hooks PCM Its setup is: stream : PLAYBACK access : RW_INTERLEAVED format : S16_LE subformat: STD channels : 2 rate : 44100 exact rate : 44100 (44100/1) msbits : 16 buffer_size : 16384 period_size : 4096 period_time : 92879 tstamp_mode : NONE period_step : 1 avail_min: 4096 period_event : 0 start_threshold : 16384 stop_threshold : 16384 silence_threshold: 0 silence_size : 0 boundary : 4611686018427387904 Slave: Hardware PCM card 1 'HDA Intel PCH' device 1 subdevice 0 Its setup is: stream : PLAYBACK access : RW_INTERLEAVED format : S16_LE subformat: STD channels : 2 rate : 44100 exact rate : 44100 (44100/1) msbits : 16 buffer_size : 16384 period_size : 4096 period_time : 92879 tstamp_mode : NONE period_step : 1 avail_min: 4096 period_event : 0 start_threshold : 16384 stop_threshold : 16384 silence_threshold: 0 silence_size : 0 boundary : 4611686018427387904 appl_ptr : 0 hw_ptr : 0 #+ | 25% Here some additional observations: * The Norlanda.wav file is played with 6 channels too pulseaudio (6 sliders at the pavucontrol input pane) but only PCM Stereo is transmitted to the amp. * I can play stereo wave files fine with the aplay command from above * If I switch to non-audio (ac3) mode, I cannot play stereo files any more, but the ac3 file produces still silence. $ iecset -D hw:1 audio 0 Mode: consumer Data: non-audio Rate: 48000 Hz Copyright: permitted Emphasis: none Category: PCM coder Original: original Clock: 1000 ppm I have already setup a build environment for the hda modules, but I got lost inside the code. Any ideas how to nail down the problem? Thank you! Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1264609/+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 633317] Re: PCM mixer too high / distortion - HDA Intel: Conexant CX20551 (Waikiki)
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
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/633317
Title:
PCM mixer too high / distortion - HDA Intel: Conexant CX20551
(Waikiki)
Status in alsa-driver package in Ubuntu:
Invalid
Bug description:
Whenever I adjust the audio from the indicator applet PCM shoots up to
between 98% and 100%, this causes distortion.
As a workaround I always set it to about 95% and adjust the master
volume using 'alsamixer'.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: libasound2 1.0.23-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic i686
NonfreeKernelModules: hsfengine nvidia
Architecture: i386
Date: Wed Sep 8 17:01:42 2010
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-lib
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: chrisw 3129 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xd640 irq 45'
Mixer name : 'Conexant CX20551 (Waikiki)'
Components : 'HDA:14f15047,103c30b2,0010'
Controls : 18
Simple ctrls : 10
DistroRelease: Ubuntu 10.10
NonfreeKernelModules: hsfengine nvidia
Package: alsa-driver (not installed)
ProcEnviron:
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Tags: maverick
Uname: Linux 2.6.35-20-generic i686
UserGroups: adm admin cdrom clamav dialout lpadmin mysql mythtv plugdev
sambashare
dmi.bios.date: 03/28/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.25
dmi.board.name: 30B3
dmi.board.vendor: Wistron
dmi.board.version: 61.58
dmi.chassis.type: 10
dmi.chassis.vendor: Wistron
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.25:bd03/28/2007:svnHewlett-Packard:pnHPPaviliondv2000(RD651EA#ABU):pvrF.25:rvnWistron:rn30B3:rvr61.58:cvnWistron:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv2000 (RD651EA#ABU)
dmi.product.version: F.25
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/633317/+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 1180593] Re: no sound from speakers [OptiPlex 320, Analog Devices AD1983, Green Line Out, Rear] No sound at all
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Invalid -- 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/1180593 Title: no sound from speakers [OptiPlex 320, Analog Devices AD1983, Green Line Out, Rear] No sound at all Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Invalid Bug description: I just switched to ubuntu this is all new to me. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.5.0-28.48-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic i686 ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: twoblue2372 F pulseaudio Date: Wed May 15 19:10:22 2013 InstallationDate: Installed on 2013-05-14 (1 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: twoblue2372 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [OptiPlex 320, Analog Devices AD1983, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.9 dmi.board.name: 0TY915 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.9:bd07/10/2007:svnDellInc.:pnOptiPlex320:pvr:rvnDellInc.:rn0TY915:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: OptiPlex 320 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1180593/+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 1178825] Re: [USB-Audio - Plantronics GameCom 780] Terrible support for this headset
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Invalid -- 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/1178825 Title: [USB-Audio - Plantronics GameCom 780] Terrible support for this headset Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Invalid Bug description: Today I bought a Plantronics GameCom 780 headset, I pluged into the USB port whishing it would work out of the box, but it didn't properly. First of all, I'm using Kubuntu 13.04, Linux Kernel version is 3.8.0-19, and, for example, I can't hear nothing if volume is less than 24%, if I put it at 20% I won't hear anything, it gets muted. Micprohone is working quite well, but the function "Loudness" isn't working, I typed Alsamixer and I selected the soundcard of the headset, Loudness appears there but it appears desactivated, and I can't enable it :/ My problems seems to be similar to this: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/961481 Do you know if this will be solved in future versions of the Linux Kernel? maybe with a new PulseAudio version? what about Alsamixer? I'm new in Linux, and this kind of problems are terrible, I know it's not Linux fault, it's GameCom fault, they should make better support for Linux... Thank you (sorry for my bad English) To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1178825/+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 989800] Re: Error alert stops appearing for the same crash after a while
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: apport (Ubuntu) Status: Incomplete => Invalid -- 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/989800 Title: Error alert stops appearing for the same crash after a while Status in Apport: Triaged Status in apport package in Ubuntu: Invalid Bug description: apport 2.0.1-0ubuntu6, Ubuntu 12.04 1. Encounter a particular crash. 2. Encounter the same crash again. 3. Encounter the same crash again. What happens: 1. An error alert appears explaining what happened. 2. An error alert appears explaining what happened. 3. Nothing. What should happen: 3. An error alert appears explaining what happened. The primary purpose of the error alert, as far as the user is concerned, is to explain what has just gone wrong. This purpose does not change no matter how often the error occurs. For fair comparison of error rates between Ubuntu versions, it may be necessary to flag these previously-suppressed errors as ones that wouldn't have been reported "by X standards". To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/989800/+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 1168206] Re: UnicodeDecodeError raised from attach_hardware()
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: apport (Ubuntu) Status: Incomplete => Invalid -- 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/1168206 Title: UnicodeDecodeError raised from attach_hardware() Status in apport package in Ubuntu: Invalid Status in xdiagnose package in Ubuntu: Fix Released Bug description: As seen on bugs #1164623 and #1162151: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/source_xserver-xorg-video-intel.py", line 660, in add_info attach_hardware(report) File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 246, in attach_hardware attach_dmi(report) File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 201, in attach_dmi value = fd.read().strip() File "/usr/lib/python3.3/codecs.py", line 300, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: invalid start byte attach_dmi() is an apport call. The dmi info's sometimes useful but not crucial to have in X bug reports, so if it's erroring we can safely skip its inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1168206/+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 1203235] Re: [H87N-WIFI, Realtek ALC892, Green Line Out, Rear] Underruns, dropouts or crackling sound
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Invalid -- 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/1203235 Title: [H87N-WIFI, Realtek ALC892, Green Line Out, Rear] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Invalid Bug description: Out of the box, ubuntu has intermittent crackling sounds on this hardware. I've tried turning off other sound devices, switching fully to ALSA, tweaking config files with stuff described here: https://wiki.ubuntu.com/Audio/PositionReporting and various other things. Nothing seems to alleviate the issues of crackling sound. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: brian 1732 F pulseaudio /dev/snd/controlC1: brian 1732 F pulseaudio /dev/snd/controlC0: brian 1732 F pulseaudio Date: Fri Jul 19 23:22:05 2013 InstallationDate: Installed on 2013-07-15 (4 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True 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: Green Line Out, Rear Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [H87N-WIFI, Realtek ALC892, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87N-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd05/07/2013:svnGigabyteTechnologyCo.,Ltd.:pnH87N-WIFI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87N-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H87N-WIFI dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1203235/+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 1181828] Re: macbook air 2,1 no sound
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Invalid -- 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/1181828 Title: macbook air 2,1 no sound Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Invalid Bug description: Hello, I installed Ubuntu raring 13.04 on a Macbook Air 2,1 and I have no sound. The card is recognized by alsamixer and pulseaudio. I put the volume to the maximum, put all the mixer unmute in alsamixer, no sound at all. Thanks for your help. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8 Uname: Linux 3.8.0-21-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rom1 1493 F pulseaudio CurrentDmesg: [8.408776] NVRM: GPU at :02:00: GPU-e1116370-0337-a0c6-6dce-80e73ebd884a Date: Sun May 19 20:29:36 2013 InstallationDate: Installed on 2013-05-19 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA21.88Z.0075.B03.0811141325 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F42D88C8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42D88C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBA21.88Z.0075.B03.0811141325:bd11/14/08:svnAppleInc.:pnMacBookAir2,1:pvr1.0:rvnAppleInc.:rnMac-F42D88C8:rvr:cvnAppleInc.:ct10:cvrMac-F42D88C8: dmi.product.name: MacBookAir2,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1181828/+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 1876886] Re: chrony autopkgtest fails on armhf (groovy)
At the actual build time it is skipped for being "non-root". But I think this is as easy as now trying to set HW-time in a container. ** Also affects: chrony (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1876886 Title: chrony autopkgtest fails on armhf (groovy) Status in chrony package in Ubuntu: New Status in libcap2 package in Ubuntu: Confirmed Bug description: Test fails on armhf only: running chronyc makestepERROR checking chronyc output OK running chronyc trimrtc ERROR checking chronyc output OK running chronyc writertcERROR This might be a new twist on https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1863590 as it is libcap2 again. This reproduces through a bunch of retries http://autopkgtest.ubuntu.com/packages/c/chrony/groovy/armhf But as I said is armfh only: http://autopkgtest.ubuntu.com/packages/chrony Flagging update-excuse, but I won't be able to get to it immediately ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1876886/+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 479365] Re: assertion failure
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: apport (Ubuntu) Status: Incomplete => Invalid -- 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/479365 Title: assertion failure Status in apport package in Ubuntu: Invalid Status in samba package in Ubuntu: Triaged Bug description: Binary package hint: squid Ubuntu 9.10 squid version 2.7.STABLE6-2ubuntu2 Som when I start up Ubuntu, I have an outstanding failure, which I try to report, but then I get a dialog box titled "Problem in squid" that says, "The problem cannot be reported: The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes." ProblemType: Bug Architecture: i386 Date: Mon Nov 9 13:01:37 2009 DistroRelease: Ubuntu 9.10 Package: squid 2.7.STABLE6-2ubuntu2 ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: squid Uname: Linux 2.6.31-14-generic i686 XsessionErrors: (gnome-settings-daemon:2050): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:2050): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (polkit-gnome-authentication-agent-1:2103): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:2074): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (nautilus:2529): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/479365/+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 892370] Re: The time zone for China should default to Beijing not Shanghai (when offline)
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtimezonemap in Ubuntu. https://bugs.launchpad.net/bugs/892370 Title: The time zone for China should default to Beijing not Shanghai (when offline) Status in Indicator Date and Time: New Status in OEM Priority Project: Won't Fix Status in OEM Priority Project oneiric series: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in OEM Priority Project quantal series: Won't Fix Status in OEM Priority Project raring series: Won't Fix Status in Ubuntu Kylin: New Status in indicator-datetime package in Ubuntu: In Progress Status in libtimezonemap package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Invalid Status in indicator-datetime source package in Quantal: Won't Fix Status in libtimezonemap source package in Quantal: Won't Fix Status in ubiquity source package in Quantal: Won't Fix Status in indicator-datetime source package in Raring: Won't Fix Status in libtimezonemap source package in Raring: Fix Released Status in ubiquity source package in Raring: Won't Fix Status in indicator-datetime source package in Saucy: Won't Fix Status in libtimezonemap source package in Saucy: Fix Released Status in ubiquity source package in Saucy: Won't Fix Bug description: When installing Ubuntu and selecting Simplified Chinese as the default language, the default timezone should point to Beijing instead of Shanghai. Everything in China is referenced to Beijing time. In mainland China this standard time is called Beijing Time (北京时间) domestically but it is commonly referred to as China Standard Time (CST) internationally. This seems to have come up a lot in past bugs: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/228554 https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/517621 Steps to recreate: 1) Install Ubuntu and select Simplified Chinese for the language. Actual Results: At the timezone page, the default city is Shanghai. Expected Results: Most Chinese users prefer it be set to Beijing. It looks as if the upstream tz database needs to be updated for Beijing for starters, as Beijing is not listed in there. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: tzdata 2011n-0ubuntu0.11.10 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Nov 18 15:26:03 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: tzdata UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/892370/+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 993400] Re: apport asked me to restart an application that had already restarted
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: apport (Ubuntu) Status: Incomplete => Invalid -- 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/993400 Title: apport asked me to restart an application that had already restarted Status in apport package in Ubuntu: Invalid Status in apport source package in Precise: Triaged Bug description: I recently received a compiz crash report notification from apport and in the dialog I was asked if I wanted to restart compiz. Given that I was actually seeing the dialog, I was in a desktop environment and compiz was already running. I naturally chose not to restart it and I wonder what would have happened had I chosen to. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: apport 2.0.1-0ubuntu7 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CheckboxSubmission: 2e6ecd139611830c78226ad04ff4c093 CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f CrashReports: 600:120:134:0:2012-04-24 13:49:18.0 -0700:2012-04-15 20:02:57.0 -0700:/var/crash/_usr_lib_ubuntuone-client_ubuntuone-login.1000.uploaded 664:1000:134:0:2012-04-23 15:49:31.0 -0700:2012-04-23 15:49:31.0 -0700:/var/crash/apport.1000.upload 640:1000:134:6005683:2012-05-01 16:01:56.0 -0700:2012-05-01 16:08:34.0 -0700:/var/crash/_usr_bin_compiz.1000.crash 600:120:134:0:2012-05-02 09:36:37.0 -0700:2012-04-30 07:35:12.0 -0700:/var/crash/apport.1000.uploaded 640:1000:134:2039844:2012-04-23 15:49:27.0 -0700:2012-04-29 14:29:59.0 -0700:/var/crash/apport.1000.crash Date: Wed May 2 09:36:37 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to precise on 2012-01-04 (118 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/993400/+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 939446] Re: apport-gtk crashed with SIGSEGV in gdk_window_set_geometry_hints()
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: apport (Ubuntu) Status: Incomplete => Invalid -- 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/939446 Title: apport-gtk crashed with SIGSEGV in gdk_window_set_geometry_hints() Status in RabbitVCS: New Status in apport package in Ubuntu: Invalid Bug description: Ran ubuntu-bug ubiquity and got this crash ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: apport-gtk 1.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.92-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Thu Feb 23 12:50:17 2012 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gtk InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk ubiquity ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f40c8973b80 : mov0x18(%rdi),%rax PC (0x7f40c8973b80) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: gdk_window_set_geometry_hints () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: apport-gtk crashed with SIGSEGV in gdk_window_set_geometry_hints() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin libvirtd lpadmin sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/rabbitvcs/+bug/939446/+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 891421] Re: Please add an accessible description to the indicators.
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: apport (Ubuntu) Status: Incomplete => Invalid -- 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/891421 Title: Please add an accessible description to the indicators. Status in apport package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: Confirmed Bug description: affects ubuntu/update-notifier ubuntu/apport tags 11y The indicator API now supports adding a textual/accessible description to indicators using the app_indicator_set_icon_full method call. It would be very useful if the update-notifier and apport indicator had this description added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/891421/+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 1088957] Re: [ThinkPad T420] hda-intel: spurious response - audio dropping out during playback
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Invalid -- 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/1088957 Title: [ThinkPad T420] hda-intel: spurious response - audio dropping out during playback Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Invalid Bug description: I am testing on raring. To reproduce try playing a you tube video, the audio will go in and out. In addition playing back music in rhythmbox will also exhibit the same problems. When looking at dmesg I see the following lines: [ 1653.495497] hda-intel: spurious response 0x40:0x3, last cmd=0x30270503 [ 1653.495498] hda-intel: spurious response 0x4011:0x3, last cmd=0x30270503 [ 1653.495500] hda-intel: spurious response 0x0:0x3, last cmd=0x30270503 [ 1653.495501] hda-intel: spurious response 0x5:0x3, last cmd=0x30270503 [ 1654.591127] hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x301f0500 Eventually after this the audio cuts out complete and nothing can be heard. Not sure if this is a pulseaudio bug or an intel driver bug. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pulseaudio 1:2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.7.0-5.13-generic 3.7.0-rc8 Uname: Linux 3.7.0-5-generic x86_64 ApportVersion: 2.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arges 2340 F pulseaudio /dev/snd/pcmC0D0p: arges 2340 F...m pulseaudio Date: Tue Dec 11 09:20:33 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2012-08-17 (116 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120807.2) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to raring on 2012-11-26 (14 days ago) dmi.bios.date: 11/28/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET67WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 4177CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET67WW(1.37):bd11/28/2011:svnLENOVO:pn4177CTO:pvrThinkPadT420:rvnLENOVO:rn4177CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4177CTO dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1088957/+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 469409] Re: Problems with audio during the execution of audio test in "System Testing" application in xubuntu 9.10
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Invalid -- 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/469409 Title: Problems with audio during the execution of audio test in "System Testing" application in xubuntu 9.10 Status in alsa-driver package in Ubuntu: Invalid Bug description: When I start System Settings application, the first test goes wrong and I was unable to hear any sound. My system is a IBM thinkpad R40 with Karmic Xubuntu ( 9.10 ). I hear pidgin sound and others but no login - startup sound. ProblemType: Bug Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: riccardo 1510 F xfce4-mixer-plu riccardo 1539 F xfce4-volumed Card0.Amixer.info: Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 11' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 26 Simple ctrls : 18 CheckboxCommand: alsa_record_playback CheckboxDescription: Pair a Bluetooth headset with your system. Then open the volume control application by right-clicking on the speaker icon in the panel and selecting "Sound Preferences". Select the "Input" tab and choose your Bluetooth device. Select the "Output" tab and choose your Bluetooth device. When you are done, click the Test button, then speak into the microphone. After a few seconds, your speech will be played back to you. Did you hear your speech played back? CheckboxTest: alsa_record_playback_bluetooth Date: Sun Nov 1 21:29:58 2009 DistroRelease: Ubuntu 9.10 InstallationMedia: Xubuntu 9.10 "Karmic Koala" - Release i386 (20091028.3) Package: alsa-base 1.0.20+dfsg-1ubuntu5 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: alsa-driver Tags: checkbox-bug Uname: Linux 2.6.31-14-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/469409/+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 1328180] Re: retraces of unity missing information
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
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/1328180
Title:
retraces of unity missing information
Status in Errors:
New
Status in apport package in Ubuntu:
Invalid
Bug description:
The following error:
https://errors.ubuntu.com/problem/4b288186d25cf35ebdcaf541459b40921fba87ba
Contains this in the stacktrace:
#7 0xb11d99f1 in
unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc(_GTask*, void*, void*,
_GCancellable*) () from /srv/daisy.ubuntu.com/production/cache/Ubuntu
14.04/cache-QumZAJ/sandbox/usr/lib/compiz/libunityshell.so
No symbol table info available.
However, the corresponding bug in Launchpad:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1047517
Contains this in the retraced stacktrace:
#7 0xb33484c9 in unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc
(job=0xb2ff4e0, canc=0x0, data=0xb2ff584) at
/build/buildd/unity-6.4.0/unity-shared/IconLoader.cpp:467
file = {object_ = 0xb4eef518}
contents = { = {},
string_ = 0x0}
length = 0
task = 0xb2ff584
One particular difference between the two reports is that the
retracing in errors was done against 14.04 and the retracing in
Launchpad was done with 13.10.
To manage notifications about this bug go to:
https://bugs.launchpad.net/errors/+bug/1328180/+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 1458169] Re: package apport 2.17.2-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: apport (Ubuntu) Status: Incomplete => Invalid -- 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/1458169 Title: package apport 2.17.2-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apport package in Ubuntu: Invalid Bug description: instalowałem arduino ProblemType: Package DistroRelease: Ubuntu 15.04 Package: apport 2.17.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportLog: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CrashReports: 600:0:118:277815:2015-05-23 14:40:30.697401285 +0200:2015-05-23 14:40:31.697401285 +0200:/var/crash/apport.0.crash Date: Sat May 23 14:40:31 2015 DuplicateSignature: package:apport:2.17.2-0ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-05-20 (3 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: apport Title: package apport 2.17.2-0ubuntu1 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/apport/+bug/1458169/+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 1064357] Re: apport crashed with : struct.error: unpack requires a bytes object of length 4 in problem_report.py, line 75, in write
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
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/1064357
Title:
apport crashed with : struct.error: unpack requires a bytes object of
length 4 in problem_report.py, line 75, in write
Status in Python:
Fix Released
Status in apport package in Ubuntu:
Invalid
Bug description:
Quantal armhf up to date
Apport crashed with the error below following an apt-xapian-index
crash. apport crash file attached.
Traceback:
Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 575, in
GLib.idle_add(lambda: self.collect_info(on_finished=self.ui_update_view))
File "/usr/lib/python3/dist-packages/apport/ui.py", line 983, in
collect_info
icthread.exc_raise()
File "/usr/lib/python3/dist-packages/apport/REThread.py", line 64, in
exc_raise
raise self._exception[1].with_traceback(self._exception[2])
File "/usr/lib/python3/dist-packages/apport/REThread.py", line 34, in run
self._retval = self.__target(*self.__args, **self.__kwargs)
File "/usr/lib/python3/dist-packages/apport/ui.py", line 61, in
thread_collect_info
report.add_gdb_info()
File "/usr/lib/python3/dist-packages/apport/report.py", line 652, in
add_gdb_info
self['CoreDump'].write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 75, in write
block = gz.read(1048576)
File "/usr/lib/python3.2/gzip.py", line 343, in read
self._read(readsize)
File "/usr/lib/python3.2/gzip.py", line 405, in _read
self._read_eof()
File "/usr/lib/python3.2/gzip.py", line 437, in _read_eof
crc32 = read32(self.fileobj)
File "/usr/lib/python3.2/gzip.py", line 37, in read32
return struct.unpack("https://bugs.launchpad.net/python/+bug/1064357/+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 1876821] Re: [needs-packaging] gtk+3.24: gtk+3.22 is discontinued
I fully agree, that this is not good for a stable update. But on the other side, developers are forced to discontinue the support for a stable Ubuntu LTS like 18.04, because there are no updates which are necessary to run the application without the newest bugfixes. This will then also force end-users to switch the OS or drop the use of the now not supported end user software, thus the complete sense of a LTS is therefore broken. Also switching to a newer ubuntu version is mostly ok for many end- users, but not for those who use a distribution building on top of Ubuntu 18.04 eg. Linux Mint(, the next release will come end of June). As a developer I wished there would be a rolling release cycle APT repository for LTS Ubuntu distributions, containing at least all stable packages with active support. -- 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/1876821 Title: [needs-packaging] gtk+3.24: gtk+3.22 is discontinued Status in gtk+3.0 package in Ubuntu: Won't Fix Bug description: Since there are no more updates released for gtk+3.22 it is important, that at least gtk+3.24 is added to ubuntu-18.04 APT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1876821/+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 997238] Re: [CA0106 - CA0106, playback] No sound at all since upgrade to 12.04
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Invalid -- 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/997238 Title: [CA0106 - CA0106, playback] No sound at all since upgrade to 12.04 Status in PulseAudio: New Status in alsa-driver package in Ubuntu: Invalid Bug description: The title sums it it up pretty well. Since I upgraded to 12.04, I have no sound anymore... ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: julien 1740 F pulseaudio Card0.Amixer.info: Card hw:0 'CA0106'/'Audigy SE [SB0570] at 0xec00 irq 20' Mixer name : 'CA0106' Components : '' Controls : 35 Simple ctrls : 18 CurrentDmesg: [2.066528] microsoft 0003:045E:00DB.0002: input,hidraw1: USB HID v1.11 Keyboard [Microsoft Natural\xffc2\xffae\xffae Ergonomic Keyboard 4000] on usb-:00:1d.0-2/input0 [2.096177] input: Microsoft Natural\xffc2\xffae\xffae Ergonomic Keyboard 4000 as /devices/pci:00/:00:1d.0/usb5/5-2/5-2:1.1/input/input4 [2.096902] microsoft 0003:045E:00DB.0003: input,hidraw2: USB HID v1.11 Device [Microsoft Natural\xffc2\xffae\xffae Ergonomic Keyboard 4000] on usb-:00:1d.0-2/input1 [4.910980] skge :05:04.0: eth1: Link is up at 100 Mbps, full duplex, flow control both [ 13.760021] eth1: no IPv6 routers present Date: Wed May 9 19:37:07 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:CA0106 failed Symptom_Card: CA0106 Soundblaster - CA0106 Symptom_DevicesInUse: 1740 julienF pulseaudio PID ACCESS COMMAND Symptom_Type: No sound at all Title: [CA0106 - CA0106, playback] No sound at all UpgradeStatus: Upgraded to precise on 2012-05-09 (0 days ago) dmi.bios.date: 12/22/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1901 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Commando 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.:bvr1901:bd12/22/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCommando: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/pulseaudio/+bug/997238/+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 1201112] Re: 64-bit GRUB refuses to Install
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: grub2 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1201112 Title: 64-bit GRUB refuses to Install Status in grub2 package in Ubuntu: Invalid Status in ucf package in Ubuntu: Triaged Bug description: On an attempt to install Saucy from 13.04 (Kubuntu), an error occurs in /usr/bin/ucfq on line 529. Initially, I fixed it by editing the file to directly call `Cwd::abs_path` and let the application continue. It didn't solve the problem (and I've redacted such changes). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: grub-efi-amd64 2.00-15ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Sun Jul 14 09:58:53 2013 EcryptfsInUse: Yes MarkForUpload: True SourcePackage: grub2 UpgradeStatus: Upgraded to saucy on 2013-07-14 (0 days ago) The error from /usr/bin/ucfq was: Undefined subroutine ::abs_path called at /usr/bin/ucfq line 529, line 21. The upgrade to Saucy was done using the executable `kubuntu-devel- release-upgrade`. I've attached a ppa.tar.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1201112/+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 1876886] Re: chrony autopkgtest fails on armhf (groovy)
It is the build phase that fails. Reproduced in armhf container on canonistack. 1. get the source and build deps 2. build that until it breaks 3. re-run via $ cd ~/chrony-3.5/test/system $ ./run -i 20 -m 2 In this repro environment I get two extra fails at: 005-scfilter Testing system call filter: non-default settings: extra_chronyd_options=-F -1 starting chronyd ERROR FAIL stopping chronyd ERROR But also the actual issues: 007-cmdmon Testing chronyc commands: starting chronyd OK running chronyc makestep ERROR checking chronyc output OK running chronyc trimrtc ERROR checking chronyc output OK running chronyc writertc ERROR checking chronyc output OK stopping chronyd OK -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1876886 Title: chrony autopkgtest fails on armhf (groovy) Status in chrony package in Ubuntu: New Status in libcap2 package in Ubuntu: Confirmed Bug description: Test fails on armhf only: running chronyc makestepERROR checking chronyc output OK running chronyc trimrtc ERROR checking chronyc output OK running chronyc writertcERROR This might be a new twist on https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1863590 as it is libcap2 again. This reproduces through a bunch of retries http://autopkgtest.ubuntu.com/packages/c/chrony/groovy/armhf But as I said is armfh only: http://autopkgtest.ubuntu.com/packages/chrony Flagging update-excuse, but I won't be able to get to it immediately ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1876886/+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 1191898] Re: [USB-Audio - USB Sound Blaster HD, playback] fails after reboot
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Invalid -- 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/1191898 Title: [USB-Audio - USB Sound Blaster HD, playback] fails after reboot Status in PulseAudio: New Status in alsa-driver package in Ubuntu: Invalid Bug description: To get the sound card to work, I have to go through this complicated process of: 1) Starting the computer without the card plugged in; 2) Plugging it in; 3) At this point, it does NOT work. I have to select it in the audio settings, try to make it lay a test sound, which it fails, and then select the on-board sound; 4) Reboot with onboard sound selected. Just logging out does NOT work; 5) After reboot, select USB Analogue Output, and it will work, however 6) After a subsequent reboot, it will fail again, and I have to unplug the card and reboot again, starting the whole cycle over. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vasco 2151 F pulseaudio /dev/snd/controlC1: vasco 2151 F pulseaudio /dev/snd/pcmC1D0p: vasco 2151 F...m pulseaudio Date: Mon Jun 17 18:57:29 2013 InstallationDate: Installed on 2012-01-20 (514 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: USB Sound Blaster HD - USB Sound Blaster HD Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - USB Sound Blaster HD, playback] fails after a while UpgradeStatus: Upgraded to raring on 2013-05-06 (42 days ago) dmi.bios.date: 05/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W240EU/W250EUQ/W270EUQ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/24/2012:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: W240EU/W250EUQ/W270EUQ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1191898/+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 1877129] [NEW] jackd won't run in realtime
Public bug reported: Was using jackd2 for ages, never had this issue. The usual limits.conf tweaks are present. Jackd won't run in realtime even as root. It's very easy to reproduce in Focal. Before upgrade, was working: Ubuntu 18.04.4 LTS uname -r kernel 5.3.0-51-generic jackd --version jackdmp version 1.9.12 tmpdir /dev/shm protocol 8 After upgrade: Ubuntu 20.04 LTS uname -r 5.4.0-29-generic jackd --version jackdmp version 1.9.12 tmpdir /dev/shm protocol 8 Simple test: jackd -R -d dummy -r192000 -p2048 jackdmp 1.9.12 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2016 Grame. Copyright 2016-2017 Filipe Coelho. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details Cannot create RT messagebuffer thread: Operation not permitted (1) Retrying messagebuffer thread without RT scheduling Messagebuffer not realtime; consider enabling RT scheduling for user no message buffer overruns Cannot create RT messagebuffer thread: Operation not permitted (1) Retrying messagebuffer thread without RT scheduling Messagebuffer not realtime; consider enabling RT scheduling for user no message buffer overruns Cannot create RT messagebuffer thread: Operation not permitted (1) Retrying messagebuffer thread without RT scheduling Messagebuffer not realtime; consider enabling RT scheduling for user no message buffer overruns JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" Cannot use real-time scheduling (RR/10)(1: Operation not permitted) AcquireSelfRealTime error I'm guessing that it's not jack itself (package ver. seems to be the same as bionic, without new feats), smth is missing in the kernel config. I would try RT kernel, but it usually does not boot at all thanks to Nvidia blob on that system. ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1877129 Title: jackd won't run in realtime Status in jackd2 package in Ubuntu: New Bug description: Was using jackd2 for ages, never had this issue. The usual limits.conf tweaks are present. Jackd won't run in realtime even as root. It's very easy to reproduce in Focal. Before upgrade, was working: Ubuntu 18.04.4 LTS uname -r kernel 5.3.0-51-generic jackd --version jackdmp version 1.9.12 tmpdir /dev/shm protocol 8 After upgrade: Ubuntu 20.04 LTS uname -r 5.4.0-29-generic jackd --version jackdmp version 1.9.12 tmpdir /dev/shm protocol 8 Simple test: jackd -R -d dummy -r192000 -p2048 jackdmp 1.9.12 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2016 Grame. Copyright 2016-2017 Filipe Coelho. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details Cannot create RT messagebuffer thread: Operation not permitted (1) Retrying messagebuffer thread without RT scheduling Messagebuffer not realtime; consider enabling RT scheduling for user no message buffer overruns Cannot create RT messagebuffer thread: Operation not permitted (1) Retrying messagebuffer thread without RT scheduling Messagebuffer not realtime; consider enabling RT scheduling for user no message buffer overruns Cannot create RT messagebuffer thread: Operation not permitted (1) Retrying messagebuffer thread without RT scheduling Messagebuffer not realtime; consider enabling RT scheduling for user no message buffer overruns JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" Cannot use real-time scheduling (RR/10)(1: Operation not permitted) AcquireSelfRealTime error I'm guessing that it's not jack itself (package ver. seems to be the same as bionic, without new feats), smth is missing in the kernel config. I would try RT kernel, but it usually does not boot at all thanks to Nvidia blob on that system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1877129/+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 1224099] Re: [Satellite P200, Realtek ALC268, Black Headphone Out, Front] No sound at all
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Invalid -- 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/1224099 Title: [Satellite P200, Realtek ALC268, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: Invalid Bug description: front headphones work perfect in ubuntu 12.04 LTS. after a fresh instllation of 13.04 - no sound comming out of headphones only front speakers are working. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ilan 4270 F pulseaudio ilan 6673 F pulseaudio /dev/snd/controlC0: ilan 4270 F pulseaudio ilan 6673 F pulseaudio Date: Wed Sep 11 23:12:43 2013 InstallationDate: Installed on 2013-09-11 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ilan 4270 F pulseaudio ilan 6673 F pulseaudio /dev/snd/controlC0: ilan 4270 F pulseaudio ilan 6673 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Satellite P200, Realtek ALC268, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.90 dmi.board.name: ISRAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.90:bd10/23/2007:svnTOSHIBA:pnSatelliteP200:pvrPSPB6E-10M04NEN:rvnTOSHIBA:rnISRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite P200 dmi.product.version: PSPB6E-10M04NEN dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1224099/+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 1835660] Re: initramfs unpacking failed
@vmc, I've noticed the same with nvme, or at least not slower. It slowed after the last update for 20.04 and updating the kernel to 5.40.0-29 however. it was almost 5 seconds faster with version -28 -- 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/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()
#1 is bug 1877075. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1865300 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback() Status in GNOME Shell: Unknown Status in glib2.0 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9 --- Happened during normal use of the desktop. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 29 19:51:58 2020 DisplayManager: gdm3 ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer InstallationDate: Installed on 2020-01-25 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax PC (0x7f5f54fa6444) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1865300/+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 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()
This is the #2 most common gnome-shell crash in focal. ** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1865300 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback() Status in GNOME Shell: Unknown Status in glib2.0 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9 --- Happened during normal use of the desktop. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 29 19:51:58 2020 DisplayManager: gdm3 ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer InstallationDate: Installed on 2020-01-25 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax PC (0x7f5f54fa6444) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1865300/+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 1071380] Re: [LIFEBOOK E8110, Realtek ALC262, Black Headphone Out, Internal] No automute
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Invalid -- 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/1071380 Title: [LIFEBOOK E8110, Realtek ALC262, Black Headphone Out, Internal] No automute Status in alsa-driver package in Ubuntu: Invalid Bug description: internal speakers don't stop playing when jack (Headphone out) is plugged in. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-18.18-lowlatency 3.5.7 Uname: Linux 3.5.0-18-lowlatency i686 ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: silverstarzero 1590 F xfce4-volumed silverstarzero 3601 F pulseaudio /dev/snd/pcmC0D0p: silverstarzero 3601 F...m pulseaudio Date: Thu Oct 25 17:50:27 2012 InstallationDate: Installed on 2012-10-22 (3 days ago) InstallationMedia: Ubuntu-Studio 12.10 "Quantal Quetzal" - Release i386 (20121017.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio interno - HDA Intel Symptom_Jack: Black Headphone Out, Internal Symptom_Type: No auto-mute between outputs Title: [LIFEBOOK E8110, Realtek ALC262, Black Headphone Out, Internal] No automute UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2006 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.14 dmi.board.name: FJNB1AF dmi.board.vendor: FUJITSU dmi.board.version: CP274210-02 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: E8110 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.14:bd08/23/2006:svnFUJITSUSIEMENS:pnLIFEBOOKE8110:pvr:rvnFUJITSU:rnFJNB1AF:rvrCP274210-02:cvnFUJITSUSIEMENS:ct10:cvrE8110: dmi.product.name: LIFEBOOK E8110 dmi.sys.vendor: FUJITSU SIEMENS mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-10-24T13:29:24.001781 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1071380/+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 1040873] Re: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all: Subwoofer not working
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Invalid -- 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/1040873 Title: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all: Subwoofer not working Status in alsa-driver package in Ubuntu: Invalid Bug description: Hi, this bug is a fork of https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/871808 because #871808 stands for a different hardware with a different solution, so people may get confused. Here is a summary (see post #48 to #54 of #871808): The subwoofer of Asus N56VZ laptop doesn't work "out of the box". #sudo hda-jack-sense-test -a : *** Without subwoofer: Pin 0x1e (Black SPDIF Out): present = No *** With subwoofer: Pin 0x1e (Black SPDIF Out): present = Yes http://www.alsa- project.org/db/?f=2778e7f430aa95ae219d0b2bc3cb5e46abd0a33a --> There are two ways of making it work: #1 a. Add to rc.local : echo 0x1e 0x99130112 > /sys/class/sound/hwC0D0/user_pin_configs echo 1 > /sys/class/sound/hwC0D0/reconfig b. Add options snd-hda-intel model=asus-mode4 in /etc/modprobe.d/alsa-base.conf c. Reboot d. Set the mode to "Analog Stereo Output" and then to "Analog Surround 5.1 output" in the sound settings panel. You have to do this each time you reboot!!! #2 a. Add to rc.local : echo 0x16 0x99130111 > /sys/class/sound/hwC0D0/user_pin_configs echo 0x1e 0x99130112 > /sys/class/sound/hwC0D0/user_pin_configs echo 1 > /sys/class/sound/hwC0D0/reconfig b. Reboot c. Set the mode to "Analog Stereo Output" and then to "Analog Surround 5.1 output" in the sound settings panel. You have to do this each time you reboot!!! Both give the same results and fix the bug. --> Can you make it work out of the box? There is still two other bugs on this laptop : - crackling audio when playing with sound volume: see https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1040867 - When I put the omputer in sleep mode, there is no way to get sound working on resume: should I open a new bug to investigate this? Regards Sam ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sam1898 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7a1 irq 47' Mixer name : 'Realtek ALC663' Components : 'HDA:10ec0663,10431477,0012' Controls : 23 Simple ctrls : 13 CheckboxSubmission: 54021779511d0213081a2b1707bf951c CheckboxSystem: 4c773cd91921f9618cc2f1893bc1a87a Date: Thu Aug 23 22:38:00 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: 1898 sam F pulseaudio PID ACCESS COMMAND Symptom_Jack: Black Headphone Out, Right Symptom_Type: No sound at all Title: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.204:bd05/11/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56VZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf:
[Touch-packages] [Bug 834895] Re: ubuntu-bug and package install failures should be disabled when a release reaches EOL
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: apport (Ubuntu) Status: Incomplete => Invalid -- 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/834895 Title: ubuntu-bug and package install failures should be disabled when a release reaches EOL Status in One Hundred Papercuts: Triaged Status in apport package in Ubuntu: Invalid Status in apport source package in Precise: Triaged Bug description: While automatic bug reporting for crashes is disabled in apport when a release becomes stable it is still possible for people to report a bug via 'ubuntu-bug'. This makes sense up until the point the release reaches EOL when ubuntu-bug should no longer be usable. Additionally, the automatic reporting of package installation failures should also be disabled when an Ubuntu release reaches EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/834895/+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 557015] Re: ALC889A 0x1458a102 probably requires model=6stack-dell quirk
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
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/557015
Title:
ALC889A 0x1458a102 probably requires model=6stack-dell quirk
Status in alsa-driver package in Ubuntu:
Invalid
Bug description:
Binary package hint: pulseaudio
Having crawled through the past LTR's issues with sound & attempting those
fixes,
(Ubuntu 7- 8+ onward) I managed to lose and positive progress & all but
1output source.
I finally gave up and set it to: options snd-hda-intel model=auto
in the alsa.base.conf which fortunately returned my audio to normal,
excepting the fact that it will not mute properly when the headphones are
plugged in.
My microphones -do- work however.
Trying the factory drivers for the sound card did not seem to make a
difference.
With luck it's just a problem with the Realtec drivers not being up to
snuff with the kernal (or something.)
Amd Athlon II x3 Lucid 6 apr 2010 daily build
dual monitors
moshpet@m-desktop:~$ hwinfo --sound
21: PCI 14.2: 0403 Audio device
[Created at pci.318]
Unique ID: 5Dex.oA41xEVyYuE
SysFS ID: /devices/pci:00/:00:14.2
SysFS BusID: :00:14.2
Hardware Class: sound
Model: "ATI SBx00 Azalia (Intel HDA)"
Vendor: pci 0x1002 "ATI Technologies Inc"
Device: pci 0x4383 "SBx00 Azalia (Intel HDA)"
SubVendor: pci 0x1458 "Giga-byte Technology"
SubDevice: pci 0xa102
Driver: "HDA Intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xfe024000-0xfe027fff (rw,non-prefetchable)
IRQ: 16 (49932 events)
Module Alias: "pci:v1002d4383sv1458sdA102bc04sc03i00"
Driver Info #0:
Driver Status: snd_hda_intel is active
Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
31: PCI 100.1: 0403 Audio device
[Created at pci.318]
Unique ID: NXNs.fzHWqBOw8N0
Parent ID: _Znp.NfWwNi5KJ96
SysFS ID: /devices/pci:00/:00:02.0/:01:00.1
SysFS BusID: :01:00.1
Hardware Class: sound
Model: "ATI RV730XT Audio device [Radeon HD 4670]"
Vendor: pci 0x1002 "ATI Technologies Inc"
Device: pci 0xaa38 "RV730XT Audio device [Radeon HD 4670]"
SubVendor: pci 0x1682 "XFX Pine Group Inc."
SubDevice: pci 0xaa38
Driver: "HDA Intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xfdefc000-0xfdef (rw,non-prefetchable)
IRQ: 30 (28 events)
Module Alias: "pci:v1002dAA38sv1682sdAA38bc04sc03i00"
Driver Info #0:
Driver Status: snd_hda_intel is active
Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #9 (PCI bridge)
aplay -l
card 0: SB [HDA ATI SB], device 0: ALC889A Analog [ALC889A Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: SB [HDA ATI SB], device 1: ALC889A Digital [ALC889A Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 3: ATI HDMI [ATI HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
moshpet@m-desktop:~$
# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7
# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS && {
/sbin/modprobe --quiet --use-blacklist snd-ioctl32 ; /sbin/modprobe --quiet
--use-blacklist snd-seq ; }
#
# Workaround at bug #499695 (reverted in Ubuntu see LP #319505)
install snd-pcm /sbin/modprobe --ignore-install snd-pcm $CMDLINE_OPTS && {
/sbin/modprobe --quiet --use-blacklist snd-pcm-oss ; : ; }
install snd-mixer /sbin/modprobe --ignore-install snd-mixer $CMDLINE_OPTS &&
{ /sbin/modprobe --quiet --use-blacklist snd-mixer-oss ; : ; }
install snd-seq /sbin/modprobe --ignore-install snd-seq $CMDLINE_OPTS && {
/sbin/modprobe --quiet --use-blacklist snd-seq-midi ; /sbin/modprobe --quiet
--use-blacklist snd-seq-oss ; : ; }
#
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi $CMDLINE_OPTS
&& { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; : ; }
# Cause optional modules to be loaded above sound card driver modules
install snd-emu10k1 /sbin/modprobe
[Touch-packages] [Bug 617842] Re: Error showing url: Operation not supported
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: apport (Ubuntu) Status: Incomplete => Invalid -- 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/617842 Title: Error showing url: Operation not supported Status in apport package in Ubuntu: Invalid Status in xdg-utils package in Ubuntu: New Bug description: Binary package hint: apport I got this error "Error showing url: Operation not supported" when I use either apport-bug or apport-cli. Ubuntu Release - Description: Ubuntu 10.04.1 LTS Release: 10.04 It try with another default webbrowser, it's the same with Opera, Google Chrome. I always got the same error, I think it's the url handler (the program which handles the url to ask the webbrowser to open it which have a problem) UPDATE I've noticed that when I use xdg-open in gnome-terminal, it always output : Error showing url: Operation not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/617842/+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 548877] Re: Trap uncaught exceptions in Java programs
This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you. ** Changed in: apport (Ubuntu) Status: Incomplete => Invalid -- 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/548877 Title: Trap uncaught exceptions in Java programs Status in apport package in Ubuntu: Invalid Bug description: Binary package hint: apport With Java becoming more of a mainstream language for free software programs, it would be nice if apport could capture crashes in these programs. I've written a bit of code for this already, which I will put into a branch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/548877/+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
