[Touch-packages] [Bug 1805027] Re: systemd-resolved can't resolve Comcast mail server addresses
*** This bug is a duplicate of bug 1811471 *** https://bugs.launchpad.net/bugs/1811471 The same symptons appear for "emea.mail.microsoft.com" even with systemd 237-3ubuntu10.21 from -updates. -- 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/1805027 Title: systemd-resolved can't resolve Comcast mail server addresses Status in systemd package in Ubuntu: Triaged Bug description: 1) Ubuntu release: 18.10 2) systemd-resolved version: (Default latest version that comes with Ubuntu 18.10) 3) Expected behavior: Comcast's POP3 mail server addresses to be resolved to IP addresses 4) Actual behavior: Comcast's POP3 mail server addresses can't be resolved to IP addresses Starting on Monday, November 19, 2018, Comcast made a DNS change related to its POP3 mail servers (mail.comcast.net and pop3.comcast.net) that prevent resolved from being able to resolve those domains into IP addresses. When I try to ping either host (mail.comcast.net or pop2.comcast.net), I get this error: tom@deathstar:~$ ping mail.comcast.net ping: mail.comcast.net: Name or service not known tom@deathstar:~$ When I manually lookup up the domain, I get these results: tom@deathstar:~$ nslookup mail.comcast.net Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: mail.comcast.net canonical name = imap.ge.xfinity.com. Name: imap.ge.xfinity.com Address: 96.118.242.209 Name: imap.ge.xfinity.com Address: 96.118.242.197 Name: imap.ge.xfinity.com Address: 96.118.242.233 Name: imap.ge.xfinity.com Address: 96.118.242.225 Name: imap.ge.xfinity.com Address: 96.118.242.226 Name: imap.ge.xfinity.com Address: 96.118.242.217 Name: imap.ge.xfinity.com Address: 96.118.242.208 Name: imap.ge.xfinity.com Address: 96.118.242.230 Name: imap.ge.xfinity.com Address: 96.118.242.232 Name: imap.ge.xfinity.com Address: 96.118.242.218 Name: imap.ge.xfinity.com Address: 96.118.242.211 Name: imap.ge.xfinity.com Address: 96.118.242.242 Name: imap.ge.xfinity.com Address: 96.118.242.221 Name: imap.ge.xfinity.com Address: 96.118.242.196 Name: imap.ge.xfinity.com Address: 96.118.208.40 Name: imap.ge.xfinity.com Address: 96.118.208.99 Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fee8:4f07 Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fe7d:1b0c Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fe25:5ae5 Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fef6:babc Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fe87:c172 Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fee6:7a57 Name: imap.ge.xfinity.com Address: 2001:558:fc11:9:f816:3eff:fe0f:a4a Name: imap.ge.xfinity.com Address: 2001:558:fc11:2:f816:3eff:fec7:cb93 Name: imap.ge.xfinity.com Address: 2001:558:fee2:1000:f816:3eff:fe42:4f14 Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:fe33:9aaa Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:feb2:8c0d Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:fef1:25a5 Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:febd:320a Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:fe36:aba3 Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:fe3f:76f2 Name: imap.ge.xfinity.com Address: 2001:558:fc18:0:f816:3eff:fe45:1d1e tom@deathstar:~$ dig mail.comcast.net ; <<>> DiG 9.11.4-3ubuntu5-Ubuntu <<>> mail.comcast.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15037 ;; flags: qr rd ra; QUERY: 1, ANSWER: 17, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;mail.comcast.net.IN A ;; ANSWER SECTION: mail.comcast.net. 15 IN CNAME imap.ge.xfinity.com. imap.ge.xfinity.com. 12 IN A 96.117.3.119 imap.ge.xfinity.com. 12 IN A 96.117.3.96 imap.ge.xfinity.com. 12 IN A 96.117.3.143 imap.ge.xfinity.com. 12 IN A 96.117.3.145 imap.ge.xfinity.com. 12 IN A 96.117.3.129 imap.ge.xfinity.com. 12 IN A 96.117.3.148 imap.ge.xfinity.com. 12 IN A 96.117.3.201 imap.ge.xfinity.com. 12 IN A 96.117.3.136 imap.ge.xfinity.com. 12 IN A 96.118.133.238 imap.ge.xfinity.com. 12 IN A 96.117.3.128 imap.ge.xfinity.com. 12 IN A 96.117.3.144 imap.ge.xfinity.com. 12 IN A 96.117.2.238 imap.ge.xfinity.com. 12 IN A 96.117.3.110 imap.ge.xfinity.com. 12 IN A 96.117.3.140 imap.ge.xfinity.com. 12 IN A 96.117.3.154
[Touch-packages] [Bug 1828190] Re: latest wget debian for ubuntu 16.04
A vulnerability in GNU Wget could allow an unauthenticated, remote attacker to execute arbitrary code or cause a denial of service (DoS) condition on a targeted system. The source code (wget 1.20.2) carrying the fix for same is available at https://ftp.gnu.org/gnu/wget/wget-1.20.2.tar.gz However, this is not available in Debian repo. Hence, how can I consume this fix (wget 1.20.2) in my solution if the package is not available in release page -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1828190 Title: latest wget debian for ubuntu 16.04 Status in wget package in Ubuntu: Invalid Bug description: We are looking for the latest debians for wget in ubuntu 16.04. Can someone help? This is to address some security vulnerabilities To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1828190/+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 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: Fix Committed Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: Fix Committed Status in apt source package in Eoan: Incomplete Status in ubuntu-release-upgrader source package in Eoan: Fix Released Bug description: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeViewNonInteractive 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging. [Regression Potential] The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong. [Original Description] I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796193/+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 1758924] Re: 'ssh-add -l' doesn't list the key email/comment (unlike gnome-keyring's agent used to)
[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/1758924 Title: 'ssh-add -l' doesn't list the key email/comment (unlike gnome- keyring's agent used to) Status in openssh package in Ubuntu: Expired Bug description: Updated today, it moved from 2018-03-26 08:11:25 upgrade gnome-keyring:amd64 3.27.4-2ubuntu1 3.28.0.1-1ubuntu1 to 2018-03-26 08:14:34 status installed gnome-keyring:amd64 3.28.0.1-1ubuntu1 After this, noticed that some local code that uses ssh key comments (from 'ssh-add -l' output) for automatic annotations is no longer working right. Previously (example from 16.04): nneul@skyhawk:~ $ ssh-add -l 2048 SHA256:.. nn...@neulinger.org (RSA) Now (from current 18): nneul@infinity:~ $ ssh-add -l 2048 SHA256:.. /users/nneul/.ssh/id_rsa (RSA) This is a negative change from my perspective as we are making use of that comment for automatic annotations (not security sensitive) and things like automatically populating git identity when managing a shared application development/server accounts. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-keyring 3.28.0.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 26 08:51:30 2018 InstallationDate: Installed on 2015-11-09 (867 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-keyring UpgradeStatus: Upgraded to bionic on 2017-12-05 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1758924/+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 1829113] [NEW] CUPS says job completed but the PDF doesnt print, wile printing via lpr works
Public bug reported: Driver installed from manufacturer's website, test page prints OK on USB printer Brother DCP-1510. When I send the PDF document for printing, the printer displays "Receiving data" but then nothing prints. CUPS says "job completed" and I cant discern any useful errors in /var/log/cups/error_log Printing the same document via lpr worked -- the document printed fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.4 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed May 15 12:08:27 2019 InstallationDate: Installed on 2019-04-12 (32 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lpstat: device for Brother-DCP-1510-series: usb://Brother/DCP-1510%20series?serial=E72065A8N348435 MachineType: Hewlett-Packard HP Z420 Workstation Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Brother-DCP-1510-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Brother-DCP-1510-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=b3062c40-ce3c-4a67-9e83-4bca7967e954 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v02.55 dmi.board.asset.tag: JPWH505625 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: JPWH505625 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v02.55:bd02/07/2013:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.product.sku: LJ449AV dmi.sys.vendor: Hewlett-Packard ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic -- 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/1829113 Title: CUPS says job completed but the PDF doesnt print, wile printing via lpr works Status in cups package in Ubuntu: New Bug description: Driver installed from manufacturer's website, test page prints OK on USB printer Brother DCP-1510. When I send the PDF document for printing, the printer displays "Receiving data" but then nothing prints. CUPS says "job completed" and I cant discern any useful errors in /var/log/cups/error_log Printing the same document via lpr worked -- the document printed fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.4 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed May 15 12:08:27 2019 InstallationDate: Installed on 2019-04-12 (32 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lpstat: device for Brother-DCP-1510-series: usb://Brother/DCP-1510%20series?serial=E72065A8N348435 MachineType: Hewlett-Packard HP Z420 Workstation Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Brother-DCP-1510-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Brother-DCP-1510-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=b3062c40-ce3c-4a67-9e83-4bca7967e954 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J61 v02.55 dmi.board.asset.tag: JPWH505625 dmi.board.name: 1589 dmi.board.vendor: Hewlett-Packard dmi.board.version: 0.00 dmi.chassis.asset.tag: JPWH505625 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ61v02.55:bd02/07/2013:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53335X G=D dmi.product.name: HP Z420 Workstation dmi.product.sku: LJ449AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1829113/+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 1829110] [NEW] package sudo 1.8.16-0ubuntu1.6 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Public bug reported: I just cant figure it out. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sudo 1.8.16-0ubuntu1.6 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue May 14 21:30:07 2019 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2019-04-23 (21 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.29ubuntu0.1 SourcePackage: sudo Title: package sudo 1.8.16-0ubuntu1.6 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK ** Affects: sudo (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 sudo in Ubuntu. https://bugs.launchpad.net/bugs/1829110 Title: package sudo 1.8.16-0ubuntu1.6 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in sudo package in Ubuntu: New Bug description: I just cant figure it out. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sudo 1.8.16-0ubuntu1.6 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue May 14 21:30:07 2019 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2019-04-23 (21 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.29ubuntu0.1 SourcePackage: sudo Title: package sudo 1.8.16-0ubuntu1.6 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1829110/+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 1829110] Re: package sudo 1.8.16-0ubuntu1.6 failed to install/upgrade: subprocess installed pre-removal script 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 sudo in Ubuntu. https://bugs.launchpad.net/bugs/1829110 Title: package sudo 1.8.16-0ubuntu1.6 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in sudo package in Ubuntu: New Bug description: I just cant figure it out. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sudo 1.8.16-0ubuntu1.6 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue May 14 21:30:07 2019 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2019-04-23 (21 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.29ubuntu0.1 SourcePackage: sudo Title: package sudo 1.8.16-0ubuntu1.6 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1829110/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
Gah. Sorry about not picking this up on my first pass through, but what's happening with Cosmic here? As far as I can tell, this also applies to Cosmic (but not Disco), and Cosmic is still supported for a couple of months (long enough that I'm hesitant to go “sure, we don't need to worry about it”). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Committed Status in libqmi source package in Bionic: Fix Committed Status in modemmanager source package in Bionic: Fix Committed Status in libmbim source package in Disco: Fix Released Status in libqmi source package in Disco: Fix Released Status in modemmanager source package in Disco: Fix Released Status in libmbim source package in Eoan: Fix Released Status in libqmi source package in Eoan: Fix Released Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1829095] [NEW] Keyborad backligt does not work
Public bug reported: I have a dell XPS14 (L421X). In releases 18.04 and lower the keyboard back light used to work. However in 18.10 and 19.04 it does not The dell_laptop model is loaded. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubuntu-desktop 1.431 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 15 11:44:51 2019 InstallationDate: Installed on 2019-04-23 (21 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1829095 Title: Keyborad backligt does not work Status in ubuntu-meta package in Ubuntu: New Bug description: I have a dell XPS14 (L421X). In releases 18.04 and lower the keyboard back light used to work. However in 18.10 and 19.04 it does not The dell_laptop model is loaded. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubuntu-desktop 1.431 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 15 11:44:51 2019 InstallationDate: Installed on 2019-04-23 (21 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1829095/+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 1829019] Re: Desktop runs at low frame rate
*** This bug is a duplicate of bug 1799266 *** https://bugs.launchpad.net/bugs/1799266 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 1799266, 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 1799266 gnome-shell uses high CPU when simply moving windows -- 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/1829019 Title: Desktop runs at low frame rate Status in xorg package in Ubuntu: New Bug description: Moving windows around and using the launcher results in low frame rate (<20 fps), instead of moving smoothly (~60fps). I don't have this issues when I watch videos on YouTube, but I find that the problem is common in all the GNOME-based distros I tried (Ubuntu, Fedora, Clear Linux). Also, the cursor runs smoothly without issues. I'm running Ubuntu 19.04 (with the default updated packages) on a Chuwi 12.3 LapBook with an Intel Celeron N3450 and 6GB of RAM, at 2736 x 1824 pixels of resolution. In addition I directly filed a bug on the GNOME-shell issue page (https://gitlab.gnome.org/GNOME/gnome-shell/issues/1237). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.405 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 14 13:34:36 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: CHUWI INNOVATION AND TECHNOLOGY(SHENZHEN)CO.,LTD NA123 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B3W6_NA123C.033 dmi.board.asset.tag: Hampoo Reserved dmi.board.name: B3W6_NA123C dmi.board.vendor: Hampoo dmi.board.version: Hampoo Reserved dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB3W6_NA123C.033:bd06/12/2017:svnCHUWIINNOVATIONANDTECHNOLOGY(SHENZHEN)CO.,LTD:pnNA123:pvrReserved:rvnHampoo:rnB3W6_NA123C:rvrHampooReserved:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ApolloLake MRD dmi.product.name: NA123 dmi.product.sku: Hampoo Reserved dmi.product.version: Reserved dmi.sys.vendor: CHUWI INNOVATION AND TECHNOLOGY(SHENZHEN)CO.,LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/1829019/+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 1829019] Re: Desktop runs at low frame rate
*** This bug is a duplicate of bug 1799266 *** https://bugs.launchpad.net/bugs/1799266 Also, it sounds like you are using fractional scaling. If so then please try scale 100% or 200% instead. Fractional scaling is expected to underperform: https://discourse.ubuntu.com/t/x11-hidpi-scaling-available-for-testing- on-disco/10293/16 -- 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/1829019 Title: Desktop runs at low frame rate Status in xorg package in Ubuntu: New Bug description: Moving windows around and using the launcher results in low frame rate (<20 fps), instead of moving smoothly (~60fps). I don't have this issues when I watch videos on YouTube, but I find that the problem is common in all the GNOME-based distros I tried (Ubuntu, Fedora, Clear Linux). Also, the cursor runs smoothly without issues. I'm running Ubuntu 19.04 (with the default updated packages) on a Chuwi 12.3 LapBook with an Intel Celeron N3450 and 6GB of RAM, at 2736 x 1824 pixels of resolution. In addition I directly filed a bug on the GNOME-shell issue page (https://gitlab.gnome.org/GNOME/gnome-shell/issues/1237). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.405 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 14 13:34:36 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: CHUWI INNOVATION AND TECHNOLOGY(SHENZHEN)CO.,LTD NA123 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B3W6_NA123C.033 dmi.board.asset.tag: Hampoo Reserved dmi.board.name: B3W6_NA123C dmi.board.vendor: Hampoo dmi.board.version: Hampoo Reserved dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB3W6_NA123C.033:bd06/12/2017:svnCHUWIINNOVATIONANDTECHNOLOGY(SHENZHEN)CO.,LTD:pnNA123:pvrReserved:rvnHampoo:rnB3W6_NA123C:rvrHampooReserved:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ApolloLake MRD dmi.product.name: NA123 dmi.product.sku: Hampoo Reserved dmi.product.version: Reserved dmi.sys.vendor: CHUWI INNOVATION AND TECHNOLOGY(SHENZHEN)CO.,LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/1829019/+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 1829053] Re: driver won't install of intel
Please try this: sudo apt update sudo apt -f install ** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) ** Changed in: xserver-xorg-video-intel (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/1829053 Title: driver won't install of intel Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: [sudo] password for sheharyar: Sorry, try again. [sudo] password for sheharyar: Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-video-intel : Depends: xorg-video-abi-20 Depends: xserver-xorg-core (>= 2:1.17.99.902) E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue May 14 22:59:45 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:143a] Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470] [1002:68e0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Park [Mobility Radeon HD 5430/5450/5470] [103c:143a] InstallationDate: Installed on 2019-04-13 (31 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: Hewlett-Packard HP G72 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=51795b73-d359-48d5-89d1-7c6297784ee8 ro nomodeset quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.48 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 143A dmi.board.vendor: Hewlett-Packard dmi.board.version: 60.50 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.48:bd11/09/2011:svnHewlett-Packard:pnHPG72NotebookPC:pvr058E11252710001620100:rvnHewlett-Packard:rn143A:rvr60.50:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV dmi.product.name: HP G72 Notebook PC dmi.product.version: 058E11252710001620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed May 15 03:54:01 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1829053/+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 1829069] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1829069 Title: Xorg freeze Status in Ubuntu: Incomplete Bug description: i can't open files app and terminal in my ubuntu while using chrome remote desktop. and also ubuntu froze ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 15 02:08:17 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: I don't know GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:2213] InstallationDate: Installed on 2019-04-01 (43 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 001 Device 004: ID 0bda:b001 Realtek Semiconductor Corp. Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=1dbcbc41-3811-4525-8a07-83de047700c3 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2213 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd09/19/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr096C11405F00050660180:rvnHewlett-Packard:rn2213:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.version: 096C11405F00050660180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1829069/+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 1829025] Re: mouse
Please describe in more detail what aspect of the mouse is not working well. According to the attached logs, it sounds like a generic "USB OPTICAL MOUSE". ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (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/1829025 Title: mouse Status in xorg-server package in Ubuntu: Incomplete Bug description: mousse dont work well ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue May 14 10:20:32 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 82946GZ/GL Integrated Graphics Controller [8086:2972] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo 82946GZ/GL Integrated Graphics Controller [17aa:300b] ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=876b673d-874d-476c-90be-90e7f71c5a7e ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2007 dmi.chassis.vendor: LENOVO dmi.product.name: 9642A34 version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue May 14 09:21:50 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1829025/+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 1829087] Re: package python3-apt 1.1.0~beta1ubuntu0.16.04.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1829087 Title: package python3-apt 1.1.0~beta1ubuntu0.16.04.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 Status in python-apt package in Ubuntu: New Bug description: MY update is not working ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-apt 1.1.0~beta1ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon May 13 10:26:06 2019 ErrorMessage: subprocess new pre-removal script returned error exit status 127 InstallationDate: Installed on 2017-12-01 (529 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: python-apt Title: package python3-apt 1.1.0~beta1ubuntu0.16.04.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1829087/+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 1829087] [NEW] package python3-apt 1.1.0~beta1ubuntu0.16.04.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127
Public bug reported: MY update is not working ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-apt 1.1.0~beta1ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon May 13 10:26:06 2019 ErrorMessage: subprocess new pre-removal script returned error exit status 127 InstallationDate: Installed on 2017-12-01 (529 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: python-apt Title: package python3-apt 1.1.0~beta1ubuntu0.16.04.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1829087 Title: package python3-apt 1.1.0~beta1ubuntu0.16.04.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 Status in python-apt package in Ubuntu: New Bug description: MY update is not working ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-apt 1.1.0~beta1ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon May 13 10:26:06 2019 ErrorMessage: subprocess new pre-removal script returned error exit status 127 InstallationDate: Installed on 2017-12-01 (529 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: python-apt Title: package python3-apt 1.1.0~beta1ubuntu0.16.04.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1829087/+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 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
** Description changed: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal - 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade + 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeViewNonInteractive 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging. [Regression Potential] The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong. [Original Description] I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04 14:20:29,580 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile -- 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/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: Fix Committed Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: Fix Committed Status in apt source package in Eoan: Incomplete Status in ubuntu-release-upgrader source package in Eoan: Fix Released Bug description: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade --frontend DistUpgradeViewNonInteractive 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the
[Touch-packages] [Bug 1806263] Re: MariaDB 10.1 server won't start when MySQL 5.7 server has been previously installed
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mariadb-10.1 (Ubuntu)
Status: New => Confirmed
--
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/1806263
Title:
MariaDB 10.1 server won't start when MySQL 5.7 server has been
previously installed
Status in apparmor package in Ubuntu:
Won't Fix
Status in mariadb-10.1 package in Ubuntu:
Confirmed
Status in mysql-5.7 package in Ubuntu:
Won't Fix
Bug description:
If you purge MySQL 5.7 server, then install MariaDB 10.1, that last
won't start due to wrong AppArmor profile.
CURRENT RESULT ON mariadb-server-10.1 package installation
...
Job for mariadb.service failed because a timeout was exceeded.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
...
# LANG=C systemctl status mariadb
* mariadb.service - MariaDB 10.1.34 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor
preset: enabled)
Active: failed (Result: timeout) since Sun 2018-12-02 17:26:09 UTC; 59s ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Main PID: 23245 (code=exited, status=0/SUCCESS)
Dec 02 17:24:37 bionic systemd[1]: Starting MariaDB 10.1.34 database server...
Dec 02 17:24:37 bionic mysqld[23245]: 2018-12-02 17:24:37 139820621216896
[Note] /usr/sbin/mysqld (mysqld 10.1.34-MariaDB-0ubuntu0.18.04.1) starting as
process 23245 ...
Dec 02 17:26:07 bionic systemd[1]: mariadb.service: Start operation timed
out. Terminating.
Dec 02 17:26:09 bionic systemd[1]: mariadb.service: Failed with result
'timeout'.
Dec 02 17:26:09 bionic systemd[1]: Failed to start MariaDB 10.1.34 database
server.
EXPECTED RESULT
MariaDB 10.1 server starting as expected.
HOWTO REPRODUCE
apt-get install mysql-server-5.7 mysql-client-5.7
apt-get purge mysql-server-5.7 mysql-client-5.7
apt-get install mariadb-server-10.1 mariadb-client-10.1
DISCUSSION
The mysql-server-5.7 package install an
/etc/apparmor.d/usr.sbin.mysqld APPARMOR(7) profile:
# dpkg -S /etc/apparmor.d/usr.sbin.mysqld
mysql-server-5.7: /etc/apparmor.d/usr.sbin.mysqld
When purging the mysql-server-5.7 server package get purged, the
/etc/apparmor.d/usr.sbin.mysqld profile is also removed but, it is
still loaded:
# aa-status | grep 'mysqld'
/usr/sbin/mysqld
This lead to MariaDB 1.0 server not being able to start due to MySQL
5.7 APPARMOR(7) profile that is still loaded.
Furthermore, the mariadb-server-10.1 also comes with an APPARMOR(7)
profile which as per it header comments is "intensionally empty to
disable apparmor by default for newer versions of MariaDB".
This is a big mistake as such a profile is simply wrong in regard of
APPARMOR_PARSER(8) and as such, won't be unloaded:
# apparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqld
# aa-status | grep 'mysqld'
/usr/sbin/mysqld
while:
# echo "/usr/sbin/mysqld { }" > /etc/apparmor.d/usr.sbin.mysqld
# apparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqld
Removal succeeded for "/usr/sbin/mysqld".
# aa-status | grep 'mysqld'
FIX PROPOSAL
1. When mysql-server-5.7 package is being removed/purged, the APPARMOR(7)
profile should be unloaded and removed ranther than be simply removed.
2. The profile provided by the mariadb-server-10.1 package should have
correct syntax in regard of APPARMOR_PARSER(8)
3. The mariadb-server-10.1 package postinst/postrm maintainer scripts should
handle apparmor profile (load/unload)
Env Ubuntu Bionic Beaver (18.04)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1806263/+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 1818204] Update Released
The verification of the Stable Release Update for linux-azure has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1818204 Title: Qualcomm Atheros QCA9377 wireless does not work Status in linux package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in network-manager source package in Bionic: Invalid Status in linux source package in Cosmic: Fix Released Status in network-manager source package in Cosmic: Invalid Bug description: === SRU Justification === [Impact] Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked [Fix] The platform in question doesn't have hardware RF switch, so quirk it off. [Test] User confirm it fixes the issue. [Regression Potential] Minimal. This fix is limited to one specific platform. === Original Bug Report === I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31). The menu shows that wireless is off. Turning on the wireless from the menu does not do anything. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 1 11:42:34 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-02-20 (8 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 130.232.69.176 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 ada277fe-966d-33ff-aba2-8ba32d6ce5a9 ethernet 155143 pe 1. maaliskuuta 2019 11.42.13 yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes enx00e04c704f68 activated /org/freedesktop/NetworkManager/ActiveConnection/11 -- virbr0 dc46fe89-5b22-438a-85d5-37be48a077ea bridge 155143 pe 1. maaliskuuta 2019 11.42.13 no 0 no/org/freedesktop/NetworkManager/Settings/2 yes virbr0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled disabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sami 1315 F pulseaudio /dev/snd/controlC0: sami 1315 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-02-20 (11 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IpRoute: default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100 130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 130.232.69.176 metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown MachineType: LENOVO 81H1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine:
[Touch-packages] [Bug 1829078] [NEW] full-upgrade will remove linux-generic
Public bug reported: For some reason there is not as new linux image package than linux headers package. Maybe this is just problem with the mirror. $ sudo apt update; sudo apt full-upgrade --assume-no Hit:1 http://mirrors.nic.funet.fi/ubuntu bionic InRelease Hit:2 http://mirrors.nic.funet.fi/ubuntu bionic-updates InRelease Hit:3 http://mirrors.nic.funet.fi/ubuntu bionic-security InRelease Hit:4 http://ppa.launchpad.net/mythbuntu/0.29/ubuntu bionic InRelease Hit:5 http://mirrors.nic.funet.fi/ubuntu bionic-proposed InRelease Ign:6 http://linux.dropbox.com/ubuntu bionic InRelease Ign:7 http://dl.google.com/linux/chrome/deb stable InRelease Get:8 http://linux.dropbox.com/ubuntu bionic Release [6 600 B] Hit:9 http://dl.google.com/linux/chrome/deb stable Release Fetched 6 600 B in 2s (3 999 B/s) Reading package lists... Done Building dependency tree Reading state information... Done 165 packages can be upgraded. Run 'apt list --upgradable' to see them. N: Ignoring file '50unattended-upgrades.orig.bionic' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: libllvm7 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: linux-generic linux-generic-hwe-18.04 The following NEW packages will be installed: libllvm8 linux-headers-4.15.0-50 linux-headers-4.15.0-50-generic linux-headers-4.18.0-20 linux-headers-4.18.0-20-generic python3-dateutil The following packages will be upgraded: bash bind9-host console-setup console-setup-linux cups cups-browsed cups-bsd cups-client cups-common cups-core-drivers cups-daemon cups-filters cups-filters-core-drivers cups-ipp-utils cups-ppdc cups-server-common debconf debconf-i18n distro-info-data dnsutils evince evince-common ffmpeg firefox firefox-locale-en firefox-locale-fi firefox-locale-ru ghostscript ghostscript-x gir1.2-gst-plugins-base-1.0 gir1.2-gstreamer-1.0 gir1.2-javascriptcoregtk-4.0 gir1.2-webkit2-4.0 gnome-software gnome-software-common gnome-software-plugin-snap gstreamer1.0-plugins-base gstreamer1.0-tools gstreamer1.0-x intel-microcode isc-dhcp-client isc-dhcp-common kbd keyboard-configuration libavcodec57 libavdevice57 libavfilter6 libavformat57 libavresample3 libavutil55 libbind9-160 libcups2 libcupscgi1 libcupsfilters1 libcupsimage2 libcupsmime1 libcupsppdc1 libdns-export1100 libdns1100 libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libegl-mesa0 libegl1-mesa libevdocument3-4 libevview3-3 libfontembed1 libgbm1 libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libgles2-mesa libglx-mesa0 libgs9 libgs9-common libgstreamer-gl1.0-0 libgstreamer-plugins-base1.0-0 libgstreamer1.0-0 libirs160 libisc-export169 libisc169 libisccc160 libisccfg160 libjavascriptcoregtk-4.0-18 libldap-2.4-2 libldap-common liblwres160 libmbim-glib4 libmbim-proxy libmm-glib0 libmysqlclient20 libnm-glib-vpn1 libnm-glib4 libnm-util2 libnm0 libpam-systemd libpng16-16 libpostproc54 libpython2.7 libpython2.7-minimal libpython2.7-stdlib libpython3.6 libpython3.6-minimal libpython3.6-stdlib libqmi-glib5 libqmi-proxy libsmbclient libswresample2 libswscale4 libsystemd0 libudev1 libwavpack1 libwayland-egl1-mesa libwbclient0 libwebkit2gtk-4.0-37 libwebkit2gtk-4.0-37-gtk2 libxatracker2 libxkbcommon-x11-0 libxkbcommon0 linux-firmware linux-headers-generic linux-headers-generic-hwe-18.04 linux-libc-dev mesa-va-drivers mesa-vdpau-drivers modemmanager mysql-client-5.7 mysql-client-core-5.7 netplan.io network-manager nplan python-apt-common python-cryptography python2.7 python2.7-minimal python3-apt python3-cryptography python3-debconf python3-distupgrade python3-distutils python3-gdbm python3-lib2to3 python3-software-properties python3.6 python3.6-minimal samba-libs software-properties-common software-properties-gtk systemd systemd-sysv tzdata ubuntu-release-upgrader-core ubuntu-release-upgrader-gtk udev unattended-upgrades update-notifier update-notifier-common wpasupplicant 161 upgraded, 6 newly installed, 2 to remove and 0 not upgraded. Need to get 82,4 MB/268 MB of archives. After this operation, 270 MB of additional disk space will be used. Do you want to continue? [Y/n] N Abort. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.10 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux
[Touch-packages] [Bug 1788048] Re: systemd journald failed unmounting var
Just to clarify, this does not hang shutdown/reboot for anyone, right? It only fails to cleanly unmount /var, right? ** Description changed: + [impact] + + on a system with /var and/or /var/log mounted separately from /, + shutdown can't unmount /var (or /var/log) cleanly because systemd- + journald is using it. + + [test case] + + install a system with /var mounted separately from / + + shutdown, and notice: + + [FAILED] Failed unmounting /var. + + [regression potential] + + TBD + + [other info] + + original description: + + -- + When the system is shut down or restarted the systemd-journal does not disassemble the disks correctly. On this thread https://unix.stackexchange.com/questions/378678/why-do-i -get-the-error-failed-unmounting-var-during-shutdown I checked what editing /etc/systemd/journald.conf to change the Storage = line to Storage = volatile the problem is solved, but some of the logs on the shutdown are lost. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Aug 20 18:15:07 2018 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2018-08-20 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: - Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet - Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=65cb761b-4881-4031-9113-e6bb6a1437b4 ro SourcePackage: systemd SystemdDelta: - [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf - [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf - - 2 overridden configuration files found. + [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf + [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf + + 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH mtime.conffile..etc.systemd.journald.conf: 2018-08-20T18:00:58.586165 ** Also affects: systemd (Ubuntu Eoan) Importance: Medium Status: Triaged ** Also affects: systemd (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1788048 Title: systemd journald failed unmounting var Status in systemd: Fix Released Status in systemd package in Ubuntu: Triaged Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: New Status in systemd source package in Disco: New Status in systemd source package in Eoan: Triaged Bug description: [impact] on a system with /var and/or /var/log mounted separately from /, shutdown can't unmount /var (or /var/log) cleanly because systemd- journald is using it. [test case] install a system with /var mounted separately from / shutdown, and notice: [FAILED] Failed unmounting /var. [regression potential] TBD [other info] original description: -- When the system is shut down or restarted the systemd-journal does not disassemble the disks correctly. On this thread https://unix.stackexchange.com/questions/378678/why- do-i-get-the-error-failed-unmounting-var-during-shutdown I checked what editing /etc/systemd/journald.conf to change the Storage = line to Storage = volatile the problem is solved, but some of the logs on the shutdown are lost. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64
[Touch-packages] [Bug 1778844] Re: nvme multipath does not report path relationships
Hello bugproxy, or anyone else affected, Accepted initramfs-tools into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.131ubuntu15.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: initramfs-tools (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: initramfs-tools (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- 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/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: In Progress Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Cosmic: Fix Committed Status in initramfs-tools source package in Disco: Fix Released Bug description: [Impact] initramfs created with MODULES=dep or kdump initrd won't boot a system with root filesystem on a multipath nvme. [Test case] Systems with nvme multipath were able to boot with the created initramfs. Also tested on systems with non-multipath nvme, and non nvme systems. In order to verify the fix, one needs to change MODULES option to dep on /etc/initramfs-tools/initramfs.conf, recreate initramfs and reboot, check the system has booted fine. That should not break on systems with non nvme disks or systems with non multipath nvme systems, and that should now work on multipath nvme systems. sed -i /MODULES=/s,=.*,=dep, /etc/initramfs-tools/initramfs.conf update-initramfs -u -k all reboot [Regression potential] A system could fail to boot because the generated initramfs was broken. The code should just add modules, which is safer than removing modules or doing any other changes. In any case, it was tested to boot on multipath nvme, non multipath nvme and non nvme systems. - Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash
[Touch-packages] [Bug 1778844] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted initramfs-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.130ubuntu3.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1778844 Title: nvme multipath does not report path relationships Status in The Ubuntu-power-systems project: In Progress Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Cosmic: Fix Committed Status in initramfs-tools source package in Disco: Fix Released Bug description: [Impact] initramfs created with MODULES=dep or kdump initrd won't boot a system with root filesystem on a multipath nvme. [Test case] Systems with nvme multipath were able to boot with the created initramfs. Also tested on systems with non-multipath nvme, and non nvme systems. In order to verify the fix, one needs to change MODULES option to dep on /etc/initramfs-tools/initramfs.conf, recreate initramfs and reboot, check the system has booted fine. That should not break on systems with non nvme disks or systems with non multipath nvme systems, and that should now work on multipath nvme systems. sed -i /MODULES=/s,=.*,=dep, /etc/initramfs-tools/initramfs.conf update-initramfs -u -k all reboot [Regression potential] A system could fail to boot because the generated initramfs was broken. The code should just add modules, which is safer than removing modules or doing any other changes. In any case, it was tested to boot on multipath nvme, non multipath nvme and non nvme systems. - Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address:
[Touch-packages] [Bug 1828749] Re: ifconfig dummy0 : Device not found
Can you please transfer this to the ifupdown package? Or should I just resubmit it from scratch? The discussions of the importance of ifconfig are beside the point. The problem presented itself during boot-up, in connection with an "auto dummy0" directive in /etc/network/interfaces. If "auto dummy0" and "ifup dummy0" are not maintained then why bother to have a dummy device at all? This is the most important context, although there are MANY others. I reported the ifconfig context because it is the /simplest/ ... not the only manifestation. And no, I'm definitely not the first person to encounter the bug. I'm just the first to report it through this channel. My first message in this thread linked to a report that came up in another context. As for the software versions: I must have typed the "apt-cache policy net-tools" in the wrong window at one point. As stated before that and after that, the fact is that bionic is buggy while xenial is not. Specifically, the buggy packages are: :; apt-cache policy net-tools net-tools: Installed: 1.60+git20161116.90da8a0-1ubuntu1 Candidate: 1.60+git20161116.90da8a0-1ubuntu1 Version table: *** 1.60+git20161116.90da8a0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status and perhaps more to the point: :; apt-cache policy ifupdown ifupdown: Installed: 0.8.17ubuntu1.1 Candidate: 0.8.17ubuntu1.1 Version table: *** 0.8.17ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.17ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828749 Title: ifconfig dummy0 : Device not found Status in net-tools package in Ubuntu: New Bug description: Desired behavior: The ifconfig command should be able to deal with the dummy device. This worked fine until recently. Observed behavior: :; ifconfig dummy0 dummy0: error fetching interface information: Device not found This problem appeared when I upgraded to bionic. Highly informative workaround: :; ip link add dummy0 type dummy That command works, and makes the problem go away permanently. The ifconfig command works fine after that. The ifup and ifdown commands also work fine after that. For convenient debugging, you can use the command: :; ip link del dummy0 type dummy which makes the problem come back. You can also experiment with dummy1 et cetera. Package ownership issues: Compare: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909204 That report was filed against ippusbxd, which is almost certainly not the relevant package. For that matter, I have no idea whether the root cause is in the net-tools package or the kernel networking stack. All I know is the ip command plays nicely with the kernel while the ifconfig command does not. Notes: The kernel module for the dummy interface is preloaded in all situations described here. That's not the issue. An apport file is attached, to describe the environment. Also, since you asked: :; apt-cache policy net-tools net-tools: Installed: 1.60-26ubuntu1 Candidate: 1.60-26ubuntu1 Version table: *** 1.60-26ubuntu1 500 500 http://ubuntu.cs.utah.edu/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status :; lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1828749/+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 1829069] [NEW] Xorg freeze
Public bug reported: i can't open files app and terminal in my ubuntu while using chrome remote desktop. and also ubuntu froze ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 15 02:08:17 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: I don't know GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:2213] InstallationDate: Installed on 2019-04-01 (43 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 001 Device 004: ID 0bda:b001 Realtek Semiconductor Corp. Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=1dbcbc41-3811-4525-8a07-83de047700c3 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2213 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd09/19/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr096C11405F00050660180:rvnHewlett-Packard:rn2213:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.version: 096C11405F00050660180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze 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/1829069 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: i can't open files app and terminal in my ubuntu while using chrome remote desktop. and also ubuntu froze ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 15 02:08:17 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: I don't know GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:2213] InstallationDate: Installed on 2019-04-01 (43 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 001 Device 004: ID 0bda:b001 Realtek Semiconductor Corp. Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic
[Touch-packages] [Bug 1828749] Re: ifconfig dummy0 : Device not found
Note that net-tools will no longer be installed by default from Eoan onwards. The default with the primary server installer on Bionic is to use systemd-networkd via netplan, not ifupdown. Both ifconfig and ifupdown are slowly passing through the various levels of deprecation in future releases of Ubuntu, although they are available (and will continue to be available) in Bionic. ** Tags added: bionic regression-release -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828749 Title: ifconfig dummy0 : Device not found Status in net-tools package in Ubuntu: New Bug description: Desired behavior: The ifconfig command should be able to deal with the dummy device. This worked fine until recently. Observed behavior: :; ifconfig dummy0 dummy0: error fetching interface information: Device not found This problem appeared when I upgraded to bionic. Highly informative workaround: :; ip link add dummy0 type dummy That command works, and makes the problem go away permanently. The ifconfig command works fine after that. The ifup and ifdown commands also work fine after that. For convenient debugging, you can use the command: :; ip link del dummy0 type dummy which makes the problem come back. You can also experiment with dummy1 et cetera. Package ownership issues: Compare: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909204 That report was filed against ippusbxd, which is almost certainly not the relevant package. For that matter, I have no idea whether the root cause is in the net-tools package or the kernel networking stack. All I know is the ip command plays nicely with the kernel while the ifconfig command does not. Notes: The kernel module for the dummy interface is preloaded in all situations described here. That's not the issue. An apport file is attached, to describe the environment. Also, since you asked: :; apt-cache policy net-tools net-tools: Installed: 1.60-26ubuntu1 Candidate: 1.60-26ubuntu1 Version table: *** 1.60-26ubuntu1 500 500 http://ubuntu.cs.utah.edu/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status :; lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1828749/+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 1828749] Re: ifconfig dummy0 : Device not found
Thank you for the additional information. If you hit the bug in an upgrade from Xenial to Bionic, then why did you report version 1.60-26ubuntu1 of net-tools as affected? This version shipped with Xenial, not Bionic. Please could you confirm the version of net-tools that affects you with this problem on Bionic? I accept that an upgrade from Xenial to Bionic that uses ifupdown will continue to do so. I hadn't considered that. However, use of dummy0 in the way that you are doing seems to me to be an unusual end-user configuration, so I think it still qualifies as Importance: Low against https://wiki.ubuntu.com/Bugs/Importance. In any case the Importance doesn't really matter; I just want to set the expectation that you shouldn't expect developers to jump on this for you, since Bionic was released over a year ago now and you appear to be the only person affected by this problem. On Tue, May 14, 2019 at 08:01:16PM -, John Denker wrote: > If it really is deprecated and unsupported, somebody > should file a separate bug against the documentation. I didn't say it was unsupported. Patches are welcome. I specifically did say it is still maintained. However everything that you can do with ifconfig you can do with ip(8), and there are many modern networking things that ifconfig does not support. ip(8) was written to replace it. ** Changed in: net-tools (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828749 Title: ifconfig dummy0 : Device not found Status in net-tools package in Ubuntu: New Bug description: Desired behavior: The ifconfig command should be able to deal with the dummy device. This worked fine until recently. Observed behavior: :; ifconfig dummy0 dummy0: error fetching interface information: Device not found This problem appeared when I upgraded to bionic. Highly informative workaround: :; ip link add dummy0 type dummy That command works, and makes the problem go away permanently. The ifconfig command works fine after that. The ifup and ifdown commands also work fine after that. For convenient debugging, you can use the command: :; ip link del dummy0 type dummy which makes the problem come back. You can also experiment with dummy1 et cetera. Package ownership issues: Compare: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909204 That report was filed against ippusbxd, which is almost certainly not the relevant package. For that matter, I have no idea whether the root cause is in the net-tools package or the kernel networking stack. All I know is the ip command plays nicely with the kernel while the ifconfig command does not. Notes: The kernel module for the dummy interface is preloaded in all situations described here. That's not the issue. An apport file is attached, to describe the environment. Also, since you asked: :; apt-cache policy net-tools net-tools: Installed: 1.60-26ubuntu1 Candidate: 1.60-26ubuntu1 Version table: *** 1.60-26ubuntu1 500 500 http://ubuntu.cs.utah.edu/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status :; lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1828749/+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 1828749] Re: ifconfig dummy0 : Device not found
*) As for priority: It's not as low as you might imagine. The problem affects not just ifconfig but also ifup, which is indispensable. It also affects the "raise network interface" target at boot time, as triggered by "auto dummy0" directives in /etc/network/interfaces. Symptom: :; ifup dummy0 Cannot find device "dummy0" Failed to bring up dummy0. This was hinted at in the original report but not emphasized. I emphasize it now. I mentioned ifconfig because it is the /simplest/ way to exhibit the bug. Feel free to change the headline of this bug to "ifup" (rather than "ifconfig") and transfer it to the ifupdown package (rather than net-tools) if you wish. This bug means that when I upgraded my machine remotely, it became unreachable, because the dummy0 interface carried the stable IP address that I was using. It took a great deal of work on my part to devise a workaround. *) In answer to your question: "until recently" means until I upgraded from xenial to bionic. I have another system still running xenial where ifconfig, ifup, and "raise network interface" all continue to work fine. The kernel version is exactly the same, 4.19.42; this may help you determine whether the regression is in user space and/or kernel space. On the other side of the same coin, I have yet another system with a squeaky clean bionic (installed ab_initio, not upgraded) that exhibits all the same problems with ifconfig, ifup, and "raise network interface". So it appears to be a bionic issue. I have no easy way to test the releases that came between xenial and bionic. All I know is that bionic is the latest LTS. It's supposed to be supported, and it's broken in a way that caused me a lot of grief. *) FURTHERMORE, there is nothing in the ifconfig man page to suggest that it is in any way deprecated. What's the deal? Choose your farce: -- Is it on double-secret probation? (Animal House) -- Doesn't it defeat the purpose of a deterrent if you keep it a secret? (Dr. Strangelove) -- Is perhaps the notice on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying "Beware of the Leopard"? (Hitchhiker's Guide) If it really is deprecated and unsupported, somebody should file a separate bug against the documentation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828749 Title: ifconfig dummy0 : Device not found Status in net-tools package in Ubuntu: Incomplete Bug description: Desired behavior: The ifconfig command should be able to deal with the dummy device. This worked fine until recently. Observed behavior: :; ifconfig dummy0 dummy0: error fetching interface information: Device not found This problem appeared when I upgraded to bionic. Highly informative workaround: :; ip link add dummy0 type dummy That command works, and makes the problem go away permanently. The ifconfig command works fine after that. The ifup and ifdown commands also work fine after that. For convenient debugging, you can use the command: :; ip link del dummy0 type dummy which makes the problem come back. You can also experiment with dummy1 et cetera. Package ownership issues: Compare: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909204 That report was filed against ippusbxd, which is almost certainly not the relevant package. For that matter, I have no idea whether the root cause is in the net-tools package or the kernel networking stack. All I know is the ip command plays nicely with the kernel while the ifconfig command does not. Notes: The kernel module for the dummy interface is preloaded in all situations described here. That's not the issue. An apport file is attached, to describe the environment. Also, since you asked: :; apt-cache policy net-tools net-tools: Installed: 1.60-26ubuntu1 Candidate: 1.60-26ubuntu1 Version table: *** 1.60-26ubuntu1 500 500 http://ubuntu.cs.utah.edu/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status :; lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1828749/+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 1773859] Re: upgrades to 18.04 fail
Still affects me on release upgrade from latest 16.04 LTS with hwe installed... -- 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Triaged Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial, ie. lxc launch ubuntu-daily:xenial test-shim-upgrade lxc exec test-shim-upgrade apt update apt install systemd-shim wget https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb apt install ./systemd-shim_10-3_amd64.deb sed 's/xenial/bionic/' -i /etc/apt/sources.list apt update apt install systemd this currently passes, however, systemd-shim remains installed. It should be removed instead. Apt install systemd should have lines like this: The following packages will be REMOVED: systemd-shim ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' ... [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+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 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
https://github.com/systemd/systemd/pull/12566 thnx @cascardo! -- 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/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udisks2 package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in systemd source package in Bionic: New Status in udisks2 source package in Bionic: Invalid Status in linux source package in Disco: New Status in systemd source package in Disco: New Status in udisks2 source package in Disco: Invalid Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: New Status in udisks2 source package in Eoan: Invalid Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1825997] Re: boot-smoke fails due to running jobs
** Changed in: systemd (Ubuntu Eoan) Assignee: (unassigned) => Dan Streetman (ddstreet) -- 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/1825997 Title: boot-smoke fails due to running jobs Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [impact] boot-smoke test reboots 5 times and verifies systemd is fully started up after each boot, including checking if there are any running jobs (with list-jobs). However, this test makes the assumption that no further jobs will be started after systemd reaches 'running' (or 'degraded') state, which is a false assumption. [test case] see various boot-smoke failures in autopkgtest.ubuntu.com [regression potential] possible false-positive or false-negative autopkgtest results. [other info] The problem appears to be that systemd reaches 'running' (or 'degraded') state, and then other systemd services are started. This confuses the boot-smoke test, because it sees that 'is-system-running' is done, but then it sees running jobs, which fails the test. What is starting jobs after systemd reaches running state appears to be X inside the test system. There are various services started by gnome-session and dbus-daemon. Additionally, from the artifacts of one example: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- bionic/bionic/i386/s/systemd/20190416_171327_478f6@/artifacts.tar.gz the artifacts/journal.txt shows that after the boot-smoke test causes the reboot and then re-ssh into the system after the reboot, it only gives the test system 9 seconds before deciding it has failed, and only 4 seconds after ssh'ing into the rebooted test system. Another wait is needed when checking for remaining running jobs. Or, the running jobs check could be removed entirely, and we can just trust that systemd correctly knows when it has reached running|degraded state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825997/+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 1500541] Re: apport-retrace crashed with IOError in __main__: [Errno 13] Permission denied: '_usr_bin_Xorg.0.crash'
** Changed in: apport (Ubuntu) Assignee: Brian Murray (brian-murray) => (unassigned) ** Changed in: apport (Ubuntu) Status: In Progress => Triaged -- 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/1500541 Title: apport-retrace crashed with IOError in __main__: [Errno 13] Permission denied: '_usr_bin_Xorg.0.crash' Status in apport package in Ubuntu: Triaged Bug description: apport did not have the permissions to read the crash report in /var/crash, since I ran it as unpriviledged user. I think apport could handle this more gracefully :) ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: apport-retrace 2.19-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportLog: Error: [Errno 13] Keine Berechtigung: '/var/log/apport.log' ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 28 19:22:10 2015 ExecutablePath: /usr/bin/apport-retrace InstallationDate: Installed on 2013-01-08 (993 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) InterpreterPath: /usr/bin/python2.7 JournalErrors: No journal files were found. -- No entries -- PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/apport-retrace _usr_bin_Xorg.0.crash PythonArgs: ['/usr/bin/apport-retrace', '_usr_bin_Xorg.0.crash'] SourcePackage: apport Title: apport-retrace crashed with IOError in __main__: [Errno 13] Permission denied: '_usr_bin_Xorg.0.crash' Traceback: Traceback (most recent call last): File "/usr/bin/apport-retrace", line 405, in out = open(options.report, 'wb') IOError: [Errno 13] Permission denied: '_usr_bin_Xorg.0.crash' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: audio bluetooth colord disk fuse games libvirtd operator pulse sudo syslog users vboxusers video whoopsie wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1500541/+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 1828892] Re: systemctl - alias service reports inactive while aliased is active
** Tags added: ddstreet-next -- 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/1828892 Title: systemctl - alias service reports inactive while aliased is active Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Xenial: Confirmed Bug description: [Impact] 'systemctl is-active' command reports an alias service as inactive even though the aliased service is active. Currently the 'systemctl is-active' command does not load units to minimise its effect on the system (i.e. that a monitoring command does not itself alter the state of the system). However, this behaviour leads to inconsistencies when services are aliased. [Test case] - Test case 1 - libvirtd alias service : libvirtd aliased service : libvirt-bin /etc/systemd/system$ ls -la libvirtd.service lrwxrwxrwx 1 root root 39 May 13 20:49 libvirtd.service -> /lib/systemd/system/libvirt-bin.service $ systemctl is-active libvirtd inactive $ systemctl is-active libvirt-bin active - Test case 2 - sshd alias service : sshd aliased service : ssh /ect/systemd/system$ ls -la sshd.service lrwxrwxrwx 1 root root 31 Mar 19 19:44 sshd.service -> /lib/systemd/system/ssh.service $ systemctl is-active sshd inactive $ systemctl is-active ssh active [Regression Potential] This fix may result into systemctl reporting inconsistent information concerning the status of a service. [Other] Upstream issue : https://github.com/systemd/systemd/issues/7875 Upstream fix : https://github.com/systemd/systemd/pull/7997 Xenial is affected, fix exists on Bionic onward. $ lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 $ apt-cache policy systemd systemd: Installed: 229-4ubuntu21.21 Candidate: 229-4ubuntu21.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828892/+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 1829053] [NEW] driver won't install of intel
Public bug reported: [sudo] password for sheharyar: Sorry, try again. [sudo] password for sheharyar: Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-video-intel : Depends: xorg-video-abi-20 Depends: xserver-xorg-core (>= 2:1.17.99.902) E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue May 14 22:59:45 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:143a] Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470] [1002:68e0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Park [Mobility Radeon HD 5430/5450/5470] [103c:143a] InstallationDate: Installed on 2019-04-13 (31 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: Hewlett-Packard HP G72 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=51795b73-d359-48d5-89d1-7c6297784ee8 ro nomodeset quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.48 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 143A dmi.board.vendor: Hewlett-Packard dmi.board.version: 60.50 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.48:bd11/09/2011:svnHewlett-Packard:pnHPG72NotebookPC:pvr058E11252710001620100:rvnHewlett-Packard:rn143A:rvr60.50:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV dmi.product.name: HP G72 Notebook PC dmi.product.version: 058E11252710001620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed May 15 03:54:01 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1829053 Title: driver won't install of intel Status in xorg package in Ubuntu: New Bug description: [sudo] password for sheharyar: Sorry, try again. [sudo] password for sheharyar: Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-video-intel : Depends: xorg-video-abi-20 Depends: xserver-xorg-core (>= 2:1.17.99.902)
[Touch-packages] [Bug 1745664] Re: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_cln
Can confirm that NSCD installation eliminated lag, reference comment #22. -- 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/1745664 Title: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create() Status in nis package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3 --- configured system to use nis. seems to be crashing when I attempt to use a NIS user account ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Fri Jan 26 13:45:06 2018 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2018-01-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at ../sysdeps/unix/sysv/linux/connect.c:26 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153 __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106 __GI_pmap_getport (address=address@entry=0x7ffc27302060, program=program@entry=17, version=version@entry=2, protocol=protocol@entry=6) at pm_getport.c:154 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136 SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-logind crashed with SIGABRT in __libc_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys sysdesign tty uucp dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1745664/+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 1800723] Re: Missing package python3.7-pip
I would really like to see pip3 not pulling in dependencies for python3.6. It interferes with other dependencies. In my case, few packages, for instance cffi is causing issues with import when compiling with python 3.7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1800723 Title: Missing package python3.7-pip Status in python-pip package in Ubuntu: Confirmed Status in python3-defaults package in Ubuntu: Confirmed Bug description: There appears to be no way to get "pip" or "python3.7 -m pip" to work after installing python3.7 using "apt install python3.7". I expected to be able to install a "python3.7-pip" package similar to the other "python3.7-*" packages but I couldn't find one. This problem appears in a clean install of 18.04 as well as 18.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1800723/+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 1800723] Re: Missing package python3.7-pip
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python-pip (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1800723 Title: Missing package python3.7-pip Status in python-pip package in Ubuntu: Confirmed Status in python3-defaults package in Ubuntu: Confirmed Bug description: There appears to be no way to get "pip" or "python3.7 -m pip" to work after installing python3.7 using "apt install python3.7". I expected to be able to install a "python3.7-pip" package similar to the other "python3.7-*" packages but I couldn't find one. This problem appears in a clean install of 18.04 as well as 18.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1800723/+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 1800723] Re: Missing package python3.7-pip
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python3-defaults (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1800723 Title: Missing package python3.7-pip Status in python-pip package in Ubuntu: Confirmed Status in python3-defaults package in Ubuntu: Confirmed Bug description: There appears to be no way to get "pip" or "python3.7 -m pip" to work after installing python3.7 using "apt install python3.7". I expected to be able to install a "python3.7-pip" package similar to the other "python3.7-*" packages but I couldn't find one. This problem appears in a clean install of 18.04 as well as 18.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1800723/+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 1800723] Re: Missing package python3.7-pip
I arrived here researching this exact issue, in my case I'd really need not to install python 3.6 since it interferes with other dependencies and makes a docker image larger. More info: https://stackoverflow.com/q/56135497/1782 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1800723 Title: Missing package python3.7-pip Status in python-pip package in Ubuntu: Confirmed Status in python3-defaults package in Ubuntu: Confirmed Bug description: There appears to be no way to get "pip" or "python3.7 -m pip" to work after installing python3.7 using "apt install python3.7". I expected to be able to install a "python3.7-pip" package similar to the other "python3.7-*" packages but I couldn't find one. This problem appears in a clean install of 18.04 as well as 18.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1800723/+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 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
** Description changed: I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. + + + Note: for quick reference to anyone coming to this bug, this behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: + + Defaultsalways_set_home -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in sudo package in Ubuntu: Confirmed Bug description: I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. Note: for quick reference to anyone coming to this bug, this behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1556302/+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 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
The *downside* of reverting our custom patch is that end-users are used to all their personal customization of applications from $HOME working; i.e. currently, when anyone runs vim, emacs, bash, etc. under sudo, any ~/.WHATEVER customization they have will be retained. This is different than, essentially, all other UNIXes, and the fix for this bug would undo that, to put us back in line with all other UNIXes - but would result in behavior change for users, where e.g. 'sudo vim' would not pick up any of their ~/.vimrc configuration (or ~/.emacs.d for emacs, etc...) Thus, this change, if we do make it, probably should only be done to Eoan and not SRUed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in sudo package in Ubuntu: Confirmed Bug description: I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. Note: for quick reference to anyone coming to this bug, this behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1556302/+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 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
Another example, which can happen in newly deployed containers/vms: ubuntu@lp1556302:~$ ls -la .bash_history ls: cannot access '.bash_history': No such file or directory ubuntu@lp1556302:~$ sudo bash root@lp1556302:~# exit exit ubuntu@lp1556302:~$ ls -la .bash_history -rw--- 1 root root 5 May 14 16:36 .bash_history -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in sudo package in Ubuntu: Confirmed Bug description: I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. Note: for quick reference to anyone coming to this bug, this behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1556302/+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 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
Further, this behavior causes root-owned files and directories in a user's home directory, e.g.: ubuntu@lp1556302:~$ ls -l /home/ubuntu/.vim* ls: cannot access '/home/ubuntu/.vim*': No such file or directory ubuntu@lp1556302:~$ sudo vim /tmp/test ubuntu@lp1556302:~$ ls -l /home/ubuntu/.vim* -rw--- 1 root root 700 May 14 16:31 /home/ubuntu/.viminfo ubuntu@lp1556302:~$ ls -ld /home/ubuntu/.emacs* ls: cannot access '/home/ubuntu/.emacs*': No such file or directory ubuntu@lp1556302:~$ sudo emacs /tmp/test ubuntu@lp1556302:~$ ls -ld /home/ubuntu/.emacs* drwx-- 2 root root 4096 May 14 16:32 /home/ubuntu/.emacs.d bug 1828208 and so on. This problem is true for *any* program/application that creates any files in $HOME, and might be run under sudo. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in sudo package in Ubuntu: Confirmed Bug description: I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. Note: for quick reference to anyone coming to this bug, this behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1556302/+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 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
For additional clarification: As mentioned already, the Ubuntu patch diverges from upstream sudo. Additionally, here what other Linux distros do: ddstreet@debian:~$ printenv | grep HOME HOME=/home/ddstreet ddstreet@debian:~$ sudo printenv | grep HOME HOME=/root [ddstreet@fedora-workstation ~]$ printenv | grep '^HOME' HOME=/home/ddstreet [ddstreet@fedora-workstation ~]$ sudo printenv | grep '^HOME' HOME=/root [ddstreet@fedora-server ~]$ printenv | grep '^HOME' HOME=/home/ddstreet [ddstreet@fedora-server ~]$ sudo printenv | grep '^HOME' HOME=/root [ddstreet@rhel-8 ~]$ printenv | grep HOME HOME=/home/ddstreet [ddstreet@rhel-8 ~]$ sudo printenv | grep HOME HOME=/root ddstreet@opensuse-15:~> printenv | grep HOME HOME=/home/ddstreet ddstreet@opensuse-15:~> sudo printenv | grep HOME HOME=/root ddstreet@sles-15:~> printenv | grep HOME HOME=/home/ddstreet ddstreet@sles-15:~> sudo printenv | grep HOME HOME=/root ddstreet@slackware:~$ printenv | grep HOME HOME=/home/ddstreet ddstreet@slackware:~$ sudo printenv | grep HOME HOME=/root And even other UNIXes: ddstreet@netbsd-8: $ printenv | grep HOME HOME=/home/ddstreet ddstreet@netbsd-8: $ sudo printenv | grep HOME HOME=/root ddstreet@freebsd-12: $ printenv | grep HOME HOME=/home/ddstreet ddstreet@freebsd-12: $ sudo printenv | grep HOME HOME=/root openbsd$ printenv | grep HOME HOME=/home/ddstreet openbsd$ sudo printenv | grep HOME HOME=/root We appear to be completely alone in adding HOME to env_keep by default. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in sudo package in Ubuntu: Confirmed Bug description: I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1556302/+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 1728093] Re: [16.04, ALC3253] Dell Latitude 5289 Combo Jack Does Not Recognize Devices
@Jeff Conner (aodhlaidir): Thanks a lot for that workaround! Did you (or anyone else) figure out how to get the audio jack to recognize a headset's microphone as well? I tried many combinations of overrides in HDAJackRetask, but nothing made headset mic work. -- 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/1728093 Title: [16.04, ALC3253] Dell Latitude 5289 Combo Jack Does Not Recognize Devices Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have a fresh installation of Ubuntu 16.04 on a Dell Latitude 5289 Ultrabook that has a single 3.5mm jack for both input and output. This installation is in a dual-boot situation with Windows 10. This device has UEFI secure boot enabled. The combo jack works perfectly in Windows 10, however, when I plug in a headset or headphone of any kind, it does not register that anything has been plugged in. The laptop is connected to a Dell dock via USB-C, so there is also USB Audio (Output only) available on the dock, but that also does not work. It worked for one session yesterday on my dock at work, however it does not work at my dock that I have at home. The internal speakers and the microphone built into the lid work fine. The Combo jack also does not work disconnected from the dock. I have installed gnome and gnome-shell, but it does not work in either gnome or unity (I continue to use lightdm so that I can switch back and forth). Neither Unity nor Gnome bring up any kind of "What Did You Plug In" dialog. alsamixer does not have a headphone option as expected pavucontrol does not allow me to select "Headphones" under the Built- in Audio Analog Stereo Port I have attempted to tweak settings in hdajackretask to no success I have attempted to add: options snd_hda_intel model=dell-headset-multi(dell-headset-dock, generic, auto, headset-mic, etc) to no success I have also tried updating my kernel to 4.13.10, to no success. I also tried 17.10 to no success. Outputs: -- uname -sr Linux 4.10.0-37-generic -- aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Audio [USB Audio], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Audio [USB Audio], device 1: USB Audio [USB Audio #1] Subdevices: 1/1 Subdevice #0: subdevice #0 cat /proc/asound/car*/co* | grep Codec Codec: Realtek ALC3253 Codec: Intel Kabylake HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1728093/+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 1562733] Re: apt signature requirements prevent updates from some repositories
** Summary changed: - apt signature requierements prevent updates from some repositories + apt signature requirements prevent updates from some repositories -- 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/1562733 Title: apt signature requirements prevent updates from some repositories Status in apt package in Ubuntu: In Progress Status in apt source package in Xenial: Won't Fix Bug description: Since xenial updated the requirements for the strength of PGP signatures of packages, packages from some repositories are no longer updated. Apt-get update reports these errors: E: Failed to fetch http://[...]/Release No Hash entry in Release file /var/lib/apt/lists/partial/[...] which is considered strong enough for security purposes E: Some index files failed to download. They have been ignored, or old ones used instead. While the motivation for the change is valid, the result is a potential security problem, as the new versions of the packages that may fix recently discovered vulnerabilities are not automatically installed. One less important but unfortunate effect is a scary message that is displayed to the user, without clear explanation that the problem needs to be addressed by the repository owner. Related: Bug #1558331 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1562733/+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 1562733] Re: apt signature requierements prevent updates from some repositories
** Tags removed: rls-x-incoming ** Tags added: rls-x-notfixing -- 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/1562733 Title: apt signature requirements prevent updates from some repositories Status in apt package in Ubuntu: In Progress Status in apt source package in Xenial: Won't Fix Bug description: Since xenial updated the requirements for the strength of PGP signatures of packages, packages from some repositories are no longer updated. Apt-get update reports these errors: E: Failed to fetch http://[...]/Release No Hash entry in Release file /var/lib/apt/lists/partial/[...] which is considered strong enough for security purposes E: Some index files failed to download. They have been ignored, or old ones used instead. While the motivation for the change is valid, the result is a potential security problem, as the new versions of the packages that may fix recently discovered vulnerabilities are not automatically installed. One less important but unfortunate effect is a scary message that is displayed to the user, without clear explanation that the problem needs to be addressed by the repository owner. Related: Bug #1558331 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1562733/+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 1373495] Re: sudo shouldn't preserve caller's HOME environment variable by default
*** This bug is a duplicate of bug 1556302 *** https://bugs.launchpad.net/bugs/1556302 I marked this as a dup of bug 1556302, as there seems to be more recent movement in that bug, and both bugs want the same thing - to revert the Ubuntu-only patch 'keep_home_by_default.patch'. ** This bug has been marked a duplicate of bug 1556302 Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1373495 Title: sudo shouldn't preserve caller's HOME environment variable by default Status in One Hundred Papercuts: Triaged Status in sudo package in Ubuntu: Triaged Bug description: Currently Ubuntu hard-coded sudo to preserve HOME environment variable to point to sudo caller's home directory by default(refer bug #760140) however this is dangerous and error-prone because the program run by root may create files (e.g. $HOME/.Xauthority , program config files) into caller's HOME directory **AS ROOT** which, will cause issue when users run the same program as their normal users' account again and even make the user failed to login(due to .Xauthority file owner is incorrect) In my opinion the Ubuntu patch(keep_home_by_default.patch)(no, Debian is NOT affected by this issue) that makes $HOME variable keep in sudo is INSANE and should be reverted(Ubuntu should use the safest configuration to general users by default), any user wish to run command as root using their HOME directory should set env_keep in /etc/sudoers themselves and acknowledging the consequences. [RootSudo - Community Help Wiki](https://help.ubuntu.com/community/RootSudo) wrongly tells that graphical application shouldn't be launched by sudo, but in fact the real issue falls into this bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-lowlatency 3.16.3 Uname: Linux 3.16.0-17-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Thu Sep 25 00:08:44 2014 InstallationDate: Installed on 2013-03-08 (564 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) SourcePackage: sudo UpgradeStatus: Upgraded to trusty on 2014-04-19 (158 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/Preserve_input_method_required_environmental_variables: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers.d.README: [modified] mtime.conffile..etc.sudoers.d.README: 2014-09-24T22:26:35.734703 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1373495/+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 1828749] Re: ifconfig dummy0 : Device not found
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please could you provide an example of reproduction steps showing the behaviour you're expecting working with "This worked fine until recently"? Perhaps you'll need an older Ubuntu release, older kernel package, or older net-tools package to do this. Once done, please change the bug status back to New. ifconfig is still maintained but deprecated in favour of ip(8). So while this may well be a valid bug that we should fix, I don't think it is of high importance any more, unless it is a regression caused by an update in an existing stable release (and there's no evidence of that in your report). So I'm setting Importance: Low for now. ** Changed in: net-tools (Ubuntu) Status: New => Incomplete ** Changed in: net-tools (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/1828749 Title: ifconfig dummy0 : Device not found Status in net-tools package in Ubuntu: Incomplete Bug description: Desired behavior: The ifconfig command should be able to deal with the dummy device. This worked fine until recently. Observed behavior: :; ifconfig dummy0 dummy0: error fetching interface information: Device not found This problem appeared when I upgraded to bionic. Highly informative workaround: :; ip link add dummy0 type dummy That command works, and makes the problem go away permanently. The ifconfig command works fine after that. The ifup and ifdown commands also work fine after that. For convenient debugging, you can use the command: :; ip link del dummy0 type dummy which makes the problem come back. You can also experiment with dummy1 et cetera. Package ownership issues: Compare: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909204 That report was filed against ippusbxd, which is almost certainly not the relevant package. For that matter, I have no idea whether the root cause is in the net-tools package or the kernel networking stack. All I know is the ip command plays nicely with the kernel while the ifconfig command does not. Notes: The kernel module for the dummy interface is preloaded in all situations described here. That's not the issue. An apport file is attached, to describe the environment. Also, since you asked: :; apt-cache policy net-tools net-tools: Installed: 1.60-26ubuntu1 Candidate: 1.60-26ubuntu1 Version table: *** 1.60-26ubuntu1 500 500 http://ubuntu.cs.utah.edu/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status :; lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1828749/+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 1796193] Re: DistUpgradeViewNonInteractive crashes / requires interaction
Hello Paul, or anyone else affected, Accepted ubuntu-release-upgrader into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /ubuntu-release-upgrader/1:19.04.16.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-release-upgrader (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco ** Changed in: ubuntu-release-upgrader (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed-cosmic -- 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/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: Fix Committed Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: Fix Committed Status in apt source package in Eoan: Incomplete Status in ubuntu-release-upgrader source package in Eoan: Fix Released Bug description: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging. [Regression Potential] The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong. [Original Description] I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version.
[Touch-packages] [Bug 1543799] Re: isc-dhcp-server & isc-dhcp-server6 systemd service units use the same RuntimeDirectory leading to loss of pid files
Seems like this would still apply to Eoan, marking rls-ee-tracking ** Tags removed: rls-x-incoming ** Tags added: rls-ee-tracking ** Changed in: isc-dhcp (Ubuntu) Status: Confirmed => Triaged ** Also affects: isc-dhcp (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: isc-dhcp (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: isc-dhcp (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: isc-dhcp (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: isc-dhcp (Ubuntu Xenial) Status: New => Triaged ** Changed in: isc-dhcp (Ubuntu Bionic) Status: New => Triaged ** Changed in: isc-dhcp (Ubuntu Cosmic) Status: New => Triaged ** Changed in: isc-dhcp (Ubuntu Disco) Status: New => Triaged ** Changed in: isc-dhcp (Ubuntu Xenial) Importance: Undecided => High ** Changed in: isc-dhcp (Ubuntu Bionic) Importance: Undecided => High ** Changed in: isc-dhcp (Ubuntu Cosmic) Importance: Undecided => Critical ** Changed in: isc-dhcp (Ubuntu Cosmic) Importance: Critical => High ** Changed in: isc-dhcp (Ubuntu Disco) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1543799 Title: isc-dhcp-server & isc-dhcp-server6 systemd service units use the same RuntimeDirectory leading to loss of pid files Status in isc-dhcp package in Ubuntu: Triaged Status in isc-dhcp source package in Xenial: Triaged Status in isc-dhcp source package in Bionic: Triaged Status in isc-dhcp source package in Cosmic: Triaged Status in isc-dhcp source package in Disco: Triaged Bug description: dhcpd reports 'Can't create PID file /run/dhcp-server/dhcpd.pid' (or '/run/dhcp-server/dhcpd6.pid' for isc-dhcp-server6), and no file is found /run/dhcp-server. Additionally, both isc-dhcp-server & isc-dhcp-server6 service unit files specify the RuntimeDirectory 'dhcp-server', which is removed when either unit stops (and thus would wipe out the other unit's pid file, were it being successfully written). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-server 4.3.3-5ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Tue Feb 9 21:34:08 2016 InstallationDate: Installed on 2016-02-09 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.dhcp.dhcpd.conf: [modified] mtime.conffile..etc.dhcp.dhcpd.conf: 2016-02-09T21:11:20.104056 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1543799/+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 1796193] Please test proposed package
Hello Paul, or anyone else affected, Accepted ubuntu-release-upgrader into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /ubuntu-release-upgrader/1:18.10.11.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1796193 Title: DistUpgradeViewNonInteractive crashes / requires interaction Status in apt package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in apt source package in Cosmic: New Status in ubuntu-release-upgrader source package in Cosmic: Fix Committed Status in apt source package in Disco: New Status in ubuntu-release-upgrader source package in Disco: Fix Committed Status in apt source package in Eoan: Incomplete Status in ubuntu-release-upgrader source package in Eoan: Fix Released Bug description: [Impact] The NonInteractive view of ubuntu-release-upgrader doesn't work so it is hard to automate upgrade testing. [Test Case] You need to create a situation where you'll receive a conffile prompt since the handling of those is broken. 1) On a bionic system modify /etc/update-manager/release-upgrades so that Prompt=normal 2) Test an upgrade from bionic to cosmic or disco i.e. run do-release-upgrade 3) Observe the upgrade hang on the '/etc/update-manager/release-upgrades' conffifle and the following in /var/log/dist-upgrade/main.log "2019-05-10 21:21:21,313 WARNING got a conffile-prompt from dpkg for file: '/etc/update-manager/release-upgrades' 2019-05-10 21:21:26,319 ERROR error 'a bytes-like object is required, not 'str'' when trying to write to the conffile" With the version of the release-upgrader from -proposed you'll no longer observe the upgrade process hanging. [Regression Potential] The fix is making it so that a byte object is passed to the prompt instead of a string one so there really isn't one, however additional logging which could result in a Traceback if the syntax of that is wrong. [Original Description] I'm trying to do some automated testing that involved upgrading a system from xenial to bionic, so I need it to not ask for user input. Before running do-release-upgrade, the system got a fresh dist-upgrade and reboot. To avoid interactive responses, I'm using: $ sudo do-release-upgrade -d -f DistUpgradeViewNonInteractive Part way through the upgrade, I do get prompted for something though: Preparing to unpack .../apt_1.6.3ubuntu0.1_amd64.deb ... Unpacking apt (1.6.3ubuntu0.1) over (1.2.27) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf: No such file or directory Setting up apt (1.6.3ubuntu0.1) ... Installing new version of config file /etc/apt/apt.conf.d/01autoremove ... Configuration file '/etc/cron.daily/apt-compat' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. Comparing the sha1 of apt-compat before the upgrade to another xenial system that has been unmodified, they are the same: In /var/log/dist-upgrade/main.log, I also found this: 2018-10-04 14:20:24,575 WARNING got a conffile-prompt from dpkg for file: '/etc/cron.daily/apt-compat' 2018-10-04
[Touch-packages] [Bug 1422096] Re: Occasionally no network on resume
No. I don't have that laptop any more though, but I do have a similar network setup (connecting via wired and wireless to the same network). This can probably be Incomplete -> expired. ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1422096 Title: Occasionally no network on resume Status in network-manager package in Ubuntu: Incomplete Bug description: Sometimes I resume and n-m thinks that lxcbr0 is a connected wired network, so doesn't connect to the wireless network that I actually want to use until I restart it. laney@iota> nmcli d DEVICE TYPE STATE CONNECTION lxcbr0 bridgeconnected lxcbr0 virbr0 bridgeconnected virbr0 50:46:5D:18:E7:06 btdisconnected -- wlan0 wifi disconnected -- eth0 ethernet unavailable -- lo loopback unmanaged -- virbr0-nic tap unmanaged -- laney@iota> nmcli d w l ifname wlan0 * SSID MODE CHAN RATE SIGNAL BARS SECURITY laney@iota> cat /etc/network/interfaces auto lo iface lo inet loopback ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu6 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Feb 15 10:37:28 2015 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-10-18 (850 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.134 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2014-07-30 (200 days ago) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1422096/+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 1523814] Re: /usr/bin/software-properties-gtk:dbus.exceptions.UnknownMethodException:/usr/bin/software-properties-gtk@101:__init__:__call__:__call__:call_blocking:_message_cb:_me
After a release it is recommended that people reboot, if this isn't being done strange things will happen. ** Changed in: software-properties (Ubuntu) Status: New => Triaged ** Changed in: software-properties (Ubuntu) Importance: High => Low ** Tags removed: rls-x-incoming ** Tags added: rls-x-notfixing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1523814 Title: /usr/bin/software-properties- gtk:dbus.exceptions.UnknownMethodException:/usr/bin/software- properties- gtk@101:__init__:__call__:__call__:call_blocking:_message_cb:_method_lookup Status in software-properties package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with version 0.96.16, the problem page at https://errors.ubuntu.com/problem/54d28e4d28f41d663f85f5262fdaa91558d3ce09 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1523814/+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 1811580] Re: systemd fails to start sshd at reboot
Thank you @vorlon . I made some test with that image on a clean server and it works with no issues, but I had issues in different servers with the same image and other worked fine with the same AMI. I use a proxy repository, this can be related to different/incompatible systemd and kernel versions installed using that repo? -- 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/1811580 Title: systemd fails to start sshd at reboot Status in systemd package in Ubuntu: Incomplete Bug description: So far reported issues turned out to be: - obsolete/buggy/vulnerable 3rd party provided kernels - bad permissions on / Please ensure / is owned by root:root. Please ensure you are running up to date kernels. === Ubuntu 16.04.5, systemd 229-4ubuntu21.15 The latest systemd update has somehow changed the method it uses to start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and /var/run/sshd/ does not already exist. Being as this is the default, virtually EVERY Ubuntu 16.04 server in the world has UsePrivilegeSeparation set to yes. Furthermore, at the time when the user performs 'apt upgrade' and receives the newest version of systemd, /var/run/sshd/ already exists, so sshd successfully reloads for as long as the server doesn't get rebooted. BUT, as soon as the server is rebooted for any reason, /var/run/sshd/ gets cleaned away, and sshd fails to start, causing the remote user to be completely locked out of his system. This is a MAJOR issue for millions of VPS servers worldwide, as they are all about to get locked out of their servers and potentially lose data. The next reboot is a ticking time bomb waiting to spring. The bomb can be defused by implicitly setting 'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however unsuspecting administrators are bound to be caught out by the millions. I got caught by it in the middle of setting up a new server yesterday, and it took a whole day to find the source. The appropriate fix would be to ensure that systemd can successfully 'start ssh.service' even when 'UsePrivilegeSeparation yes' is set. systemd needs to test that /var/run/sshd/ exists before starting sshd, just as the init.d script for sshd does. openssl could also be patched so that UsePrivilegeSeparation is no longer enabled by default, however that is not going to solve the problem for millions of pre- existing config files. Only an update to openssl to force-override that flag to 'no' would solve the problem. Thus systemd still needs to be responsible for ensuring that it inits sshd properly by ensuring that /var/run/sshd/ exists before it sends the 'start' command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+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 1794478] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2019-05-14 11:09 EDT--- IBM bugzilla status -> closed, Fix Released with Bionic.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Released Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+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 1822270] Re: Debconf readline frontend does not show options
makedumpfile failures in bionic probably are due to bug 1790788 which is in -proposed, and so should be ignorable -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1822270 Title: Debconf readline frontend does not show options Status in debconf package in Ubuntu: Fix Released Status in debconf source package in Xenial: Fix Committed Status in debconf source package in Bionic: Fix Committed Status in debconf source package in Cosmic: Fix Committed Status in debconf source package in Disco: Fix Committed Status in debconf source package in Eoan: Fix Released Status in debconf package in Debian: Fix Released Bug description: [Impact] debconf prompts the user for input before displaying options [Description] When upgrading packages with apt or dpkg, debconf scripts are ran through 'run-parts' with the '--report' flag. This causes script output to be handled through pipes set up by run-parts, and buffers output from maintainer scripts nicely for formatting. If debconf makes use of the readline frontend, any prompts will bypass the run-parts buffers and be displayed directly to /dev/tty. This generally causes the prompt to be displayed before the user gets any of the available options for it, and printing will block until the user inputs a valid option. Upstream commit: https://salsa.debian.org/pkg- debconf/debconf/commit/48c5ce38cfd5 [Test Case] 1) Deploy a VM through e.g. uvt-kvm $ uvt-kvm create disco release=disco 2) Remove the whiptail package to force the readline frontend in debconf root@disco:~# apt remove --purge whiptail -y 3) Install grub-legacy-ec2 and prepare /boot/grub/menu.lst for an upgrade through run-parts root@disco:~# apt update && apt install -y grub-legacy-ec2 root@disco:~# rm -f /boot/grub/menu.lst* root@disco:~# touch -d "4 years ago" /boot/grub/menu.lst 4) Invoke run-parts as in a kernel upgrade (kernel version doesn't matter, we just need it to think menu.lst needs an upgrade) root@disco:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d --report ... /etc/kernel/postinst.d/x-grub-legacy-ec2: debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.) debconf: falling back to frontend: Readline Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... What would you like to do about menu.lst? The "What would you like to do about menu.lst?" prompt will block until the user enter a valid option, even though it's being displayed before the available options. [Regression Potential] We could hit regressions if changing debconf's printing to /dev/tty is expected by other programs. The changes are needed only in the readline frontend, so that would minimize impact of any possible regressions. The fixes will be thoroughly tested with autopkgtest and use-case scenarios. # # # # [Original Description] When upgrading the kernel on a recent Bionic minimal image, the user is prompted to resolve a conflict in the file /boot/grub/menu.lst. The minimal images do not have dialog/whiptail installed, so debconf falls back to using the readline frontend. The user sees the prompt: "What would you like to do about menu.lst?" but is not presented with the list of options to choose from. If a valid option is typed in, debconf will continue processing correctly and the list of options appears on the screen. See also https://pastebin.ubuntu.com/p/8xvSn88SKG/ STEPS TO REPRODUCE: Launch the minimal Bionic image with serial 20190212 http://cloud- images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04 -minimal-cloudimg-amd64.img for example via multipass and run `apt-get update` and `apt-get dist- upgrade`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+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 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
** Changed in: network-manager (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Committed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Released Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+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 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Released Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+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 1829025] [NEW] mouse
Public bug reported: mousse dont work well ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue May 14 10:20:32 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 82946GZ/GL Integrated Graphics Controller [8086:2972] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo 82946GZ/GL Integrated Graphics Controller [17aa:300b] ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=876b673d-874d-476c-90be-90e7f71c5a7e ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2007 dmi.chassis.vendor: LENOVO dmi.product.name: 9642A34 version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue May 14 09:21:50 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1829025 Title: mouse Status in xorg package in Ubuntu: New Bug description: mousse dont work well ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-48.51~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue May 14 10:20:32 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 82946GZ/GL Integrated Graphics Controller [8086:2972] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo 82946GZ/GL Integrated Graphics Controller [17aa:300b] ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=876b673d-874d-476c-90be-90e7f71c5a7e ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2007 dmi.chassis.vendor: LENOVO dmi.product.name: 9642A34 version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue May 14 09:21:50 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1829025/+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 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS Status in openssl package in Ubuntu: Fix Released Status in python-tornado package in Ubuntu: Confirmed Status in libio-socket-ssl-perl source package in Bionic: Incomplete Status in libnet-ssleay-perl source package in Bionic: Incomplete Status in openssl source package in Bionic: Fix Committed Status in python-cryptography source package in Bionic: Fix Committed Status in python2.7 source package in Bionic: Fix Committed Status in python3.6 source package in Bionic: Fix Committed Status in python3.7 source package in Bionic: Fix Committed Status in r-cran-openssl source package in Bionic: Fix Committed Status in ruby-openssl source package in Bionic: Fix Committed Status in ruby2.5 source package in Bionic: Confirmed Bug description: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Test cases for the python updates] python3.7 is a preview in bionic as a non-supported/non-default version of python3. Passing it's own autopkgtests is sufficient validation for python3.7. It includes a point release update, with OpenSSL 1.1.1 compat and features. python3.6 not only has OpenSSL 1.1.1 compat and features patches, but also includes a point release update to 3.6.8. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python3.6 and python3-defaults with regressions already fixed in the individual packages as appropriate. python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1 compat only. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python2.7 and python-defaults with regressions already fixed in the individual packages as appropriate. The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1 and python point releases as seen in: http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html And analyzed in https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652 [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes * Notable changes are listed here https://wiki.openssl.org/index.php/TLS1.3 * Most common connectivity issues so far: - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. Solution is client change to set hostname, or to clamp down the client to TLSv1.2. - session negotiation is different in TLSv1.3, existing client code may fail to create/negotiate/resume session. Clients need to learn how to use session callback. - non-application data records. TLSv1.3 sends more of these, when compared with previous versions, and some applications may not handle this correctly. Resulting in application data not being available, when previously expected. Mitigation around these involve disabling/enabling SSL_MODE_AUTO_RETRY or setting max protocol version to TLSv1.2. For example see discussion identified in the perl stack https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034 Similar hangs are possible with prior versions of TLS as well, it is however easier to trigger this with TLSv1.3. * This update bundles python 3.6 and 3.7 point releases [Other Info] * Previous FFe for OpenSSL in 18.10 is at https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092 * TLS v1.3 support in NSS is expected to make it to 18.04 via
[Touch-packages] [Bug 1821640] Re: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system
@vorlon: I tried to explain the advantages of handling versioned kernel packages uniformly in: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/comments/5 U-u and update-manager use the patterns not just for removal but also for _protecting_ the running kernel and not autoremoving it, thus having accurate patterns helps not breaking the system as well. I'm adding an autopkgtest in u-u to check if every versioned kernel pattern is covered to not miss any and prevent bugs like LP: #1698159: https://github.com/mvo5/unattended-upgrades/pull/199 -- 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/1821640 Title: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: In Progress Status in apt source package in Cosmic: Incomplete Status in apt source package in Disco: Fix Committed Status in apt source package in Eoan: Fix Released Bug description: [Impact] Unattended-upgrades keeps versioned kernel packages because they don't match known kernel package patterns: ... Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it would also remove the following packages which should be kept in this step: linux-image-unsigned-4.18.0-14-generic ... For reproduction see LP: #1795696, but running u-u with --verbose. And APT does not apply proper kernel-version based protection to it. [Test case] linux-image-unsigned should popup in the same list in 01autoremove-kernels as linux-signed-image, and should be autoremovable iff it's signed counterpart is autoremovable. [Regression potential] Not really any, it's just an additional string in the entry. The only difference really possible therefore is that the set of autoremovable packages changes and unattended-upgrades and friends might autoremove different sets of them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+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 1829019] [NEW] Desktop runs at low frame rate
Public bug reported: Moving windows around and using the launcher results in low frame rate (<20 fps), instead of moving smoothly (~60fps). I don't have this issues when I watch videos on YouTube, but I find that the problem is common in all the GNOME-based distros I tried (Ubuntu, Fedora, Clear Linux). Also, the cursor runs smoothly without issues. I'm running Ubuntu 19.04 (with the default updated packages) on a Chuwi 12.3 LapBook with an Intel Celeron N3450 and 6GB of RAM, at 2736 x 1824 pixels of resolution. In addition I directly filed a bug on the GNOME-shell issue page (https://gitlab.gnome.org/GNOME/gnome-shell/issues/1237). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.405 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 14 13:34:36 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: CHUWI INNOVATION AND TECHNOLOGY(SHENZHEN)CO.,LTD NA123 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B3W6_NA123C.033 dmi.board.asset.tag: Hampoo Reserved dmi.board.name: B3W6_NA123C dmi.board.vendor: Hampoo dmi.board.version: Hampoo Reserved dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB3W6_NA123C.033:bd06/12/2017:svnCHUWIINNOVATIONANDTECHNOLOGY(SHENZHEN)CO.,LTD:pnNA123:pvrReserved:rvnHampoo:rnB3W6_NA123C:rvrHampooReserved:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ApolloLake MRD dmi.product.name: NA123 dmi.product.sku: Hampoo Reserved dmi.product.version: Reserved dmi.sys.vendor: CHUWI INNOVATION AND TECHNOLOGY(SHENZHEN)CO.,LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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 disco performance 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/1829019 Title: Desktop runs at low frame rate Status in xorg package in Ubuntu: New Bug description: Moving windows around and using the launcher results in low frame rate (<20 fps), instead of moving smoothly (~60fps). I don't have this issues when I watch videos on YouTube, but I find that the problem is common in all the GNOME-based distros I tried (Ubuntu, Fedora, Clear Linux). Also, the cursor runs smoothly without issues. I'm running Ubuntu 19.04 (with the default updated packages) on a Chuwi 12.3 LapBook with an Intel Celeron N3450 and 6GB of RAM, at 2736 x 1824 pixels of resolution. In addition I directly filed a bug on the GNOME-shell issue page (https://gitlab.gnome.org/GNOME/gnome-shell/issues/1237). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.405 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 14 13:34:36 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2212] LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: CHUWI INNOVATION AND TECHNOLOGY(SHENZHEN)CO.,LTD NA123 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8
[Touch-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
** Changed in: udisks2 (Ubuntu Bionic) Status: New => Invalid ** Changed in: udisks2 (Ubuntu Disco) Status: New => Invalid ** Changed in: udisks2 (Ubuntu Eoan) Status: New => Invalid -- 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/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in udisks2 package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in systemd source package in Bionic: New Status in udisks2 source package in Bionic: Invalid Status in linux source package in Disco: New Status in systemd source package in Disco: New Status in udisks2 source package in Disco: Invalid Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: New Status in udisks2 source package in Eoan: Invalid Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1829017] [NEW] [SRU] Enable support for Train Cloud Archive
Public bug reported: Please add support for: cloud-archive:train cloud-archive:train-proposed This will also need to be SRU'd back to bionic. [Impact] End users have to manually enable the train cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:train sudo add-apt-repository cloud-archive:train-proposed [Regression potential] Limited - just a data item addition ** Affects: software-properties (Ubuntu) Importance: High Status: Triaged ** Affects: software-properties (Ubuntu Bionic) Importance: High Status: Triaged ** Affects: software-properties (Ubuntu Eoan) Importance: High Status: Triaged ** Also affects: software-properties (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Bionic) Status: New => Triaged ** Changed in: software-properties (Ubuntu Eoan) Status: New => Triaged ** Changed in: software-properties (Ubuntu Bionic) Importance: Undecided => High ** Changed in: software-properties (Ubuntu Eoan) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1829017 Title: [SRU] Enable support for Train Cloud Archive Status in software-properties package in Ubuntu: Triaged Status in software-properties source package in Bionic: Triaged Status in software-properties source package in Eoan: Triaged Bug description: Please add support for: cloud-archive:train cloud-archive:train-proposed This will also need to be SRU'd back to bionic. [Impact] End users have to manually enable the train cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:train sudo add-apt-repository cloud-archive:train-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1829017/+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 1829018] [NEW] logrotate changing the date & time of files to today's date during second time execution while deleting old logs
Public bug reported:
using ubuntu 14.04 ISO image
logrotate version is 3.8.7
below configuration i am using in logrotate:
/home/data/logs/production_logs/int_conf??.log*-
/home/data/logs/production_logs/rou_stat.log*-
/home/data/feedLogs/genericLog/*.*.dup
/home/data/feedLogs/genericLog/*.*.log
{
rotate 0
missingok
sharedscripts
firstaction
find /home/data/logs/production_logs -maxdepth 1 -mtime +10
-name "int_conf??.log*-" -print -delete
find /home/data/logs/production_logs -maxdepth 1 -mtime +10
-name "rou_stat.log*-" -print -delete
find /home/data/feedLogs/genericLog -maxdepth 1 -mtime +10
-name "R.*.dup" -print -delete
find /home/data/feedLogs/genericLog -maxdepth 1 -mtime +10
-name "R.*.log" -print -delete
endscript
}
results:
when i run first time it is working as expected (removing old logs and not
touching other logs)
and when i run again it is not removing any logs as expected but
changing timestamp so it is a problem as removing old logs is completely
depend on modified timme (-mtime) on find command
please suggest not to modify timestamp when i run second time
** Affects: logrotate (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1829018
Title:
logrotate changing the date & time of files to today's date during
second time execution while deleting old logs
Status in logrotate package in Ubuntu:
New
Bug description:
using ubuntu 14.04 ISO image
logrotate version is 3.8.7
below configuration i am using in logrotate:
/home/data/logs/production_logs/int_conf??.log*-
/home/data/logs/production_logs/rou_stat.log*-
/home/data/feedLogs/genericLog/*.*.dup
/home/data/feedLogs/genericLog/*.*.log
{
rotate 0
missingok
sharedscripts
firstaction
find /home/data/logs/production_logs -maxdepth 1 -mtime +10
-name "int_conf??.log*-" -print -delete
find /home/data/logs/production_logs -maxdepth 1 -mtime +10
-name "rou_stat.log*-" -print -delete
find /home/data/feedLogs/genericLog -maxdepth 1 -mtime +10
-name "R.*.dup" -print -delete
find /home/data/feedLogs/genericLog -maxdepth 1 -mtime +10
-name "R.*.log" -print -delete
endscript
}
results:
when i run first time it is working as expected (removing old logs and not
touching other logs)
and when i run again it is not removing any logs as expected but
changing timestamp so it is a problem as removing old logs is
completely depend on modified timme (-mtime) on find command
please suggest not to modify timestamp when i run second time
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1829018/+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 1010421] Re: Text antialiasing is green.....
The reporter said it's fixed for him, closing. If you have similar issues on newer version better to open a new report with the system info and a screenshot ** Changed in: fontconfig (Ubuntu) Importance: Undecided => Low ** Changed in: fontconfig (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1010421 Title: Text antialiasing is green. Status in fontconfig package in Ubuntu: Fix Released Bug description: g. So upgraded to Gimp 2.8 and now text antialaising is green. Use white text on a black background to check it out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1010421/+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 1821640] Re: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system
I am not convinced that this change is appropriate. No metapackages depend on linux-image-unsigned-$ver, this is NOT expected to be installed on end user systems (it's an implementation detail of our kernel signing process) and I don't think it's necessary to handle it specially for apt autoremoval because it should NEVER be present on the system as a dependency of another package. So why does any actual user have this package installed except by manual user action that they can also revert manually? If this *is* needed, then please include a complete step-by-step test case for verification of the fix. ** Changed in: apt (Ubuntu Cosmic) Status: In Progress => Incomplete -- 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/1821640 Title: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: In Progress Status in apt source package in Cosmic: Incomplete Status in apt source package in Disco: Fix Committed Status in apt source package in Eoan: Fix Released Bug description: [Impact] Unattended-upgrades keeps versioned kernel packages because they don't match known kernel package patterns: ... Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it would also remove the following packages which should be kept in this step: linux-image-unsigned-4.18.0-14-generic ... For reproduction see LP: #1795696, but running u-u with --verbose. And APT does not apply proper kernel-version based protection to it. [Test case] linux-image-unsigned should popup in the same list in 01autoremove-kernels as linux-signed-image, and should be autoremovable iff it's signed counterpart is autoremovable. [Regression potential] Not really any, it's just an additional string in the entry. The only difference really possible therefore is that the set of autoremovable packages changes and unattended-upgrades and friends might autoremove different sets of them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+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 1821640] Re: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system
** Tags added: id-5ca77e29a04a8142d5a182be -- 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/1821640 Title: Missing pattern for linux-image-unsigned keeps autoremovable kernels on the system Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: In Progress Status in apt source package in Cosmic: In Progress Status in apt source package in Disco: Fix Committed Status in apt source package in Eoan: Fix Released Bug description: [Impact] Unattended-upgrades keeps versioned kernel packages because they don't match known kernel package patterns: ... Keeping auto-removable linux-modules-4.18.0-14-generic package(s) because it would also remove the following packages which should be kept in this step: linux-image-unsigned-4.18.0-14-generic ... For reproduction see LP: #1795696, but running u-u with --verbose. And APT does not apply proper kernel-version based protection to it. [Test case] linux-image-unsigned should popup in the same list in 01autoremove-kernels as linux-signed-image, and should be autoremovable iff it's signed counterpart is autoremovable. [Regression potential] Not really any, it's just an additional string in the entry. The only difference really possible therefore is that the set of autoremovable packages changes and unattended-upgrades and friends might autoremove different sets of them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821640/+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 1828657] Re: Slow resume after lid close/open
** Package changed: apport (Ubuntu) => linux (Ubuntu) -- 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/1828657 Title: Slow resume after lid close/open Status in linux package in Ubuntu: Incomplete Bug description: Summary 1.) Release Info: Description: Ubuntu 19.04 Release: 19.04 2.) Package version: linux-image-5.0.0-13-generic 3.) Expected behavior: Computer resumes shortly after opening lid. 4.) Actual behavior: Computer takes ~2 minutes to resume after opening lid. I have installed Ubuntu 19.04 (Disco Dingo) on my Lenovo Flex 6-11IGM. I found that when it resumes from sleep after opening the lid, it takes a long time to resume (~2 minutes). While experimenting with the upstream kernel releases, I found that the problem was introduced with version 5.0.5 version of the Linux kernel; the problem does not occur when I run version 5.0.4. I've narrowed the culprit down to the following commit in the upstream kernel: a57af6d07... ALSA: hda - Enforces runtime_resume after S3 and S4 for each codec This change was applied to the ubuntu kernel with commit 9c51afaceb61459d2becac8fb32c860bb084e643. The following messages appear in the system log upon resume with the released ubuntu kernel: May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel :00:0e.0: azx_get_response timeout, switching to polling mode: last cmd=0x20bf8100 May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: hid-sensor-hub 001F:8086:22D8.0003: timeout waiting for response from ISHTP device May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 May 05 20:22:11 brian-Lenovo-FLEX-6-11IGM kernel: snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -11 These messages do not appear in the system log upon resume when running with upstream kernel version 5.0.4. I have upgraded the system BIOS to the latest from Lenovo (6qcn47ww), but the problem persists. For now, I will run with the 5.0.4 version of the upstream kernel, as I am not experiencing any issues with it. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828657/+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 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS Status in openssl package in Ubuntu: Fix Released Status in python-tornado package in Ubuntu: Confirmed Status in libio-socket-ssl-perl source package in Bionic: Incomplete Status in libnet-ssleay-perl source package in Bionic: Incomplete Status in openssl source package in Bionic: Fix Committed Status in python-cryptography source package in Bionic: Fix Committed Status in python2.7 source package in Bionic: Fix Committed Status in python3.6 source package in Bionic: Fix Committed Status in python3.7 source package in Bionic: Fix Committed Status in r-cran-openssl source package in Bionic: Fix Committed Status in ruby-openssl source package in Bionic: Fix Committed Status in ruby2.5 source package in Bionic: Confirmed Bug description: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Test cases for the python updates] python3.7 is a preview in bionic as a non-supported/non-default version of python3. Passing it's own autopkgtests is sufficient validation for python3.7. It includes a point release update, with OpenSSL 1.1.1 compat and features. python3.6 not only has OpenSSL 1.1.1 compat and features patches, but also includes a point release update to 3.6.8. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python3.6 and python3-defaults with regressions already fixed in the individual packages as appropriate. python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1 compat only. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python2.7 and python-defaults with regressions already fixed in the individual packages as appropriate. The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1 and python point releases as seen in: http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html And analyzed in https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652 [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes * Notable changes are listed here https://wiki.openssl.org/index.php/TLS1.3 * Most common connectivity issues so far: - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. Solution is client change to set hostname, or to clamp down the client to TLSv1.2. - session negotiation is different in TLSv1.3, existing client code may fail to create/negotiate/resume session. Clients need to learn how to use session callback. - non-application data records. TLSv1.3 sends more of these, when compared with previous versions, and some applications may not handle this correctly. Resulting in application data not being available, when previously expected. Mitigation around these involve disabling/enabling SSL_MODE_AUTO_RETRY or setting max protocol version to TLSv1.2. For example see discussion identified in the perl stack https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034 Similar hangs are possible with prior versions of TLS as well, it is however easier to trigger this with TLSv1.3. * This update bundles python 3.6 and 3.7 point releases [Other Info] * Previous FFe for OpenSSL in 18.10 is at https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092 * TLS v1.3 support in NSS is expected to make it to 18.04 via
[Touch-packages] [Bug 1010421] Re: Text antialiasing is green.....
I'm still seeing this on version Version: 2.10.6-3 on Kubuntu 18.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1010421 Title: Text antialiasing is green. Status in fontconfig package in Ubuntu: Confirmed Bug description: g. So upgraded to Gimp 2.8 and now text antialaising is green. Use white text on a black background to check it out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1010421/+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 1828998] Re: package linux-firmware 1.127.24 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 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/1828998 Title: package linux-firmware 1.127.24 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1 Status in initramfs-tools package in Ubuntu: New Bug description: Failed to install ipython ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-firmware 1.127.24 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Tue May 14 19:34:57 2019 Dependencies: DuplicateSignature: package:linux-firmware:1.127.24:子进程 已安装 post-installation 脚本 返回了错误号 1 ErrorMessage: 子进程 已安装 post-installation 脚本 返回了错误号 1 InstallationDate: Installed on 2014-08-18 (1729 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.23 SourcePackage: initramfs-tools Title: package linux-firmware 1.127.24 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1 UpgradeStatus: Upgraded to trusty on 2019-05-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1828998/+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 1826870] Re: cache.commit() doesn't release the archives lock
bionic: Only apt-clone and snapcraft left after retries. Retried them both with themselves as triggers, and they're still failing, so no regressions either. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1826870 Title: cache.commit() doesn't release the archives lock Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Committed Status in python-apt source package in Bionic: Fix Committed Status in python-apt source package in Cosmic: Fix Released Status in python-apt package in Debian: Fix Released Bug description: [Impact] cache.commit() does not release all the locks it acquires as part of committing. This is a regression of locking fixes in bug 1795407. [Test case] This script should work: #!/usr/bin/env python import apt import subprocess cache = apt.Cache() pkg = cache["hello"] pkg.mark_install() cache.commit() subprocess.check_call(["apt", "remove", "--yes", "hello"]) [Regression potential] Other new locking bugs could pop up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826870/+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 1828998] [NEW] package linux-firmware 1.127.24 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1
Public bug reported: Failed to install ipython ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-firmware 1.127.24 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Tue May 14 19:34:57 2019 Dependencies: DuplicateSignature: package:linux-firmware:1.127.24:子进程 已安装 post-installation 脚本 返回了错误号 1 ErrorMessage: 子进程 已安装 post-installation 脚本 返回了错误号 1 InstallationDate: Installed on 2014-08-18 (1729 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.23 SourcePackage: initramfs-tools Title: package linux-firmware 1.127.24 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1 UpgradeStatus: Upgraded to trusty on 2019-05-14 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- 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/1828998 Title: package linux-firmware 1.127.24 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1 Status in initramfs-tools package in Ubuntu: New Bug description: Failed to install ipython ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-firmware 1.127.24 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Tue May 14 19:34:57 2019 Dependencies: DuplicateSignature: package:linux-firmware:1.127.24:子进程 已安装 post-installation 脚本 返回了错误号 1 ErrorMessage: 子进程 已安装 post-installation 脚本 返回了错误号 1 InstallationDate: Installed on 2014-08-18 (1729 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.23 SourcePackage: initramfs-tools Title: package linux-firmware 1.127.24 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回了错误号 1 UpgradeStatus: Upgraded to trusty on 2019-05-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1828998/+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 1779289] Re: [regression] bluetooth mouse not reconnected on reboot
Sorry, I forgot to add the package version to my previous comment (is there no way to edit a comment?): I've tested with gnome-bluetooth 3.28.0-2ubuntu0.2 from bionic-proposed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779289 Title: [regression] bluetooth mouse not reconnected on reboot Status in bluez package in Ubuntu: Invalid Status in gnome-bluetooth package in Ubuntu: Fix Released Status in gnome-bluetooth source package in Bionic: Fix Committed Bug description: * Impact Bluetooth pointer devices are not always correctly paired, which leads to have them failing to connect or not auto-reconnecting * Test case Pair a bluetooth mouse, it should re-connect automatically after suspend/resume or reboot cycles * Regression potential The change makes all devices go through pairing with the standard code that should work fine but we should keep an eye if it confuses some devices and lead to prompt for a PIN when that shouldn't be needd -- This affects at least 2 different bluetooth mice(both logitech) The behavior is that initial config when using the gui works but that the resulting "/var/lib/bluetooth///info" file does not contain a [LinkKey] section as the mouse does not require a pin. This mouse was connection on reboot under 16.04 so it's a new bug for 18.04 When setting up the mouse using bluetoothctl the info file is correctly written with a [LinkKey] section and everything works, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-bluetooth 3.28.0-2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 29 11:27:27 2018 InstallationDate: Installed on 2018-06-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+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 1826870] Re: cache.commit() doesn't release the archives lock
xenial: None of the failures are regressions; the apport one we can also see just with apport as trigger. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1826870 Title: cache.commit() doesn't release the archives lock Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Committed Status in python-apt source package in Bionic: Fix Committed Status in python-apt source package in Cosmic: Fix Released Status in python-apt package in Debian: Fix Released Bug description: [Impact] cache.commit() does not release all the locks it acquires as part of committing. This is a regression of locking fixes in bug 1795407. [Test case] This script should work: #!/usr/bin/env python import apt import subprocess cache = apt.Cache() pkg = cache["hello"] pkg.mark_install() cache.commit() subprocess.check_call(["apt", "remove", "--yes", "hello"]) [Regression potential] Other new locking bugs could pop up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826870/+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 1763763] Re: Duplicate apps in Open With Other Application
The issue is fixed in >= Cosmic. We could workaround it in bionic but it's low priority at this point ** Changed in: gtk+3.0 (Ubuntu) Status: Triaged => Fix Released -- 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/1763763 Title: Duplicate apps in Open With Other Application Status in gtk+3.0 package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Invalid Bug description: Test Case = 1. Create a text file foo.txt 2. Open your file browser (nautilus) and right-click on the file. 3. Select Open Application With 4. In the dialog, click Show All Applications Duplicates == There are duplicates for at least Archive Manager Files (3 versions!) Rhythmbox Videos Text Editor (I see this when I right-click on something that isn't a text file) Other Info == This is triggered by: 1. The system shows apps with NoDisplay=true. This is a useful feature because it allows for a vim.desktop to be able to open files without cluttering the Activities Overview (but that's a different topic. See Debian 879157) 2. We specifically added compatibility .desktop file for upgraders for several main apps. The .desktop files were renamed upstream for better compatibility with Flatpak. (AppStream recommends the reverse-domain org.gnome.gedit.desktop style too). Seb suggested this issue can be fixed with a blacklist in gtk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763763/+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 1624571] Re: White lines visible around LibreOffice toolbars in when using GTK3
** Changed in: libreoffice (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1624571 Title: White lines visible around LibreOffice toolbars in when using GTK3 Status in Ubuntu MATE: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: There are some portions where the theme is not consistent like on the right side "x" and so on. In the pictures you will see a comparation side by side with UBUNTU Mate 16.04 with Mate 1.14 gtk2 ppa The top bar from the picture it's from 16.10 and the next bar it's from 16.04 OS: Ubuntu 16.10 daily Interface : Mate 1.15.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1624571/+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 1825946] Re: 'nm' autopkgtest fails due to GI stderr output
Dan, if you are on it, preparing a network-manager SRU for Xenial, could
you also add the patch which fixes bug 1754671? Here we also need a
network-manager SRU for.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1825946
Title:
'nm' autopkgtest fails due to GI stderr output
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Xenial:
In Progress
Status in network-manager source package in Bionic:
Fix Released
Bug description:
[impact]
'nm' testcase contains:
from gi.repository import NetworkManager, NMClient, GLib
which generates output to stderr:
/tmp/autopkgtest.naU0ts/build.riU/src/debian/tests/nm:23: PyGIWarning:
NetworkManager was imported without specifying a version first. Use
gi.require_version('NetworkManager', '1.0') before import to ensure that the
right version gets loaded.
the gi.require_version call has already been added to cosmic and
disco.
[test case]
see http://autopkgtest.ubuntu.com/packages/network-manager bionic test
results.
[other info]
this only fails intermittently, but the failure is clearly not an
actual problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1825946/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic
The network-manager SRU 1.10.14-0ubuntu2 is in -updates now and the autopkg test got successfully repeated with it, so this SRU can be tranferred to -updates, too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1819615 Title: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic Status in OEM Priority Project: In Progress Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Bionic: Fix Committed Status in libqmi source package in Bionic: Fix Committed Status in modemmanager source package in Bionic: Fix Committed Status in libmbim source package in Disco: Fix Released Status in libqmi source package in Disco: Fix Released Status in modemmanager source package in Disco: Fix Released Status in libmbim source package in Eoan: Fix Released Status in libqmi source package in Eoan: Fix Released Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] * The new modemmanager package adds DW5820e and DW5821 support. * This modemmanager version is needed to support new devices. [Test Case] * install modemmanager, libmbim, and libqmi from -proposed * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) [Regression Potential] * The package comes from Disco and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] To have Bionic, the current LTS, working with as wide of a range of modems as possible we need to have it upgraded to the current 1.10 versions. Also the underlying libraries need to get upgraded appropriately. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1777512] Re: key retrieval timeouts cause failures
We've also been seeing keyserver request failures during our CI/Build process ** Also affects: juju Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1777512 Title: key retrieval timeouts cause failures Status in CDO QA System Tests: Confirmed Status in juju: New Status in software-properties package in Ubuntu: New Bug description: We have been seeing keyserver timeouts causing failed runs at an increased rate recently (over the last 6+ months). Here is an example failure: [10.244.40.32] sudo: add-apt-repository -k https://keyserver.ubuntu.com/ --yes "ppa:curtin-dev/proposed" [10.244.40.32] out: Error: retrieving gpg key timed out. One idea is that this needs to be addressed by making the client (software-properties) more robust. We have an RT about this: https://portal.admin.canonical.com/C112309/ To manage notifications about this bug go to: https://bugs.launchpad.net/cdoqa-system-tests/+bug/1777512/+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
