[Touch-packages] [Bug 1806226] Re: Dell C2665dnf gets broken installation
I get the same issue. Printing a test page on this queue gives me the same PDL error. What package should this bug be assigned to? -- 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/1806226 Title: Dell C2665dnf gets broken installation Status in cups package in Ubuntu: Incomplete Bug description: My apologies if this is the wrong package to file this bug against... I just installed 18.04 on a new machine. Very conveniently, it found my Dell C2665dnf printer and set up an ipp printer for it. Unfortunately, the printer configuration doesn't work. Printing a test page gives 016-720 PDL error. I can install the Dell-created printer filter and PPD and create a printer that works fine, and I have this setup on another 18.04 machine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 2 01:28:28 2018 InstallationDate: Installed on 2018-12-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: device for Dell-C2665dnf-Color-MFP: dnssd://Dell%20C2665dnf%20Color%20MFP%20(D3%3A8E%3AA3)._pdl-datastream._tcp.local/?uuid=e72bf300-1dd2-11b2-ad7c-080037d38ea3 device for Dell_C2665dnf_Color_MFP_D3_8E_A3_: ipp://Dell-C2665dnf-D38EA3.local:631/ipp/print MachineType: LENOVO 2344BPU Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Dell_C2665dnf_Color_MFP_D3_8E_A3_.ppd', '/etc/cups/ppd/Dell-C2665dnf-Color-MFP.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Dell_C2665dnf_Color_MFP_D3_8E_A3_.ppd: Permission denied grep: /etc/cups/ppd/Dell-C2665dnf-Color-MFP.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET93WW (2.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 2344BPU dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET93WW(2.53):bd03/08/2013:svnLENOVO:pn2344BPU:pvrThinkPadT430:rvnLENOVO:rn2344BPU:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2344BPU dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1806226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
I'm confirming 239-7ubuntu10.5 fixed this issue on my system (Kubuntu 18.10). Please, add the fix to Bionic also. Thanks. -- 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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806458] Re: Intel I219-V ethernet connection lost
If it's similar to LP: #1785171, would it be possible to do a kernel bisection? -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.
[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => High ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => High ** Changed in: systemd (Ubuntu Cosmic) Importance: Undecided => High -- 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/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Installation of latest systemd update in -security hangs with current versions of unattended-upgrades in supported releases. The u-u-side fix is tracked in LP: #1778219. [Regression Potential] * The daemons, shipped in deb:systemd, are not attempted to be restarted because despite package installation the system is in the middle of shutting down. This means that currently running daemons may be helding up open files on the filesystem, however all process are being stopped and killed as part of shutdown. Hence the worst possible regression from this, is an unclean shutdown, but even that shouldn't happen with this update. [Test Case] Reproduction: rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown Creating uu-systemd-onshutdown Starting uu-systemd-onshutdown rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@uu-systemd-onshutdown:~# apt list --upgradable Listing... Done apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 [upgradable from: 0.19.8.1-6] kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 2.56.2-0ubuntu0.18.04.2] libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 2.56.2-0ubuntu0.18.04.2] libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable from: 0.6-3ubuntu0.1] libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] root@uu-systemd-onshutdown:~# reboot Session terminated, terminating shell...Terminated root@uu-systemd- rbalint@yogi:~$ rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# tail /var/log/unattended-upgrades/unattended-upgrades-dpkg.log Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ... Setting up libsystemd0:amd64 (237-3ubuntu10.6) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Setting up systemd (237-3ubuntu10.6) ... Failed to try-restart systemd-networkd.ser
[Touch-packages] [Bug 1702793] Re: Full backport SRU for unattended-upgrades
** Changed in: unattended-upgrades (Ubuntu Xenial) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1702793 Title: Full backport SRU for unattended-upgrades Status in unattended-upgrades package in Ubuntu: In Progress Status in unattended-upgrades source package in Xenial: Fix Committed Bug description: [Impact] * I would like to propose a one-off full backport of unattended-upgrades 1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because selectively backporting fixes for crashes and for issues that made u-u unreliable would be more risky thanks to the huge number of fixes and the inter-dependencies between them. [Test Case] * Since this backport involves fixing several bugs and this bug itself covers the full backport this is an overview of all LP bugs the upload fixes: - most important bugs (feel free to add more) + LP: #1615381 : apt-get autoremove may remove current kernel All LP bugs fixed by the backport, comments are welcome: + LP: #1230246 could use SRU template but seems straightforward + LP: #1260041 SRU template ok + LP: #1396787 SRU template ok + LP: #1446552 SRU template ok + LP: #1455097 SRU template ok + LP: #1458204 could use SRU template but seems straightforward + LP: #1577215 could use SRU template but seems straightforward + LP: #1602536 SRU template ok + LP: #1615381 could use SRU template but seems straightforward + LP: #1624644 SRU template ok + LP: #1649709 not affecting xenial + LP: #1654070 could use SRU template but seems straightforward + LP: #1654600 SRU template ok + LP: #1675079 SRU template ok + LP: #1680599 could use SRU template but seems straightforward + LP: #1686470 SRU template ok + LP: #1690980 SRU template ok + LP: #1698159 SRU template ok + LP: #1702793 this bug + LP: #1714019 just a merge request + LP: #1718419 just a merge request + LP: #1719630 SRU template ok + LP: #1722426 just a merge request + LP: #1737442 SRU template ok + LP: #1737635 SRU template ok + LP: #1737637 SRU template ok + LP: #1737717 SRU template ok + LP: #1741579 SRU template ok + LP: #1764797 just a merge request + LP: #1773033 SRU template ok + LP: #1775292 SRU template ok + LP: #1775307 SRU template ok + LP: #1778219 SRU template ok + LP: #1778800 SRU template ok + LP: #1779157 SRU template ok + LP: #1781176 SRU template ok + LP: #1781183 SRU template ok + LP: #1781446 SRU template ok + LP: #1781586 SRU template ok + LP: #1785093 SRU template ok + LP: #1789637 SRU template ok + LP: #1803749 SRU template ok [Regression Potential] * Due to this update covering the full backport unattended-upgrades can regress in any imaginable way including failing to install, upgrade, run, or removing essential packages from the system. Those are unlikely.* There are open bugs about u-u being slower than in the past, thus this may be a likely regression but IMO the pending speed optimizations should not be blocking the backport because the reliability issues are more important to fix and speed optimizations can be cherry-picked later. [Other Info] I asked for an exception for the package in following the SRU process: https://lists.ubuntu.com/archives/ubuntu-release/2018-May/004479.html I'm preparing the backport in ppa:rbalint/scratch and also run autopkgtests on it in addition to testing it manually in VMs. [Original Bug Text] Changes to support day-of-week patching and logging to syslog were added to upstream (https://github.com/mvo5/unattended-upgrades) over a year ago. These changes are not present in the latest Xenial nor Trusty packages (0.90 and 0.82.1) - requesting that these changes be pulled from upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1702793/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
** Bug watch removed: Debian Bug tracker #797108 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797108 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1654600 Title: unattended-upgrade-shutdown hangs when /var is a separate filesystem Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Yakkety: Fix Released Status in unattended-upgrades source package in Zesty: Fix Released Status in unattended-upgrades package in Debian: Fix Released Bug description: [SRU justification] This fix is needed to make sure that the system does not hang on shutdown when /var is a speparate file system [Impact] System can hang up to 10 minutes if not fixed. [Fix] Change the systemd unit's ExecStart to an ExecStop so the unit is correctly sequenced. Change WantedBy to multi-user.target. This requires working around Debian Bug #797108 which causes the new unit not to be enabled. Remove the unneeded override_dh_isntallinit Add Default-Start levels to the SysV initscript Improve DEP8 testing [Test Case] In a VM with /var separated from the / file system, shutdown the VM. It will hang for 10 minutes [Regression] Upgrade has been tested on Xenial, Yakkety, Zesty. do-release-upgrade has been tested from Trusty to Xenial. All behave as expected. A change of behavior may occur now that the systemd unit is correctly enabled, which would make functionalities like InstallOnShutdown to work as expected whereas it could have been broken previously. This cannot be considered as a regression as it is expected behavior. Shutdown may be slowed down as it now correctly depends on /var and /boot to be available so the unit will run earlier than previously. [Original description of the problem] The systemd unit file unattended-upgrades.service is used to stop a running unattended-upgrade process during shutdown. This unit file is running together with all filesystem unmount services. The unattended-upgrades service checks if the lockfile for unattended-upgrade (in /var/run) exists, and if it does, there is an unattended-upgrade in progress and the service will wait until it finishes (and therefore automatically wait at shutdown). However, if /var is a separate filesystem, it will get unmounted even though /var/run is a tmpfs that's still mounted on top of the /var/run directory in the /var filesystem. The unattended-upgrade script will fail to find lockfile, sleeps for 5 seconds, and tries to check the lockfile again. After 10 minutes (the default timeout), it will finally exit and the system will continue shutdown. The problem is the error handling in /usr/share/unattended-upgrades/unattended-upgrade-shutdown where it tries to lock itself: while True: res = apt_pkg.get_lock(options.lock_file) logging.debug("get_lock returned %i" % res) # exit here if there is no lock if res > 0: logging.debug("lock not taken") break lock_was_taken = True The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an error. File descriptors are just C file descriptors, so they are always positive integers. The code should check the result to be negative, not positive. I have attached a patch to reverse the logic. Additional information: 1) Description: Ubuntu 16.04.1 LTS Release: 16.04 2) unattended-upgrades: Installed: 0.90ubuntu0.3 Candidate: 0.90ubuntu0.3 Version table: *** 0.90ubuntu0.3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 0.90 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages 3) Fast reboot 4) Very slow reboot (after a 10 minutes timeout) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1489154] Re: NetworkManager does not start / fails to start
** Changed in: hundredpapercuts Status: Incomplete => Confirmed -- 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/1489154 Title: NetworkManager does not start / fails to start Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Yesterday i did the upgrade to version 1.0.4 of NetworkManger. Today my Xubuntu 15.10 cannot connect to the net, and wants to upload a crash report. This also fails cause the start of the NetworkManger fails after booting. Trying manually to start with ~$ sudo systemctl start NetworkManager leads that the icon comes up, disappears, comes up, disappears for 3, 4 times and then it's gone forever. ~$ journalctl -xe Aug 26 22:02:34 Wily NetworkManager[1578]: monitoring ifupdown state file '/run/network/ifstate'. Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVxlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVethFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMTunFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMMacvlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMInfinibandFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMGreFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMEthernetFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBridgeFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBondFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMAtmManager (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMWifiFactory (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBluezManager (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMWwanFactory (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so) Aug 26 22:02:34 Wily NetworkManager[1578]: WiFi enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: WWAN enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: WiMAX enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: Networking is enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Aug 26 22:02:34 Wily NetworkManager[1578]: (lo): link connected Aug 26 22:02:34 Wily NetworkManager[1578]: (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1) Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): link connected Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): new Ethernet device (carrier: ON, driver: 'e1000', ifindex: 2) Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Aug 26 22:02:34 Wily NetworkManager[1578]: keyfile: add connection in-memory (4251ae7f-22a1-4de8-8f11-7a62fd420d65,"Kabelnetzwerkverbindung 1") Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): created default wired connection 'Kabelnetzwerkverbindung 1' Aug 26 22:02:34 Wily NetworkManager[1578]: urfkill disappeared from the bus Aug 26 22:02:34 Wily NetworkManager[1578]: wpa_supplicant running Aug 26 22:02:34 Wily NetworkManager[1578]: ModemManager available in the bus Aug 26 22:02:34 Wily NetworkManager[1578]: ofono is now available Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): GLib-GObject-WARNING **: /build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 'ModemAdded' is invalid for instance Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): GLib-GObject-WARNING **: /build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 'ModemRemoved' is invalid for instan Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): GLib-CRITICAL **: g_variant_get_va: assertion 'value != NULL' failed Aug 26 22:02:34 Wily kernel: NetworkManager[1578]: segfault at c ip b6f4b97a sp bffb4890 error 4 in libglib-2.0.so.0.4504.0[b6ec8000+127000] Aug 26 22:02:34 Wily systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=11/SEGV Aug 26 22:02:34 Wily systemd[1]: NetworkManag
[Touch-packages] [Bug 1767322] Re: "Activation of network connection failed" popup shows incessantly
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1767322 Title: "Activation of network connection failed" popup shows incessantly Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: All network connections work normally, however the popup "Activation of network connection failed" keeps showing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:04:56 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-03 (24 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 600 192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 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-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806797] Re: Xorg freeze
Does the problem only occur in Xorg sessions (the "Ubuntu" login option)? Or does it also occur in "Ubuntu on Wayland" sessions? ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Summary changed: - Xorg freeze + Frozen (black) screen on resume/unlock ** Tags added: black-screen resume suspend-resume -- 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/1806797 Title: Frozen (black) screen on resume/unlock Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have a monitor to which I connect using an HDMI cable. While connected, I have 2 displays and I can use both fine. When I disconnect, it is also fine, until I close the laptop or it goes to sleep. When it wakes up, I get the unlock/login screen, and I can login fine as anyone but myself. When I login as myself (i.e., unlock the screen rather than login), I get a completely black screen. I can get the login/unlock screen back using Ctrl-Alt-F1, and repeat an attempt to unlock with the same result - black screen. My only options appears to be reboot or kill the X server from the console (Ctrl-Alt-F2, login and kill). This started to happen recently (a month?) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 21:18:19 2018 DistUpgraded: 2018-10-28 13:01:03,617 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: system76, 1.0.0~1540923431~18.10~33e9d57~dev, 4.18.0-11-generic, x86_64: installed system76, 1.0.0~1540923431~18.10~33e9d57~dev, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics Controller [1558:6504] MachineType: System76, Inc. Gazelle Pro ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=7d2767f3-1197-464e-97fa-45cecbaa7e66 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to cosmic on 2018-10-28 (37 days ago) dmi.bios.date: 06/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.04SB.01RSY5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Gazelle Pro dmi.board.vendor: System76, Inc. dmi.board.version: gazp9c dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.04SB.01RSY5:bd06/04/2015:svnSystem76,Inc.:pnGazellePro:pvrgazp9c:rvnSystem76,Inc.:rnGazellePro:rvrgazp9c:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Gazelle Pro dmi.product.sku: Not Applicable dmi.product.version: gazp9c dmi.sys.vendor: System76, Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2015-10-05T22:04:33.987988 version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Sat Oct 14 23:40:31 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1806797/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806797] [NEW] Xorg freeze
Public bug reported: I have a monitor to which I connect using an HDMI cable. While connected, I have 2 displays and I can use both fine. When I disconnect, it is also fine, until I close the laptop or it goes to sleep. When it wakes up, I get the unlock/login screen, and I can login fine as anyone but myself. When I login as myself (i.e., unlock the screen rather than login), I get a completely black screen. I can get the login/unlock screen back using Ctrl-Alt-F1, and repeat an attempt to unlock with the same result - black screen. My only options appears to be reboot or kill the X server from the console (Ctrl-Alt-F2, login and kill). This started to happen recently (a month?) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 4 21:18:19 2018 DistUpgraded: 2018-10-28 13:01:03,617 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: system76, 1.0.0~1540923431~18.10~33e9d57~dev, 4.18.0-11-generic, x86_64: installed system76, 1.0.0~1540923431~18.10~33e9d57~dev, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics Controller [1558:6504] MachineType: System76, Inc. Gazelle Pro ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=7d2767f3-1197-464e-97fa-45cecbaa7e66 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to cosmic on 2018-10-28 (37 days ago) dmi.bios.date: 06/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.04SB.01RSY5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Gazelle Pro dmi.board.vendor: System76, Inc. dmi.board.version: gazp9c dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.04SB.01RSY5:bd06/04/2015:svnSystem76,Inc.:pnGazellePro:pvrgazp9c:rvnSystem76,Inc.:rnGazellePro:rvrgazp9c:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Gazelle Pro dmi.product.sku: Not Applicable dmi.product.version: gazp9c dmi.sys.vendor: System76, Inc. modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2015-10-05T22:04:33.987988 version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Sat Oct 14 23:40:31 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic freeze third-party-packages 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/1806797 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I have a monitor to which I connect using an HDMI cable. While connected, I have 2 displays and I can use both fine. When I disconnect, it is also fine, until I close the laptop or it goes to sleep. When it wakes up, I get the unlock/login screen, and I can login fine as anyone but myself. When I login as myself (i.e., unlock the screen rather than login), I get a completely black screen. I can get the login/unlock screen back using Ctrl-Alt-F1, and repeat an attempt to unlock with the same result - black screen. My only options appears to be reboot or kill the X server from the console (Ctrl-Alt-F2, login and kill). This started to happen recently (a month?) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 .tm
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows
Wasn't this already verified by Dimitri on 2017-08-01? -- 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/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in apt source package in Yakkety: Won't Fix Status in unattended-upgrades source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Released Status in unattended-upgrades source package in Zesty: Fix Released Status in apt source package in Artful: Fix Released Status in unattended-upgrades source package in Artful: Fix Released Status in apt package in Debian: Fix Released Status in unattended-upgrades package in Debian: Fix Released Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. * Downgrade systemd to the release version of the package (from -security). Remove apt periodic stamp files rm /var/lib/apt/periodic/*. Then run 'sudo systemctl start apt-daily.service'. Confirm that the systemd package is downloaded, but not upgraded. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they prefer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801496] Re: Printing job in 16.04 is slower than in 14.04
Dear Till, I'am very sorry to bother you again. We are still working hard to looking for cause why Ubuntu 16.04 printing performance slowdown. We figure out that there are many cause may slowdown the print job. The other cause than OS may slowdown the print job, and we are working on those cause’s investigation. Here are some slowdown point about OS issues that we can't investigation deeper, we hope that you(or your team) can offer a help for the investigation. The phenomenon that print jobs slower in 16.04 is more obvious when printing many single page jobs in the same time. We use a printing manual to simulate the continuous printing. The printing result shows that Ubuntu 16.04 is slower than 14.04. Below is the printing time: Ubuntu 14.04: Round 1: 12.86(s) Round 2: 12.56(s) Aver: 12.73(s) Ubuntu 16.04: Round 1: 14.09(s) Round 2: 13.98(s) Aver: 14.29(s) Attach file introduction: Test log: \PS_Driver_log\PS_Driver_log\Log\error_log20181204_14.04Origin_A4_7ods_job47_53 \PS_Driver_log\PS_Driver_log\Log\error_log20181204_16.04Origin_A4_7ods_job83_89 Test Driver: \PS_Driver_log\PS_Driver\Ricoh-Basic-PS-PPDv1.12.1.tar.gz Test file: \PS_Driver_log\Testfile\testlinux.ods Printing manual: \PS_Driver_log.zip\TestManualOfContinuousPrinting.docx By the way, the printing performance is unstable, some times the slowdown of Ubuntu 16.04 is obvious. But what we can confirm is that Ubuntu 16.04 is slower all the time. We appreciate that you can do we a favor on the investigation why 16.04's printing performance slowdown. Best Regards, ** Attachment added: "PS_Driver_log.zip" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1801496/+attachment/5219187/+files/PS_Driver_log.zip -- 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/1801496 Title: Printing job in 16.04 is slower than in 14.04 Status in cups package in Ubuntu: Incomplete Bug description: Ubuntu 16.04LTS OS Version: 16.04.5 CUPS Version: 2.1.3 Ghostscript Version: 9.25 (2018-09-13) Printing job in 16.04 is slower than in 14.04 We(RICOH printer driver developer) are report a problem from our printer users: I print file Ubuntu 14.04.5, CUPS 2.1.3,Ghostscript 9.25 is fast(12 Seconds). But, after I update to Ubuntu 16.04, CUPS 2.1.3, Ghostscript 9.25, I print the same file with the same driver is slow(326 Seconds). I figure out that all the print jobs is much slower on Ubuntu 16.04. I view the "CUPS Error Log", it shows that there are three points which maybe the reasons that makes the print job slowly. FIRST: By counting the time from "Starting renderer" to "renderer exited with status 0", we figure out that 16.04 spend more time than 14.04 on "renderer" process. So we assuming that:"renderer" is one of the key process that makes the print job slowly. "Starting renderer with command: \"printf \'\\033%%-12345X@PJL JOB\\012\';printf \'@PJL SET DATAMODE=TWIN\\ @PJL EOJ\\012\\033%%-12345X\'\"" . renderer exited with status 0" SECOND: On 16.04, a print job outputs lots of logs as below: "[Job xxx] Removing document files." This step(“Removing document files”)does not exsit on 14.04. The phenomenon that print jobs slower in 16.04 is more obvious when printing many jobs in the same time. THIRD We tried drivers form other company(HP,Brother…), the printings also slow down in Ubuntu 16.04 than 14.04. Our question is: 1. Do you have any plan to improve the performance of printing on Ubuntu 16.04? 2. Do you have any workaround before this problems fixed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1801496/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 237743] Re: Include compizconfig-settings-manager by default
Closing this old bug as we've moved on from compiz ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Invalid -- 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/237743 Title: Include compizconfig-settings-manager by default Status in ubuntu-meta package in Ubuntu: Invalid Status in compizconfig-settings-manager package in Baltix: New Bug description: Compiz-Fusion is getting to be an enormously powerful desktop effects platform. Unfortunately, new Ubuntu users can only experience two preset levels of the compositing manager. This can be easily remedied by installing the compizconfig-settings-manager (CCSM), which shows up as "Advanced Desktop Effects Settings" in the System>Preferences menu. It also creates a "Custom" button in the System>Preferences>Appearance>Visual Effects tab. I propose to make the CCSM installed by default, so users can customize their desktop effects easily during LiveCD mode or initially after a clean install. There are several reasons for this: 1) Gain easy customization of Compiz-Fusion. The main reason many causal users switch to Ubuntu is because they see the awesome visual effects (wobbly windows, desktop cube, etc.). However, by default the Desktop Cube exists as a plugin, but you easily can't enable it without the CCSM. The plugins are already there, users just need the GUI to enable them. 2) Customizing desktop effects could be done in LiveCD mode. This would be enormously helpful for small demonstrations. You would be able to just pop in the LiveCD and show off some great desktop effects. No internet connection or lengthy repository update and install needed. (Yes, I know this might be slow, but LiveCDs are easily converted to LiveUSBs, which may make custom desktop effects feasible) 2) Users could customize desktop effects without a connection to the internet. Users would have instant access to customizable desktop effects upon a new install. This is also useful for demonstration purposes as a lecturer can show how easy it is to jump from MS Windows (dull) to 3D WOBBLY WINDOWS ON A CUBE (woot!). Once again, no internet connection needed. Ubuntu Forums thread: http://ubuntuforums.org/showthread.php?t=581491 Launchpad Blueprint: https://blueprints.launchpad.net/ubuntu/+spec/compiz-advanced-config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/237743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 561627] Re: ecryptfs-utils should be installed by default
Unfortunately ecryptfs was removed as part of the installer in 18.04. Only full disk encryption for an automated setup at the moment. ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Invalid -- 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/561627 Title: ecryptfs-utils should be installed by default Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Last Saturday I lost my Lucid (due to other issues, unrelated to this bug). I then decided to reinstall from the 2010-04-11 alternate ISO. During the install I kept some partitions, including /home. After install completed I tried to login to Gnome, and got some weird messages stating gconf could not access the gconf data, etc. The gnome startup then completeld with an emtpy window. Moved to a vTerm, logged in, and found the usual two links created by ecryptfs stating the home directory was encrypted. To my surprise, ecryptfs-utils was not installed. Manually installed it, rebooted, and life was good. This is a corner case, of course. But I would expect a lot of users to use home dir encryption, and to recover systems maintaining /home. Given we have been moving to have customers either encrypt the whole partition or their home directories, and given the chance of a reinstall *keeping* /home, ecryptfs-utils should *always* be installed. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: ubuntu-standard 1.195 ProcVersionSignature: Ubuntu 2.6.32-20.29-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-20-generic x86_64 Architecture: amd64 CheckboxSubmission: 23f39d583e289591efa3692115f3f5f2 CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Mon Apr 12 11:20:06 2010 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100411) ProcEnviron: LC_TIME=en_DK.utf8 PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: ubuntu-meta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/561627/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1806687] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 23
No problem, although availability is part of the CIA triad, and if there is a problem with certificates, then there could be a problem with availability. Larry -- How much do you really know about how to use email? http://www.101emailetiquettetips.com/ "Act only according to that maxim whereby you can at the same time will that it should become a universal law without contradiction.” — Immanuel Kant, Grounding for the Metaphysics of Morals. -- On Tue, Dec 4, 2018 at 2:40 PM Eduardo dos Santos Barretto < 1806...@bugs.launchpad.net> wrote: > Thanks for taking the time to report this bug and helping to make Ubuntu > better. We appreciate the difficulties you are facing, but this appears > to be a "regular" (non-security) bug. I have unmarked it as a security > issue since this bug does not show evidence of allowing attackers to > cross privilege boundaries nor directly cause loss of data/privacy. > Please feel free to report any other bugs you may find. > > ** Information type changed from Private Security to Public > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1806687 > > Title: > package ca-certificates 20180409 failed to install/upgrade: installed > ca-certificates package post-installation script subprocess returned > error exit status 23 > > Status in ca-certificates package in Ubuntu: > New > > Bug description: > Occurred during upgrade to 18.04 > > ProblemType: Package > DistroRelease: Ubuntu 18.04 > Package: ca-certificates 20180409 > ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 > Uname: Linux 4.4.0-140-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.5 > Architecture: amd64 > Date: Tue Dec 4 08:07:58 2018 > ErrorMessage: installed ca-certificates package post-installation script > subprocess returned error exit status 23 > InstallationDate: Installed on 2016-04-11 (966 days ago) > InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 > (20160217.1) > PackageArchitecture: all > Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, > 3.6.7-1~18.04 > PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, > 2.7.15~rc1-1 > RelatedPackageVersions: >dpkg 1.19.0.5ubuntu2.1 >apt 1.6.6 > SourcePackage: ca-certificates > Title: package ca-certificates 20180409 failed to install/upgrade: > installed ca-certificates package post-installation script subprocess > returned error exit status 23 > UpgradeStatus: Upgraded to bionic on 2018-12-04 (0 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1806687/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1806687 Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 23 Status in ca-certificates package in Ubuntu: New Bug description: Occurred during upgrade to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Tue Dec 4 08:07:58 2018 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 23 InstallationDate: Installed on 2016-04-11 (966 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 23 UpgradeStatus: Upgraded to bionic on 2018-12-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1806687/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398537] Re: gdebi 0.9.5.3 crashing
** Tags added: bionic ** Changed in: gdebi (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1398537 Title: gdebi 0.9.5.3 crashing Status in gdebi package in Ubuntu: New Bug description: Using gdebi 0.9.5.3-ubuntu2 and gdebi-core 0.9.5.3-ubuntu2 on Trusty 14.10 I tried upgrading the two packages to the 14.10 versions using dpkg and they installed fine but the same crash happened. I'm not sure what is going on. I right click an application (like the official release debi of Teamviewer) and gdebi starts up, begins its scan, then terminates. I think it is failing during its scan for dependencies. I tried reporting this using ubuntu-bug in a terminal but that didn't work so I am not sure how to get all the required supported applications. Is anyone else experiencing this crash? Suggestions? I don't use gdebi much but it is more convenient that firing up a terminal window and typing dpkg everytime I want to install a package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1398537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
** Tags added: indeed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop mongodb I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1398537] Re: gdebi 0.9.5.3 crashing
I tried it recently with xubuntu 18.04.1 and the gui still crashes. I uninstalled gdebi and went back to dpkg from the command line. I will try again on the next LTS release. On Tue, 4 Dec 2018 at 08:30, Paul White <1398...@bugs.launchpad.net> wrote: > We are sorry that we do not always have the capacity to review all > reported bugs in a timely manner. You reported this bug some time ago > and there have been many changes in Ubuntu since that time. > > Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015. > > Do you still see a problem related to the one that you reported in a > currently supported version of Ubuntu? > > Please let us know if you do. Alternatively, this bug report can be left > to expire in approximately 60 days time. > > Thank you for helping make Ubuntu better.related > > Paul White > [Ubuntu Bug Squad] > > > ** Changed in: gdebi (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1398537 > > Title: > gdebi 0.9.5.3 crashing > > Status in gdebi package in Ubuntu: > Incomplete > > Bug description: > Using gdebi 0.9.5.3-ubuntu2 > and gdebi-core 0.9.5.3-ubuntu2 > on Trusty 14.10 > > I tried upgrading the two packages to the 14.10 versions using dpkg > and they installed fine but the same crash happened. > > I'm not sure what is going on. I right click an application (like the > official release debi of Teamviewer) and gdebi starts up, begins its > scan, then terminates. I think it is failing during its scan for > dependencies. > > I tried reporting this using ubuntu-bug in a terminal but that didn't > work so I am not sure how to get all the required supported > applications. > > Is anyone else experiencing this crash? Suggestions? I don't use gdebi > much but it is more convenient that firing up a terminal window and > typing dpkg everytime I want to install a package. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1398537/+subscriptions > -- *David Scott*, BSc BA telegram: @slumbergod www.GarciaScott.dx.am -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1398537 Title: gdebi 0.9.5.3 crashing Status in gdebi package in Ubuntu: Incomplete Bug description: Using gdebi 0.9.5.3-ubuntu2 and gdebi-core 0.9.5.3-ubuntu2 on Trusty 14.10 I tried upgrading the two packages to the 14.10 versions using dpkg and they installed fine but the same crash happened. I'm not sure what is going on. I right click an application (like the official release debi of Teamviewer) and gdebi starts up, begins its scan, then terminates. I think it is failing during its scan for dependencies. I tried reporting this using ubuntu-bug in a terminal but that didn't work so I am not sure how to get all the required supported applications. Is anyone else experiencing this crash? Suggestions? I don't use gdebi much but it is more convenient that firing up a terminal window and typing dpkg everytime I want to install a package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1398537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
I would have expected something in dmesg. After test, check timestamps of other logfiles in /var/log - maybe you then find a log which contains useful information. -- 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/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1228383] Re: gdebi-gtk crashed with SIGSEGV in gtk_label_set_text()
Thanks for your reply. Bug report no longer valid as 13.10 EOL Issue not confirmed by another user No action taken on bug report So marking "Invalid" to close ** Changed in: gdebi (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1228383 Title: gdebi-gtk crashed with SIGSEGV in gtk_label_set_text() Status in gdebi package in Ubuntu: Invalid Bug description: gdebi-gtk crashed on notebook turn-on (not used, but might have had unfinished business with virtualbox?) ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gdebi 0.9.1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Fri Sep 20 17:36:02 2013 ExecutablePath: /usr/share/gdebi/gdebi-gtk InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/gdebi-gtk --non-interactive /media/ian/Nemesis1/Software/Internet\ Software/Virtualbox/For\ Ubuntu\ 13.04/virtualbox-4.2_4.2.18-88780~Ubuntu~raring_amd64.deb ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash TERM=unknown SegvAnalysis: Segfault happened at: 0x7ffdb30fef8e :cmp %rax,(%rdx) PC (0x7ffdb30fef8e) ok source "%rax" ok destination "(%rdx)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gdebi StacktraceTop: gtk_label_set_text () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gdebi-gtk crashed with SIGSEGV in gtk_label_set_text() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1228383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
Hi Brian, thank you for providing this fix. It works fine on a minimal 18.10 server. I installed systemd 239-7ubuntu10.5 on a updated system. ** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot
This bug was fixed in the package netplan.io - 0.40.2.2 --- netplan.io (0.40.2.2) cosmic; urgency=medium * Fix idempotency in renaming: bond members should be exempt from rename, as they may all share a single MAC for the bond device. (LP: #1802322) * tests/integration.py: add test designed to catch the above regression. netplan.io (0.40.2.1) cosmic; urgency=medium * Fix typo breaking rename on 'netplan apply'. (LP: #1770082) -- Mathieu Trudel-Lapierre Wed, 21 Nov 2018 14:28:42 -0500 ** Changed in: netplan.io (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1770082 Title: systemd-networkd not renaming devices on boot Status in netplan: Fix Released Status in cloud-init package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in nplan source package in Xenial: Fix Released Status in netplan.io source package in Bionic: Fix Committed Status in netplan.io source package in Cosmic: Fix Released Bug description: [Impact] Systems relying on renaming network interfaces at boot and when 'netplan apply' is run. [Test case] - Write a new netplan YAML (adjusting for current system as necessary): network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:de:bd:f6 set-name: myif0 - Bring down interface : 'ip link set dev ens3 down' - Run 'netplan apply' - Verify that the device is correctly renamed to 'myif0'. - Reboot. - Make sure the device is correctly renamed to 'myif0'. [Regression potential] Changes in rename logic to add udev rules may otherwise impact applying different settings to the network interfaces. Changes in settings on network interfaces, missing parameters (especially on bonds, bridges) should be investigated as potential regressions. Other failures to apply network settings might also happen if there's a race between applying renames via the udev rules, and using the new names to apply configuration changes to the interfaces. === systemd issue === Renaming devices doesn't seem to work. If I disable all other network configuration and create /etc/systemd/network/10-network.link with: [Match] MACAddress=52:54:00:c1:c9:bb [Link] Name=myiface3 I expect this to cause the device with that MAC address to be renamed to myiface3. However, when I reboot, I instead see: $ ip l 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff The device is not renamed. This link file is pretty much identical to Example 2 in https://www.freedesktop.org/software/systemd/man/systemd.link.html. The renaming does work if I boot with net.ifnames=0, and oddly, it also works if I unbind the device and rebind it as netplan apply does. No setting of NamePolicy seems to help. === Original Bug == 'set-name:' doesn't change the name of a network interface on boot, it only works when you do netplan apply. Say I take this 50-cloud-init.yaml file: # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:de:bd:f6 set-name: ens3 Say I change set-name to 'myiface3' and reboot. I expect that the device will be called myiface3 and brought up fine with dhcp. However, instead I see: $ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff The name has not been changed, and the device has not been brought up. If I run netplan apply however, I see the following: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6
[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Yes, I can confirm that bluetooth works well, but I hope we can find a way to use internal sound, it's a good quality speaker for a small laptop :) -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled
@vtapia, did you also test if 'ping' and/or 'telnet' DNS resolution was fixed as well? i.e. currently: ubuntu@lp1804487:~$ ping testing.irongiantdesign.com ping: testing.irongiantdesign.com: Temporary failure in name resolution ubuntu@lp1804487:~$ telnet testing.irongiantdesign.com telnet: could not resolve testing.irongiantdesign.com/telnet: Temporary failure in name resolution ubuntu@lp1804487:~$ ssh testing.irongiantdesign.com ssh: Could not resolve hostname testing.irongiantdesign.com: Temporary failure in name resolution ubuntu@lp1804487:~$ host testing.irongiantdesign.com testing.irongiantdesign.com has address 253.0.0.23 testing.irongiantdesign.com has address 253.0.0.6 testing.irongiantdesign.com has address 253.0.0.28 testing.irongiantdesign.com has address 253.0.0.25 testing.irongiantdesign.com has address 253.0.0.22 testing.irongiantdesign.com has address 253.0.0.5 testing.irongiantdesign.com has address 253.0.0.10 testing.irongiantdesign.com has address 253.0.0.4 testing.irongiantdesign.com has address 253.0.0.16 testing.irongiantdesign.com has address 253.0.0.2 testing.irongiantdesign.com has address 253.0.0.7 testing.irongiantdesign.com has address 253.0.0.26 testing.irongiantdesign.com has address 173.236.154.252 testing.irongiantdesign.com has address 253.0.0.21 testing.irongiantdesign.com has address 253.0.0.27 testing.irongiantdesign.com has address 253.0.0.13 testing.irongiantdesign.com has address 253.0.0.3 testing.irongiantdesign.com has address 253.0.0.1 testing.irongiantdesign.com has address 253.0.0.24 testing.irongiantdesign.com has address 253.0.0.12 testing.irongiantdesign.com has address 253.0.0.9 testing.irongiantdesign.com has address 253.0.0.20 testing.irongiantdesign.com has address 253.0.0.8 testing.irongiantdesign.com has address 253.0.0.15 testing.irongiantdesign.com has address 253.0.0.19 testing.irongiantdesign.com has address 253.0.0.17 testing.irongiantdesign.com has address 253.0.0.18 testing.irongiantdesign.com has address 253.0.0.14 testing.irongiantdesign.com has address 253.0.0.11 That doesn't appear fixed with the latest systemd...? ubuntu@lp1804487:~$ dpkg -l |grep 'ii systemd ' ii systemd239-7ubuntu10.5 amd64 system and service manager ubuntu@lp1804487:~$ ping testing.irongiantdesign.com ping: testing.irongiantdesign.com: Temporary failure in name resolution ubuntu@lp1804487:~$ telnet testing.irongiantdesign.com telnet: could not resolve testing.irongiantdesign.com/telnet: Temporary failure in name resolution ubuntu@lp1804487:~$ ssh testing.irongiantdesign.com ssh: Could not resolve hostname testing.irongiantdesign.com: Temporary failure in name resolution -- 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/1804487 Title: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd package in Debian: Fix Released Bug description: [Impact] TCP stub is cutting down the payload to 512 bytes when EDNS is disabled. This makes non-EDNS clients (nslookup) receive a "shortened" answer even when UDP returns a truncated reply for a new TCP query. For instance, - If the client supports EDNS: $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 - If the client does not support EDNS: $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 29 In the second case, no-EDNS, TCP should provide the complete answer, but it's capped at UDP's size. [Test Case] Query systemd-resolved with a domain name that resolves to multiple (lots.. 30+) A records. A client with EDNS support (dig) will receive all of them, a client without support (nslookup or dig +noedns) will have a truncated list. Using the example above: EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l [Regression potential] Minimal. This change only affects TCP requests, and the new size is already used in the code for other requests. [Other Info] Upstream bug: https://github.com/systemd/systemd/issues/10816 Fixed upstream with commit: https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce [Original Description] Querying a domain name that has >512 bytes in records (e.g. 30+ A records), the number of results depends on the DNS client used: - If the client supports EDNS: $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -
[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
The only workaround that I have found till now is using a bluetooth headset. It works perfectly well. -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780319] Re: openssl des3 decryption fails in 18.04
I also get the same error when I run the following command to decrypt the file. openssl aes-256-cbc -d -in secretfile.txt.enc -out secretfile.txt -pass file:secret.key -- 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/1780319 Title: openssl des3 decryption fails in 18.04 Status in openssl package in Ubuntu: Won't Fix Bug description: Since I upgraded to Ubuntu 18.04 I get ~$ openssl des3 -d /tmp/loesenord.htm enter des-ede3-cbc decryption password: bad decrypt 140555004862912:error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt:../crypto/evp/evp_enc.c:536: The encryption was done with Ubuntu 17.10. And the decryption worked well in 17.10. Encryption/decryption in Ubuntu 18.04 works well. ~$ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 ~$ apt-cache policy openssl openssl: Installed: 1.1.0g-2ubuntu4.1 Candidate: 1.1.0g-2ubuntu4.1 Version table: *** 1.1.0g-2ubuntu4.1 500 500 http://se.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.1.0g-2ubuntu4 500 500 http://se.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1780319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806399] Re: package python3-minimal 3.6.7-1~18.04 failed to install/upgrade: installed python3-minimal package post-installation script subprocess returned error exit status 127
>From the attached DpkgHistoryLog.txt I can infer that the problem started after removing python3. I'd try something like what was posted there: https://askubuntu.com/questions/914556/python-3-not-working cd /tmp apt-get download python3 python3.6 python3-minimal python3.6-minimal libpython3.6-minimal sudo dpkg -i *python3*.deb sudo apt install -f -- 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/1806399 Title: package python3-minimal 3.6.7-1~18.04 failed to install/upgrade: installed python3-minimal package post-installation script subprocess returned error exit status 127 Status in python3-defaults package in Ubuntu: New Bug description: lkjhgfdsazASDERTYUIOP'/;.LKJHGFDSZ ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-minimal 3.6.7-1~18.04 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: python3-minimal:amd64: Configure python3:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Dec 3 23:48:46 2018 DpkgTerminalLog: Setting up python3-minimal (3.6.7-1~18.04) ... /var/lib/dpkg/info/python3-minimal.postinst: 5: /var/lib/dpkg/info/python3-minimal.postinst: py3compile: not found dpkg: error processing package python3-minimal (--configure): installed python3-minimal package post-installation script subprocess returned error exit status 127 DuplicateSignature: package:python3-minimal:3.6.7-1~18.04 Setting up python3-minimal (3.6.7-1~18.04) ... /var/lib/dpkg/info/python3-minimal.postinst: 5: /var/lib/dpkg/info/python3-minimal.postinst: py3compile: not found dpkg: error processing package python3-minimal (--configure): installed python3-minimal package post-installation script subprocess returned error exit status 127 ErrorMessage: installed python3-minimal package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2018-01-05 (332 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.6m, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: python3-defaults Title: package python3-minimal 3.6.7-1~18.04 failed to install/upgrade: installed python3-minimal package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2018-09-27 (67 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1806399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806750] Re: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato
Solved! Thank you very much -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1806750 Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato Status in glib2.0 package in Ubuntu: New Bug description: I don't know the shown error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: linux-libc-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Dec 4 19:27:27 2018 ErrorMessage: problemi con le dipendenze - lasciato non configurato InstallationDate: Installed on 2018-11-10 (24 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: glib2.0 Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1806750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806687] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 23
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1806687 Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 23 Status in ca-certificates package in Ubuntu: New Bug description: Occurred during upgrade to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Tue Dec 4 08:07:58 2018 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 23 InstallationDate: Installed on 2016-04-11 (966 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 23 UpgradeStatus: Upgraded to bionic on 2018-12-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1806687/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled
Cosmic verifing # Before the fix ii systemd 239-7ubuntu10 amd64 system and service manager #EDNS query $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 #No EDNS query falling back to TCP $ dig +noall +answer +noedns testing.irongiantdesign.com @127.0.0.53 | wc -l 29 #No EDNS query ignoring the truncate flag (stick to UDP only) $ dig +noall +answer +noedns +ignore testing.irongiantdesign.com @127.0.0.53 | wc -l 29 - With the fix: systemd 239-7ubuntu10.5 #EDNS query $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 #No EDNS query falling back to TCP $ dig +noall +answer +noedns testing.irongiantdesign.com @127.0.0.53 | wc -l 30 #No EDNS query ignoring the truncate flag (stick to UDP only) $ dig +noall +answer +noedns +ignore testing.irongiantdesign.com @127.0.0.53 | wc -l 29 ** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1804487 Title: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd package in Debian: Fix Released Bug description: [Impact] TCP stub is cutting down the payload to 512 bytes when EDNS is disabled. This makes non-EDNS clients (nslookup) receive a "shortened" answer even when UDP returns a truncated reply for a new TCP query. For instance, - If the client supports EDNS: $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 - If the client does not support EDNS: $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 29 In the second case, no-EDNS, TCP should provide the complete answer, but it's capped at UDP's size. [Test Case] Query systemd-resolved with a domain name that resolves to multiple (lots.. 30+) A records. A client with EDNS support (dig) will receive all of them, a client without support (nslookup or dig +noedns) will have a truncated list. Using the example above: EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l [Regression potential] Minimal. This change only affects TCP requests, and the new size is already used in the code for other requests. [Other Info] Upstream bug: https://github.com/systemd/systemd/issues/10816 Fixed upstream with commit: https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce [Original Description] Querying a domain name that has >512 bytes in records (e.g. 30+ A records), the number of results depends on the DNS client used: - If the client supports EDNS: $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 - If the client does not support EDNS: $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 29 Normally a client that doesn't support EDNS would receive a truncated reply from the initial UDP connection (limited by the spec to 512 bytes) and a second query would be established via TCP to receive the complete results. In this case, the number of results is the same regardless of the protocol used (29). Upstream bug: https://github.com/systemd/systemd/issues/10816 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1804487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806727] Re: KDE: Eqonomize doesn't appear in the K-Menu
** Package changed: xorg (Ubuntu) => eqonomize (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/1806727 Title: KDE: Eqonomize doesn't appear in the K-Menu Status in eqonomize package in Ubuntu: New Bug description: This fixes it: sudo mv /usr/share/mimelnk/application/x-eqonomize.desktop /usr/share/applications ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Tue Dec 4 17:46:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Cedar [Radeon HD 5000/6000/7350/8350 Series] [1043:0471] InstallationDate: Installed on 2018-10-05 (60 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd11/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78LLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 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/+source/eqonomize/+bug/1806727/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
** Also affects: landscape-client (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: landscape-client (Ubuntu Trusty) Status: New => In Progress ** Changed in: landscape-client (Ubuntu Trusty) Importance: Undecided => High ** Changed in: landscape-client (Ubuntu Trusty) Assignee: (unassigned) => Simon Poirier (simpoir) -- 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Trusty: In Progress Status in systemd source package in Trusty: New Status in landscape-client source package in Xenial: In Progress Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: In Progress Status in systemd source package in Bionic: Fix Committed Status in landscape-client source package in Cosmic: In Progress Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806750] Re: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato
Some users at the Linux Mint forums have that problem because of HP Printer drivers downloaded directly from HP. (https://forums.linuxmint.com/viewtopic.php?f=18&t=273104&start=40) Please open the terminal and run this command: sudo rm /usr/share/python3/runtime.d/hplip-data.rtupdate Then try the update again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1806750 Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato Status in glib2.0 package in Ubuntu: New Bug description: I don't know the shown error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: linux-libc-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Dec 4 19:27:27 2018 ErrorMessage: problemi con le dipendenze - lasciato non configurato InstallationDate: Installed on 2018-11-10 (24 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: glib2.0 Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1806750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 33394] Re: Installing syslog-ng shouldn't remove ubuntu-minimal
This has been fixed (due to the change to journald). ** Changed in: ubuntu-meta (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-meta in Ubuntu. https://bugs.launchpad.net/bugs/33394 Title: Installing syslog-ng shouldn't remove ubuntu-minimal Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: The current deps make installing syslog-ng remove ubuntu-minimal. If ubuntu-minimal were to depend on: sysklogd | system-log-daemon then one could install syslog-ng without removing ubuntu-minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/33394/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
** Changed in: landscape-client (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: landscape-client (Ubuntu Xenial) Assignee: (unassigned) => Simon Poirier (simpoir) -- 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: In Progress Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: In Progress Status in systemd source package in Bionic: Fix Committed Status in landscape-client source package in Cosmic: In Progress Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1802653] Re: [HDA-Intel - HDA ATI HDMI, playback] No sound at all
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1802653 Title: [HDA-Intel - HDA ATI HDMI, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: v ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: betab 2401 F pulseaudio /dev/snd/pcmC1D1p: betab 2401 F...m pulseaudio /dev/snd/controlC0: betab 2401 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Nov 10 14:46:54 2018 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: betab 2401 F pulseaudio /dev/snd/pcmC1D1p: betab 2401 F...m pulseaudio /dev/snd/controlC0: betab 2401 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA ATI HDMI, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: Default string dmi.board.name: A320M-DS2-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: 7438518-007 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd12/05/2017:svnNOVATECHLTD:pnBB-95004:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-DS2-CF:rvrx.x:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: BB-95004 dmi.product.sku: BB-95004 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1802653/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
** Merge proposal linked: https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358165 -- 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: In Progress Status in systemd source package in Bionic: Fix Committed Status in landscape-client source package in Cosmic: In Progress Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806750] [NEW] package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato
Public bug reported: I don't know the shown error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: linux-libc-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Dec 4 19:27:27 2018 ErrorMessage: problemi con le dipendenze - lasciato non configurato InstallationDate: Installed on 2018-11-10 (24 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: glib2.0 Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1806750 Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato Status in glib2.0 package in Ubuntu: New Bug description: I don't know the shown error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: linux-libc-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Dec 4 19:27:27 2018 ErrorMessage: problemi con le dipendenze - lasciato non configurato InstallationDate: Installed on 2018-11-10 (24 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: glib2.0 Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1806750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
** Changed in: landscape-client (Ubuntu Cosmic) Status: Fix Committed => In Progress ** Changed in: landscape-client (Ubuntu Cosmic) Assignee: Dave Jones (waveform) => Simon Poirier (simpoir) -- 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: In Progress Status in systemd source package in Bionic: Fix Committed Status in landscape-client source package in Cosmic: In Progress Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803487] Re: gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → gweather_location_format_two_deserialize → gweather_location_deserialize → ffi_call_unix64
Hello errors.ubuntu.com, or anyone else affected, Accepted libgweather into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libgweather/3.28.2-1~ubuntu18.04.1 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. ** Changed in: libgweather (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1803487 Title: gnome-shell crashes with SIGSEGV in gweather_location_common_deserialize → gweather_location_format_two_deserialize → gweather_location_deserialize → ffi_call_unix64 → ffi_call Status in gnome-shell package in Ubuntu: Fix Released Status in libgweather package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in libgweather source package in Bionic: Fix Committed Bug description: [ Description ] The second stable release in the 3.28 series. [ QA ] Run Ubuntu session, expect the shell to show weather information and not to crash on timezone changes https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Weather location might be leaked. However this is very safe as upstream fix comes with proper testing. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.3-0ubuntu0.18.04.3, the problem page at https://errors.ubuntu.com/problem/4ff1b7671a7dc53f26da1c0f78af65d0cc5168fa contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784347] Re: ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting partitions name for the mpath
** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1784347 Title: ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting partitions name for the mpath Status in The Ubuntu-power-systems project: Fix Committed Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Bionic: Incomplete Bug description: [Impact] Any user of Ubuntu on multipath, where the default path separator has been changed to something else. This possibly affects other scenarios where the partition separator can be changed. [Test case] 1) Install Ubuntu on multipath system 2) Change /etc/multipath.conf to set "path_separator" to "" or "p". 3) Reboot 4) Run 'sudo fdisk -l /dev/mapper/mpathX', to display a device's partitions where the path separator would be visible. [Regression potential] Minimal. This only affects display. Default separator on Ubuntu remains "-part". If the separator is not one of "", "p", or "-part", then "-part" would be used, as is already the case. == Comment: #0 - Chanh H. Nguyen - 2018-01-09 11:14:07 == We have the Ubuntu1804 installed on our BostonLC system. Create a SAN via the Emulex adapter to have the mpath disk. Running the fdisk -l and ls -l showing the conflict name for the mpath. :~# uname -a Linux boslcp4 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@boslcp4:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Bionic Beaver (development branch)" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic :~# fdisk -l /dev/mapper/mpatha Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 32768 bytes / 32768 bytes Disklabel type: dos Disk identifier: 0xa5be904b Device Boot StartEnd Sectors Size Id Type /dev/mapper/mpatha-part1 2048 419432447 419430400 200G 83 Linux /dev/mapper/mpatha-part2 419432448 838862847 419430400 200G 83 Linux /dev/mapper/mpatha-part3 838862848 1258291199 419428352 200G 83 Linux :~# ls -l /dev/mapper/mpatha* lrwxrwxrwx 1 root root 7 Jan 9 04:04 /dev/mapper/mpatha -> ../dm-0 lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha1 -> ../dm-1 lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha2 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha3 -> ../dm-3 == Comment: #2 - Chanh H. Nguyen - 2018-01-09 11:35:04 == I just modify the partitions and it is still showing the conflicting name on partitions. :~# ls -l /dev/mapper/mpatha* lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha -> ../dm-0 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha1 -> ../dm-1 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha2 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha3 -> ../dm-3 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha4 -> ../dm-4 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha5 -> ../dm-5 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha6 -> ../dm-6 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha7 -> ../dm-7 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha8 -> ../dm-8 :~# fdisk -l /dev/mapper/mpatha Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 32768 bytes / 32768 bytes Disklabel type: dos Disk identifier: 0xa5be904b Device Boot StartEnd Sectors Size Id Type /dev/mapper/mpatha-part12048 419432447 419430400 200G 83 Linux /dev/mapper/mpatha-part2 419432448 838862847 419430400 200G 83 Linux /dev/mapper/mpatha-part3 838862848 964691967 125829120 60G 83 Linux /dev/mapper/mpatha-part4 964691968 1258291199 293599232 140G 5 Extended /dev/mapper/mpatha-part5 964694016 1006637055 41943040 20G 83 Linux /dev/mapper/mpatha-part6 1006639104 1048582143 41943040 20G 83 Linux /dev/mapper/mpatha-part7 1048584192 1090527231 41943040 20G 83 Linux /dev/mapper/mpatha-part8 1090529280 1132472319 41943040 20G 83 Linux == Comment: #5 - Kyle Mahlkuch - 2018-06-26 13:50:
[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
Thank you very much, Dimitri -- I am interested in this also. I tested that PPA on a test web server running nginx, uwsgi, uwsgi- plugin-python3, Django 1.11(.16), and a Python 3.6 'pyvenv' virtual environment using 'psycopg2' to connect to a PostgreSQL 10 server via the pre-built Python wheel for 'psycopg2_binary' version 2.7.5. I could immediately connect to nginx over TLS 1.3 without any problems, and the Qualys SSL Labs scan also reported that all was well with TLS 1.3. However, the web app under uwsgi crashed (segfaulted) on any request, with a stack trace at https://pastebin.com/DLGiuKfR I was relatively surprised that the 'psycopg2_binary' Python wheel seemed to bundle its own version of libssl-8bb9b3dd.so.1.0.2o -- and it looks like there's some incompatibility with this build of Python and OpenSSL 1.1.1. I removed this Python package and installed 'psycopg2' instead, and saw the same behavior. I was able to fix this by reinstalling psycopg2 from source with 'pip install --no-binary=":all:" psycopg2', and now everything works well with the web app. I'm not sure how much of a problem this is at this stage, or who has the responsibility to address it (Ubuntu developers or whoever built the psycopg2 wheel), but I figured I may as well mention this anyway. It's great that everything was fine with nginx without any effort on my part; thanks! -- 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: 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 [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 [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 security updates * TLS v1.3 support in GnuTLS is expected to be available in 19.04 * Test OpenSSL is being prepared in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU
This was done inside a VM. This was all done in a single /etc/systemd/network/10-netplan-ens3.network file. Note that [Link] is a valid section in a .network file. Note that i took netplan generated .network file as a base, and then modified it with above shown options. Disabled netplan. Rebooted. I'm not quite sure how you can reproduce this inside a lxd container, since it's not using a physical link, but a .netdev devices. I expect that specifying similar things in .network should work, but it might not. That is because a veth pair is precreated outside of the container, and one may need to adjust the host-side of the veth pair which is a priviledged operation. Note that e.g. one can set MTU on virtual devices created using .netdev units. -- 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/1671951 Title: networkd should allow configuring IPV6 MTU Status in cloud-init package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Status in cloud-init source package in Bionic: Confirmed Status in netplan.io source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Bug description: = systemd = [Impact] * IPv6 traffic failing to send/receive due to incompatible/low MTU setting. Specifically, IPv6 traffic may have higher MTU requirements than IPv4 traffic and thus may need to be overridden and/or set to a higher value than IPv6 traffic. [Test Case] * Use IPv6MTUBytes= setting in a .network unit * Restart systemd-network * Check that there no error messages / warnings about not-recognizing this option * Check that MTU bytes, is at least IPv6MTUBytes on the interface [Regression Potential] * This is a future compatible backport of an additional keyword not used by default. It may result in MTU change to a higher value, which should not cause loss of connectivity. [Other Info] * Original bug report below = end of systemd = 1) Zesty 2) systemd-232-19 3) I need to configure the IPV6 MTU for tunneling by adding an IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 static address in the [Network] section 4) networkd does not parse or read the value and does not apply this configuration to the interface. Upstream has discussed this issue here: https://github.com/systemd/systemd/pull/1533 But it's been closed in favor of only setting via RA. However, we know of multiple use-case which are currently supported in ifdupdown where we want to retain control over IPV6 MTU values outside of PMTU Discovery configurations. Some context from those discussions >> Client systems that route their ipv6 packets to a 6in4 router also >> have to have their ipv6 mtu lowered. They could lower their link mtu, >> so their ipv6 packets are small enough, but that reduces performance >> of their ipv4 network. Yes. Anything that creates a PMTUD black hole can result in situations where the higher header overhead of IPv6 will cause IPv4 to pass but IPv6 traffic to be dropped. One example here is egress from an ipsec tunnel wherein the next hop MTU is too low for IPv6 datagrams to pass. Another is VM -> whatever -> host bridge -> tunnel ingress. If the datagram cannot enter the tunnel due to size, it is dropped, and an ICMP response uses the tunnel address as a source, which may not be routable back to the origin. This one is an issue with IPv4 as well, and is one case where manually setting the IPv6 MTU lower than the (also manually set) device MTU is of benefit. In essence, any of these sort of cases that require an explicit setting of the device MTU will likely require a setting of the IPv6 mtu as well to account for its larger header overhead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 963946] Re: ubuntu-desktop unnecessarily hard depends on xterm while it already depends on gnome-terminal
We fixed this in 18.04 :) ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Fix Released -- 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/963946 Title: ubuntu-desktop unnecessarily hard depends on xterm while it already depends on gnome-terminal Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: As as per the summery, the ubuntu-desktop meta package unnecessarily hard depends on xterm, while it already depends on gnome-terminal. Given that gnome-terminal is clearly much more capable and provides terminal emulation, adding a second terminal emulator is unnecessary and might cause confusion. This bug affects oneiric and precise. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubuntu-desktop 1.265 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Sat Mar 24 14:29:25 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301) ProcEnviron: LANGUAGE=en_IE:en LANG=en_IE.UTF-8 SHELL=/bin/bash 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/963946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU
On Tue, Dec 4, 2018 at 9:31 AM Ryan Harper wrote: > > > On Tue, Dec 4, 2018 at 6:31 AM Dimitri John Ledkov > wrote: > >> Using systemd 237-3ubuntu10.10 >> >> Using: >> [Match] >> Name=ens3 >> [Network] >> DHCP=ipv4 >> IPv6MTUBytes=1600 >> [Link] >> MTUBytes=1800 >> [DHCP] >> UseMTU=no >> RouteMetric=100 >> > > Do you put this in the same .network file or .link file? > FWIW, I'm not able to make this work inside a LXD container. Could you provide more details on how you validated and in what environment? -- 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/1671951 Title: networkd should allow configuring IPV6 MTU Status in cloud-init package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Status in cloud-init source package in Bionic: Confirmed Status in netplan.io source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Bug description: = systemd = [Impact] * IPv6 traffic failing to send/receive due to incompatible/low MTU setting. Specifically, IPv6 traffic may have higher MTU requirements than IPv4 traffic and thus may need to be overridden and/or set to a higher value than IPv6 traffic. [Test Case] * Use IPv6MTUBytes= setting in a .network unit * Restart systemd-network * Check that there no error messages / warnings about not-recognizing this option * Check that MTU bytes, is at least IPv6MTUBytes on the interface [Regression Potential] * This is a future compatible backport of an additional keyword not used by default. It may result in MTU change to a higher value, which should not cause loss of connectivity. [Other Info] * Original bug report below = end of systemd = 1) Zesty 2) systemd-232-19 3) I need to configure the IPV6 MTU for tunneling by adding an IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 static address in the [Network] section 4) networkd does not parse or read the value and does not apply this configuration to the interface. Upstream has discussed this issue here: https://github.com/systemd/systemd/pull/1533 But it's been closed in favor of only setting via RA. However, we know of multiple use-case which are currently supported in ifdupdown where we want to retain control over IPV6 MTU values outside of PMTU Discovery configurations. Some context from those discussions >> Client systems that route their ipv6 packets to a 6in4 router also >> have to have their ipv6 mtu lowered. They could lower their link mtu, >> so their ipv6 packets are small enough, but that reduces performance >> of their ipv4 network. Yes. Anything that creates a PMTUD black hole can result in situations where the higher header overhead of IPv6 will cause IPv4 to pass but IPv6 traffic to be dropped. One example here is egress from an ipsec tunnel wherein the next hop MTU is too low for IPv6 datagrams to pass. Another is VM -> whatever -> host bridge -> tunnel ingress. If the datagram cannot enter the tunnel due to size, it is dropped, and an ICMP response uses the tunnel address as a source, which may not be routable back to the origin. This one is an issue with IPv4 as well, and is one case where manually setting the IPv6 MTU lower than the (also manually set) device MTU is of benefit. In essence, any of these sort of cases that require an explicit setting of the device MTU will likely require a setting of the IPv6 mtu as well to account for its larger header overhead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 40189] Re: [SRU] [xenial] [bionic] autofs needs to be restarted to pick up some shares
The issue seems to have returned with an update in 16.04 in mid- november. I will continue to peruse the above solutions and see if there's anything I have not tried yet but so far no joy. OpenLDAP + autofs still requires a restart of autofs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/40189 Title: [SRU] [xenial] [bionic] autofs needs to be restarted to pick up some shares Status in autofs package in Ubuntu: Fix Released Status in autofs5 package in Ubuntu: Invalid Status in upstart package in Ubuntu: Invalid Status in autofs source package in Xenial: Incomplete Bug description: I am using autofs to access shares on a Windows XP machine from a Kubuntu AMD64 machine. The problems applies in both Breezy and Dapper. EDIT: confirmed with similar configuration on Intrepid with a NetApp filer hosting NFS. Server OS removed from summary. When I first try to access the mount point via cd or in Konqueror it does not exist. However, if I then restart autofs (/etc/init.d/autofs restart) everythin then works OK. My config files are: auto.master # # $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $ # # Sample auto.master file # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # For details of the format look at autofs(5). #/misc/etc/auto.misc --timeout=60 #/misc/etc/auto.misc #/net /etc/auto.net /petunia /etc/petunia.misc --timeout=60 petunia.misc # # $Id: auto.misc,v 1.2 2003/09/29 08:22:35 raven Exp $ # # This is an automounter map and it has the following format # key [ -mount-options-separated-by-comma ] location # Details may be found in the autofs(5) manpage cd -fstype=iso9660,ro,nosuid,nodev :/dev/cdrom tony -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/tony chris -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/chris shared-fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/SharedDocs linuxbackups -fstype=smbfs,defaults,password=xxx,fmask=777,dmask=777 ://192.168.1.2/linuxbackups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/40189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]
excellent, I'll prepare the sru for cosmic bionic will get 1.20.3 as part of 18.04.2 HWE stack ** Changed in: mesa (Ubuntu Bionic) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu Cosmic) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu Disco) Status: Confirmed => Invalid ** Changed in: xorg-server (Ubuntu Disco) Status: Incomplete => Fix Released ** Changed in: xorg-server (Ubuntu Cosmic) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1754693 Title: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps] Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Fix Released Status in mesa source package in Bionic: Invalid Status in xorg-server source package in Bionic: Confirmed Status in mesa source package in Cosmic: Invalid Status in xorg-server source package in Cosmic: Triaged Status in mesa source package in Disco: Invalid Status in xorg-server source package in Disco: Fix Released Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ve
[Touch-packages] [Bug 1799364] Re: The wlan/bt hotkey doesn't work for all Dell Latitude and Precision computers
Hello Shih-Yuan, or anyone else affected, Accepted systemd into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.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-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: systemd (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- 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/1799364 Title: The wlan/bt hotkey doesn't work for all Dell Latitude and Precision computers Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Released Bug description: [Impact] * All Dell Latitude and Precision computer users can not use the wlan/bt hotkey. [Test Case] * Use any Dell Latitude and Precision computer to check the wlan/bt hotkey. * If you don't have the computer above, you can use the following command to check, and the expected output is "KEYBOARD_KEY_88=!wlan" instead of "KEYBOARD_KEY_88=!". `systemd-hwdb query evdev:atkbd:dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: | grep KEYBOARD_KEY_88` [Regression Potential] * No regression [Other Info] * None Just install the official Ubuntu 18.10 on any Dell Latitude or Precision computer and press wlan/bt hotkey on the keyboard. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 15:37:41 2018 InstallationDate: Installed on 2018-10-23 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:5520 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=be88d6f2-7d21-4a3c-b384-0c5356fb9220 ro quiet splash vt.handoff=1 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. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.0.24 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3300 dmi.product.sku: 08BB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1799364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled
Hello Victor, or anyone else affected, Accepted systemd into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.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-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: systemd (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- 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/1804487 Title: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd package in Debian: Fix Released Bug description: [Impact] TCP stub is cutting down the payload to 512 bytes when EDNS is disabled. This makes non-EDNS clients (nslookup) receive a "shortened" answer even when UDP returns a truncated reply for a new TCP query. For instance, - If the client supports EDNS: $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 - If the client does not support EDNS: $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 29 In the second case, no-EDNS, TCP should provide the complete answer, but it's capped at UDP's size. [Test Case] Query systemd-resolved with a domain name that resolves to multiple (lots.. 30+) A records. A client with EDNS support (dig) will receive all of them, a client without support (nslookup or dig +noedns) will have a truncated list. Using the example above: EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l [Regression potential] Minimal. This change only affects TCP requests, and the new size is already used in the code for other requests. [Other Info] Upstream bug: https://github.com/systemd/systemd/issues/10816 Fixed upstream with commit: https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce [Original Description] Querying a domain name that has >512 bytes in records (e.g. 30+ A records), the number of results depends on the DNS client used: - If the client supports EDNS: $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 - If the client does not support EDNS: $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 29 Normally a client that doesn't support EDNS would receive a truncated reply from the initial UDP connection (limited by the spec to 512 bytes) and a second query would be established via TCP to receive the complete results. In this case, the number of results is the same regardless of the protocol used (29). Upstream bug: https://github.com/systemd/systemd/issues/10816 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1804487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799251] Re: mount options for /run should be the same as initramfs tools
Hello Dimitri, or anyone else affected, Accepted systemd into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.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-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: systemd (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- 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/1799251 Title: mount options for /run should be the same as initramfs tools Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: Fix Committed Bug description: mount options for /run should be the same as initramfs tools [Impact] * /run is mounted with different options on initrd boots, and initrd- less boots. For consistency it should be the same * In particular, this causes overuse of RAM on hosts with dense deployment of containers. Specifically, runtime journald takes up at most 10% or /run, which is capped at 10% of ram, thus 1% of total RAM. However, on initrd-less boots (like lxd launch ubuntu-daily:foo), /run takes up all of RAM, and thus run-time journal is now capped at 10% of RAM. Which is really bad when one deploys more than 10 containers... [Test Case] * Check total RAM on the host with `free -h` * lxd launch ubuntu-daily:release * In that container check the size of /run with `df -h | grep '/run$'` * /run should roughly be 1/10th of the total RAM. [Regression Potential] * /run is meant to be small, and it is small on systems booted with initrd and everything works fine there. Reducing the default size of /run in the containers should not have averse impacts. The most notable change is that runtime journald is now capped 10x smaller in the containers, to the same size as on the hosts. If that is not enough, one should $ sudo mkdir /var/log/journal to have a larger persistent journal. [Other Info] * This issue got escalated as affecting production deployments in the Canonical datacentre. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804584] Re: LG screen reported as being a Goldstar one
Hello Sebastien, or anyone else affected, Accepted systemd into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.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-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: systemd (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- 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/1804584 Title: LG screen reported as being a Goldstar one Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Released Bug description: * Impact The GNOME configuration interface labels LG screens as being from Goldstar, that's because the hwdb has an outdate record for the brand and still its old name, that has been fixed upstream now with https://github.com/systemd/systemd/commit/c6d7a5e9 * Test case - connect to a LG screen - log into an Ubuntu/GNOME session - open gnome-control-center display section -> the screen should be described as from LG and not from Goldstar * Regression potential It's just a name change in the hwdb data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804584/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
Hello Rene, or anyone else affected, Accepted systemd into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.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-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: systemd (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- 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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805358] Re: autopkgtest boot-and-services fails on many architectures very often since systemd/239-7ubuntu12
Hello Christian, or anyone else affected, Accepted systemd into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.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-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: systemd (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- 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/1805358 Title: autopkgtest boot-and-services fails on many architectures very often since systemd/239-7ubuntu12 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * Boot and services autopkgtest case has become flakey, especially on ppc64el but other architectures too. [Test Case] * Check that boot-and-services passes more reliably [Regression Potential] * this is a test change only [Other Info] * gdm3 used to start reliably, in nested qemu, with dummy xorg, but it doesn't anymore. Thus stop testing gdm3 coming up as part of the systemd autopkgtest. Mostly, because in realisty it's not that interesting to see if gdm3 works with dummy xorg, as we mostly care about gdm3 working on bare-metal with proper graphics cards intel/amd/nvidia/etc. I appreciate that some old known issues on 'upstream' are fixed. But looking at the current tests I see that often on amd64 (2/3 and very often on ppc64le (4/4 since ubuntu12 and 11/11 before that version). Looking at the list of people hitting retry and the list of packages blocked that seems an issue that must be checked. See current head of tests at: amd64: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/amd64 ppc64el: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/ppc64el One example log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/s/systemd/20181126_074048_cb8d2@/log.gz Example of the error that one can see in the log: test_no_failed (__main__.ServicesTest) No failed units ... journal for failed service user@118.service --- -- Logs begin at Tue 2018-10-30 09:54:39 UTC, end at Mon 2018-11-26 07:05:17 UTC. -- Nov 26 07:05:09 autopkgtest systemd[1]: Starting User Manager for UID 118... Nov 26 07:05:10 autopkgtest systemd[1292]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0) Nov 26 07:05:10 autopkgtest systemd[1292]: Failed to fully start up daemon: Permission denied Nov 26 07:05:10 autopkgtest systemd[1]: user@118.service: Failed with result 'protocol'. Nov 26 07:05:10 autopkgtest systemd[1]: Failed to start User Manager for UID 118. FAIL == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.Xm5RBa/build.JSa/src/debian/tests/boot-and-services", line 62, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['user@118.service loaded failed failed User Manager for UID 118'] != [] First list contains 1 additional elements. First extra element 0: 'user@118.service loaded failed failed User Manager for UID 118' - ['user@118.service loaded failed failed User Manager for UID 118'] + [] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804864] Re: autopkgtest regression TEST-22-TMPFILES are not executable
Hello Dimitri, or anyone else affected, Accepted systemd into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu10.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-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: systemd (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- 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/1804864 Title: autopkgtest regression TEST-22-TMPFILES are not executable Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * Newly added testcase in a security upload used a traditional GNU patch format, instead of using extended git patch format, as supported by GNU patch. Therefore, executable bits on shells scripts were lost, resulting in autopkgtest failures. [Test Case] * `upstream` test/TEST-22-TMPFILES autopkgtest case should pass. [Regression Potential] * This is testcode change only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784347] Re: ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting partitions name for the mpath
Please help to validate this SRU. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1784347 Title: ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting partitions name for the mpath Status in The Ubuntu-power-systems project: Fix Committed Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Bionic: Incomplete Bug description: [Impact] Any user of Ubuntu on multipath, where the default path separator has been changed to something else. This possibly affects other scenarios where the partition separator can be changed. [Test case] 1) Install Ubuntu on multipath system 2) Change /etc/multipath.conf to set "path_separator" to "" or "p". 3) Reboot 4) Run 'sudo fdisk -l /dev/mapper/mpathX', to display a device's partitions where the path separator would be visible. [Regression potential] Minimal. This only affects display. Default separator on Ubuntu remains "-part". If the separator is not one of "", "p", or "-part", then "-part" would be used, as is already the case. == Comment: #0 - Chanh H. Nguyen - 2018-01-09 11:14:07 == We have the Ubuntu1804 installed on our BostonLC system. Create a SAN via the Emulex adapter to have the mpath disk. Running the fdisk -l and ls -l showing the conflict name for the mpath. :~# uname -a Linux boslcp4 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@boslcp4:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Bionic Beaver (development branch)" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic :~# fdisk -l /dev/mapper/mpatha Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 32768 bytes / 32768 bytes Disklabel type: dos Disk identifier: 0xa5be904b Device Boot StartEnd Sectors Size Id Type /dev/mapper/mpatha-part1 2048 419432447 419430400 200G 83 Linux /dev/mapper/mpatha-part2 419432448 838862847 419430400 200G 83 Linux /dev/mapper/mpatha-part3 838862848 1258291199 419428352 200G 83 Linux :~# ls -l /dev/mapper/mpatha* lrwxrwxrwx 1 root root 7 Jan 9 04:04 /dev/mapper/mpatha -> ../dm-0 lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha1 -> ../dm-1 lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha2 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha3 -> ../dm-3 == Comment: #2 - Chanh H. Nguyen - 2018-01-09 11:35:04 == I just modify the partitions and it is still showing the conflicting name on partitions. :~# ls -l /dev/mapper/mpatha* lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha -> ../dm-0 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha1 -> ../dm-1 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha2 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha3 -> ../dm-3 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha4 -> ../dm-4 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha5 -> ../dm-5 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha6 -> ../dm-6 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha7 -> ../dm-7 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha8 -> ../dm-8 :~# fdisk -l /dev/mapper/mpatha Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 32768 bytes / 32768 bytes Disklabel type: dos Disk identifier: 0xa5be904b Device Boot StartEnd Sectors Size Id Type /dev/mapper/mpatha-part12048 419432447 419430400 200G 83 Linux /dev/mapper/mpatha-part2 419432448 838862847 419430400 200G 83 Linux /dev/mapper/mpatha-part3 838862848 964691967 125829120 60G 83 Linux /dev/mapper/mpatha-part4 964691968 1258291199 293599232 140G 5 Extended /dev/mapper/mpatha-part5 964694016 1006637055 41943040 20G 83 Linux /dev/mapper/mpatha-part6 1006639104 1048582143 41943040 20G 83 Linux /dev/mapper/mpatha-part7 1048584192 1090527231 41943040 20G 83 Linux /dev/mapper/mpatha-part8 1090529280 1132472319 41943040 20G 83 Linux == Comment: #5 - Kyle Mahlkuch - 2018-06-26 13:50:12 == I have created and submitted a patch that should help with this bug. I will
[Touch-packages] [Bug 1806727] [NEW] KDE: Eqonomize doesn't appear in the K-Menu
Public bug reported: This fixes it: sudo mv /usr/share/mimelnk/application/x-eqonomize.desktop /usr/share/applications ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Tue Dec 4 17:46:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Cedar [Radeon HD 5000/6000/7350/8350 Series] [1043:0471] InstallationDate: Installed on 2018-10-05 (60 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd11/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78LLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 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 kubuntu 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/1806727 Title: KDE: Eqonomize doesn't appear in the K-Menu Status in xorg package in Ubuntu: New Bug description: This fixes it: sudo mv /usr/share/mimelnk/application/x-eqonomize.desktop /usr/share/applications ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Tue Dec 4 17:46:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Cedar [Radeon HD 5000/6000/7350/8350 Series] [1043:0471] InstallationDate: Installed on 2018-10-05 (60 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd11/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78LLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A
[Touch-packages] [Bug 1806728] [NEW] shell config /etc/profile does not set $PATH
Public bug reported: lsb_release -rd Description:Ubuntu 16.04.5 LTS Release:16.04 apt-cache policy base-files base-files: Installed: 9.4ubuntu4.7 grep -e PATH -e environment /usr/share/base-files/profile | wc -l 0 expectation: /etc/profile should source /etc/environment to set the $PATH variable reality: /etc/profile does not set $PATH scenario: when chroot-ing from arch linux into ubuntu linux, and running 'source /etc/profile' then $PATH does not contain /bin:/sbin:/usr/sbin which are needed to run 'apt-get update && apt-get upgrade' ... otherwise 'apt-get update' fails with Unknown error executing apt-key and 'apt-get upgrade' fails with Processing triggers for cracklib-runtime (2.9.2-1ubuntu1) ... /var/lib/dpkg/info/cracklib-runtime.postinst: 7: /var/lib/dpkg/info/cracklib-runtime.postinst: update-cracklib: not found dpkg: error processing package cracklib-runtime (--unpack): subprocess installed post-installation script returned error exit status 127 only after 'source /etc/environment' all runs fine. /etc/environment vs /etc/profile: environment is for all programs, profile is only for shells. but shells also need the $PATH variable, so including environment in profile does make sense, at least to me. ** Affects: base-files (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1806728 Title: shell config /etc/profile does not set $PATH Status in base-files package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 apt-cache policy base-files base-files: Installed: 9.4ubuntu4.7 grep -e PATH -e environment /usr/share/base-files/profile | wc -l 0 expectation: /etc/profile should source /etc/environment to set the $PATH variable reality: /etc/profile does not set $PATH scenario: when chroot-ing from arch linux into ubuntu linux, and running 'source /etc/profile' then $PATH does not contain /bin:/sbin:/usr/sbin which are needed to run 'apt-get update && apt-get upgrade' ... otherwise 'apt-get update' fails with Unknown error executing apt-key and 'apt-get upgrade' fails with Processing triggers for cracklib-runtime (2.9.2-1ubuntu1) ... /var/lib/dpkg/info/cracklib-runtime.postinst: 7: /var/lib/dpkg/info/cracklib-runtime.postinst: update-cracklib: not found dpkg: error processing package cracklib-runtime (--unpack): subprocess installed post-installation script returned error exit status 127 only after 'source /etc/environment' all runs fine. /etc/environment vs /etc/profile: environment is for all programs, profile is only for shells. but shells also need the $PATH variable, so including environment in profile does make sense, at least to me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1806728/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806458] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1806458/+attachment/5218995/+files/ProcModules.txt -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled B
[Touch-packages] [Bug 1806463] Re: Unattended-Upgrade::InstallOnShutdown "true" not working
I just confirmed that InstallOnShutdown does work, it is triggered by PrepareForShutdown(), not the TERM signal: balint@yogi:~$ lxc launch ubuntu:cosmic cc-lp-1806463 Creating cc-lp-1806463 Starting cc-lp-1806463 rbalint@yogi:~$ lxc shell cc-lp-1806463 root@cc-lp-1806463:~# apt update ... root@cc-lp-1806463:~# apt install unattended-upgrades ... root@cc-lp-1806463:~# reboot ... # enable InstallOnShutdown: root@cc-lp-1806463:~# vi /etc/apt/apt.conf.d/50unattended-upgrades root@cc-lp-1806463:~# dbus-send --system --print-reply --dest=org.freedesktop.login1 /org/freedesktop/login1 "org.freedesktop.login1.Manager.Reboot" boolean:false method return time=1543938923.733435 sender=:1.2 -> destination=:1.14 serial=32 reply_serial=2 root@cc-lp-1806463:~# top ... PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 547 root 20 0 257324 86180 49460 S 1.0 0.5 0:02.81 unattended-upgr 567 root 20 0 258132 73168 36236 S 0.0 0.5 0:00.08 unattended-upgr 237 root 20 0 627388 30768 16548 S 0.0 0.2 0:00.34 snapd 233 root 20 0 125852 21016 12980 S 0.0 0.1 0:00.09 unattended-upgr 229 root 20 0 47400 17436 9696 S 0.0 0.1 0:00.09 networkd-dispat 578 root 20 0 18760 11192 2748 D 19.0 0.1 0:00.34 dpkg ... root@cc-lp-1806463:~# Session terminated, terminating shell...logout ...terminated. rbalint@yogi:~$ lxc shell cc-lp-1806463 mesg: ttyname failed: No such device root@cc-lp-1806463:~# cat /var/log/unattended-upgrades/unattended-upgrades unattended-upgrades-dpkg.log unattended-upgrades-shutdown.log unattended-upgrades.log root@cc-lp-1806463:~# cat /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2018-12-04 15:54:11,587 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running 2018-12-04 15:55:23,748 WARNING - Running unattended-upgrades in shutdown mode 2018-12-04 15:55:23,765 WARNING - Unattended-upgrade in progress during shutdown, please don't turn off the computer Progress: 0.0025 % (perl-base,perl-modules-5.26,libperl5.26,perl) 2018-12-04 15:55:26,737 WARNING - Unattended-upgrade in progress during shutdown, please don't turn off the computer Progress: 0.0 % (perl-modules-5.26) 2018-12-04 15:55:29,740 WARNING - Unattended-upgrade in progress during shutdown, please don't turn off the computer Progress: 20.0 % (perl-modules-5.26) 2018-12-04 15:55:32,742 WARNING - Unattended-upgrade in progress during shutdown, please don't turn off the computer Progress: 80.0 % (perl-modules-5.26) 2018-12-04 15:55:35,746 WARNING - Unattended-upgrade in progress during shutdown, please don't turn off the computer Progress: 46.1538 % (perl) 2018-12-04 15:55:38,747 WARNING - Unattended-upgrade in progress during shutdown, please don't turn off the computer Progress: 92.3077 % (perl) 2018-12-04 15:55:41,752 WARNING - Unattended-upgrade in progress during shutdown, please don't turn off the computer Progress: 92.3077 % (perl) 2018-12-04 15:55:41,769 INFO - All upgrades installed For more details please see the /usr/share/doc/unattended-upgrades/NEWS.Debian.gz, the changelog, and LP: #1803137. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1806463 Title: Unattended-Upgrade::InstallOnShutdown "true" not working Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Cosmic, unattended-upgrades 1.5ubuntu3.18.10.0 Trying to get install-on-shutdown working. Added << Unattended- Upgrade::InstallOnShutdown "true"; >> to apt.conf. It appears that the logic for install-on-shutdown is in /usr/share /unattended-upgrades/unattended-u
[Touch-packages] [Bug 1806458] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1806458/+attachment/5218989/+files/Dependencies.txt -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled
[Touch-packages] [Bug 1398537] Re: gdebi 0.9.5.3 crashing
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015. Do you still see a problem related to the one that you reported in a currently supported version of Ubuntu? Please let us know if you do. Alternatively, this bug report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better.related Paul White [Ubuntu Bug Squad] ** Changed in: gdebi (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1398537 Title: gdebi 0.9.5.3 crashing Status in gdebi package in Ubuntu: Incomplete Bug description: Using gdebi 0.9.5.3-ubuntu2 and gdebi-core 0.9.5.3-ubuntu2 on Trusty 14.10 I tried upgrading the two packages to the 14.10 versions using dpkg and they installed fine but the same crash happened. I'm not sure what is going on. I right click an application (like the official release debi of Teamviewer) and gdebi starts up, begins its scan, then terminates. I think it is failing during its scan for dependencies. I tried reporting this using ubuntu-bug in a terminal but that didn't work so I am not sure how to get all the required supported applications. Is anyone else experiencing this crash? Suggestions? I don't use gdebi much but it is more convenient that firing up a terminal window and typing dpkg everytime I want to install a package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1398537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1228383] Re: gdebi-gtk crashed with SIGSEGV in gtk_label_set_text()
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. Do you still see a problem related to the one that you reported in a currently supported version of Ubuntu? Please let us know if you do. Alternatively, this bug report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better.related Paul White [Ubuntu Bug Squad] ** Changed in: gdebi (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1228383 Title: gdebi-gtk crashed with SIGSEGV in gtk_label_set_text() Status in gdebi package in Ubuntu: Incomplete Bug description: gdebi-gtk crashed on notebook turn-on (not used, but might have had unfinished business with virtualbox?) ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gdebi 0.9.1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Fri Sep 20 17:36:02 2013 ExecutablePath: /usr/share/gdebi/gdebi-gtk InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/gdebi-gtk --non-interactive /media/ian/Nemesis1/Software/Internet\ Software/Virtualbox/For\ Ubuntu\ 13.04/virtualbox-4.2_4.2.18-88780~Ubuntu~raring_amd64.deb ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash TERM=unknown SegvAnalysis: Segfault happened at: 0x7ffdb30fef8e :cmp %rax,(%rdx) PC (0x7ffdb30fef8e) ok source "%rax" ok destination "(%rdx)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gdebi StacktraceTop: gtk_label_set_text () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gdebi-gtk crashed with SIGSEGV in gtk_label_set_text() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1228383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783170] Re: package unattended-upgrades 1.1ubuntu1.18.04.4 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error ex
*** This bug is a duplicate of bug 1638492 *** https://bugs.launchpad.net/bugs/1638492 ** This bug has been marked a duplicate of bug 1638492 package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1783170 Title: package unattended-upgrades 1.1ubuntu1.18.04.4 failed to install/upgrade: installed unattended-upgrades package post- installation script subprocess returned error exit status 128 Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: 789 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-29.31-lowlatency 4.15.18 Uname: Linux 4.15.0-29-lowlatency x86_64 .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sat Jul 21 18:28:51 2018 ErrorMessage: installed unattended-upgrades package post-installation script subprocess returned error exit status 128 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.4 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 128 UpgradeStatus: Upgraded to bionic on 2018-05-13 (71 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-20T23:44:01.023912 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1783170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799977] Re: [MIR] gssdp
@doc depend & vcs reference have been fixed in 1.0.2-3 which just got uploaded to Debian (and going to be autosynced to disco) the tests are not integration ones so unsure they are really useful as autopkgtest but I'm unsure what are the best/common practices there, I can add them still if you want -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gssdp in Ubuntu. https://bugs.launchpad.net/bugs/1799977 Title: [MIR] gssdp Status in gssdp package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian, the package was in main in the past and needs to be re- promoted * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on gssdp * Security No CVE/known security issue * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is being used during build * Dependendies The package dependencies are in main * Standards compliance the package is using standard packaging (dh11), the standards-version is 4.1.1, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssdp/+bug/1799977/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752059] Re: package unattended-upgrades 0.90ubuntu0.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1638492 *** https://bugs.launchpad.net/bugs/1638492 ** This bug has been marked a duplicate of bug 1638492 package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1752059 Title: package unattended-upgrades 0.90ubuntu0.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: package unattended-upgrades 0.90ubuntu0.9 failed to install/upgrade: subprocess installed post-installation no script returned error exit (status unknown). Just stopped "debconf" opened and when I close it : "it seems you have modified the content of "/etc/apt/apt.conf.d/10periodic" ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.9 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.15 Architecture: amd64 Date: Tue Feb 27 11:33:37 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2018-02-26 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-02-26T23:42:00.409854 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1752059/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799974] Re: [MIR] gupnp
Same as gssdp, the doc/depends issue is fixed in 1.0.3-2 in Debian/going to be autosynced. The tests are not integration tests so unsure there is much value having them as autopkgtests? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gupnp in Ubuntu. https://bugs.launchpad.net/bugs/1799974 Title: [MIR] gupnp Status in gupnp package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian, the package was in main in the past and needs to be re- promoted * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on rygel which depends on the gupnp libraries * Security There is an old CVE recorded/fixed https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2174 * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is used during build * Dependendies The package uses standard desktop libraries that are already in main * Standards compliance the package is using standard packaging (dh10), the standards-version is 4.2, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1799974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638492] Re: unattended-upgrades post-installation script returned error exit status 128 due to debconf passthrough frontend failing
** Summary changed: - package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 + unattended-upgrades post-installation script returned error exit status 128 due to debconf passthrough frontend failing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1638492 Title: unattended-upgrades post-installation script returned error exit status 128 due to debconf passthrough frontend failing Status in unattended-upgrades package in Ubuntu: In Progress Bug description: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 2 09:21:06 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-07-29 (95 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "1"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-09-14T10:24:20.453516 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1638492/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806458] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1806458/+attachment/5219036/+files/ProcInterrupts.txt -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Fi
[Touch-packages] [Bug 1806458] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1806458/+attachment/5219031/+files/Dependencies.txt -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled
[Touch-packages] [Bug 1806458] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1806458/+attachment/5219034/+files/ProcCpuinfoMinimal.txt -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family:
[Touch-packages] [Bug 1806458] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1806458/+attachment/5219033/+files/ProcCpuinfo.txt -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled B
[Touch-packages] [Bug 1806458] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1806458/+attachment/5219035/+files/ProcEnviron.txt -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled B
[Touch-packages] [Bug 1806458] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1806458/+attachment/5219038/+files/UdevDb.txt -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M.
[Touch-packages] [Bug 1806458] Re: Intel I219-V ethernet connection lost
apport information ** Description changed: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) Inst
[Touch-packages] [Bug 1806458] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1806458/+attachment/5219037/+files/ProcModules.txt -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled B
[Touch-packages] [Bug 1806708] Re: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.0 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1638492 *** https://bugs.launchpad.net/bugs/1638492 ** This bug has been marked a duplicate of bug 1638492 unattended-upgrades post-installation script returned error exit status 128 due to debconf passthrough frontend failing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1806708 Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.0 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in unattended-upgrades package in Ubuntu: New Bug description: Normal update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 1.1ubuntu1.18.04.7~16.04.0 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Dec 4 12:15:17 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2018-03-28 (251 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.0 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-07-09T18:55:55.032675 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1806708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806458] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1806458/+attachment/5219032/+files/Lspci.txt -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dm
[Touch-packages] [Bug 1806458] Re: Intel I219-V ethernet connection lost
again with new kernel and x11 session -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.
[Touch-packages] [Bug 1806458] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1806458/+attachment/5218993/+files/ProcEnviron.txt -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled B
[Touch-packages] [Bug 1806458] Re: Intel I219-V ethernet connection lost
Same problem with standard kernel. -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.ver
[Touch-packages] [Bug 1806458] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1806458/+attachment/5218996/+files/UdevDb.txt -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M.
[Touch-packages] [Bug 1806458] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1806458/+attachment/5218990/+files/Lspci.txt -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dm
[Touch-packages] [Bug 1806458] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1806458/+attachment/5218991/+files/ProcCpuinfo.txt -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled B
[Touch-packages] [Bug 1577926] Re: apt-key works fine, yet apt fails with "Could not execute 'apt-key'"
i had the same error while chroot-ing from arch linux into ubuntu linux. fixed the issue with: source /etc/environment ... to set the correct $PATH and maybe: echo 'APT::Sandbox::User "root";' >/etc/apt/apt.conf.d/00temp ... as suggested earlier -- 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/1577926 Title: apt-key works fine, yet apt fails with "Could not execute 'apt-key'" Status in apt package in Ubuntu: Confirmed Bug description: Apt can fail to verify a Release file which verifies just fine when calling apt-key directly. Please advise how i can supply further debug information to help fix the underlying bug. Expected: apt-get should only report that a repository is not signed when no such signature was found. If a signature was in fact successfully acquired but not verified, apt-get should report failure to verify instead. apt-get should have a meaningful error message when calling apt-key fails. Bonus: Calling apt-key should not fail when the same thing works fine on command line. A reference to "Debug::Acquire::gpgv" should be in apt-secure(8) documentation. Observed: # uname -a Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 i686 i686 i686 GNU/Linux # chroot reproducable $ uname -a Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 armv7l armv7l armv7l GNU/Linux $ lsb_release -a 2>/dev/null Distributor ID: Ubuntu Description: Ubuntu 16.04 LTS Release: 16.04 Codename: xenial $ apt-get -o "Debug::Acquire::gpgv=true" update Get:1 http://ports.ubuntu.com xenial-security InRelease [92.2 kB] 0% [1 InRelease gpgv 92.2 kB]igners Preparing to exec: /usr/bin/apt-key --quiet --readonly verify --status-fd 3 /tmp/apt.sig.jYGUCG /tmp/apt.data.uTkX1c gpgv exited with status 111 Summary: Good: Bad: Worthless: SoonWorthless: NoPubKey: Ign:1 http://ports.ubuntu.com xenial-security InRelease Fetched 92.2 kB in 1s (79.5 kB/s) Reading package lists... Done W: GPG error: http://ports.ubuntu.com xenial-security InRelease: Could not execute 'apt-key' to verify signature (is gnupg installed?) W: The repository 'http://ports.ubuntu.com xenial-security InRelease' is not signed. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. $ /usr/bin/apt-key --quiet --readonly verify --status-fd /dev/stderr /tmp/apt.sig.jYGUCG /tmp/apt.data.uTkX1c gpgv: Signature made Tue May 3 19:02:17 2016 UTC using DSA key ID 437D05B5 [GNUPG:] SIG_ID e53PXRjA/EMb7CuZJtAicvvUm60 2016-05-03 1462302137 [GNUPG:] GOODSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key gpgv: Good signature from "Ubuntu Archive Automatic Signing Key " [GNUPG:] VALIDSIG 630239CC130E1A7FD81A27B140976EAF437D05B5 2016-05-03 1462302137 0 4 0 17 10 01 630239CC130E1A7FD81A27B140976EAF437D05B5 gpgv: Signature made Tue May 3 19:02:17 2016 UTC using RSA key ID C0B21F32 [GNUPG:] SIG_ID kCsrLo9VUm7YcYhhqQUw2fbWoY4 2016-05-03 1462302137 [GNUPG:] GOODSIG 3B4FE6ACC0B21F32 Ubuntu Archive Automatic Signing Key (2012) gpgv: Good signature from "Ubuntu Archive Automatic Signing Key (2012) " [GNUPG:] VALIDSIG 790BC7277767219C42C86F933B4FE6ACC0B21F32 2016-05-03 1462302137 0 4 0 1 10 01 790BC7277767219C42C86F933B4FE6ACC0B21F32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1577926/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806458] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1806458/+attachment/5218992/+files/ProcCpuinfoMinimal.txt -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family:
[Touch-packages] [Bug 1754693] Re: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps]
I can confirm with the PPA enabled I no longer see classic snaps crash when running wayland on cosmic. I tested vscode and slack. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1754693 Title: Xwayland/Xorg crashed with SIGSEGV in st_renderbuffer_delete() from _mesa_reference_renderbuffer_() [often when running Skype or Slack snaps] Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Status in mesa source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Status in mesa source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Incomplete Status in mesa source package in Disco: Confirmed Status in xorg-server source package in Disco: Incomplete Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evde
[Touch-packages] [Bug 1720499] Re: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
>From DpkgTerminalLog.txt: ... /usr/bin/ucf: line 567: awk: command not found dpkg: error processing package unattended-upgrades (--configure): subprocess installed post-installation script returned error exit status 127 It looks like awk is missing from the system which either means that the filesystem is damaged or base-files is also missing which is an unsupported configuration. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1720499 Title: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in unattended-upgrades package in Ubuntu: Invalid Bug description: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.8 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Sep 30 10:12:12 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2017-05-18 (134 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-06-16T13:22:47.273361 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1720499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU
On Tue, Dec 4, 2018 at 6:31 AM Dimitri John Ledkov wrote: > Using systemd 237-3ubuntu10.10 > > Using: > [Match] > Name=ens3 > [Network] > DHCP=ipv4 > IPv6MTUBytes=1600 > [Link] > MTUBytes=1800 > [DHCP] > UseMTU=no > RouteMetric=100 > Do you put this in the same .network file or .link file? -- 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/1671951 Title: networkd should allow configuring IPV6 MTU Status in cloud-init package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Status in cloud-init source package in Bionic: Confirmed Status in netplan.io source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Bug description: = systemd = [Impact] * IPv6 traffic failing to send/receive due to incompatible/low MTU setting. Specifically, IPv6 traffic may have higher MTU requirements than IPv4 traffic and thus may need to be overridden and/or set to a higher value than IPv6 traffic. [Test Case] * Use IPv6MTUBytes= setting in a .network unit * Restart systemd-network * Check that there no error messages / warnings about not-recognizing this option * Check that MTU bytes, is at least IPv6MTUBytes on the interface [Regression Potential] * This is a future compatible backport of an additional keyword not used by default. It may result in MTU change to a higher value, which should not cause loss of connectivity. [Other Info] * Original bug report below = end of systemd = 1) Zesty 2) systemd-232-19 3) I need to configure the IPV6 MTU for tunneling by adding an IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 static address in the [Network] section 4) networkd does not parse or read the value and does not apply this configuration to the interface. Upstream has discussed this issue here: https://github.com/systemd/systemd/pull/1533 But it's been closed in favor of only setting via RA. However, we know of multiple use-case which are currently supported in ifdupdown where we want to retain control over IPV6 MTU values outside of PMTU Discovery configurations. Some context from those discussions >> Client systems that route their ipv6 packets to a 6in4 router also >> have to have their ipv6 mtu lowered. They could lower their link mtu, >> so their ipv6 packets are small enough, but that reduces performance >> of their ipv4 network. Yes. Anything that creates a PMTUD black hole can result in situations where the higher header overhead of IPv6 will cause IPv4 to pass but IPv6 traffic to be dropped. One example here is egress from an ipsec tunnel wherein the next hop MTU is too low for IPv6 datagrams to pass. Another is VM -> whatever -> host bridge -> tunnel ingress. If the datagram cannot enter the tunnel due to size, it is dropped, and an ICMP response uses the tunnel address as a source, which may not be routable back to the origin. This one is an issue with IPv4 as well, and is one case where manually setting the IPv6 MTU lower than the (also manually set) device MTU is of benefit. In essence, any of these sort of cases that require an explicit setting of the device MTU will likely require a setting of the IPv6 mtu as well to account for its larger header overhead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652785] Re: package unattended-upgrades 0.90ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1638492 *** https://bugs.launchpad.net/bugs/1638492 ** This bug has been marked a duplicate of bug 1638492 package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1652785 Title: package unattended-upgrades 0.90ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Was playing a game in fullscreen mode while the updates ran, in case that affects things. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.2 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic i686 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: i386 Date: Tue Dec 27 09:26:49 2016 DuplicateSignature: package:unattended-upgrades:0.90ubuntu0.2 Installing new version of config file /etc/logrotate.d/unattended-upgrades ... frontend: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. dpkg: error processing package unattended-upgrades (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-09-04 (844 days ago) InstallationMedia: It PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-12-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1652785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696237] Re: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1638492 *** https://bugs.launchpad.net/bugs/1638492 ** This bug has been marked a duplicate of bug 1638492 package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1696237 Title: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Just rebooted this evening and seen this error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.6 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Tue Jun 6 20:17:09 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2015-10-09 (606 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2017-01-25 (131 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "1"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "1"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-04-24T10:11:39.287010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1696237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1228383] Re: gdebi-gtk crashed with SIGSEGV in gtk_label_set_text()
Hi Paul Ubuntu 18.10 runs fine - the only issue it has is to run SciLab - never opens, however on Mint no problem. I've reported this earlier. Ian On Wed, Dec 5, 2018 at 3:30 AM Paul White <1228...@bugs.launchpad.net> wrote: > We are sorry that we do not always have the capacity to review all > reported bugs in a timely manner. You reported this bug some time ago > and there have been many changes in Ubuntu since that time. > > Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. > > Do you still see a problem related to the one that you reported in a > currently supported version of Ubuntu? > > Please let us know if you do. Alternatively, this bug report can be left > to expire in approximately 60 days time. > > Thank you for helping make Ubuntu better.related > > Paul White > [Ubuntu Bug Squad] > > ** Changed in: gdebi (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1228383 > > Title: > gdebi-gtk crashed with SIGSEGV in gtk_label_set_text() > > Status in gdebi package in Ubuntu: > Incomplete > > Bug description: > gdebi-gtk crashed on notebook turn-on (not used, but might have had > unfinished business with virtualbox?) > > ProblemType: Crash > DistroRelease: Ubuntu 13.10 > Package: gdebi 0.9.1ubuntu1 > ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 > Uname: Linux 3.11.0-8-generic x86_64 > ApportVersion: 2.12.4-0ubuntu1 > Architecture: amd64 > Date: Fri Sep 20 17:36:02 2013 > ExecutablePath: /usr/share/gdebi/gdebi-gtk > InterpreterPath: /usr/bin/python2.7 > MarkForUpload: True > PackageArchitecture: all > ProcCmdline: /usr/bin/python /usr/bin/gdebi-gtk --non-interactive > /media/ian/Nemesis1/Software/Internet\ Software/Virtualbox/For\ Ubuntu\ > 13.04/virtualbox-4.2_4.2.18-88780~Ubuntu~raring_amd64.deb > ProcEnviron: >LANGUAGE=en_NZ:en >PATH=(custom, no user) >LANG=en_NZ.UTF-8 >SHELL=/bin/bash >TERM=unknown > SegvAnalysis: >Segfault happened at: 0x7ffdb30fef8e : > cmp%rax,(%rdx) >PC (0x7ffdb30fef8e) ok >source "%rax" ok >destination "(%rdx)" (0x) not located in a known VMA > region (needed writable region)! > SegvReason: writing unknown VMA > Signal: 11 > SourcePackage: gdebi > StacktraceTop: >gtk_label_set_text () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 >g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 >?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 >g_signal_emit_valist () from > /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 >g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 > Title: gdebi-gtk crashed with SIGSEGV in gtk_label_set_text() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1228383/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1228383 Title: gdebi-gtk crashed with SIGSEGV in gtk_label_set_text() Status in gdebi package in Ubuntu: Incomplete Bug description: gdebi-gtk crashed on notebook turn-on (not used, but might have had unfinished business with virtualbox?) ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gdebi 0.9.1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 Date: Fri Sep 20 17:36:02 2013 ExecutablePath: /usr/share/gdebi/gdebi-gtk InterpreterPath: /usr/bin/python2.7 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/gdebi-gtk --non-interactive /media/ian/Nemesis1/Software/Internet\ Software/Virtualbox/For\ Ubuntu\ 13.04/virtualbox-4.2_4.2.18-88780~Ubuntu~raring_amd64.deb ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash TERM=unknown SegvAnalysis: Segfault happened at: 0x7ffdb30fef8e :cmp %rax,(%rdx) PC (0x7ffdb30fef8e) ok source "%rax" ok destination "(%rdx)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gdebi StacktraceTop: gtk_label_set_text () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gdebi-gtk crashed with SIGSEGV in gtk_label_set_text() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications
[Touch-packages] [Bug 1577926] Re: apt-key works fine, yet apt fails with "Could not execute 'apt-key'"
i had the same error while chroot-ing from arch linux into ubuntu linux. fixed the bug with: PATH="$PATH:/bin:/sbin" [and maybe `echo 'APT::Sandbox::User "root";' >/etc/apt/apt.conf.d/00temp`] running `source /etc/profile` did not help. -- 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/1577926 Title: apt-key works fine, yet apt fails with "Could not execute 'apt-key'" Status in apt package in Ubuntu: Confirmed Bug description: Apt can fail to verify a Release file which verifies just fine when calling apt-key directly. Please advise how i can supply further debug information to help fix the underlying bug. Expected: apt-get should only report that a repository is not signed when no such signature was found. If a signature was in fact successfully acquired but not verified, apt-get should report failure to verify instead. apt-get should have a meaningful error message when calling apt-key fails. Bonus: Calling apt-key should not fail when the same thing works fine on command line. A reference to "Debug::Acquire::gpgv" should be in apt-secure(8) documentation. Observed: # uname -a Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 i686 i686 i686 GNU/Linux # chroot reproducable $ uname -a Linux hostname 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:34:49 UTC 2016 armv7l armv7l armv7l GNU/Linux $ lsb_release -a 2>/dev/null Distributor ID: Ubuntu Description: Ubuntu 16.04 LTS Release: 16.04 Codename: xenial $ apt-get -o "Debug::Acquire::gpgv=true" update Get:1 http://ports.ubuntu.com xenial-security InRelease [92.2 kB] 0% [1 InRelease gpgv 92.2 kB]igners Preparing to exec: /usr/bin/apt-key --quiet --readonly verify --status-fd 3 /tmp/apt.sig.jYGUCG /tmp/apt.data.uTkX1c gpgv exited with status 111 Summary: Good: Bad: Worthless: SoonWorthless: NoPubKey: Ign:1 http://ports.ubuntu.com xenial-security InRelease Fetched 92.2 kB in 1s (79.5 kB/s) Reading package lists... Done W: GPG error: http://ports.ubuntu.com xenial-security InRelease: Could not execute 'apt-key' to verify signature (is gnupg installed?) W: The repository 'http://ports.ubuntu.com xenial-security InRelease' is not signed. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. $ /usr/bin/apt-key --quiet --readonly verify --status-fd /dev/stderr /tmp/apt.sig.jYGUCG /tmp/apt.data.uTkX1c gpgv: Signature made Tue May 3 19:02:17 2016 UTC using DSA key ID 437D05B5 [GNUPG:] SIG_ID e53PXRjA/EMb7CuZJtAicvvUm60 2016-05-03 1462302137 [GNUPG:] GOODSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key gpgv: Good signature from "Ubuntu Archive Automatic Signing Key " [GNUPG:] VALIDSIG 630239CC130E1A7FD81A27B140976EAF437D05B5 2016-05-03 1462302137 0 4 0 17 10 01 630239CC130E1A7FD81A27B140976EAF437D05B5 gpgv: Signature made Tue May 3 19:02:17 2016 UTC using RSA key ID C0B21F32 [GNUPG:] SIG_ID kCsrLo9VUm7YcYhhqQUw2fbWoY4 2016-05-03 1462302137 [GNUPG:] GOODSIG 3B4FE6ACC0B21F32 Ubuntu Archive Automatic Signing Key (2012) gpgv: Good signature from "Ubuntu Archive Automatic Signing Key (2012) " [GNUPG:] VALIDSIG 790BC7277767219C42C86F933B4FE6ACC0B21F32 2016-05-03 1462302137 0 4 0 1 10 01 790BC7277767219C42C86F933B4FE6ACC0B21F32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1577926/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
** Changed in: mesa (Ubuntu Cosmic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: New Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
** Changed in: gtk+3.0 (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) ** Changed in: gtk+3.0 (Ubuntu Bionic) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) ** Changed in: gtk+3.0 (Ubuntu Cosmic) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- 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/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability Status in cups-filters package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Triaged Status in cups-filters source package in Bionic: Invalid Status in gtk+3.0 source package in Bionic: New Status in cups-filters source package in Cosmic: Invalid Status in gtk+3.0 source package in Cosmic: New Bug description: I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 Note the un-reaped gs process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 15:07:49 2018 InstallationDate: Installed on 2010-09-24 (2757 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission denied: '/etc/cups/cupsd.conf'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1763520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805857] Re: network-manager dep8 failure blocks dnsmasq proposed migration
** Also affects: network-manager (Ubuntu Disco) Importance: High Status: Triaged ** Changed in: network-manager (Ubuntu Disco) Assignee: (unassigned) => Iain Lane (laney) -- 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/1805857 Title: network-manager dep8 failure blocks dnsmasq proposed migration Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Disco: Triaged Bug description: dnsmasq 2.80-1 is blocked from migrating to the release pocket because of, amongst other things, a network-manager dep8 regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1805857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806708] Re: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.0 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1806708 Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.0 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in unattended-upgrades package in Ubuntu: New Bug description: Normal update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 1.1ubuntu1.18.04.7~16.04.0 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Dec 4 12:15:17 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2018-03-28 (251 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.0 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-07-09T18:55:55.032675 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1806708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806708] [NEW] package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.0 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: Normal update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 1.1ubuntu1.18.04.7~16.04.0 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Dec 4 12:15:17 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2018-03-28 (251 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.0 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-07-09T18:55:55.032675 ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1806708 Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.0 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in unattended-upgrades package in Ubuntu: New Bug description: Normal update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 1.1ubuntu1.18.04.7~16.04.0 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Dec 4 12:15:17 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2018-03-28 (251 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.0 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-07-09T18:55:55.032675 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1806708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798313] Re: traceoute6 gives error sendto: Invalid argument
While reviewing the nominated bugs we decided it would be good to fix but not important enough to rls track it, so tagging rls-bb-notfixing ** Tags removed: rls-bb-incoming ** Tags added: rls-bb-notfixing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1798313 Title: traceoute6 gives error sendto: Invalid argument Status in Iputils: Fix Released Status in iputils package in Ubuntu: Confirmed Status in iputils package in Debian: Fix Released Bug description: When running the following command all get is an error. (traceroute6.db works) # traceroute6.iputils 2001:4860:4860:: traceroute to 2001:4860:4860:: (2001:4860:4860::) from 2a00:8780:3:42:b92a:b222:8bed:4a9b, 30 hops max, 24 byte packets sendto: Invalid argument 1 traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1 *sendto: Invalid argument traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1 *sendto: Invalid argument traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1 * This seems like a regression of Debian bug https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=843264 Package version installed: iputils-tracepath 3:20161105-1ubuntu2 amd64 # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/iputils/+bug/1798313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1327041] Re: gdebi won't display content of gzip compressed files
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Your problem may have been fixed with some of the updates. It would help us a lot if you could test on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once in a terminal: apport-collect and then change the status of the bug back to "New". Please add any additional information that you think might be relevant. Alternatively, please confirm that this is no longer a problem and that we can close the bug report. If we do not hear from you this bug report will expire in approximately 60 days time. Thank you again for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: gdebi (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1327041 Title: gdebi won't display content of gzip compressed files Status in gdebi package in Ubuntu: Incomplete Bug description: When I open a .deb file in gdebi and go to the "Included files" tab and click on a gzip compressed file, it should normally show its content on the right side. Instead it displays this error message: Error reading file content 'initial_value must be str or None, not bytes' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1327041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806458] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1806458/+attachment/5218981/+files/Lspci.txt -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dm