[Touch-packages] [Bug 1811596] Re: Ubuntu Single Sign-On GUI not showing login button
I had this problem last year and found a fix by asking here: https://askubuntu.com/questions/1025923/ubuntu-18-04-unity-cant-login- to-my-ubuntu-sso-account-from-unity-control-cen But when I tried logging in on a new installation today, it worked without enabling CSD. Maybe it got fixed? I'm using 18.04.2 now BTW -- 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/1811596 Title: Ubuntu Single Sign-On GUI not showing login button Status in gnome-online-accounts package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Invalid Bug description: System Settings->Online Accounts->Ubuntu Single Sign-On I can enter my email address and password abd select "I have an Ubuntu Single Sign-On account". But there is no "Save" or "Login" or any other button. I can only close the window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1811596/+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 1780552] Re: PulseAudio not running
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1780552 Title: PulseAudio not running Status in pulseaudio package in Ubuntu: Expired Bug description: Can't turn on the audio in control Panel!! No Sound Symbol indicates in status bar!! Fix the bug soon. i using without sound since may.I am looking for a update to fix.But i Still looking to get any update from your side.I send bug report before a week.No Replays from you. Please replay me soon I'M looking for some to fix the Bug! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Jul 7 20:49:19 2018 InstallationDate: Installed on 2018-02-11 (146 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PackageArchitecture: all PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PNFDX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd04/22/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0PNFDX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1780552/+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 1820608] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1820608 Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Expired Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Mar 18 13:38:42 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-01-21 (56 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1820608/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
Yes, and it looks like you need to be a list member first. you could register this list from: https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss -- 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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) 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_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
So is the next step that I should post this to pulseaudio- disc...@lists.freedesktop.org? Do I need to be a list member to post there? -- 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/1828136 Title: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: After rebooting I have no sound. My sound device doesn't show up at all in the mixer. Running "sudo alsa force-reload" corrects the problem, until the next reboot. This problem started in 18.10 and persists now in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 21:50:22 2019 InstallationDate: Installed on 2014-04-19 (1844 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) 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_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. Symptom_Jack: Grey SPDIF Out, Rear Symptom_Type: No sound at all Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 DistroRelease: Ubuntu 19.04 HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a InstallationDate: Installed on 2014-04-19 (1845 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/tcsh ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+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 1607075] Re: systemd 229-4ubuntu7 ADT test failure with linux 4.4.0-33.52
It appears that keyboard-setup.service works reliably in both xenial and eoan. So closing this bug task now. ** Changed in: console-setup (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1607075 Title: systemd 229-4ubuntu7 ADT test failure with linux 4.4.0-33.52 Status in Auto Package Testing: Fix Released Status in autopkgtest package in Ubuntu: Fix Released Status in console-setup package in Ubuntu: Fix Released Bug description: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/s/systemd/20160727_170251@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1607075/+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 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
Any news here? :( If helps, I've also upgraded from Xenial long time ago. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen. Additionally, if I wait a very long time the screen does not lock either. Switching from LightDM to GDM3 fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 6 09:17:35 2017 DisplayManager: lightdm InstallationDate: Installed on 2016-01-22 (592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+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 1826387] Re: systemd-networkd restart brings down bond slaves
** Changed in: systemd Status: Unknown => 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/1826387 Title: systemd-networkd restart brings down bond slaves Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: New Bug description: Reported upstream as https://github.com/systemd/systemd/issues/10118 Ubuntu bionic, systemd version 237-3ubuntu10.19 When systemd-networkd is used to manage network bonds, upon systemd- networkd, bonds are brought down for ~10 seconds affecting connectivity to the server. From networkd logs (truncated to: ``` # journalctl -b -u systemd-networkd | grep enp3s0f Apr 25 12:45:33 compute01 systemd-networkd[30824]: Ignoring /etc/systemd/network/01-enp3s0f1.network, because it's not a regular file with suffix .netdev. Apr 25 12:45:33 compute01 systemd-networkd[30824]: Ignoring /etc/systemd/network/00-enp3s0f0.network, because it's not a regular file with suffix .netdev. Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Flags change: +SLAVE +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link 6 added Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: udev initialized link Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Saved original MTU: 9000 Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Flags change: +SLAVE +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link 3 added Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: udev initialized link Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Saved original MTU: 9000 Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link state is up-to-date Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: found matching network '/etc/systemd/network/01-enp3s0f1.network' Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not managed by us Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Started LLDP. Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Enslaving by 'bond0' Apr 25 12:45:33 compute01 systemd-networkd[30824]: bond0: Link 'enp3s0f1' was up when attempting to enslave it. Bringing link down. Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Bringing link down Apr 25 12:45:33 compute01 systemd-networkd[30824]: bond0: Enslaving link 'enp3s0f1' Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link state is up-to-date Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: found matching network '/etc/systemd/network/00-enp3s0f0.network' Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link does not request DHCPv6 prefix delegation Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Started LLDP. Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Enslaving by 'bond0' Apr 25 12:45:33 compute01 systemd-networkd[30824]: bond0: Link 'enp3s0f0' was up when attempting to enslave it. Bringing link down. Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Bringing link down Apr 25 12:45:33 compute01 systemd-networkd[30824]: bond0: Enslaving link 'enp3s0f0' Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Flags change: -UP -LOWER_UP -RUNNING Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Stopped LLDP. Apr 25 12:45:33 compu
[Touch-packages] [Bug 554172] Re: system services using "console output" not starting at boot
FrankStefani, given the scope of this closed report was fixed in Ubuntu 10.10 (i.e. pre-dating your usage of 12.04), it had and has nothing to do with your problem. However, regarding the problem you are experiencing, it is most helpful if you use the computer the problem is reproducible with and file a new report by running the following from a terminal: ubuntu-bug cups Also, please feel free to subscribe me to it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/554172 Title: system services using "console output" not starting at boot Status in linux package in Ubuntu: Invalid Status in upstart package in Ubuntu: Fix Released Status in linux source package in Lucid: Won't Fix Status in upstart source package in Lucid: Fix Released Status in linux source package in Maverick: Won't Fix Status in upstart source package in Maverick: Fix Released Bug description: Binary package hint: cups Cups is not loading on my machine at boot, must run sudo /etc/init.d/cups start to after booting to print. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: cups 1.4.2-10 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Apr 2 13:07:35 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100401) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Connection refused MachineType: Dell Inc. Studio XPS 1340 Papersize: letter PpdFiles: Brother-HL-2170W-series: Brother HL-2170W Foomatic/pxlmono (recommended) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=615bbe85-506a-4152-af5a-a5c2da303d83 ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: cups dmi.bios.date: 09/08/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0Y279R dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.asset.tag: 1234567890 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0Y279R:rvrA11:cvnDellInc.:ct8:cvrA11: dmi.product.name: Studio XPS 1340 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554172/+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 554172] Re: system services using "console output" not starting at boot
Your comment describes an issue entirely unrelated to this bug report. Please file a separate bug report against the cups package using ubuntu- bug cups. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/554172 Title: system services using "console output" not starting at boot Status in linux package in Ubuntu: Invalid Status in upstart package in Ubuntu: Fix Released Status in linux source package in Lucid: Won't Fix Status in upstart source package in Lucid: Fix Released Status in linux source package in Maverick: Won't Fix Status in upstart source package in Maverick: Fix Released Bug description: Binary package hint: cups Cups is not loading on my machine at boot, must run sudo /etc/init.d/cups start to after booting to print. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: cups 1.4.2-10 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Apr 2 13:07:35 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100401) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Connection refused MachineType: Dell Inc. Studio XPS 1340 Papersize: letter PpdFiles: Brother-HL-2170W-series: Brother HL-2170W Foomatic/pxlmono (recommended) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=615bbe85-506a-4152-af5a-a5c2da303d83 ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: cups dmi.bios.date: 09/08/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0Y279R dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.asset.tag: 1234567890 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0Y279R:rvrA11:cvnDellInc.:ct8:cvrA11: dmi.product.name: Studio XPS 1340 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554172/+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 554172] Re: system services using "console output" not starting at boot
Unbelievable: After many years with Ubuntu-12.04 to 16.04, followed by Linux Mint up to 19.3 (Ubuntu 18.04), I switched to a fresh new install of Lubuntu-19.04 a week ago... and have this strange printer disappear problem for the first time ever! Today is May 18th, 2019 - that is over threet years(!!!) after the last entry in this list. How can that be? What's wrong? -- My printing system for the last 12-15 years based on cups with the following setup: * 1 network laser printer * 3 "symbolic" printers which are a copy of the former, to set defaults for particular uses: "monoprinter" (grayscale), "colorprinter" (full color) and "labelprinter" (use of manual feed) # lpstat -s device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print device for colorprinter: ipp://BRN30055C78CF3B.local:631/ipp/print device for labelprinter: ipp://BRN30055C78CF3B.local:631/ipp/print device for monoprinter: ipp://BRN30055C78CF3B.local:631/ipp/print # ls -l ppd/ total 96 -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O Besides the different settings in /etc/cups/printers.conf, the DeviceURI is the same for all four while the UUID differs: UUID urn:uuid:f81a64b6-71d2-3878-71cf-1b1fd6b4dba3 DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print UUID urn:uuid:63efeecc-be6e-3065-6c0c-9a73bdd0dd62 DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print UUID urn:uuid:756313d5-4548-327f-666b-9f2edf2c8942 DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print UUID urn:uuid:c4abcfb1-c1f2-34fd-4e8f-514209e3e5e9 DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print Any help / hint / solution is highly appreciated - TIA. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/554172 Title: system services using "console output" not starting at boot Status in linux package in Ubuntu: Invalid Status in upstart package in Ubuntu: Fix Released Status in linux source package in Lucid: Won't Fix Status in upstart source package in Lucid: Fix Released Status in linux source package in Maverick: Won't Fix Status in upstart source package in Maverick: Fix Released Bug description: Binary package hint: cups Cups is not loading on my machine at boot, must run sudo /etc/init.d/cups start to after booting to print. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: cups 1.4.2-10 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Apr 2 13:07:35 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100401) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Connection refused MachineType: Dell Inc. Studio XPS 1340 Papersize: letter PpdFiles: Brother-HL-2170W-series: Brother HL-2170W Foomatic/pxlmono (recommended) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=615bbe85-506a-4152-af5a-a5c2da303d83 ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: cups dmi.bios.date: 09/08/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0Y279R dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.asset.tag: 1234567890 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0Y279R:rvrA11:cvnDellInc.:ct8:cvrA11: dmi.product.name: Studio XPS 1340 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554172/+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 577859] Re: printer disappears
*** This bug is a duplicate of bug 554172 *** https://bugs.launchpad.net/bugs/554172 Unbelievable: After years with Ubuntu-12.04 to 16.04, followed by Linux Mint up to 19.3 (Ubuntu 18.04), I switched to a fresh new install of Lubuntu-19.04 a week ago... and have this strange printer disappear problem for the first time ever! Today is May 18th, 2019 - that is eight years(!!!) after the last entry in this list. How can that be? What's wrong? -- My printing system for the last 12-15 years based on cups with the following setup: * 1 network laser printer * 3 "symbolic" printers which are a copy of the former, to set defaults for particular uses: "monoprinter" (grayscale), "colorprinter" (full color) and "labelprinter" (use of manual feed) # lpstat -s device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print device for colorprinter: ipp://BRN30055C78CF3B.local:631/ipp/print device for labelprinter: ipp://BRN30055C78CF3B.local:631/ipp/print device for monoprinter: ipp://BRN30055C78CF3B.local:631/ipp/print # ls -l ppd/ total 96 -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O Besides the different settings in /etc/cups/printers.conf, the DeviceURI is the same for all four while the UUID differs: UUID urn:uuid:f81a64b6-71d2-3878-71cf-1b1fd6b4dba3 DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print UUID urn:uuid:63efeecc-be6e-3065-6c0c-9a73bdd0dd62 DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print UUID urn:uuid:756313d5-4548-327f-666b-9f2edf2c8942 DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print UUID urn:uuid:c4abcfb1-c1f2-34fd-4e8f-514209e3e5e9 DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print Any help / hint / solution is highly appreciated - TIA. -- 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/577859 Title: printer disappears Status in cups package in Ubuntu: Confirmed Bug description: Binary package hint: cups some days ago I've done a fresh install of ubuntu 10.04. It's now the second time that when I try to print a document the printer has disappeared. In the box where one normally selects the printer there's only the option 'Custom...' Workaround: reinstallation of the cups package. After reinstallation the deskjet printer can be selected again. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: cups 1.4.3-1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic-pae 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sun May 9 16:35:56 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) Lpstat: device for Deskjet-6500: hp:/usb/Deskjet_6500?serial=MY47F2P1FH040N MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Deskjet-6500: HP Deskjet 6500 hpijs, 3.10.2 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic-pae root=UUID=b80b8efa-19f2-4c3b-b161-caa4fcce9aff ro quiet splash ProcEnviron: LANG=nl_BE.utf8 SHELL=/bin/bash SourcePackage: cups dmi.bios.date: 11/27/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0105 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5LD2-X/GBL dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: Rev 1.xx dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0105:bd11/27/2007:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5LD2-X/GBL:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx: dmi.product.name: System Product Name dmi.product.version: Rev 1.xx dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/577859/+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 1829621] [NEW] No sound after suspend
Public bug reported: On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available. Thanks a lot :) Additional information: Laptop: HP 14-ma0307ng Ubuntu 19.04 Audio: sudo lspci -v | grep -A7 -i "audio" 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) Subsystem: Hewlett-Packard Company Device 84b6 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at a131 (64-bit, non-prefetchable) [size=16K] Memory at a100 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 5835 F pulseaudio /dev/snd/pcmC0D0c: harry 5835 F...m pulseaudio /dev/snd/pcmC0D0p: harry 5835 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 18 19:12:01 2019 InstallationDate: Installed on 2019-04-30 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-ma0xxx dmi.product.sku: 4DL72EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: 19.04 suspend-resume -- 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/1829621 Title: No sound after suspend Status in pulseaudio package in Ubuntu: New Bug description: On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available. Thanks a lot :) Additional information: Laptop: HP 14-ma0307ng Ubuntu 19.04 Audio: sudo lspci -v | grep -A7 -i "audio" 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) Subsystem: Hewlett-Packard Company Device 84b6 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at a131 (64-bit, non-prefetchable) [size=16K] Memory at a100 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 5835 F pulseaudio /dev/snd/pcmC0D0c: harry 5835 F...m pulseaudio /dev/snd/pcmC0D0p: harry 5835 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 18 19:12:01 2019 InstallationDate: Installed on 2019-04-30 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-ma0xxx dmi.product.sku: 4DL72EA#ABD dmi.product.version: Type1ProductConfigI
[Touch-packages] [Bug 1799279] Re: kernel update hangs inside update-secureboot-policy
*** This bug is a duplicate of bug 1827697 *** https://bugs.launchpad.net/bugs/1827697 This is being tracked in bug #1827697 ** Changed in: apt (Ubuntu) Status: Confirmed => Invalid ** This bug has been marked a duplicate of bug 1827697 Enroll key whiptail prompt blocks kernel header package upgrades -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1799279 Title: kernel update hangs inside update-secureboot-policy Status in apt package in Ubuntu: Invalid Bug description: I just ran `apt-get --auto-remove dist-upgrade` on 18.04. It is hung on update-secureboot-policy waiting for confirmation from whiptail. apt-get --auto-remove dist-upgrade | -/usr/bin/dpkg --status-fd 80 --configure --pending | -/bin/sh /var/lib/dpkg/info/linux-headers-4.15.0-38-generic.postinst configure | -run-parts --report --exit-on-error --arg=4.15.0-38-generic /etc/kernel/header_postinst.d | -/bin/sh /usr/lib/dkms/dkms_autoinstaller start 4.15.0-38-generic | -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic | -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic | -/usr/bin/perl -w /usr/share/debconf/frontend /usr/sbin/update-secureboot-policy --enroll-key | -/bin/sh /usr/sbin/update-secureboot-policy --enroll-key -whiptail --backtitle Package configuration --title Configuring Secure Boot --output-fd 12 --nocancel --msgbox Your system has UEFI Secure Boot enabled. UEFI Secure Boot requires additional configuration to work with third-party drivers. The system will assist you in configuring UEFI Secure Boot. To permit the use of third-party drivers, a new Machine-Owner Key (MOK) has been generated. This key now needs to be enrolled in your system's firmware. To ensure that this change is being made by you as an authorized user, and not by an attacker, you must choose a password now and then confirm the change after reboot using the same password, in both the "Enroll MOK" and "Change Secure Boot state" menus that will be presented to you when this system reboots. If you proceed but do not confirm the password upon reboot, Ubuntu will still be able to boot on your system but any hardware that requires third-party drivers to work correctly may not be usable. --scrolltext 20 77 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.3ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 15:15:56 2018 InstallationDate: Installed on 2018-09-27 (25 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1799279/+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 1829609] Re: files in sudoers.d no longer being read or honored
This bug appears to be related to KDEneon only. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hostname in Ubuntu. https://bugs.launchpad.net/bugs/1829609 Title: files in sudoers.d no longer being read or honored Status in hostname package in Ubuntu: New Bug description: Previously reported bug not ever assigned: https://bugs.launchpad.net/ubuntu/+s...e/+bug/1584549 Currently using KDEneon User Edition LTS 18.04 fully updated. No known entry format in /etc/sudoers.d/ appear to be read by sudoers any longer. All files under /etc/sudoers.d/ are permissions 0440 and root owned. visudo -c confirms the syntax passes the checks. Prior to last month, files in suoders.d were read and worked IF you used the FQDM and not the hostname (as should be allowed thus the prior bug report). Some update must have broken the usage. I have attempted the following formats in /etc/sudoers.d/apt; stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt- get,/usr/bin/apt,/usr/bin/add-apt-repository,/usr/bin/apt-add- repository stuart office = (root) NOPASSWD: /usr/bin/apt- get,/usr/bin/apt,/usr/bin/add-apt-repository,/usr/bin/apt-add- repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-get stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt stuart office.smith.lan = (root) NOPASSWD: /usr/bin/add-apt-repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-add-repository stuart ALL = (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin /add-apt-repository,/usr/bin/apt-add-repository ALL ALL= (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin/add- apt-repository,/usr/bin/apt-add-repository The first one above worked in 16.04. Prior to that (15.04) the second one worked. I have tried all of these and none are honored. apt-cache policy sudo sudo: Installed: 1.8.21p2-3ubuntu1 Candidate: 1.8.21p2-3ubuntu1 Version table: *** 1.8.21p2-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1829609/+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 1829609] Re: files in sudoers.d no longer being read or honored
This appears to be KDEneon only. Please close. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hostname in Ubuntu. https://bugs.launchpad.net/bugs/1829609 Title: files in sudoers.d no longer being read or honored Status in hostname package in Ubuntu: New Bug description: Previously reported bug not ever assigned: https://bugs.launchpad.net/ubuntu/+s...e/+bug/1584549 Currently using KDEneon User Edition LTS 18.04 fully updated. No known entry format in /etc/sudoers.d/ appear to be read by sudoers any longer. All files under /etc/sudoers.d/ are permissions 0440 and root owned. visudo -c confirms the syntax passes the checks. Prior to last month, files in suoders.d were read and worked IF you used the FQDM and not the hostname (as should be allowed thus the prior bug report). Some update must have broken the usage. I have attempted the following formats in /etc/sudoers.d/apt; stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt- get,/usr/bin/apt,/usr/bin/add-apt-repository,/usr/bin/apt-add- repository stuart office = (root) NOPASSWD: /usr/bin/apt- get,/usr/bin/apt,/usr/bin/add-apt-repository,/usr/bin/apt-add- repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-get stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt stuart office.smith.lan = (root) NOPASSWD: /usr/bin/add-apt-repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-add-repository stuart ALL = (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin /add-apt-repository,/usr/bin/apt-add-repository ALL ALL= (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin/add- apt-repository,/usr/bin/apt-add-repository The first one above worked in 16.04. Prior to that (15.04) the second one worked. I have tried all of these and none are honored. apt-cache policy sudo sudo: Installed: 1.8.21p2-3ubuntu1 Candidate: 1.8.21p2-3ubuntu1 Version table: *** 1.8.21p2-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1829609/+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 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
So, 4 weeks later, after my previous comments, and now running stably: Upgraded to 5.0.0-15 today via command line with 'do-release-upgrade'. The triggers looping error still happens but this gets mopped up by dpkg --configure -a which the upgrade script autoruns for you. The 'system error detected' pop-up was still there but I was able to cure this via: https://gitlab.freedesktop.org/spice/linux/vd_agent/commit/098268a33c7c8008ccec9050aea8f0763f1c06d5 '/var/run' is a symlink but errors still happen; just edit out the '/var' prefix for the PIDfile entry in /lib/systemd/system/spice- vdagent.service. I think this above is connected to the problems with virtual box too. Also edit the files /usr/lib/tmpfiles.d/spice-vdagentd.conf & speech- despatcher.conf while you are there. See 'cat /var/log/syslog' and you will see similar errors main spice one that's detailed. VirtualBox itself upgraded without problem, as I was using the ubuntu packages this time. I just needed to editions, from file > prefs, to get get the machines to load up. Don't think this was of significance, but who knows,so I probably should mention another couple of fixes I did before the upgrade, based on syslog entries: This one here for OID file not found errors: https://askubuntu.com/questions/1102926/colord-errors-in-var-log-syslog- in-18-10 The other was commenting out 'max-height' and 'max-width' from gtk- widgets.css in /usr/share/themes/Ambiant-MATE/gtk-3.0. Annoying error that I have been meaning to sort out for a while now ... I have tested this all day. Run it through its paces. Still a few little grumbles showing in the syslog but nothing serious I tend to think. I am guessing things trying to launch before AppArmor will let them, that's all. Seems good. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: New Status in bamf package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.
[Touch-packages] [Bug 1488620] Re: Add LZ4 support to initramfs-tools
Ubuntu core devices forced set LZMA which is now unsupported, fixing to use LZ4 on these now as well. ** Also affects: initramfs-tools-ubuntu-core (Ubuntu) Importance: Undecided Status: New -- 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/1488620 Title: Add LZ4 support to initramfs-tools Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: New Status in initramfs-tools package in Debian: Fix Released Bug description: Original Bug Text = I found that I could enable LZ4 compression for initramfs on my vivid machine by installing liblz4-tool package, adding one line to mkinitramfs and installing a kernel compiled with CONFIG_CRYPTO_LZ4=y. Please include support for (legacy) LZ4. Attached patch includes changes made to the latest version (initramfs- tools_0.120ubuntu3). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1488620/+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 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume
FWIW, I ran into this after updating to 19.04 from 18.04. Audio working fine with HDMI (yay) but not with back panel audio (boo) unless I ran aplay as root, e.g. sudo aplay -D sysdefault:CARD=PCH /usr/share/sounds/alsa/Front_Left.wav ps showed timidity running. 'sudo apt remove timidity; sudo killall timidity' resolved the problem. -- 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/1822426 Title: 19.04 Built in Intel HDA sound is disabled upon resume Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: With 19.04, Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller intermittently is not enabled when resuming from sleep. The HDMI sound device is enabled but that is not hooked up on my system. New with 19.04, when sound works after resume, an icon labeled "Built in Audio Stereo" appears during the resume process. Unsure if this is related, but sound seems to sleep when not in use. Launching sound enabled apps produces a quiet "tick, thud" sound as sound system turns on. When sound is not working, killall pusleaudio "fixes" the issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: darin 4814 F pulseaudio /dev/snd/controlC1: darin 4814 F pulseaudio /dev/snd/controlC0: darin 4814 F pulseaudio CurrentDesktop: KDE Date: Sat Mar 30 10:20:24 2019 InstallationDate: Installed on 2018-01-13 (441 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112) SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago) dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO 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.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822426/+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 1829610] Re: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04
** Attachment added: "Reproducing screenshot of the reproducing clip" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1829610/+attachment/5264682/+files/2019-05-18%2022-22-44%20%E7%9A%84%E8%9E%A2%E5%B9%95%E6%93%B7%E5%9C%96.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829610 Title: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04 Status in gstreamer1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: * The reproducing files are created using SimpleScreenRecorder and OBS Studio * The problem isn't reproduced using `gst-play-1.0 _media_file_` * The system is using intel integrated graphics(Coffee Lake), no other graphics hardware is available * `gstreamer1.0-libav` package is installed ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libgstreamer1.0-0 1.15.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 18 21:43:24 2019 InstallationDate: Installed on 2019-05-08 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] 沒有此一檔案或目錄: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1829610/+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 1829610] Re: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04
Note that regular video clips downloaded from Youtube also reproduce this bug: https://www.youtube.com/watch?v=feOq6MWeUXA -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829610 Title: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04 Status in gstreamer1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: * The reproducing files are created using SimpleScreenRecorder and OBS Studio * The problem isn't reproduced using `gst-play-1.0 _media_file_` * The system is using intel integrated graphics(Coffee Lake), no other graphics hardware is available * `gstreamer1.0-libav` package is installed ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libgstreamer1.0-0 1.15.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 18 21:43:24 2019 InstallationDate: Installed on 2019-05-08 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] 沒有此一檔案或目錄: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1829610/+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 1829610] Re: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04
** Attachment added: "Mediainfo output of the reproducing clip" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1829610/+attachment/5264681/+files/simplescreenrecorder-2019-05-18_21.41.21.mkv.mediainfo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829610 Title: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04 Status in gstreamer1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: * The reproducing files are created using SimpleScreenRecorder and OBS Studio * The problem isn't reproduced using `gst-play-1.0 _media_file_` * The system is using intel integrated graphics(Coffee Lake), no other graphics hardware is available * `gstreamer1.0-libav` package is installed ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libgstreamer1.0-0 1.15.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 18 21:43:24 2019 InstallationDate: Installed on 2019-05-08 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] 沒有此一檔案或目錄: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1829610/+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 1829610] [NEW] Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04
Public bug reported: * The reproducing files are created using SimpleScreenRecorder and OBS Studio * The problem isn't reproduced using `gst-play-1.0 _media_file_` * The system is using intel integrated graphics(Coffee Lake), no other graphics hardware is available * `gstreamer1.0-libav` package is installed ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libgstreamer1.0-0 1.15.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 18 21:43:24 2019 InstallationDate: Installed on 2019-05-08 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] 沒有此一檔案或目錄: '/var/log/Xorg.0.log' ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Also affects: totem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829610 Title: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04 Status in gstreamer1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: * The reproducing files are created using SimpleScreenRecorder and OBS Studio * The problem isn't reproduced using `gst-play-1.0 _media_file_` * The system is using intel integrated graphics(Coffee Lake), no other graphics hardware is available * `gstreamer1.0-libav` package is installed ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libgstreamer1.0-0 1.15.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 18 21:43:24 2019 InstallationDate: Installed on 2019-05-08 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] 沒有此一檔案或目錄: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1829610/+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 1829610] Re: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04
** Attachment added: "Reproducing clip" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1829610/+attachment/5264680/+files/simplescreenrecorder-2019-05-18_21.41.21.mkv -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829610 Title: Totem displayed distorted image when playing certain H.264 videos in Ubuntu 19.04 Status in gstreamer1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: * The reproducing files are created using SimpleScreenRecorder and OBS Studio * The problem isn't reproduced using `gst-play-1.0 _media_file_` * The system is using intel integrated graphics(Coffee Lake), no other graphics hardware is available * `gstreamer1.0-libav` package is installed ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libgstreamer1.0-0 1.15.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 18 21:43:24 2019 InstallationDate: Installed on 2019-05-08 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] 沒有此一檔案或目錄: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1829610/+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 1829609] [NEW] files in sudoers.d no longer being read or honored
Public bug reported: Previously reported bug not ever assigned: https://bugs.launchpad.net/ubuntu/+s...e/+bug/1584549 Currently using KDEneon User Edition LTS 18.04 fully updated. No known entry format in /etc/sudoers.d/ appear to be read by sudoers any longer. All files under /etc/sudoers.d/ are permissions 0440 and root owned. visudo -c confirms the syntax passes the checks. Prior to last month, files in suoders.d were read and worked IF you used the FQDM and not the hostname (as should be allowed thus the prior bug report). Some update must have broken the usage. I have attempted the following formats in /etc/sudoers.d/apt; stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt- get,/usr/bin/apt,/usr/bin/add-apt-repository,/usr/bin/apt-add-repository stuart office = (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin /add-apt-repository,/usr/bin/apt-add-repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-get stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt stuart office.smith.lan = (root) NOPASSWD: /usr/bin/add-apt-repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-add-repository stuart ALL = (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin /add-apt-repository,/usr/bin/apt-add-repository ALL ALL= (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin/add- apt-repository,/usr/bin/apt-add-repository The first one above worked in 16.04. Prior to that (15.04) the second one worked. I have tried all of these and none are honored. apt-cache policy sudo sudo: Installed: 1.8.21p2-3ubuntu1 Candidate: 1.8.21p2-3ubuntu1 Version table: *** 1.8.21p2-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: hostname (Ubuntu) Importance: Undecided Status: New ** Tags: sudo sudoers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hostname in Ubuntu. https://bugs.launchpad.net/bugs/1829609 Title: files in sudoers.d no longer being read or honored Status in hostname package in Ubuntu: New Bug description: Previously reported bug not ever assigned: https://bugs.launchpad.net/ubuntu/+s...e/+bug/1584549 Currently using KDEneon User Edition LTS 18.04 fully updated. No known entry format in /etc/sudoers.d/ appear to be read by sudoers any longer. All files under /etc/sudoers.d/ are permissions 0440 and root owned. visudo -c confirms the syntax passes the checks. Prior to last month, files in suoders.d were read and worked IF you used the FQDM and not the hostname (as should be allowed thus the prior bug report). Some update must have broken the usage. I have attempted the following formats in /etc/sudoers.d/apt; stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt- get,/usr/bin/apt,/usr/bin/add-apt-repository,/usr/bin/apt-add- repository stuart office = (root) NOPASSWD: /usr/bin/apt- get,/usr/bin/apt,/usr/bin/add-apt-repository,/usr/bin/apt-add- repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-get stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt stuart office.smith.lan = (root) NOPASSWD: /usr/bin/add-apt-repository stuart office.smith.lan = (root) NOPASSWD: /usr/bin/apt-add-repository stuart ALL = (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin /add-apt-repository,/usr/bin/apt-add-repository ALL ALL= (root) NOPASSWD: /usr/bin/apt-get,/usr/bin/apt,/usr/bin/add- apt-repository,/usr/bin/apt-add-repository The first one above worked in 16.04. Prior to that (15.04) the second one worked. I have tried all of these and none are honored. apt-cache policy sudo sudo: Installed: 1.8.21p2-3ubuntu1 Candidate: 1.8.21p2-3ubuntu1 Version table: *** 1.8.21p2-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1829609/+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 1584549] Re: sudoers not honoring hostnames
Now using 18.04 KDEneon and last month sometime an update broke this functionality even further. The FQDN and indeed no other format works any longer. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hostname in Ubuntu. https://bugs.launchpad.net/bugs/1584549 Title: sudoers not honoring hostnames Status in hostname package in Ubuntu: Confirmed Bug description: New Kubuntu 16.04 install, adding features from previous 15.04 install. Added exact copy of /etc/sudoers.d/apt from 15.04 to 16.04 but it does not work as expected. File contents: myusername myhostname = NOPASSWD: /usr/bin/apt, /usr/bin/apt-get, /usr/bin/add-apt-repository results in 15.04 in user "myusername" being able to run apt, apt-get, and add-apt-repository from the CLI using sudo without a password prompt. However, same exact syntax in 16.04 results in password prompt. In the 16.04 install, changing "myhostname" to "ALL" resumes the no password behavior. Both installs have exact same /etc/hosts files, running on bare metal on the same system, and the "hostname" command results in the same reply with the correct hostname. I have compared the subject files several times and there are no differences. No errors editing any of the files using visudo. Permissions and syntax same on both systems. This leads me to conclude sudoers is not honoring the hostname in the sudoers file(s). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hostname/+bug/1584549/+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 1572752] Re: improve UTC setting migration on upgrades
** Tags added: id-5cdeb9fd019d774244463b71 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1572752 Title: improve UTC setting migration on upgrades Status in sysvinit package in Ubuntu: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: [SRU Justification] On upgrade, some users who have selected a non-default setting for their clock handling in the installer will see prompts for a conffile they never edited by hand. [Regression potential] Because we are adding a pre-dependency to a package, there is risk of this causing upgrade failures. The upgrade path should be tested aggressively with different profiles from both 14.04 and 15.10 before publishing to -updates. [Test case] 1. On a newly-installed 14.04 system, edit /etc/default/rcS to contain 'UTC=no' instead of 'UTC=yes'. Make no other changes to this file. 2. Enable -proposed in your apt sources. 3. Run do-release-upgrade or update-manager to upgrade to 16.04. 4. Confirm that the upgrade succeeds. 5. Confirm that you are not shown a conffile prompt for /etc/default/rcS on upgrade. 6. Confirm that /etc/adjtime has been created, with 'LOCAL' as the third line of the file. 7. Repeat steps 1-6 for a newly-installed 15.10 system. slangasek | pitti: I see sysvinit Breaks: systemd (<< 228-5ubuntu3), but that doesn't enforce systemd 228-5ubuntu3 being configured before sysvinit, which means the conffile may already be migrated away before systemd postinst runs... I think the right way to do this is with initscripts Pre-Depends: systemd, and for initscripts' preinst script to handle any conffile cleaning so that users are spared conffile prompts on upgrade pitti | slangasek: ah, good point; this needs to be tested thoroughly, pre-depends have some habit of causing trouble See bug 1541532 and http://launchpadlibrarian.net/236311219/systemd_228-5ubuntu2_228-5ubuntu3.diff.gz and http://launchpadlibrarian.net/236367969/sysvinit_2.88dsf-59.3ubuntu1_2.88dsf-59.3ubuntu2.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1572752/+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 1389336] Re: Use geoclue-2.0
geoclue and ubuntu-geoip are being removed in eoan now ** Changed in: ubuntu-geoip (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtlocation-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Won't Fix Status in qtlocation-opensource-src package in Ubuntu: Fix Released Status in ubuntu-geoip package in Ubuntu: Won't Fix Status in webkit2gtk package in Ubuntu: Fix Released Status in webkitgtk package in Ubuntu: Fix Released Status in qtlocation-opensource-src package in Debian: Fix Released Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+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 1799279] Re: kernel update hangs inside update-secureboot-policy
Still present in 19.04 (kubuntu in my case). It's very annoying that every time I have to upgrade the kernel my call to "apt dist-upgrade" hangs and I have to kill update-secureboot-policy to complete the upgrade. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1799279 Title: kernel update hangs inside update-secureboot-policy Status in apt package in Ubuntu: Confirmed Bug description: I just ran `apt-get --auto-remove dist-upgrade` on 18.04. It is hung on update-secureboot-policy waiting for confirmation from whiptail. apt-get --auto-remove dist-upgrade | -/usr/bin/dpkg --status-fd 80 --configure --pending | -/bin/sh /var/lib/dpkg/info/linux-headers-4.15.0-38-generic.postinst configure | -run-parts --report --exit-on-error --arg=4.15.0-38-generic /etc/kernel/header_postinst.d | -/bin/sh /usr/lib/dkms/dkms_autoinstaller start 4.15.0-38-generic | -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic | -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic | -/usr/bin/perl -w /usr/share/debconf/frontend /usr/sbin/update-secureboot-policy --enroll-key | -/bin/sh /usr/sbin/update-secureboot-policy --enroll-key -whiptail --backtitle Package configuration --title Configuring Secure Boot --output-fd 12 --nocancel --msgbox Your system has UEFI Secure Boot enabled. UEFI Secure Boot requires additional configuration to work with third-party drivers. The system will assist you in configuring UEFI Secure Boot. To permit the use of third-party drivers, a new Machine-Owner Key (MOK) has been generated. This key now needs to be enrolled in your system's firmware. To ensure that this change is being made by you as an authorized user, and not by an attacker, you must choose a password now and then confirm the change after reboot using the same password, in both the "Enroll MOK" and "Change Secure Boot state" menus that will be presented to you when this system reboots. If you proceed but do not confirm the password upon reboot, Ubuntu will still be able to boot on your system but any hardware that requires third-party drivers to work correctly may not be usable. --scrolltext 20 77 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.3ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 15:15:56 2018 InstallationDate: Installed on 2018-09-27 (25 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1799279/+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 1829599] [NEW] Does not report error about setting an unsupported resample method
Public bug reported: Command 'pulseaudio --dump-resample-methods' displays available resample methods, but there are more methods described in 'man pulse- daemon.conf'. For example, if I run 'pulseaudio --resample-method=soxr- hq'. Either it should be documented which resample method is used, if an unavailable one is requested, or it should report an error. Anyway, as for 'pulseaudio --resample-method=' tab completion in Bash works well listing available methods. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE Date: Sat May 18 10:26:58 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (1699 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to xenial on 2018-04-14 (398 days ago) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1829599 Title: Does not report error about setting an unsupported resample method Status in pulseaudio package in Ubuntu: New Bug description: Command 'pulseaudio --dump-resample-methods' displays available resample methods, but there are more methods described in 'man pulse- daemon.conf'. For example, if I run 'pulseaudio --resample-method =soxr-hq'. Either it should be documented which resample method is used, if an unavailable one is requested, or it should report an error. Anyway, as for 'pulseaudio --resample-method=' tab completion in Bash works well listing available methods. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE Date: Sat May 18 10:26:58 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (1699 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to xenial on 2018-04-14 (398 days ago) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829599/+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
