[Touch-packages] [Bug 1777994] [NEW] the header xcb/xinput.h is missing
Public bug reported: I suspect this means there should be another package, libxcb-xinput-dev perhaps? I already did sudo apt install "libxcb*dev" to get all related dev packages, but none of them provide xcb/xinput.h. The result is that when building Qt from source, it's necessary to use a copy of this file which Qt provides (qtbase/src/3rdparty/xcb/include/xcb/xinput.h), because it's missing from the system. So if you don't give the option -qt-xcb to configure, then Qt will be built without multi-touch support. https://bugreports.qt.io/browse/QTBUG-69045 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libxcb1-dev 1.13-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 21 08:32:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3802] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80Y7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: libxcb UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB dmi.modalias: dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB: dmi.product.family: YOGA 920-13IKB dmi.product.name: 80Y7 dmi.product.version: Lenovo YOGA 920-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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: libxcb (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1777994 Title: the header xcb/xinput.h is missing Status in libxcb package in Ubuntu: New Bug description: I suspect this means there should be another package, libxcb-xinput- dev perhaps? I already did sudo apt install "libxcb*dev" to get all related dev packages, but none of them provide xcb/xinput.h. The result is that when building Qt from source, it's necessary to use a copy of this file which Qt provides (qtbase/src/3rdparty/xcb/include/xcb/xinput.h), because it's missing from the system. So if you don't give the option -qt-xcb to configure, then Qt will be built without multi-touch support. https://bugreports.qt.io/browse/QTBUG-69045 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libxcb1-dev 1.13-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 21 08:32:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3802] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80Y7 ProcKernel
[Touch-packages] [Bug 1554065] Re: Logitech presenter only working partially
I tried exactly the solution above using Ubuntu 16.04, but it does not help. Does anybody have a clue? -- 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/1554065 Title: Logitech presenter only working partially Status in systemd package in Ubuntu: New Bug description: The Logitech R400 presenter's buttons for starting a presentation and toggling the screen to black does not work any more since at least Ubuntu 13.10 [1] (it had worked in a previous Ubuntu version I do not remember exactly and it still worked in Debian 7 Wheezy but also does not work any more in Debian 8 Jessie). The buttons for the next and previous slide still do. [1] https://forum.ubuntuusers.de/topic/probleme-mit-logitech-r400 -presenter-unter-13-/ This presenter model has probably been one of the most widely spread ones since many years. I've bought mine in 2010 and it still is the best selling presenter on amazon.com and amazon.de. So really a lot of people are affected (moreover, similar Logitech models do exist, too). The problem seems to be in file /lib/udev/hwdb.d/60-keyboard.hwdb – the "displaytoggle" and "presentation" entries do not seem to be mapped to a key correctly (I do not understand how that mapping works in more detail). As a workaround, the Logitech R400 entry in this file can be changed (see attached patch) followed by sudo udevadm hwdb --update but it does not seem to be a real solution as other devices are probably affected, too. The real solution would probably be to get the "toggledisplay" etc. entries in this configuration file to be mapped correctly. latest Ubuntu version tested: 15.10 udev package version: 225-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1554065/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Please note that there is a change between 0.130ubuntu3.1 and 0.130ubuntu3.2 0.130ubuntu3.1 (/etc/initramfs-tool/conf.d/resume not deleted by hand) : 30s delay at boot 0.130ubuntu3.1 (/etc/initramfs-tool/conf.d/resume deleted by hand) : 30s delay at boot 0.130ubuntu3.2 (/etc/initramfs-tool/conf.d/resume not deleted by hand) : 30s delay at boot 0.130ubuntu3.2 (/etc/initramfs-tool/conf.d/resume deleted by hand) : no delay at boot Please note that once the /etc/initramfs-tool/conf.d/resume file has been removed neither 3.1 nor 3.2 will re-create it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: In Progress Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774831] Re: package systemd 237-3ubuntu10 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1774831 Title: package systemd 237-3ubuntu10 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in systemd package in Ubuntu: Confirmed Bug description: I tried to install a package (libboost-all-dev) and this error message was in my terminal, after a while a report problem popup box popped up on my screen and i want to fix this issue that is why i reported the error. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Sat Jun 2 23:57:29 2018 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP EliteBook 8460p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2dbe94c9-bbad-4c6a-b67e-5b4c0eb387b0 ro quiet splash Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 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.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. Title: package systemd 237-3ubuntu10 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.22 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4A dmi.chassis.asset.tag: CNU2241WLL dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774831/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
As you requested, the full output of sudo update-initramfs -u : pim@pim:~$ sudo update-initramfs -u [sudo] password for pim: update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic pim@pim:~$ After that the 30 second delay is still there. The warning messages only appears when I manually remove the /etc/initramfs-tool/conf.d/resume file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: In Progress Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758498] Re: perl crashed with SIGABRT in _dbus_abort()
This bug occurs often, 2 or 3 times per week. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1758498 Title: perl crashed with SIGABRT in _dbus_abort() Status in perl package in Ubuntu: Confirmed Bug description: I was browsing the internet using firefox installed from ubuntu repo ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: perl-base 5.26.1-5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Fri Mar 23 22:56:12 2018 ExecutablePath: /usr/bin/perl InstallationDate: Installed on 2018-03-15 (9 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: perl StacktraceTop: _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3 _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so Perl_pp_entersub () Title: perl crashed with SIGABRT in _dbus_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1758498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777966] Re: I get a notification error saying "Error:BrokenCount>0", after running "sudo apt update && sudo apt dist-upgrade" even though a manual check for broken packages yiel
** Attachment added: "Results of running "sudo apt-get install --fix-broken"" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1777966/+attachment/5154813/+files/apt-get%20install%20--fix-broken%20results.png -- 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/1777966 Title: I get a notification error saying "Error:BrokenCount>0", after running "sudo apt update && sudo apt dist-upgrade" even though a manual check for broken packages yielded no results. Status in apt package in Ubuntu: New Bug description: Immediately after installing Ubuntu 18.04, I rebooted the machine, logged into admin account, configured software update to enable the Canonical partners repository, opened Terminal, and ran "sudo apt update && sudo dist-upgrade" Upon installing all packages, an error notification appears on the menu bar saying "Error:BrokenCount>0'. This usually means that your installed packages have unmet dependences" When I clicked on Check for Updates, nothing happened. I went to run "sudo apt install -f", 0 packages were installed or trained. This indicates that the error was falsely flagged and therefore a bug. Steps to Reproduce: 1. Install Ubuntu 18.04 2. Boot into the admin account on a Xorg session 3. Open Terminal and run "sudo apt update && sudo dist-upgrade" 4. Notice that an error notification appears on the right of the menu bar on top Rebooting the machine fixed the issue, but this bug should not happened immediately after running Ubuntu for the first time and checking for updates via Terminal. The timestamp for the issue itself is Wednesday, June 20, 2018, at around 9:30 PM, EDT. 1) Ubuntu 18.04 2) apt Installed: 1.6.1 3) Error notification is absent because no such error happened; all the dependencies and packages are properly installed. 4) I get a false error saying "BrokenCount>0" even though searching for broken packages yielded no results. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 20 21:17:46 2018 InstallationDate: Installed on 2018-06-21 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1777966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777966] [NEW] I get a notification error saying "Error:BrokenCount>0", after running "sudo apt update && sudo apt dist-upgrade" even though a manual check for broken packages yi
Public bug reported: Immediately after installing Ubuntu 18.04, I rebooted the machine, logged into admin account, configured software update to enable the Canonical partners repository, opened Terminal, and ran "sudo apt update && sudo dist-upgrade" Upon installing all packages, an error notification appears on the menu bar saying "Error:BrokenCount>0'. This usually means that your installed packages have unmet dependences" When I clicked on Check for Updates, nothing happened. I went to run "sudo apt install -f", 0 packages were installed or trained. This indicates that the error was falsely flagged and therefore a bug. Steps to Reproduce: 1. Install Ubuntu 18.04 2. Boot into the admin account on a Xorg session 3. Open Terminal and run "sudo apt update && sudo dist-upgrade" 4. Notice that an error notification appears on the right of the menu bar on top Rebooting the machine fixed the issue, but this bug should not happened immediately after running Ubuntu for the first time and checking for updates via Terminal. The timestamp for the issue itself is Wednesday, June 20, 2018, at around 9:30 PM, EDT. 1) Ubuntu 18.04 2) apt Installed: 1.6.1 3) Error notification is absent because no such error happened; all the dependencies and packages are properly installed. 4) I get a false error saying "BrokenCount>0" even though searching for broken packages yielded no results. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 20 21:17:46 2018 InstallationDate: Installed on 2018-06-21 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Software Update settings" https://bugs.launchpad.net/bugs/1777966/+attachment/5154810/+files/Screenshot%20from%202018-06-20%2021-34-31.png -- 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/1777966 Title: I get a notification error saying "Error:BrokenCount>0", after running "sudo apt update && sudo apt dist-upgrade" even though a manual check for broken packages yielded no results. Status in apt package in Ubuntu: New Bug description: Immediately after installing Ubuntu 18.04, I rebooted the machine, logged into admin account, configured software update to enable the Canonical partners repository, opened Terminal, and ran "sudo apt update && sudo dist-upgrade" Upon installing all packages, an error notification appears on the menu bar saying "Error:BrokenCount>0'. This usually means that your installed packages have unmet dependences" When I clicked on Check for Updates, nothing happened. I went to run "sudo apt install -f", 0 packages were installed or trained. This indicates that the error was falsely flagged and therefore a bug. Steps to Reproduce: 1. Install Ubuntu 18.04 2. Boot into the admin account on a Xorg session 3. Open Terminal and run "sudo apt update && sudo dist-upgrade" 4. Notice that an error notification appears on the right of the menu bar on top Rebooting the machine fixed the issue, but this bug should not happened immediately after running Ubuntu for the first time and checking for updates via Terminal. The timestamp for the issue itself is Wednesday, June 20, 2018, at around 9:30 PM, EDT. 1) Ubuntu 18.04 2) apt Installed: 1.6.1 3) Error notification is absent because no such error happened; all the dependencies and packages are properly installed. 4) I get a false error saying "BrokenCount>0" even though searching for broken packages yielded no results. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 20 21:17:46 2018 InstallationDate: Installed on 2018-06-21 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1777966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771539] Re: Xorg crash
Mario Costa: A) Could you please provide the result of the following terminal command: sudo cat /var/lib/whoopsie/whoopsie-id B) To see if this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the result? ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1771539 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: When I try to use ubuntu with dual desktop display it crashes continuously, and entering into login mode. I cannot use dual display. To use an external monitor, I have to start the laptop with the computer closed. It seems to be related to the graphic card, maybe dual graphic card of the laptop. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Classic:GNOME Date: Wed May 16 10:36:05 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990] InstallationDate: Installed on 2017-12-13 (153 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=e1833df7-4a4b-41b2-8393-d88536dd0165 ro quiet splash radeon.runpm=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.39 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: 5CG44010XD dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.39:bd09/26/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Mar 8 12:39:32 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771539] Re: Xorg crash
** Changed in: xorg (Ubuntu) Status: Incomplete => New -- 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/1771539 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: When I try to use ubuntu with dual desktop display it crashes continuously, and entering into login mode. I cannot use dual display. To use an external monitor, I have to start the laptop with the computer closed. It seems to be related to the graphic card, maybe dual graphic card of the laptop. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Classic:GNOME Date: Wed May 16 10:36:05 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990] InstallationDate: Installed on 2017-12-13 (153 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=e1833df7-4a4b-41b2-8393-d88536dd0165 ro quiet splash radeon.runpm=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.39 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: 5CG44010XD dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.39:bd09/26/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Mar 8 12:39:32 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
** Changed in: python3-defaults (Debian) Status: Unknown => New -- 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/1768379 Title: python3-minimal should predepend on versioned version of python3-minimal Status in python3-defaults package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python3-defaults package in Debian: New Bug description: do-release-upgrade -d on my 16.04 LTS unity laptop lead to an install failure: Fetched 2,320 MB in 6s (27.8 MB/s) Upgrading Inhibiting until Ctrl+C is pressed... Fetched 0 B in 0s (0 B/s) Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file (Reading database ... 373383 files and directories currently installed.) Preparing to unpack .../base-files_10.1ubuntu2_amd64.deb ... Unpacking base-files (10.1ubuntu2) over (9.4ubuntu4.6) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ... update-initramfs: deferring update (trigger activated) Processing triggers for cracklib-runtime (2.9.2-1ubuntu1) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic Setting up base-files (10.1ubuntu2) ... Installing new version of config file /etc/debian_version ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Updating /etc/profile to current default. motd-news.service is a disabled or a static unit, not starting it. Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../debianutils_4.8.4_amd64.deb ... Unpacking debianutils (4.8.4) over (4.7) ... Processing triggers for man-db (2.7.5-1) ... Setting up debianutils (4.8.4) ... (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ... Unpacking bash (4.4.18-2ubuntu1) over (4.3-14ubuntu1.2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for man-db (2.7.5-1) ... Setting up bash (4.4.18-2ubuntu1) ... Installing new version of config file /etc/bash.bashrc ... Installing new version of config file /etc/skel/.profile ... update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../libcomerr2_1.44.1-1_amd64.deb ... Unpacking libcomerr2:amd64 (1.44.1-1) over (1.42.13-1ubuntu1) ... Selecting previously unselected package libcom-err2:amd64. Preparing to unpack .../libcom-err2_1.44.1-1_amd64.deb ... Unpacking libcom-err2:amd64 (1.44.1-1) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Setting up libcom-err2:amd64 (1.44.1-1) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... (Reading database ... 373391 files and directories currently installed.) Preparing to unpack .../libkeyutils1_1.5.9-9.2ubuntu2_amd64.deb ... Unpacking libkeyutils1:amd64 (1.5.9-9.2ubuntu2) over (1.5.9-8ubuntu1) ... Preparing to unpack .../libk5crypto3_1.16-2build1_amd64.deb ... Unpacking libk5crypto3:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../libkrb5support0_1.16-2build1_amd64.deb ... Unpacking libkrb5support0:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../libgssapi-krb5-2_1.16-2build1_amd64.deb ... Unpacking libgssapi-krb5-2:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../libkrb5-3_1.16-2build1_amd64.deb ... Unpacking libkrb5-3:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../liblzma5_5.2.2-1.3_amd64.deb ... De-con
[Touch-packages] [Bug 1777942] Re: package libpam-runtime 1.1.8-3.2ubuntu2 failed to install/upgrade: package libpam-runtime is not ready for configuration cannot configure (current status 'half-insta
Thank you for taking the time to report this issue and help to improve Ubuntu. Unfortunately the logs included in your report are incomplete and only show the end state of the system: dpkg: error processing package libpam-runtime (--configure): package libpam-runtime is not ready for configuration cannot configure (current status 'half-installed') This does not tell us why this package entered this "half-installed" state. Without more information, it's not possible to address this failure. Please provide logs showing the root failure, if you're able. ** Changed in: pam (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1777942 Title: package libpam-runtime 1.1.8-3.2ubuntu2 failed to install/upgrade: package libpam-runtime is not ready for configuration cannot configure (current status 'half-installed') Status in pam package in Ubuntu: Incomplete Bug description: I was trying to install gparted when this happed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpam-runtime 1.1.8-3.2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-powerpc-smp 4.4.13 Uname: Linux 4.4.0-31-powerpc-smp ppc ApportVersion: 2.20.1-0ubuntu2.1 Architecture: powerpc Date: Wed Jun 20 23:06:02 2018 DuplicateSignature: package:libpam-runtime:1.1.8-3.2ubuntu2 Processing triggers for libc-bin (2.23-0ubuntu10) ... dpkg: error processing package libpam-runtime (--configure): package libpam-runtime is not ready for configuration ErrorMessage: package libpam-runtime is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-06-18 (2 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release powerpc (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: pam Title: package libpam-runtime 1.1.8-3.2ubuntu2 failed to install/upgrade: package libpam-runtime is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1777942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574351] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in
** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1574351 Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 Status in perl package in Ubuntu: Confirmed Bug description: Don't run aplication after upgrade from 14.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libperl5.22 5.22.1-9 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 21:08:20 2016 DpkgTerminalLog: Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ... Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 DuplicateSignature: Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 InstallationDate: Installed on 2016-04-24 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: perl Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1574351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770682] Re: Scanner driver failed to install. package libperl5.26 5.26.1-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz'
*** This bug is a duplicate of bug 1574351 *** https://bugs.launchpad.net/bugs/1574351 ** This bug has been marked a duplicate of bug 1574351 package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1770682 Title: Scanner driver failed to install. package libperl5.26 5.26.1-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 Status in perl package in Ubuntu: Confirmed Bug description: HP 1510 PSC scanner driver failed to install ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libperl5.26 5.26.1-6 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri May 11 18:01:31 2018 DuplicateSignature: package:libperl5.26:5.26.1-6 Unpacking libperl5.26:i386 (5.26.1-6) ... dpkg: error processing archive /tmp/apt-dpkg-install-bTjSsG/30-libperl5.26_5.26.1-6_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 InstallationDate: Installed on 2018-05-02 (8 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 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.1 SourcePackage: perl Title: package libperl5.26 5.26.1-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1770682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722185] Re: Crash installing packages using debconf
Merged upstream -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1722185 Title: Crash installing packages using debconf Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Bionic: In Progress Bug description: [Impact] Installing .deb package via PackageKit (e.g. using GNOME Software) don't work reliably when the packages use debconf. This is due to a faulty implementation of debconf handling in PackageKit. [Test Case] 1. Download opera deb file from opera.com 2. Run the file to launch gnome-software 3. Install it 4. Proceed with the debconf prompt Expected result: A debconf dialog appears asking if you want to "update Opera with the rest of the system?". The dialog closes when completed and the package is installed. Actual result: The dialog shows, but never closes and becomes unresponsive. Force closing the dialog causes a crash. [Regression Potential] The change is quite large, so there is a reasonable chance of introducing new bugs in debconf handling. However, the existing code has some obviously wrong codepaths, so the new code is probably a lower risk than the existing code. Crash reports: https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1722185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765892] Re: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags added: triggers-unprocessed -- 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/1765892 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in glib2.0 package in Ubuntu: New Bug description: I dont know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:amd64 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Fri Apr 20 20:34:12 2018 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-07-19 (275 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: glib2.0 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2018-04-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1765892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433761] Re: apt-key and add-apt-repository don't honor Acquire::http::Proxy
@miskokot Probably best to open this up in a new bug report if you think there is an error. However, I can at least confirm that having http_proxy and https_proxy set does yield connections to my proxy with apt-add- repository root@bionic:~# http_proxy=http://10.5.0.5:8000 https_proxy=http://10.5.0.5:8000 apt-add-repository ppa:canonical- kernel-team/ppa Notice, that your example has you doing an 'echo $http...' to prove that things are set, however that doesn't show if the variable is exported (available to suprocesses). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1433761 Title: apt-key and add-apt-repository don't honor Acquire::http::Proxy Status in software-properties package in Ubuntu: Fix Released Bug description: When setting the proxy server globally on the system for the APT package manager, add-apt-repository ignores the setting. This issue is present on all versions of Debian that I have tested. # cat /etc/apt/apt.conf.d/80proxy Acquire::http::proxy "http://w.x.y.z:/";; # apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5A9A06AEF9CB8DB0 Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.TIa517Kcw8 --no-auto-check-trustdb --trust-model always --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-squeeze-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg --keyring /etc/apt/trusted.gpg.d/saltstack-salt.gpg --keyserver keyserver.ubuntu.com --recv-keys 5A9A06AEF9CB8DB0 gpg: requesting key F9CB8DB0 from hkp server keyserver.ubuntu.com gpg: keyserver timed out gpg: keyserver receive failed: keyserver error This has serious repercussions. Unattended installs such as juju, maas, etc are all affected for anyone who is working behind a proxy. This is the case for most enterprise environments where such maas and juju setups will be tested out, and as such has great repercussions for Canonical as a viable supplier of OpenStack environments: if your product fails to install, you're not going to get the business. Considering that: * The setting to use already exists in /etc/apt/apt.conf and that all other tools use this correctly * The serious impact of this issue for downstream projects and Debian usage in the enterprise * The long time this issue has been standing and has affected people I suggest that this either 1) be fixed, or 2) the apt-key and add-apt-repository programs are renamed so that it is made clear they are not part of the APT suite of programs and therefor cannot be trusted to behave as if they were part of APT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1433761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
** Bug watch added: Debian Bug tracker #901001 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901001 ** Also affects: python3-defaults (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901001 Importance: Unknown Status: Unknown -- 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/1768379 Title: python3-minimal should predepend on versioned version of python3-minimal Status in python3-defaults package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Status in python3-defaults package in Debian: Unknown Bug description: do-release-upgrade -d on my 16.04 LTS unity laptop lead to an install failure: Fetched 2,320 MB in 6s (27.8 MB/s) Upgrading Inhibiting until Ctrl+C is pressed... Fetched 0 B in 0s (0 B/s) Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file (Reading database ... 373383 files and directories currently installed.) Preparing to unpack .../base-files_10.1ubuntu2_amd64.deb ... Unpacking base-files (10.1ubuntu2) over (9.4ubuntu4.6) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ... update-initramfs: deferring update (trigger activated) Processing triggers for cracklib-runtime (2.9.2-1ubuntu1) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic Setting up base-files (10.1ubuntu2) ... Installing new version of config file /etc/debian_version ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Updating /etc/profile to current default. motd-news.service is a disabled or a static unit, not starting it. Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../debianutils_4.8.4_amd64.deb ... Unpacking debianutils (4.8.4) over (4.7) ... Processing triggers for man-db (2.7.5-1) ... Setting up debianutils (4.8.4) ... (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ... Unpacking bash (4.4.18-2ubuntu1) over (4.3-14ubuntu1.2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for man-db (2.7.5-1) ... Setting up bash (4.4.18-2ubuntu1) ... Installing new version of config file /etc/bash.bashrc ... Installing new version of config file /etc/skel/.profile ... update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../libcomerr2_1.44.1-1_amd64.deb ... Unpacking libcomerr2:amd64 (1.44.1-1) over (1.42.13-1ubuntu1) ... Selecting previously unselected package libcom-err2:amd64. Preparing to unpack .../libcom-err2_1.44.1-1_amd64.deb ... Unpacking libcom-err2:amd64 (1.44.1-1) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Setting up libcom-err2:amd64 (1.44.1-1) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... (Reading database ... 373391 files and directories currently installed.) Preparing to unpack .../libkeyutils1_1.5.9-9.2ubuntu2_amd64.deb ... Unpacking libkeyutils1:amd64 (1.5.9-9.2ubuntu2) over (1.5.9-8ubuntu1) ... Preparing to unpack .../libk5crypto3_1.16-2build1_amd64.deb ... Unpacking libk5crypto3:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../libkrb5support0_1.16-2build1_amd64.deb ... Unpacking libkrb5support0:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../libgssapi-krb5-2_1.16-2build1_amd64.deb ... Unpacking libgssapi-krb5-2:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing
[Touch-packages] [Bug 1777942] Re: package libpam-runtime 1.1.8-3.2ubuntu2 failed to install/upgrade: package libpam-runtime is not ready for configuration cannot configure (current status 'half-insta
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1777942 Title: package libpam-runtime 1.1.8-3.2ubuntu2 failed to install/upgrade: package libpam-runtime is not ready for configuration cannot configure (current status 'half-installed') Status in pam package in Ubuntu: New Bug description: I was trying to install gparted when this happed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpam-runtime 1.1.8-3.2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-powerpc-smp 4.4.13 Uname: Linux 4.4.0-31-powerpc-smp ppc ApportVersion: 2.20.1-0ubuntu2.1 Architecture: powerpc Date: Wed Jun 20 23:06:02 2018 DuplicateSignature: package:libpam-runtime:1.1.8-3.2ubuntu2 Processing triggers for libc-bin (2.23-0ubuntu10) ... dpkg: error processing package libpam-runtime (--configure): package libpam-runtime is not ready for configuration ErrorMessage: package libpam-runtime is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-06-18 (2 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release powerpc (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: pam Title: package libpam-runtime 1.1.8-3.2ubuntu2 failed to install/upgrade: package libpam-runtime is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1777942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777942] [NEW] package libpam-runtime 1.1.8-3.2ubuntu2 failed to install/upgrade: package libpam-runtime is not ready for configuration cannot configure (current status 'half-ins
Public bug reported: I was trying to install gparted when this happed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpam-runtime 1.1.8-3.2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-powerpc-smp 4.4.13 Uname: Linux 4.4.0-31-powerpc-smp ppc ApportVersion: 2.20.1-0ubuntu2.1 Architecture: powerpc Date: Wed Jun 20 23:06:02 2018 DuplicateSignature: package:libpam-runtime:1.1.8-3.2ubuntu2 Processing triggers for libc-bin (2.23-0ubuntu10) ... dpkg: error processing package libpam-runtime (--configure): package libpam-runtime is not ready for configuration ErrorMessage: package libpam-runtime is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-06-18 (2 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release powerpc (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: pam Title: package libpam-runtime 1.1.8-3.2ubuntu2 failed to install/upgrade: package libpam-runtime is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package powerpc xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1777942 Title: package libpam-runtime 1.1.8-3.2ubuntu2 failed to install/upgrade: package libpam-runtime is not ready for configuration cannot configure (current status 'half-installed') Status in pam package in Ubuntu: New Bug description: I was trying to install gparted when this happed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpam-runtime 1.1.8-3.2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-31.50-powerpc-smp 4.4.13 Uname: Linux 4.4.0-31-powerpc-smp ppc ApportVersion: 2.20.1-0ubuntu2.1 Architecture: powerpc Date: Wed Jun 20 23:06:02 2018 DuplicateSignature: package:libpam-runtime:1.1.8-3.2ubuntu2 Processing triggers for libc-bin (2.23-0ubuntu10) ... dpkg: error processing package libpam-runtime (--configure): package libpam-runtime is not ready for configuration ErrorMessage: package libpam-runtime is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-06-18 (2 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release powerpc (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: pam Title: package libpam-runtime 1.1.8-3.2ubuntu2 failed to install/upgrade: package libpam-runtime is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1777942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766542] Re: Installation blocks when the machine is behind a proxy server
This bug was fixed in the package apt - 1.7.0~alpha0ubuntu2 --- apt (1.7.0~alpha0ubuntu2) cosmic; urgency=medium [ David Kalnischkies ] * Add boilerplate plural form to po/apt-all.pot * don't try SRV requests based on IP addresses * use 127.0.0.1 instead of localhost as default Tor proxy * Extend apt build-dep pkg/release to switch dep as needed * Support release selector for volatile files as well * Start pkg records for deb files with dpkg output * Deprectate buggy/incorrect Rls/PkgFile::IsOk methods * Support --with-source in show & search commands * Support local files as arguments in show command (Closes: 883206) * Drop alternative URIs we got a hash-based fail from * Handle by-hash URI construction more centrally * Don't force the same mirror for by-hash URIs * Reword error for timed out read/write on SOCKS proxy (Closes: #898886) * Don't show acquire warning for "hidden" components (Closes: #879591) * Use a steady clock source for progress reporting * Use steady clock source for bandwidth limitation [ Filipe Brandenburger ] * Update .gitignore * Increase debug verbosity in `apt-get autoremove` * Extend test-apt-get-autoremove to check debug output [ Julian Andres Klode ] * tests: Do not expect requested-by if sudo was invoked by root * Run tests on GitLab CI * Handle a missed case of timed out ip addresses (LP: #1766542) * Lower default timeout from 120s to 30s * apt-key: Pass all instead of gpg-agent to gpgconf --kill (LP: #1773992) * Fix lock counting in debSystem [ annadane ] * Add verb 'be' to NEWS entry for 1.5~beta1 (Closes: 892792) [ Алексей Шилин ] * Russian program translation update (Closes: 898797) [ Frans Spiesschaert ] * Dutch program translation update (Closes: #900589) * Dutch manpage translation update (Closes: #900602) -- Julian Andres Klode Tue, 19 Jun 2018 17:12:51 +0200 ** Changed in: apt (Ubuntu) Status: Fix Committed => Fix Released -- 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/1766542 Title: Installation blocks when the machine is behind a proxy server Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Incomplete Status in apt source package in Bionic: New Status in ubiquity source package in Bionic: New Bug description: When the machine is behind a proxy server, the installation will block for a while (several minutes) to retrieve the package lists. The timeouts are too long and makes user feels the machine may have some problems. The symptom is similar with bug #14599, but it seems the apt-setup module was rewritten. Another method to trigger this issue is to make the machine cannot access to the Internet, for instance: a wrong gateway. Image: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773992] Re: apt-key adv should gpgconf --kill all the things after execution
This bug was fixed in the package apt - 1.7.0~alpha0ubuntu2 --- apt (1.7.0~alpha0ubuntu2) cosmic; urgency=medium [ David Kalnischkies ] * Add boilerplate plural form to po/apt-all.pot * don't try SRV requests based on IP addresses * use 127.0.0.1 instead of localhost as default Tor proxy * Extend apt build-dep pkg/release to switch dep as needed * Support release selector for volatile files as well * Start pkg records for deb files with dpkg output * Deprectate buggy/incorrect Rls/PkgFile::IsOk methods * Support --with-source in show & search commands * Support local files as arguments in show command (Closes: 883206) * Drop alternative URIs we got a hash-based fail from * Handle by-hash URI construction more centrally * Don't force the same mirror for by-hash URIs * Reword error for timed out read/write on SOCKS proxy (Closes: #898886) * Don't show acquire warning for "hidden" components (Closes: #879591) * Use a steady clock source for progress reporting * Use steady clock source for bandwidth limitation [ Filipe Brandenburger ] * Update .gitignore * Increase debug verbosity in `apt-get autoremove` * Extend test-apt-get-autoremove to check debug output [ Julian Andres Klode ] * tests: Do not expect requested-by if sudo was invoked by root * Run tests on GitLab CI * Handle a missed case of timed out ip addresses (LP: #1766542) * Lower default timeout from 120s to 30s * apt-key: Pass all instead of gpg-agent to gpgconf --kill (LP: #1773992) * Fix lock counting in debSystem [ annadane ] * Add verb 'be' to NEWS entry for 1.5~beta1 (Closes: 892792) [ Алексей Шилин ] * Russian program translation update (Closes: 898797) [ Frans Spiesschaert ] * Dutch program translation update (Closes: #900589) * Dutch manpage translation update (Closes: #900602) -- Julian Andres Klode Tue, 19 Jun 2018 17:12:51 +0200 ** Changed in: apt (Ubuntu) Status: Fix Committed => Fix Released -- 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/1773992 Title: apt-key adv should gpgconf --kill all the things after execution Status in apt package in Ubuntu: Fix Released Bug description: apt-key adv should gpgconf --kill all the things after execution to ensure that e.g. dirmngr processes are not left hanging around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1773992/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509562] Re: no icons for menu, folders, directories, files
Still present in 18.04. Installing Oxygen theme and systemsettings and setting substitutions icons to oxygen solves the problem. TODO: Add to some package configure script! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1509562 Title: no icons for menu, folders, directories, files Status in dolphin package in Ubuntu: Confirmed Status in kate package in Ubuntu: Confirmed Status in kdepim package in Ubuntu: Confirmed Status in konsole package in Ubuntu: Confirmed Status in kstars package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: no icons for menu, folders, directories, files I am using Xubuntu 15.10 as the Guest in Virtualbox 5.0.8 r103449. This happened after a recent Xubuntu update. Info: $ apt-cache policy dolphin dolphin: Installed: 4:15.08.2-0ubuntu1 Candidate: 4:15.08.2-0ubuntu1 Version table: *** 4:15.08.2-0ubuntu1 0 500 http://mirror.cogentco.com/pub/linux/ubuntu/ wily/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: dolphin 4:15.08.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Fri Oct 23 17:35:08 2015 InstallationDate: Installed on 2015-06-01 (144 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150521) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dolphin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1509562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772542] Re: after waking from sleep i get text radeon error message then return login screen
** Description changed: my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE desktops added) I sleep my XFCE (xubuntu) machine rather than turning it off at night. Today as with yesterday morning, instead of getting the locker-screen after hitting the power-button to wake my machine, i get a blank screen with a RADEON two-line text message top left on screen which appear only momentarily as screen is erased and I get the login/greeter screen. (it's happened 4-5 times, but does NOT happen every time) I can login fine, but my xfce session is new. I have grep'd for the message I see (yesterday & today), but can't find it as i usually recall little but the radeon word... sudo lshw -C video *-display description: VGA compatible controller product: Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:e000-efff memory:f7de-f7df ioport:dc00(size=256) memory:c-d guiverc@d960-ubu2:/var/crash$ pwd /var/crash guiverc@d960-ubu2:/var/crash$ ls -la total 35332 drwxrwsrwt 2 rootwhoopsie 4096 May 22 09:41 . drwxr-xr-x 15 rootroot 4096 Nov 16 2017 .. -rw-r- 1 guiverc whoopsie50003 May 21 10:32 _usr_bin_caffeine.1000.crash -rw-r- 1 guiverc whoopsie 880121 May 21 10:33 _usr_bin_light-locker.1000.crash -rw-rw-r-- 1 guiverc whoopsie0 May 21 10:33 _usr_bin_light-locker.1000.upload -rw-r- 1 guiverc whoopsie 35234566 May 21 10:32 _usr_lib_xorg_Xorg.1000.crash (these files are dated yesteday - i didn't find anything for today) extract of /var/log/auth.log (copied from `view` hence line numbers) // last-night - 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) - 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered - 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered - 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) + 48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) + 49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered + 50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered + 51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) // overnight - 52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session opened for user root by (uid=0) - 53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session closed for user root - 54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered - 55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered - 56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) - 57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' finished. - 58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): session closed for user guiverc - 59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed for user root - 60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. - 61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. - 62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22. - 63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus) - 64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting. - 65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22. - 66
[Touch-packages] [Bug 1746638] Re: [GeForce 6150SE nForce 430] PC freezes and crashes
I can confirm I'm having the same problem. This problem arised to me since Debian Jessie. The workaround was to install Nvidia proprietary drivers, but support for nvidia-304xx was dropped on Xorg 1.20. Adding "NvMSI=0 NvPCIE=0" to kernel boot line seems to make crashes less predictable. The only workaround is to boot with "nouveau.noaccel=1" but this make any graphical application unusably slow. Back to Windows. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1746638 Title: [GeForce 6150SE nForce 430] PC freezes and crashes Status in xorg package in Ubuntu: Confirmed Bug description: When using the nouveau graphics driver my pc freezes and crashes. WORKAROUND: Use the proprietary nvidia driver. WORKAROUND: Use PPA from https://launchpad.net/~oibaf/+archive/ubuntu /graphics-drivers ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Thu Feb 1 01:36:25 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] [1043:8234] InstallationDate: Installed on 2017-11-23 (69 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus CX3900/DX4000/DX4050] Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0602 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N-MX SE Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx: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.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Feb 1 01:34:53 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputHID 1241:1166MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1749722] Re: NTP: take into account systemd-timesyncd where present
This bug is believed to be fixed in cloud-init in version 18.3. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: cloud-init 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/1749722 Title: NTP: take into account systemd-timesyncd where present Status in cloud-init: Fix Released Status in systemd package in Ubuntu: New Bug description: Currently, the NTP module configures ntpd during cloud-init install by installing and configuring ntpd. ntpd competes with systemd-timesyncd on systemd distros like Ubuntu Xenial. Ideally the NTP module should configure systemd-timesyncd where present, falling back to ntpd where not present. This stops two separate daemons (ntpd and systemd-timesyncd) competing with each other to set the time, where systemd-timesyncd (on Ubuntu at least) has an internal hardcoded compiled in timeserver to fall back on if no timeserver is configured (which is bad, but what can you do). The competing timeserver behaviour is invisible when the machine can see the net, but logs this error constantly when the machine cannot see the net: systemd-timesyncd[527]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com). To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1749722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1768230 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: In Progress Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777739] Re: systemd-journald crashed with SIGABRT in pthread_sigmask()
The link to the duplicate bug does not exists anymore. It was https://bugs.launchpad.net/bugs/1761784. I removed the link so this bug can be worked on. ** This bug is no longer a duplicate of private bug 1761784 -- 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/139 Title: systemd-journald crashed with SIGABRT in pthread_sigmask() Status in systemd package in Ubuntu: New Bug description: No clue what caused this. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 Date: Tue Jun 19 07:12:55 2018 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2016-05-22 (757 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard HP EliteBook Folio 9470m ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=en_CA.utf8 LC_MONETARY=unm_US.utf8 LC_NUMERIC=unm_US.utf8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=7ea7dcf2-f245-43a2-807a-8b662df596bb ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: systemd StacktraceTop: pthread_sigmask (how=2, newmask=, oldmask=0x0) at ../sysdeps/unix/sysv/linux/pthread_sigmask.c:50 journal_file_set_offline () from /lib/systemd/libsystemd-shared-237.so ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-237.so Title: systemd-journald crashed with SIGABRT in pthread_sigmask() UpgradeStatus: Upgraded to bionic on 2018-05-19 (31 days ago) UserGroups: sambashare dmi.bios.date: 07/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IBD Ver. F.46 dmi.board.name: 18DF dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 62.17 dmi.chassis.asset.tag: CNU317CDD9 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IBDVer.F.46:bd07/16/2013:svnHewlett-Packard:pnHPEliteBookFolio9470m:pvrA1029C1102:rvnHewlett-Packard:rn18DF:rvrKBCVersion62.17:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook Folio 9470m dmi.product.version: A1029C1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/139/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763611] Re: Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs
*** This bug is a duplicate of bug 1768230 *** https://bugs.launchpad.net/bugs/1768230 ** This bug has been marked a duplicate of bug 1768230 Long time booting : Failed to connect to lvmetad. Falling back to device scanning. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1763611 Title: Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs Status in initramfs-tools package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Fix Released Bug description: See this thread at the Ubuntu Forums: https://ubuntuforums.org/showthread.php?t=2388799 How come the ultra light Lubuntu Bionic needs 40 seconds from the grub menu to the log in screen, while the corresponding Kubuntu and Xubuntu Bionic can do it in 10 seconds in my Toshiba laptop? All the operating systems were installed from the Bionic Beta-2 desktop 64-bit iso files and made up to date today (and reside in a new SSD connected via the internal SATA bay). -o- and to summarize the conclusion https://ubuntuforums.org/showthread.php?t=2388799&page=2&p=13756324#post13756324 This supports the assumption, that there are problems for Lubuntu to manage SSDs with 4096 byte size physical sectors. But the other flavours of Ubuntu can manage it. Let us hope that this can help the Lubuntu developer to find and squash the bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lubuntu-desktop 0.93 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Apr 13 09:59:42 2018 InstallationDate: Installed on 2018-04-06 (7 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180405) SourcePackage: lubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1763611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
If the output is that which you posted in comment #25: I: The initramfs will attempt to resume from /dev/dm-1 I: (/dev/mapper/xubuntu--vg-swap_1) ... then that is exactly what we *expect* to see as the output and it needs investigating why this does not take precedence over /etc /initramfs-tool/conf.d/resume for you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: In Progress Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Upgrading initramfs-tools to 0.130ubuntu3.2 should be sufficient to resolve the symptom of this bug, even with a broken /etc/initramfs- tools/conf.d/resume still on disk. Marc, when you are able to still reproduce this bug with initramfs-tools 0.130ubuntu3.2, what is the full output of 'sudo update-initramfs -u'? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: In Progress Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667512] Re: update-initramfs hangs on upgrade, dpkg unusable, unbootable system
** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Triaged ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1667512 Title: update-initramfs hangs on upgrade, dpkg unusable, unbootable system Status in initramfs-tools package in Ubuntu: Triaged Bug description: At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. vmlinuz(/boot/vmlinuz-4.4.0-63-generic ) points to /boot/vmlinuz-4.4.0-63-generic (/boot/vmlinuz-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic ^CFailed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 1052. dpkg: error processing package linux-image-4.4.0-63-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-4.4.0-63-generic; however: Package linux-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-signed-image-4.4.0-63-generic: linux-signed-image-4.4.0-63-generic depends on linux-image-4.4.0-63-generic (= 4.4.0-63.84); however: Package linux-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-signed-image-4.4.0-63-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-signed-image-generic: linux-signed-image-generic depends on linux-signed-image-4.4.0-63-generic; however: Package linux-signed-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-signed-image-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-extra-4.4.0-63-generic: linux-image-extra-4.4.0-63-generic depends on linux-image-4.4.0-63-generic; however: Package linux-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-image-extra-4.4.0-63-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic:
[Touch-packages] [Bug 736349] Re: "Test speakers" is silent
> For me, installing libcanberra-pulse worked. So many thanks for this! This is still required to fix things on Ubuntu 18.04! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-sounds in Ubuntu. https://bugs.launchpad.net/bugs/736349 Title: "Test speakers" is silent Status in OEM Priority Project: Fix Released Status in gnome-media package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Invalid Status in ubuntu-sounds package in Ubuntu: Invalid Bug description: Binary package hint: gnome-media My speakers are working fine (I can year playback with Banshee and VLC), but "Test speakers" is silent. I hear nothing when I press on the "Test" button. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-media 2.32.0-0ubuntu5 Uname: Linux 2.6.38-020638-generic x86_64 Architecture: amd64 Date: Wed Mar 16 20:30:19 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100921.1) ProcEnviron: LANGUAGE=de_DE:en LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-media UpgradeStatus: Upgraded to natty on 2011-03-11 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/736349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667512] Re: update-initramfs hangs on upgrade, dpkg unusable, unbootable system
Re comment #7, coreutils 8.24 added the ability to do "sync -f FILENAME" to sync only the file system containing FILENAME. I think update- initramfs should probably be changed to use that in xenial and newer. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1667512 Title: update-initramfs hangs on upgrade, dpkg unusable, unbootable system Status in initramfs-tools package in Ubuntu: Confirmed Bug description: At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. vmlinuz(/boot/vmlinuz-4.4.0-63-generic ) points to /boot/vmlinuz-4.4.0-63-generic (/boot/vmlinuz-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic ^CFailed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 1052. dpkg: error processing package linux-image-4.4.0-63-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-4.4.0-63-generic; however: Package linux-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-signed-image-4.4.0-63-generic: linux-signed-image-4.4.0-63-generic depends on linux-image-4.4.0-63-generic (= 4.4.0-63.84); however: Package linux-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-signed-image-4.4.0-63-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-signed-image-generic: linux-signed-image-generic depends on linux-signed-image-4.4.0-63-generic; however: Package linux-signed-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-signed-image-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-extra-4.4.0-63-generic: linux-image-extra-4.4.0-63-generic depends on linux-image-4.4.0-63-generic; however: Package linux-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-image-extra-4.4.0-63-generic (--configure): dependency problems - leaving unconfigured dpkg:
[Touch-packages] [Bug 1667512] Re: update-initramfs hangs on upgrade, dpkg unusable, unbootable system
(A versioned Depends or versioned Breaks as appropriate on coreutils would probably be a good idea, at least in xenial to avoid upgrade problems from trusty.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1667512 Title: update-initramfs hangs on upgrade, dpkg unusable, unbootable system Status in initramfs-tools package in Ubuntu: Confirmed Bug description: At least four users, including myself, are having an issue with update-initramfs hanging while updating ubuntu 16.04. The bug has been documented while attempting an update to multiple kernel versions ( 4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or install to fail, and may also lead to an unbootable system. User #1 (me): $ uname -a Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt-get upgrade Fetched 1,571 MB in 2min 9s (12.2 MB/s) Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 344634 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ... Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.7.5-1) ... Processing triggers for cracklib-runtime (2.9.2-1build2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for initramfs-tools (0.122ubuntu8.8) ... update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic Uh oh! Let's try to troubleshoot. $ sudo killall dpkg $ sudo dpkg --configure -a Setting up initramfs-tools (0.122ubuntu8.8) ... update-initramfs: deferring update (trigger activated) Setting up base-files (9.4ubuntu4.4) ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ... Running depmod. update-initramfs: deferring update (hook will be called later) initrd.img(/boot/initrd.img-4.4.0-63-generic ) points to /boot/initrd.img-4.4.0-63-generic (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. vmlinuz(/boot/vmlinuz-4.4.0-63-generic ) points to /boot/vmlinuz-4.4.0-63-generic (/boot/vmlinuz-4.4.0-63-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-63-generic /boot/vmlinuz-4.4.0-63-generic update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic ^CFailed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 1052. dpkg: error processing package linux-image-4.4.0-63-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-4.4.0-63-generic; however: Package linux-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-signed-image-4.4.0-63-generic: linux-signed-image-4.4.0-63-generic depends on linux-image-4.4.0-63-generic (= 4.4.0-63.84); however: Package linux-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-signed-image-4.4.0-63-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-signed-image-generic: linux-signed-image-generic depends on linux-signed-image-4.4.0-63-generic; however: Package linux-signed-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-signed-image-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-extra-4.4.0-63-generic: linux-image-extra-4.4.0-63-generic depends on linux-image-4.4.0-63-generic; however: Package linux-image-4.4.0-63-generic is not configured yet. dpkg: error processing package linux-image-extra-4.4.0-63-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-
[Touch-packages] [Bug 1777706] Re: modemmanager 1.7.990-1ubuntu1
** Tags added: cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/106 Title: modemmanager 1.7.990-1ubuntu1 Status in modemmanager package in Ubuntu: Confirmed Bug description: modemmanager 1.7.990-1ubuntu1 not working in Cosmic. Need to downgrade to modemmanager 1.6.8-2ubuntu1 to have mobile broadband working again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/106/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777902] [NEW] In Xubuntu, unable to set the printer property to black & white
Public bug reported: In Xubuntu, system-config-printer does not allow to set the printer by default on "Black and white". The only choice is "Color". system-config-printer version: 1.5.11 Xubuntu: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic Printer: HP Envy 4500 ** Affects: address-book-app (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Capture d’écran_2018-06-20_17-36-34.png" https://bugs.launchpad.net/bugs/1777902/+attachment/5154689/+files/Capture%20d%E2%80%99%C3%A9cran_2018-06-20_17-36-34.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1777902 Title: In Xubuntu, unable to set the printer property to black & white Status in address-book-app package in Ubuntu: New Bug description: In Xubuntu, system-config-printer does not allow to set the printer by default on "Black and white". The only choice is "Color". system-config-printer version: 1.5.11 Xubuntu: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic Printer: HP Envy 4500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1777902/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 827151] Re: Annoying log message "DIGEST-MD5 common mech free"
Hello Also in xenial but in the apache log I found Jun 20 10:44:05 localhost apache2: DIGEST-MD5 common mech free Jun 20 10:44:53 localhost apache2: message repeated 22 times: [ DIGEST-MD5 common mech free] dpkg -l libsasl2-modules Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-===-===-=== ii libsasl2-modules:amd642.1.26.dfsg1-14buil amd64 Cyrus SASL - pluggable authentication modules Cheers Miguel -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/827151 Title: Annoying log message "DIGEST-MD5 common mech free" Status in Cyrus-sasl2: New Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Trusty: Triaged Status in cyrus-sasl2 source package in Xenial: Incomplete Status in cyrus-sasl2 source package in Yakkety: Fix Released Status in cyrus-sasl2 package in Debian: Fix Released Bug description: I recently updated the libsasl2-modules to 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric. That triggered the bug also described in Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932 The annoying message is logged in auth.log. In my case, it is associated with svnserve: svnserve: DIGEST-MD5 common mech free I'm not exactly sure what action triggers the message, but I can investigate more if required. $ lsb_release -rd Description:Ubuntu oneiric (development branch) Release:11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'
Hello Mathieu, or anyone else affected, Accepted initramfs-tools into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.125ubuntu12.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. 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! ** Changed in: initramfs-tools (Ubuntu Artful) Status: Confirmed => Fix Committed ** Tags added: verification-needed-artful ** Changed in: initramfs-tools (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1769682 Title: NFS-based remote root hangs when running 'netplan apply' Status in initramfs-tools package in Ubuntu: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Invalid Status in initramfs-tools source package in Xenial: Fix Committed Status in netplan.io source package in Xenial: Invalid Status in nplan source package in Xenial: Fix Released Status in initramfs-tools source package in Artful: Fix Committed Status in netplan.io source package in Artful: Invalid Status in nplan source package in Artful: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in netplan.io source package in Bionic: Fix Released Status in nplan source package in Bionic: Invalid Bug description: [Impact] Netboot users with a remote filesystem over NFS (possibly over other networked filesystems). [Test cases] 1) Boot a system with its root filesystem over NFS. 2) Run 'sudo netplan apply' 3) Validate that the system remains responsive and keeps connectivity over the same IP address as it had. [Regression potential] This SRU changes network properties, and enforces that networkd does not release and re-request an IP address from DHCP when it is restarted. Environments relying on the IP release/renew behavior may find themselves staying on the previous IP address, which might negatively impact connectivity. Changes in connectivity on a system running netplan should be investigated as a potential regression from this SRU. Other regression possibilities would include failure to get a new IP address over time (usually seen as losing connectivity) or possible IP conflicts on a network. --- With a system booted on the network, with its remote root fs on NFS: Running 'netplan apply' restarts systemd-networkd, which releases the IP received from DHCP. With no IP (and and IP potentially changing), the NFS server can't be reached so the system hangs. 'netplan apply' or restarting systemd-networkd should not affect teh system, it should continue working normally despite "changing" network states, as long as the effective IP remains the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769682] Please test proposed package
Hello Mathieu, or anyone else affected, Accepted initramfs-tools into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.122ubuntu8.12 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1769682 Title: NFS-based remote root hangs when running 'netplan apply' Status in initramfs-tools package in Ubuntu: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Invalid Status in initramfs-tools source package in Xenial: Fix Committed Status in netplan.io source package in Xenial: Invalid Status in nplan source package in Xenial: Fix Released Status in initramfs-tools source package in Artful: Fix Committed Status in netplan.io source package in Artful: Invalid Status in nplan source package in Artful: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in netplan.io source package in Bionic: Fix Released Status in nplan source package in Bionic: Invalid Bug description: [Impact] Netboot users with a remote filesystem over NFS (possibly over other networked filesystems). [Test cases] 1) Boot a system with its root filesystem over NFS. 2) Run 'sudo netplan apply' 3) Validate that the system remains responsive and keeps connectivity over the same IP address as it had. [Regression potential] This SRU changes network properties, and enforces that networkd does not release and re-request an IP address from DHCP when it is restarted. Environments relying on the IP release/renew behavior may find themselves staying on the previous IP address, which might negatively impact connectivity. Changes in connectivity on a system running netplan should be investigated as a potential regression from this SRU. Other regression possibilities would include failure to get a new IP address over time (usually seen as losing connectivity) or possible IP conflicts on a network. --- With a system booted on the network, with its remote root fs on NFS: Running 'netplan apply' restarts systemd-networkd, which releases the IP received from DHCP. With no IP (and and IP potentially changing), the NFS server can't be reached so the system hangs. 'netplan apply' or restarting systemd-networkd should not affect teh system, it should continue working normally despite "changing" network states, as long as the effective IP remains the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750465] Re: upgrade attempting to process triggers out of order (package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving trig
Dear Kubuntu, Mate, and Gnome flavour folks: Please also fix the bug in stable releases. -- 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/1750465 Title: upgrade attempting to process triggers out of order (package plymouth- theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed) Status in apt package in Ubuntu: Invalid Status in budgie-artwork package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Fix Released Status in ubuntu-gnome-default-settings package in Ubuntu: Fix Released Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in apt source package in Xenial: Invalid Status in kubuntu-settings source package in Xenial: Confirmed Status in plymouth source package in Xenial: Fix Released Status in ubuntu-gnome-default-settings source package in Xenial: Confirmed Status in ubuntu-mate-artwork source package in Xenial: Confirmed Status in apt source package in Artful: Invalid Status in budgie-artwork source package in Artful: Fix Released Status in kubuntu-settings source package in Artful: Confirmed Status in plymouth source package in Artful: Fix Released Status in ubuntu-gnome-default-settings source package in Artful: Confirmed Status in ubuntu-mate-artwork source package in Artful: Confirmed Bug description: [SRU Justification] A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail because of trying to process triggers out of order. Since the trigger being run is that of the currently-installed plymouth package, it is not guaranteed to be sufficient to fix the version of the package in 18.04. [Test case] 1. Install plymouth-themes-ubuntu-text from -proposed. 2. Run a release upgrade with each of update-manager -d, do-release-upgrade -d, and apt-get dist-upgrade (the last after manually changing sources.list). 3. Verify that in each case, the upgrade completes successfully, with no errors about out-of-order trigger configuration. [Regression potential] noawait triggers have been supported in dpkg since 1.16.1, which is older than the version in precise (https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html). A noawait trigger is considered appropriate whenever the triggered package does not need to block the triggering package. There is no reason for a plymouth theme package to need to block configuration of an essential package in this case. noawait triggers are well-exercised in the distro now, so the risk of regression from this change should be low. There is unfortunately not a known reproducer for the original bug, so the test case, while it should guard against regressions, is not strong confirmation that the bug is fixed. [Original description] Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Feb 18 23:41:49 2018 DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-10-24 (118 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5567 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.5.1 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth Title: package plymouth-theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-02-19 (0 days ago) dmi.bios.date: 01/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 01W6F7 d
[Touch-packages] [Bug 1583237] Re: lxc-attach strange tty behavior (kills command) when stderr is redirected to a file
Another demonstration: * This one does not work: sudo lxc-attach --name utest_generic_tests -- /bin/bash -c "/usr/bin/python -c 'from ctypes import *; memset(0,1,1)'"; echo $? 0 * This one works: sudo lxc-attach --name utest_generic_tests -- /bin/bash -c "/usr/bin/python -c 'from ctypes import *; memset(0,1,1)' 2>&2"; echo $? /bin/bash: line 1: 2286 Segmentation fault (core dumped) /usr/bin/python -c 'from ctypes import *; memset(0,1,1)' 2>&2 139 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1583237 Title: lxc-attach strange tty behavior (kills command) when stderr is redirected to a file Status in lxc package in Ubuntu: New Bug description: On a fresh Ubuntu 16 release, commands started by lxc-attach such as dd are being killed WHEN REDIRECTING stderr (to a file), and lxc- attach return a zero status. Command works fine without the redirection. This scenario is working on Ubuntu 15 with previous lxc release, but not on new LXC 2.0.0 (same issue on 2.0.1 too) sudo apt-get -y install lxc sudo lxc-create -n utest -t ubuntu -- -a amd64 -b $USER sudo lxc-start -d --name utest sudo lxc-attach -n utest -- dd if=/dev/zero of=/tmp/foo bs=1M count=10 2>/tmp/bar sudo lxc-attach -n utest -- ls -lh /tmp/foo -rw-r--r-- 1 root root 0 May 18 05:46 /tmp/foo Might be related to bug 1553097 (and/or https://github.com/lxc/lxc/pull/873) NOTE: Sometimes the "sudo lxc-attach -n utest_bizio_tests -- ls -lh /tmp/foo" ALSO does not return anything (no output) I'm available for any additional info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1583237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670494] Re: 'wpa_supplicant -D nl80211 -W' hangs with some Intel cards
This is still broken in Artful, but is fixed in Bionic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1670494
Title:
'wpa_supplicant -D nl80211 -W' hangs with some Intel cards
Status in wpa package in Ubuntu:
Confirmed
Bug description:
init_wpa_supplicant() in /etc/wpa_supplicant/functions.sh runs
wpa_supplicant with the -W option, which causes it to wait for wpa_cli
to attach. init_wpa_supplicant() then attaches wpa_cli to
wpa_supplicant.
When the nl80211 driver is used with some Intel cards, wpa_supplicant
automatically defines a second p2p_dev_${WPA_IFACE} interface. If
multiple interfaces are defined in wpa_supplicant, then wpa_supplicant
will wait for multiple wpa_cli instances to attach. Since
init_wpa_supplicant() only attaches a single wpa_cli process, this
causes wpa_supplicant to hang, which ultimately leads to a timeout and
causes interface configuration to fail.
This has been fixed upstream:
http://lists.infradead.org/pipermail/hostap/2015-December/034410.html
And also in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833402
However, the updated wpa_supplicant has not made it to Ubuntu (not
even Zesty), and the "-m ''" workaround mentioned in the mailing list
thread associated with the upstream fix does not work with the version
of wpa_supplicant that comes with Ubuntu.
Could the P2P patches that were merged into Debian be merged into
Ubuntu?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1670494/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761096] Re: dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed
I confirm that every second $ systemctl restart dnsmasq hangs Also I confirm that removing squid resolved the situation. I found that it does this: 1. /bin/sh /etc/init.d/dnsmasq systemd-stop-resolvconf 2. /bin/sh /etc/init.d/dnsmasq systemd-start-resolvconf Both will call hooks like: 0 0 11642 11634 20 0 4364 660 wait S? 0:00 \_ run-parts --arg=-a --arg=lo.dnsmasq /etc/resolvconf/update.d 0 0 11659 11642 20 0 4364 664 wait S? 0:00 \_ run-parts /etc/resolvconf/update-libc.d 0 0 11672 11659 20 0 4504 704 wait S? 0:00 \_ /bin/sh /etc/resolvconf/update-libc.d/squid 0 0 11673 11672 20 0 4504 1648 wait S? 0:00 \_ /bin/sh /usr/sbin/invoke-rc.d squid reload 4 0 11691 11673 20 0 24888 1388 poll_s S? 0:00 \_ systemctl reload squid.service This is what actually times out - the squid hook. The "systemctl reload squid.service" call seems to take too long every second time?! A single "systemctl reload squid.service" for these seems to take ~100 seconds for me. OTOH a direct call to it is fast every time. This needs to be debugged in detail, but seems well reproducible. ** Also affects: dnsmasq (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: dnsmasq (Ubuntu Xenial) Status: New => Confirmed ** Changed in: dnsmasq (Ubuntu) Status: New => Fix Released ** Changed in: dnsmasq (Ubuntu Xenial) Importance: Undecided => High ** Tags added: server-next ** Also affects: squid (Ubuntu) Importance: Undecided Status: New ** Changed in: squid (Ubuntu Xenial) Status: New => Confirmed ** Changed in: squid (Ubuntu Xenial) Importance: Undecided => High ** Changed in: squid (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1761096 Title: dnsmasq starts with error on Ubuntu Xenial amd64 when squid installed Status in dnsmasq package in Ubuntu: Fix Released Status in squid package in Ubuntu: Fix Released Status in dnsmasq source package in Xenial: Confirmed Status in squid source package in Xenial: Confirmed Bug description: Setup to reproduce: Ubuntu Xenial amd64 net install iso from http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer- amd64/current/images/netboot/mini.iso Install system with mostly defaults + LVM + OpenSSH server Note that this bug applies to both DHCP and static IP+DNS network configurations Once server rebooted and is available, log in and install dnsmasq + squid: apt-get update && apt-get install squid dnsmasq output of this can be found at https://pastebin.com/9Atuipju journalctl -xe output at https://pastebin.com/uLhfM4jN Furthermore at this point I can run alternating errors root@ubuntu-min:~# date ; service dnsmasq start ; date Wed Apr 4 09:18:07 CEST 2018 Wed Apr 4 09:18:07 CEST 2018 root@ubuntu-min:~# date ; service dnsmasq stop ; date Wed Apr 4 09:18:39 CEST 2018 Wed Apr 4 09:18:39 CEST 2018 root@ubuntu-min:~# date ; service dnsmasq start ; date Wed Apr 4 09:19:10 CEST 2018 Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl status dnsmasq.service" and "journalctl -xe" for details. Wed Apr 4 09:20:40 CEST 2018 root@ubuntu-min:~# date ; service dnsmasq start ; date Wed Apr 4 09:42:57 CEST 2018 Wed Apr 4 09:42:57 CEST 2018 root@ubuntu-min:~# date ; service dnsmasq stop ; date Wed Apr 4 09:43:14 CEST 2018 Wed Apr 4 09:43:14 CEST 2018 root@ubuntu-min:~# date ; service dnsmasq start ; date Wed Apr 4 09:43:26 CEST 2018 Job for dnsmasq.service failed because a timeout was exceeded. See "systemctl status dnsmasq.service" and "journalctl -xe" for details. Wed Apr 4 09:44:56 CEST 2018 and so on... Each and every 1 out of 2 stop/start cycle fails in 1m30s timeout Complete journalctl -xe output attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1761096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707136] Re: ryncd does not start when RSYNC_ENABLE is specified
Per former comments marking as fixed and adding Xenial task. It is still an issue in Xenial, but since no one here was participating I wonder about the severity. Also we would certainly not backport the fix that was taken. I filtered it a bit and it looks like http://paste.ubuntu.com/p/TNvQpqbNRb/ So with that you still won't be able to get it through /etc/default/rsyncd. All you'd find is a comment in there how to do it now. Marking it low due to that ** Also affects: rsync (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: rsync (Ubuntu) Status: Confirmed => Fix Released ** Changed in: rsync (Ubuntu Xenial) Status: New => Triaged ** Changed in: rsync (Ubuntu Xenial) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1707136 Title: ryncd does not start when RSYNC_ENABLE is specified Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Xenial: Triaged Status in rsync package in Debian: Fix Released Bug description: In the good old days, all you needed to ensure rsyncd started upon boot was to set RSYNC_ENABLE to true in /etc/default/rsync. With the systemd transition, this broke, and you need to manually issue systemctl enable rsync in order for it to be wanted by multi-user.target, which causes it to start upon boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1707136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1743873] Re: rsync version for xenial
For the usual SRU policy [1] it is unlikely and would require a lot of exceptions and checks to take the full 3.1.2. You'd really have to show that it is not working at all. Otherwise usually only individual fixes are backported. The other issue you mentioned is already tracked on it's own so I won't consider that for the xenial task here for it. [1]: https://wiki.ubuntu.com/StableReleaseUpdates ** Also affects: rsync (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: rsync (Ubuntu) Status: Confirmed => Fix Released ** Changed in: rsync (Ubuntu Xenial) Status: New => Opinion ** Changed in: rsync (Ubuntu Xenial) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1743873 Title: rsync version for xenial Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Xenial: Opinion Status in rsync package in Debian: Fix Released Bug description: Any chance that rsync could be updated to 3.1.2 for xenial? The --backup-dir option in 3.1.1 doesn't work properly - it creates empty directories even when no files need to be put in them. Thanks, -Jeff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1743873/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
** Summary changed: - python3-minimal should depend on versioned version of python3-minimal + python3-minimal should predepend on versioned version of python3-minimal -- 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/1768379 Title: python3-minimal should predepend on versioned version of python3-minimal Status in python3-defaults package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: do-release-upgrade -d on my 16.04 LTS unity laptop lead to an install failure: Fetched 2,320 MB in 6s (27.8 MB/s) Upgrading Inhibiting until Ctrl+C is pressed... Fetched 0 B in 0s (0 B/s) Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file Extracting templates from packages: 100% Preconfiguring packages ... setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file (Reading database ... 373383 files and directories currently installed.) Preparing to unpack .../base-files_10.1ubuntu2_amd64.deb ... Unpacking base-files (10.1ubuntu2) over (9.4ubuntu4.6) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ... update-initramfs: deferring update (trigger activated) Processing triggers for cracklib-runtime (2.9.2-1ubuntu1) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic Setting up base-files (10.1ubuntu2) ... Installing new version of config file /etc/debian_version ... Installing new version of config file /etc/issue ... Installing new version of config file /etc/issue.net ... Installing new version of config file /etc/lsb-release ... Updating /etc/profile to current default. motd-news.service is a disabled or a static unit, not starting it. Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.4) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.122ubuntu8.11) ... update-initramfs: Generating /boot/initrd.img-4.4.0-122-generic (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../debianutils_4.8.4_amd64.deb ... Unpacking debianutils (4.8.4) over (4.7) ... Processing triggers for man-db (2.7.5-1) ... Setting up debianutils (4.8.4) ... (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../bash_4.4.18-2ubuntu1_amd64.deb ... Unpacking bash (4.4.18-2ubuntu1) over (4.3-14ubuntu1.2) ... Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for man-db (2.7.5-1) ... Setting up bash (4.4.18-2ubuntu1) ... Installing new version of config file /etc/bash.bashrc ... Installing new version of config file /etc/skel/.profile ... update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode (Reading database ... 373388 files and directories currently installed.) Preparing to unpack .../libcomerr2_1.44.1-1_amd64.deb ... Unpacking libcomerr2:amd64 (1.44.1-1) over (1.42.13-1ubuntu1) ... Selecting previously unselected package libcom-err2:amd64. Preparing to unpack .../libcom-err2_1.44.1-1_amd64.deb ... Unpacking libcom-err2:amd64 (1.44.1-1) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Setting up libcom-err2:amd64 (1.44.1-1) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... (Reading database ... 373391 files and directories currently installed.) Preparing to unpack .../libkeyutils1_1.5.9-9.2ubuntu2_amd64.deb ... Unpacking libkeyutils1:amd64 (1.5.9-9.2ubuntu2) over (1.5.9-8ubuntu1) ... Preparing to unpack .../libk5crypto3_1.16-2build1_amd64.deb ... Unpacking libk5crypto3:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../libkrb5support0_1.16-2build1_amd64.deb ... Unpacking libkrb5support0:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../libgssapi-krb5-2_1.16-2build1_amd64.deb ... Unpacking libgssapi-krb5-2:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack .../libkrb5-3_1.16-2build1_amd64.deb ... Unpacking libkrb5-3:amd64 (1.16-2build1) over (1.13.2+dfsg-5ubuntu2) ... Preparing to unpack
[Touch-packages] [Bug 1773334] Re: Ubuntu 18.04 mounted network shares not appearing under devices in file manager
I have patched glib to fix this. Could you try the version in my PPA and verify that it works? -- 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/1773334 Title: Ubuntu 18.04 mounted network shares not appearing under devices in file manager Status in glib2.0 package in Ubuntu: Triaged Bug description: Apologies if this is not the correct package to file this bug/regression against. On my 18.04 desktop installs (Gnome shell and Ubuntu Mate) when mounting network shares (SMB and NFS) they no longer appear under Devices in file manager (Nautilus or Caja), the mounts do succeed and are accessible at their mount points. In 16.04 and 17.10 these mounts appeared under Devices (Screenshot of mounted network shares on Ubuntu Mate 17.10 attached) I am using the following code to mount NFS shares `sudo mount.nfs 192.168.2.123:/mnt/freenas-data1/photobackup /media/philroche/photobackup` and for SMB shares `sudo mount.cifs //192.168.2.123/photobackup /media/philroche/photobackup` Is this a bug/regression, or perhaps it is an intentional change? I did ask this on IRC in #ubuntu and askubuntu.com but no reply. Expected behaviour: I expected the mounted network shares to appear under Devices in File manager Actual behaviour: Mounting network shares does succeed as expected but does not appear under Devices in File manager as it did in previous releases. Requested details: Description: Ubuntu 18.04 LTS Release: 18.04 udisks2: Installed: 2.7.6-3 Candidate: 2.7.6-3 Version table: *** 2.7.6-3 500 500 http://ie.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1773334/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1745664] Re: systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create()
My computer continues to crash on a daily basis. It locks up and reboots. And this error report pops up. I've no idea how to track this down. I tried enabling kdump-tools but couldn't get it to work. System would not reboot into kdump kernel when I manually triggered the test crash. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1745664 Title: systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create() Status in systemd package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3 --- configured system to use nis. seems to be crashing when I attempt to use a NIS user account ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Fri Jan 26 13:45:06 2018 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2018-01-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at ../sysdeps/unix/sysv/linux/connect.c:26 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153 __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106 __GI_pmap_getport (address=address@entry=0x7ffc27302060, program=program@entry=17, version=version@entry=2, protocol=protocol@entry=6) at pm_getport.c:154 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136 SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-logind crashed with SIGABRT in __libc_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys sysdesign tty uucp dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1745664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771539] Re: Xorg crash
Since I've reinstalled the ubuntu 16.04, the problem persists, but the kernel parameter (radeon.runpm=0) is no longer present. I'll provide another log dump, when as soon as the problem occurs again. mc -- 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/1771539 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: When I try to use ubuntu with dual desktop display it crashes continuously, and entering into login mode. I cannot use dual display. To use an external monitor, I have to start the laptop with the computer closed. It seems to be related to the graphic card, maybe dual graphic card of the laptop. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Classic:GNOME Date: Wed May 16 10:36:05 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990] InstallationDate: Installed on 2017-12-13 (153 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=e1833df7-4a4b-41b2-8393-d88536dd0165 ro quiet splash radeon.runpm=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.39 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: 5CG44010XD dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.39:bd09/26/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Mar 8 12:39:32 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 677743]
http://wow.honeyrum.com
Doug Greenstein
--
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/677743
Title:
[Realtek ALC662 rev1] Playback problem Rhythm box will not play. there
is no sound. I may have erased some necessary sub programs while I was
trying to get real player to work.
Status in alsa-driver package in Ubuntu:
Invalid
Bug description:
I'm a novice to computers and Linux. Have the latest version of Ubuntu
which I down-loaded a few days ago. The Rhythm box player was working
fine when I first used it. As I said I added some GStreamer components
which than caused the Rhythm box not to work and then I undid them.
The real player still doesn't work. I really didn't know what I was
doing!
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: alsa-base 1.0.23+dfsg-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: NVidia [HDA NVidia], device 0: ALC662 rev1 Analog [ALC662 rev1
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: douglas1641 F pulseaudio
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xfbef8000 irq 22'
Mixer name : 'Realtek ALC662 rev1'
Components : 'HDA:10ec0662,103c2a99,00100101'
Controls : 18
Simple ctrls : 11
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbfec000 irq 44'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100100'
Controls : 4
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Fri Nov 19 23:25:32 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
PackageArchitecture: all
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SelectedCard: 0 NVidia HDA-Intel - HDA NVidia
SourcePackage: alsa-driver
Symptom: audio
Title: [Realtek ALC662 rev1] Playback problem
dmi.bios.date: 11/06/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.15
dmi.board.name: Narra6
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 6.01
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.15:bd11/06/2009:svnHP-Pavilion:pnAY643AA-ABAs5310f:pvr:rvnPEGATRONCORPORATION:rnNarra6:rvr6.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: AY643AA-ABA s5310f
dmi.sys.vendor: HP-Pavilion
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/677743/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576353] Re: Install openssh-server with disabled password auth by default on servers
** Tags added: id-5a4c19be676c7709fe6b2d20 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1576353 Title: Install openssh-server with disabled password auth by default on servers Status in Ubuntu CD Images: In Progress Status in livecd-rootfs package in Ubuntu: New Status in openssh package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: New Bug description: we want to remove 'cloud-image' seed and join it with 'server' seed. openssh-server is one of the few (3) packages that are in cloud image and not in 'ubuntu-server'. We'd like to have the server iso install openssh-server by default and prompt the user if they want to enable it or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1576353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777870] [NEW] package console-setup 1.108ubuntu15.4 [origin: Ubuntu] failed to install/upgrade: problemas de dependencias - se deja sin configurar
Public bug reported: No hablo ingles, pero entiendo un poco y me dice algo sobre un error en la consola ProblemType: Package DistroRelease: elementary 0.4.1 Package: console-setup 1.108ubuntu15.4 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Jun 20 08:17:27 2018 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2018-01-15 (155 days ago) InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921) Keyboard: XKBLAYOUT="latam" XKBVARIANT="" BACKSPACE="guess" XKBMODEL="pc105" XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll" PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: console-setup Title: package console-setup 1.108ubuntu15.4 [origin: Ubuntu] failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package loki third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1777870 Title: package console-setup 1.108ubuntu15.4 [origin: Ubuntu] failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in console-setup package in Ubuntu: New Bug description: No hablo ingles, pero entiendo un poco y me dice algo sobre un error en la consola ProblemType: Package DistroRelease: elementary 0.4.1 Package: console-setup 1.108ubuntu15.4 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Jun 20 08:17:27 2018 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2018-01-15 (155 days ago) InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921) Keyboard: XKBLAYOUT="latam" XKBVARIANT="" BACKSPACE="guess" XKBMODEL="pc105" XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll" PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: console-setup Title: package console-setup 1.108ubuntu15.4 [origin: Ubuntu] failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1777870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777476] Re: non-installable in chroots without udev installed due to bad postinst file
Selecting previously unselected package rfkill. (Reading database ... 12129 files and directories currently installed.) Preparing to unpack rfkill_0.5-1ubuntu3.1_amd64.deb ... Unpacking rfkill (0.5-1ubuntu3.1) ... Setting up rfkill (0.5-1ubuntu3.1) ... I like it! ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1777476 Title: non-installable in chroots without udev installed due to bad postinst file Status in rfkill package in Ubuntu: Fix Released Status in rfkill source package in Xenial: Fix Committed Status in rfkill source package in Artful: Won't Fix Bug description: [Impact] packages using rfkill in build-dependencies are not installable. [Test Case] Install rfkill in a chroot without udev installed Unpacking rfkill (0.5-1ubuntu3) ... Setting up rfkill (0.5-1ubuntu3) ... /var/lib/dpkg/info/rfkill.postinst: 5: /var/lib/dpkg/info/rfkill.postinst: udevadm: not found dpkg: error processing package rfkill (--configure): subprocess installed post-installation script returned error exit status 127 [Regression Potential] * None, udev is already installed in user machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1777476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777476] Re: non-installable in chroots without udev installed due to bad postinst file
Hello LocutusOfBorg, or anyone else affected, Accepted rfkill into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/rfkill/0.5-1ubuntu3.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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: rfkill (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1777476 Title: non-installable in chroots without udev installed due to bad postinst file Status in rfkill package in Ubuntu: Fix Released Status in rfkill source package in Xenial: Fix Committed Status in rfkill source package in Artful: Won't Fix Bug description: [Impact] packages using rfkill in build-dependencies are not installable. [Test Case] Install rfkill in a chroot without udev installed Unpacking rfkill (0.5-1ubuntu3) ... Setting up rfkill (0.5-1ubuntu3) ... /var/lib/dpkg/info/rfkill.postinst: 5: /var/lib/dpkg/info/rfkill.postinst: udevadm: not found dpkg: error processing package rfkill (--configure): subprocess installed post-installation script returned error exit status 127 [Regression Potential] * None, udev is already installed in user machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1777476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442915] Re: Missing package installation console output message in gdebi-kde
** Changed in: gdebi Status: Unknown => 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/1442915 Title: Missing package installation console output message in gdebi-kde Status in gdebi: New Status in gdebi package in Ubuntu: New Bug description: As attached screenshot, no console output is listed in the "Show details" textbox during package installation. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gdebi-kde 0.9.5.3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 CurrentDesktop: KDE Date: Sat Apr 11 23:35:47 2015 PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdebi/+bug/1442915/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
This bug was fixed in the package menu - 2.1.47ubuntu2.1 --- menu (2.1.47ubuntu2.1) bionic; urgency=medium * Switch triggers to use noawait (LP: #1768905) -- Julian Andres Klode Tue, 05 Jun 2018 10:48:23 -0700 ** Changed in: menu (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1768905 Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Incomplete Status in menu package in Ubuntu: Fix Released Status in apt source package in Xenial: Confirmed Status in menu source package in Xenial: Fix Committed Status in apt source package in Artful: Confirmed Status in menu source package in Artful: Fix Released Status in apt source package in Bionic: Confirmed Status in menu source package in Bionic: Fix Released Status in menu package in Debian: New Bug description: [Impact] Breaks some upgrades, depending on install order. [Test case] N/A. After consultation with the dpkg maintainer and investigating the situation, it's reasonably safe to assume that noawait is the right thing to do: * the intended use for the trigger is to run _after_ packages with .menu files are configured, not before; therefore * the file trigger is triggered manually from the postinst again, discussion has been that the file trigger is not actually needed. [Regression potential] Menu might not be updated correctly [Original bug report] I get this error when I update to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: menu 2.1.47ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 16:51:28 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 libstdc++6 8-20180414-1ubuntu2 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2018-04-11 (22 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 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.1 SourcePackage: menu Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777856] [NEW] Gedit opens files in new windows instead of new tabs
Public bug reported: If you already have one file open in gedit, and then open another file using any method (e.g. if you double click on another file in nautilus), gedit should open it in a new tab, but it does not. ProblemType: Bug DistroRelease: Arch 2018.06.01 Package: gedit 3.28.1-1 ProcVersionSignature: Linux version 4.17.2-1-ARCH (builduser@heftig-9574) (gcc version 8.1.1 20180531 (GCC)) #1 SMP PREEMPT Sat Jun 16 11:08:59 UTC 2018 Uname: 4.17.2-1-ARCH Architecture: amd64 CurrentDesktop: arch:GNOME Date: Wed jun 20 12:41:56 CEST 2018 ProcEnviron: TERM=gnome-terminal LANG=cs_CZ.UTF-8 SHELL=/bin/bash SourcePackage: gedit ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- 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/1777856 Title: Gedit opens files in new windows instead of new tabs Status in gtk+3.0 package in Ubuntu: New Bug description: If you already have one file open in gedit, and then open another file using any method (e.g. if you double click on another file in nautilus), gedit should open it in a new tab, but it does not. ProblemType: Bug DistroRelease: Arch 2018.06.01 Package: gedit 3.28.1-1 ProcVersionSignature: Linux version 4.17.2-1-ARCH (builduser@heftig-9574) (gcc version 8.1.1 20180531 (GCC)) #1 SMP PREEMPT Sat Jun 16 11:08:59 UTC 2018 Uname: 4.17.2-1-ARCH Architecture: amd64 CurrentDesktop: arch:GNOME Date: Wed jun 20 12:41:56 CEST 2018 ProcEnviron: TERM=gnome-terminal LANG=cs_CZ.UTF-8 SHELL=/bin/bash SourcePackage: gedit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1777856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777854] [NEW] package systemd 237-3ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
Public bug reported: I've tried to upgrade from 16.04.4 LTS to 18.04 LTS ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39 Uname: Linux 3.13.0-105-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Jun 20 11:32:21 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2015-04-22 (1154 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-105-generic root=/dev/mapper/hostname--vg-root ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: systemd Title: package systemd 237-3ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: Upgraded to bionic on 2018-06-20 (0 days ago) dmi.bios.date: 09/21/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- 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/1777854 Title: package systemd 237-3ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 Status in systemd package in Ubuntu: New Bug description: I've tried to upgrade from 16.04.4 LTS to 18.04 LTS ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39 Uname: Linux 3.13.0-105-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Jun 20 11:32:21 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2015-04-22 (1154 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-105-generic root=/dev/mapper/hostname--vg-root ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: systemd Title: package systemd 237-3ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: Upgraded to bionic on 2018-06-20 (0 days ago) dmi.bios.date: 09/21/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1777854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1723403] Re: Gedit doesn't Gain Focus Upon Opening a File in Nautilus
It happens also on Xorg to me -- 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/1723403 Title: Gedit doesn't Gain Focus Upon Opening a File in Nautilus Status in GTK+: New Status in gtk+3.0 package in Ubuntu: Triaged Bug description: If you already have one tab open in gedit, and then minimize gedit, if you double click on another file in nautilus, gedit should regain focus, but it does not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gedit 3.22.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 13 06:26:01 2017 InstallationDate: Installed on 2017-10-13 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1723403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442915] Re: Missing package installation console output message in gdebi-kde
** Bug watch added: Debian Bug tracker #782422 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782422 ** Also affects: gdebi via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782422 Importance: Unknown Status: Unknown -- 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/1442915 Title: Missing package installation console output message in gdebi-kde Status in gdebi: Unknown Status in gdebi package in Ubuntu: New Bug description: As attached screenshot, no console output is listed in the "Show details" textbox during package installation. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gdebi-kde 0.9.5.3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 CurrentDesktop: KDE Date: Sat Apr 11 23:35:47 2015 PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdebi/+bug/1442915/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers
I think I narrowed it down to these: v4.14 - No issue observed v4.15-rc-1 - Issue observed Wherever the issue is observed, if I blacklist or rmmod ahci driver before reboot, no issue is observed (because the SATA ODD is gone now). -- 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/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers Status in dellserver: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in systemd source package in Bionic: New Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777839] [NEW] package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: When i try to install audio driver, i found this issue ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jun 20 11:10:12 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 DpkgHistoryLog: Start-Date: 2018-06-20 11:08:35 Requested-By: anandharaj (1001) Upgrade: snapd:amd64 (2.32.9+18.04, 2.33+18.04), initramfs-tools-bin:amd64 (0.130ubuntu3.1, 0.130ubuntu3.2), libgcrypt20:amd64 (1.8.1-4ubuntu1, 1.8.1-4ubuntu1.1), libgcrypt20:i386 (1.8.1-4ubuntu1, 1.8.1-4ubuntu1.1), libmozjs-52-0:amd64 (52.3.1-7fakesync1, 52.8.1-0ubuntu0.18.04.1), initramfs-tools-core:amd64 (0.130ubuntu3.1, 0.130ubuntu3.2), initramfs-tools:amd64 (0.130ubuntu3.1, 0.130ubuntu3.2) Remove: linux-image-extra-4.4.0-127-generic:amd64 (4.4.0-127.153) ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=fb742fda-003f-4ce7-a4d6-52b47cd24bbb InstallationDate: Installed on 2016-08-23 (665 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 413c:2501 Dell Computer Corp. Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E5470 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic.efi.signed root=UUID=7ec171db-716a-4bcf-b66d-9249ce6ae583 ro recovery nomodeset PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8 SourcePackage: initramfs-tools Title: package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.6 dmi.board.name: 0MT53G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.6:bd12/08/2017:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0MT53G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5470 dmi.sys.vendor: Dell Inc. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-from-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1777839 Title: package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: When i try to install audio driver, i found this issue ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jun 20 11:10:12 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 DpkgHistoryLog: Start-Date: 2018-06-20 11:08:35 Requested-By: anandharaj (1001) Upgrade: snapd:amd64 (2.32.9+18.04, 2.33+18.04), initramfs-tools-bin:amd64 (0.130ubuntu3.1, 0.130ubuntu3.2), libgcrypt20:amd64 (1.8.1-4ubuntu1, 1.8.1-4ubuntu1.1), libgcrypt20:i386 (1.8.1-4ubuntu1, 1.8.1-4ubuntu1.1), libmozjs-52-0:amd64 (52.3.1-7fakesync1, 52.8.1-0ubuntu0.18.04.1), initramfs-tools-core:amd64 (0.130ubuntu3.1, 0.130ubuntu3.2), initramfs-tools:amd64 (0.130ubuntu3.1, 0.130ubuntu3.2) Remove: linux-image-extra-4.4.0-127-generic:amd64 (4.4.0-127.153) ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=fb742fda-003f-4ce7-a4d
[Touch-packages] [Bug 1777839] Re: package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1777839 Title: package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: When i try to install audio driver, i found this issue ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jun 20 11:10:12 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 DpkgHistoryLog: Start-Date: 2018-06-20 11:08:35 Requested-By: anandharaj (1001) Upgrade: snapd:amd64 (2.32.9+18.04, 2.33+18.04), initramfs-tools-bin:amd64 (0.130ubuntu3.1, 0.130ubuntu3.2), libgcrypt20:amd64 (1.8.1-4ubuntu1, 1.8.1-4ubuntu1.1), libgcrypt20:i386 (1.8.1-4ubuntu1, 1.8.1-4ubuntu1.1), libmozjs-52-0:amd64 (52.3.1-7fakesync1, 52.8.1-0ubuntu0.18.04.1), initramfs-tools-core:amd64 (0.130ubuntu3.1, 0.130ubuntu3.2), initramfs-tools:amd64 (0.130ubuntu3.1, 0.130ubuntu3.2) Remove: linux-image-extra-4.4.0-127-generic:amd64 (4.4.0-127.153) ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=fb742fda-003f-4ce7-a4d6-52b47cd24bbb InstallationDate: Installed on 2016-08-23 (665 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 413c:2501 Dell Computer Corp. Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E5470 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic.efi.signed root=UUID=7ec171db-716a-4bcf-b66d-9249ce6ae583 ro recovery nomodeset PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8 SourcePackage: initramfs-tools Title: package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.6 dmi.board.name: 0MT53G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.6:bd12/08/2017:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0MT53G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1777839/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
same here. A fix would be highly appreciated. -- 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: Connection to open or WPA secured wifi works without any issues. Connection to WPA2/PEAP fails. Repeatedly asks for username/password. Possible gnome-shell integration issue. The system was updated from Xenial to Bionic in mid-January. At that time this WPA2/PEAP setup worked without any issues. With the updates coming in the last week of January / First February week - the bug was experienced. 1) ➜ syncthing git:(master) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) - up to date packages [code] ➜ cat /etc/apt/sources.list |egrep -v '^#' deb http://cz.archive.ubuntu.com/ubuntu/ bionic main restricted deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates main restricted deb http://cz.archive.ubuntu.com/ubuntu/ bionic universe deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates universe deb http://cz.archive.ubuntu.com/ubuntu/ bionic multiverse deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates multiverse deb http://security.ubuntu.com/ubuntu/ bionic-security multiverse main universe restricted [/code] Note: # some pkg version related to problem might be from proposed-updates repo 2b) [code] dpkg -l |egrep -i 'network manager|networkm|libnm' ii gir1.2-networkmanager-1.0:amd641.8.4-1ubuntu4 amd64GObject introspection data for the libnm-glib/libnm-util library ii gir1.2-nm-1.0:amd641.8.4-1ubuntu4 amd64GObject introspection data for the libnm library ii gir1.2-nmgtk-1.0:amd64 1.8.10-2ubuntu1 amd64GObject introspection data for libnm-gtk ii libnm-glib-vpn1:amd64 1.8.4-1ubuntu4 amd64network management framework (GLib VPN shared library) ii libnm-glib4:amd64 1.8.4-1ubuntu4 amd64network management framework (GLib shared library) ii libnm-gtk0:amd64 1.8.10-2ubuntu1 amd64library for wireless and mobile dialogs (libnm-glib version) ii libnm-util2:amd64 1.8.4-1ubuntu4 amd64network management framework (shared library) ii libnm0:amd64 1.8.4-1ubuntu4 amd64GObject-based client library for NetworkManager ii libnma0:amd64 1.8.10-2ubuntu1 amd64library for wireless and mobile dialogs (libnm version) ii libproxy1-plugin-networkmanager:amd64 0.4.15-0ubuntu1 amd64automatic proxy configuration management library (Network Manager plugin) ii network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu4 all NetworkManager configuration to enable connectivity checking ii strongswan-nm 5.6.1-2ubuntu1 amd64strongSwan plugin to interact with NetworkManager ii wpasupplicant 2:2.6-15ubuntu2 amd64client support for WPA and WPA2 (IEEE 802.11i) [/code] 3,4) Connection to open or WPA secured wifi works withou any issues. Connection to WPA2/PLEAP (without cert, just with username/password fails). Although wifi layer get's is associated the client (network-manager) possibly due to bug deauthenticate itself without establishing an IP connection. Connect to network. 5) Logs (syslog/kernel) Core moments: [code] Feb 12 09:19:02 dontpanic NetworkManager[1125]: [1518423542.9125] keyfile: update /etc/NetworkManager/system-connections/WiFi (82c55e94-907a-458a-ae31-8cbd75db0fa5,"WiFi") Feb 12 09:19:02 dontpanic gnome-shell[4284]: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed and ... Feb 12 09:19:02 dontpanic NetworkManager[1125]: [1518423542.9450] device (wlp4s0): Activation: (wifi) connection 'WiFi' has security, and secrets exist. No new secrets needed. Feb 12 09:19:02 dontpanic NetworkManager[1125]: [1518423542.9450] Config: added 'ssid' val
[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Tested http://cdimage.ubuntu.com/daily-live/20180620/cosmic-desktop- amd64.iso, which includes initramfs-tools 0.130ubuntu3.2. It is still affected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: In Progress Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
[Test case] 1. Install using the "Use LVM" option in the desktop installer. - installed using xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. - sure it does - file /etc/initramfs-tools/conf.d/resume exists 6. Install initramfs-tools from bionic-proposed. - file /etc/initramfs-tools/conf.d/resume still exists 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. - problem persists. apt list initramfs-tools Listing... Done initramfs-tools/bionic-proposed,bionic-proposed,now 0.130ubuntu3.2 all [installed] The workaround is to delete /etc/initramfs-tools/conf.d/resume. ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: In Progress Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768488] Re: dependency problem lightdm -> pam
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1768488 Title: dependency problem lightdm -> pam Status in lightdm package in Ubuntu: Confirmed Bug description: Hi, I've installed Lubuntu 18.04 and found that problem: the display-manager service complains: ● lightdm.service - Light Display Manager Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; vendor preset: enabled) Active: active (running) since Wed 2018-05-02 11:36:27 CEST; 1min 22s ago Docs: man:lightdm(1) Process: 1717 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, status=0/SUCCESS) Main PID: 1720 (lightdm) Tasks: 6 (limit: 4915) CGroup: /system.slice/lightdm.service ├─1720 /usr/sbin/lightdm ├─1726 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch └─1786 lightdm --session-child 12 19 Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM adding faulty module: pam_kwallet5.so Mai 02 11:36:29 pcdanisch lightdm[1735]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0) Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or directory Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: pam_gnome_keyring.so Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: pam_kwallet.so Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: pam_kwallet5.so Mai 02 11:36:30 pcdanisch lightdm[1786]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "danisch" It's because /etc/pam.d/lightdm and /etc/pam.d/lightdm-greeter try to load pam modules which are not installed since there are not dependencies to libpam-gnome-keyring libpam-kwallet4 libpam-kwallet5 If it is not intended to let things run into error message (and possible further trouble), you should either remove these lines from the config files or add dependencies to pull in that packages. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: LXDE Date: Wed May 2 12:21:26 2018 InstallationDate: Installed on 2018-04-30 (2 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1768488/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772898] Re: [SRU] New stable release 1.14.1
Releasing this SRU is blocked on getting the corresponding gst-plugins- bad1.0 release to migrate out of cosmic-proposed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1772898 Title: [SRU] New stable release 1.14.1 Status in gst-libav1.0 package in Ubuntu: In Progress Status in gst-plugins-bad1.0 package in Ubuntu: In Progress Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: In Progress Status in gst-python1.0 package in Ubuntu: In Progress Status in gst-rtsp-server1.0 package in Ubuntu: In Progress Status in gstreamer-editing-services1.0 package in Ubuntu: In Progress Status in gstreamer-vaapi package in Ubuntu: In Progress Status in gstreamer1.0 package in Ubuntu: Fix Committed Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1772898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769682] Re: NFS-based remote root hangs when running 'netplan apply'
Today, I can confirm that with netplan.io 0.36.2 and initramfs-tools 0.130ubuntu3.2 the bug (initially supplied by me as duplicate #1767359) is fixed. I simply added the -proposed repo, ran apt update&upgrade, reactivated a minimal netplan config, and rebooted the virtual machine which uses an nfsroot filesystem. It booted straight, and I could confirm from syslog that systemd-network took the DHCP client role, as configured by my netplan config. Thanks a lot for your efforts! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1769682 Title: NFS-based remote root hangs when running 'netplan apply' Status in initramfs-tools package in Ubuntu: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Invalid Status in initramfs-tools source package in Xenial: Confirmed Status in netplan.io source package in Xenial: Invalid Status in nplan source package in Xenial: Fix Released Status in initramfs-tools source package in Artful: Confirmed Status in netplan.io source package in Artful: Invalid Status in nplan source package in Artful: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in netplan.io source package in Bionic: Fix Released Status in nplan source package in Bionic: Invalid Bug description: [Impact] Netboot users with a remote filesystem over NFS (possibly over other networked filesystems). [Test cases] 1) Boot a system with its root filesystem over NFS. 2) Run 'sudo netplan apply' 3) Validate that the system remains responsive and keeps connectivity over the same IP address as it had. [Regression potential] This SRU changes network properties, and enforces that networkd does not release and re-request an IP address from DHCP when it is restarted. Environments relying on the IP release/renew behavior may find themselves staying on the previous IP address, which might negatively impact connectivity. Changes in connectivity on a system running netplan should be investigated as a potential regression from this SRU. Other regression possibilities would include failure to get a new IP address over time (usually seen as losing connectivity) or possible IP conflicts on a network. --- With a system booted on the network, with its remote root fs on NFS: Running 'netplan apply' restarts systemd-networkd, which releases the IP received from DHCP. With no IP (and and IP potentially changing), the NFS server can't be reached so the system hangs. 'netplan apply' or restarting systemd-networkd should not affect teh system, it should continue working normally despite "changing" network states, as long as the effective IP remains the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763611] Re: Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1763611 Title: Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs Status in initramfs-tools package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Fix Released Bug description: See this thread at the Ubuntu Forums: https://ubuntuforums.org/showthread.php?t=2388799 How come the ultra light Lubuntu Bionic needs 40 seconds from the grub menu to the log in screen, while the corresponding Kubuntu and Xubuntu Bionic can do it in 10 seconds in my Toshiba laptop? All the operating systems were installed from the Bionic Beta-2 desktop 64-bit iso files and made up to date today (and reside in a new SSD connected via the internal SATA bay). -o- and to summarize the conclusion https://ubuntuforums.org/showthread.php?t=2388799&page=2&p=13756324#post13756324 This supports the assumption, that there are problems for Lubuntu to manage SSDs with 4096 byte size physical sectors. But the other flavours of Ubuntu can manage it. Let us hope that this can help the Lubuntu developer to find and squash the bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lubuntu-desktop 0.93 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Apr 13 09:59:42 2018 InstallationDate: Installed on 2018-04-06 (7 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180405) SourcePackage: lubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1763611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
