[Touch-packages] [Bug 1767535] Re: package python-crypto 2.6.1-4build1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 126
[Expired for python-crypto (Ubuntu) because there has been no activity for 60 days.] ** Changed in: python-crypto (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1767535 Title: package python-crypto 2.6.1-4build1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 126 Status in python-crypto package in Ubuntu: Expired Bug description: I tried updating ubuntu and then i got this error. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-crypto 2.6.1-4build1 ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21 Uname: Linux 3.19.0-61-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Fri Apr 27 18:49:42 2018 DuplicateSignature: package:python-crypto:2.6.1-4build1:subprocess new pre-removal script returned error exit status 126 ErrorMessage: subprocess new pre-removal script returned error exit status 126 InstallationDate: Installed on 2016-05-15 (712 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.6 apt 1.0.1ubuntu2.14 SourcePackage: python-crypto Title: package python-crypto 2.6.1-4build1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 126 UpgradeStatus: Upgraded to trusty on 2018-04-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1767535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779237] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
Thank you so much sudo apt-get install --reinstall hplip hplip-data sudo apt-get install --reinstall python3 Updates work Printer works too -- 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/1779237 Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: Invalid Bug description: Only Ubuntu Update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jun 28 22:51:28 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-13 (76 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: python3-defaults Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782854] Re: CRITICAL BUG IN initramfs-tools 0.131ubuntu1: Failed to execute /init (error -13)
** Tags added: block-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/1782854 Title: CRITICAL BUG IN initramfs-tools 0.131ubuntu1: Failed to execute /init (error -13) Status in initramfs-tools package in Ubuntu: Fix Committed Bug description: I'm running cosmic with proposed enabled (yes, I know...) and just updated initramfs to 0.131ubuntu1 Upon reboot, I've got the message from summary. Then I rebooted into a previous kernel version (4.15) and ran 'update-initramfs -u -k all' and that was stupid because it screwed the old initramfs... Comparing new (4.17) and old (not updated 4.15) initramfs images on another computer with Intel Core 2 Duo T9300 (x64), I've got this: sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.17.0-5-generic kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/.enuineIntel.align.0123456789abc kernel/x86/microcode/GenuineIntel.bin 98 blocks sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.15.0-23-generic . kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/AuthenticAMD.bin 56 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1782854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782854] Re: CRITICAL BUG IN initramfs-tools 0.131ubuntu1: Failed to execute /init (error -13)
** Changed in: initramfs-tools (Ubuntu) Status: New => Fix Committed ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Critical -- 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/1782854 Title: CRITICAL BUG IN initramfs-tools 0.131ubuntu1: Failed to execute /init (error -13) Status in initramfs-tools package in Ubuntu: Fix Committed Bug description: I'm running cosmic with proposed enabled (yes, I know...) and just updated initramfs to 0.131ubuntu1 Upon reboot, I've got the message from summary. Then I rebooted into a previous kernel version (4.15) and ran 'update-initramfs -u -k all' and that was stupid because it screwed the old initramfs... Comparing new (4.17) and old (not updated 4.15) initramfs images on another computer with Intel Core 2 Duo T9300 (x64), I've got this: sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.17.0-5-generic kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/.enuineIntel.align.0123456789abc kernel/x86/microcode/GenuineIntel.bin 98 blocks sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.15.0-23-generic . kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/AuthenticAMD.bin 56 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1782854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779438] Re: Cannot resolve names using systemd-resolved stub resolver
Ok, thanks for the suggestion there Dimitri. I ran a wireshark to see what happened when I pinged the hostname which would inevitably fail, and I got nothing in wireshark. What I think is happening and makes most sense is that the stub resolver is eating up my DNS lookup and not forwarding it onto my nameserver. This is why there is no network traffic for the ping as the resolve just fails inside the stub resolver. Is the nsswitch.conf a clue here? hosts: files mdns4_minimal [NOTFOUND=return] dns Does that mean that if there is not hostname found, it returns and not forwards to dns? After the failed wireshark, I switched the /etc/resolv.conf to not point to the stub-resolv.conf and all is well again. I would still like to help fix this issue though. -- 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/1779438 Title: Cannot resolve names using systemd-resolved stub resolver Status in systemd package in Ubuntu: Incomplete Bug description: Description: Ubuntu 18.04 LTS Release: 18.04 I am running a clean install of Ubuntu 18.04. This bug was also present for me on a clean install of Ubuntu 17.10 and I had a solution, but it appears to no longer work. What I expect to happen: Ping other hosts on network by name What happened instead: I can't ping other machines on network via name. From my Ubuntu 18.04 machine, I `ping ubuntu-test-1` and `ping ubuntu-test-1.localdomain` but neither work. I can ping by IP address though. The other machines on the network are Ubuntu Server 16.04.3 machines and can ping each other by name also. All machines on network including problem one receive DHCP leases from same server (192.168.20.1) I believe the problem is systemd-resolved stub resolver. `cat /etc/resolv.conf` # This file is managed by man:systemd-resolved(8). Do not edit. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "systemd-resolve --status" to see details about the uplink DNS servers # currently in use. # # Third party programs must not access this file directly, but only through the # symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way, # replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 search localdomain If I change the nameserver line to the IP of my nameserver, not the stub, resolution works. nameserver 192.168.20.1 search localdomain Now I can ping hosts by name. I used to solve this problem like this... `sudo systemctl disable systemd-resolved.service` `echo "nameserver 192.168.20.1" | sudo tee -a /etc/resolvconf/resolv.conf.d/tail` `sudo reboot` But /etc/resolvconf/resolv.conf.d no longer exists, and it's about time this problem was fixed :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782835] Re: d-i step "Configure the keyboard" fails
This bug was fixed in the package console-setup - 1.178ubuntu4 --- console-setup (1.178ubuntu4) cosmic; urgency=medium * debian/console-setup-udeb.postinst: Guard the dpkg call in the postinst, so it isn't attempted in the debian-installer environment (LP: #1782835) -- Adam Conrad Fri, 20 Jul 2018 14:22:45 -0600 ** Changed in: console-setup (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 console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1782835 Title: d-i step "Configure the keyboard" fails Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Bionic: Fix Committed Bug description: Testing a bionic build of d-i w/ proposed results in a failure. From d-i's /var/log/syslog: Jul 20 20:01:04 main-menu[897]: INFO: Menu item 'di-utils-shell' selected Jul 20 20:03:23 main-menu[897]: INFO: Menu item 'console-setup-udeb' selected Jul 20 20:03:25 main-menu[897]: (process:1567): /var/lib/dpkg/info/console-setup-udeb.postinst: line 52: dpkg-query: not found Jul 20 20:03:25 main-menu[897]: WARNING **: Configuring 'console-setup-udeb' failed with error code 127 Jul 20 20:03:25 main-menu[897]: WARNING **: Menu item 'console-setup-udeb' failed. Jul 20 20:03:41 main-menu[897]: INFO: Menu item 'di-utils-shell' selected Jul 20 20:03:46 kernel: [ 224.155631] random: crng init done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1782835/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
Verified the test case again, this time by upgrading from version 1.178ubuntu2 to 1.178ubuntu2.2, which was uploaded to address the regression reported in bug #1782835. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in console-setup source package in Bionic: Fix Committed Status in gnome-control-center source package in Bionic: Invalid Bug description: [Impact] The keyboard-configuration package provides a tool for configuring the keyboard via /etc/default/keyboard. However, there are desktop GUIs which provide such tools as well, and in the case of gnome-control- center it has another idea of what /etc/default/keyboard should contain. In short: The different tools don't play well together. The proposed upload does not claim to fix all issues with this incompatibility. But one of the annoyances is that a pure upgrade of the keyboard-configuration package may result in a changed keyboard configuration without the user asking for it. The proposed upload does address that particular issue on desktop systems. [Test Case] 1. On an Ubuntu 18.04 system, make sure that the contents of /etc/default/keyboard is 'the g-c-c style', for instance: XKBLAYOUT=se,us BACKSPACE=guess XKBVARIANT=, 2. Reboot. 3. Upgrade to the version of the keyboard-configuration package in bionic-proposed. => Find that /etc/default/keyboard was not changed through the upgrade. 4. Run the command sudo dpkg-reconfigure keyboard-configuration => Find that you are now offered to change your keyboard configuration. [Regression Potential] As a result of this upload, and unlike before, no keyboard configuration will happen behind the scenes on a desktop system due to an upgrade of the keyboard-configuration package. This is the desired change, and I can't think of a case when a user would want the configuration to be changed without having asked for it. [Original description] Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland
I just wanted to state that this issue seems to have resolved itself. I've grabbed the updated packages from apt and these are what I believe the relevant updates were. Is there any more information that might be more useful? Start-Date: 2018-07-10 18:20:32 libwayland-egl1-mesa:amd64 (18.0.0~rc5-1ubuntu1, 18.0.5-0ubuntu0~18.04.1) 2018-07-19 21:31:00 gdm3:amd64 (3.28.2-0ubuntu1.2, 3.28.2-0ubuntu1.3) gir1.2-gdm-1.0:amd64 (3.28.2-0ubuntu1.2, 3.28.2-0ubuntu1.3) libgdm1:amd64 (3.28.2-0ubuntu1.2, 3.28.2-0ubuntu1.3) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1760201 Title: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: WORKAROUND: Edit /etc/gdm3/custom.conf and uncomment: #WaylandEnable=false --- Ubuntu 18.04(Updated 30.03.2018) System Language: Turkish Please check screenshots --- ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-24 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Tags: bionic Uname: Linux 4.15.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782854] Re: CRITICAL BUG IN initramfs-tools 0.131ubuntu1: Failed to execute /init (error -13)
The other computer (main one I'm writing from) got the same message after update to 0.131ubuntu1, so I booted with the older kernel (4.15), downgraded initramfs-tools, initramfs-tools-bin and initramfs-tools-core to 0.130ubuntu10 and successfully rebooted with the new kernel. I saved the broken and working initrd.img-4.17.0-5-generic images. Please advise if and where to upload them (27MB each). -- 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/1782854 Title: CRITICAL BUG IN initramfs-tools 0.131ubuntu1: Failed to execute /init (error -13) Status in initramfs-tools package in Ubuntu: New Bug description: I'm running cosmic with proposed enabled (yes, I know...) and just updated initramfs to 0.131ubuntu1 Upon reboot, I've got the message from summary. Then I rebooted into a previous kernel version (4.15) and ran 'update-initramfs -u -k all' and that was stupid because it screwed the old initramfs... Comparing new (4.17) and old (not updated 4.15) initramfs images on another computer with Intel Core 2 Duo T9300 (x64), I've got this: sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.17.0-5-generic kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/.enuineIntel.align.0123456789abc kernel/x86/microcode/GenuineIntel.bin 98 blocks sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.15.0-23-generic . kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/AuthenticAMD.bin 56 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1782854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782835] Re: d-i step "Configure the keyboard" fails
I rebuilt bionic d-i against proposed and the problem is now gone. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1782835 Title: d-i step "Configure the keyboard" fails Status in console-setup package in Ubuntu: Fix Committed Status in console-setup source package in Bionic: Fix Committed Bug description: Testing a bionic build of d-i w/ proposed results in a failure. From d-i's /var/log/syslog: Jul 20 20:01:04 main-menu[897]: INFO: Menu item 'di-utils-shell' selected Jul 20 20:03:23 main-menu[897]: INFO: Menu item 'console-setup-udeb' selected Jul 20 20:03:25 main-menu[897]: (process:1567): /var/lib/dpkg/info/console-setup-udeb.postinst: line 52: dpkg-query: not found Jul 20 20:03:25 main-menu[897]: WARNING **: Configuring 'console-setup-udeb' failed with error code 127 Jul 20 20:03:25 main-menu[897]: WARNING **: Menu item 'console-setup-udeb' failed. Jul 20 20:03:41 main-menu[897]: INFO: Menu item 'di-utils-shell' selected Jul 20 20:03:46 kernel: [ 224.155631] random: crng init done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1782835/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782854] [NEW] CRITICAL BUG IN initramfs-tools 0.131ubuntu1: Failed to execute /init (error -13)
Public bug reported: I'm running cosmic with proposed enabled (yes, I know...) and just updated initramfs to 0.131ubuntu1 Upon reboot, I've got the message from summary. Then I rebooted into a previous kernel version (4.15) and ran 'update-initramfs -u -k all' and that was stupid because it screwed the old initramfs... Comparing new (4.17) and old (not updated 4.15) initramfs images on another computer with Intel Core 2 Duo T9300 (x64), I've got this: sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.17.0-5-generic kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/.enuineIntel.align.0123456789abc kernel/x86/microcode/GenuineIntel.bin 98 blocks sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.15.0-23-generic . kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/AuthenticAMD.bin 56 blocks ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic ** Tags added: cosmic ** Summary changed: - CRITICAL BUG IN 0.131ubuntu1: Failed to execute /init (error -13) + CRITICAL BUG IN initramfs-tools 0.131ubuntu1: Failed to execute /init (error -13) -- 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/1782854 Title: CRITICAL BUG IN initramfs-tools 0.131ubuntu1: Failed to execute /init (error -13) Status in initramfs-tools package in Ubuntu: New Bug description: I'm running cosmic with proposed enabled (yes, I know...) and just updated initramfs to 0.131ubuntu1 Upon reboot, I've got the message from summary. Then I rebooted into a previous kernel version (4.15) and ran 'update-initramfs -u -k all' and that was stupid because it screwed the old initramfs... Comparing new (4.17) and old (not updated 4.15) initramfs images on another computer with Intel Core 2 Duo T9300 (x64), I've got this: sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.17.0-5-generic kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/.enuineIntel.align.0123456789abc kernel/x86/microcode/GenuineIntel.bin 98 blocks sm4rk0@Aspire-5336:~$ cpio -t < /boot/initrd.img-4.15.0-23-generic . kernel kernel/x86 kernel/x86/microcode kernel/x86/microcode/AuthenticAMD.bin 56 blocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1782854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777415] Re: Local authorization bypass by using suspend mode
Jarno, sorry, that was a typo on my part. It looks like mate's screenlocker is mate-screensaver. Thanks -- 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/1777415 Title: Local authorization bypass by using suspend mode Status in Unity: New Status in pam package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Version: Ubuntu 16.04.04 LTS Desktop, all packets are updated at 15.06.2018 Affects: access to latest user opened applications, that can contain sensitive information (documents, private information, passwords, etc.) How to reproduce: 1. open some applications (LibreOffice, browsers, editors, ...) 2. go to suspend mode 3. extract hard drive 4. wake up 5. after that can be several behaviors: * Ubuntu show lock screen. Enter ANY password -> access granted. * Ubuntu show lock screen. Enter ANY password, access denied. Fast press the hardware shutdown button -> access granted. * Ubuntu does not show lock screen, only black screen. We can repeat actions like in previous paragraphs To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1777415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778844] Re: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state
** Changed in: ubuntu-power-systems Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash,kdump is not working and system enters into initramfs state Status in The Ubuntu-power-systems project: Incomplete Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in makedumpfile package in Ubuntu: New Status in initramfs-tools source package in Bionic: New Status in linux source package in Bionic: New Status in makedumpfile source package in Bionic: New Bug description: Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 0063 [ 73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 31da0058 [ 73.058099] GPR08: 0007 0001 90001003 [ 73.058099] GPR12: c07f24a0 c7a2e400 0e4fa497c900 [ 73.058099] GPR16: 0e4f79cc94b0 0e4f79d567e0 0e4f79d88204 0e4f79d56818 [ 73.058099] GPR20: 0e4f79d8d5d8 0001 7efce644 [ 73.058099] GPR24: 7efce640 0e4f79d8afb4 c15e9aa8 0
[Touch-packages] [Bug 1777994] Re: the header xcb/xinput.h is missing
This bug was fixed in the package libxcb - 1.13-2 --- libxcb (1.13-2) unstable; urgency=medium [ Timo Aaltonen ] * Package libxcb-xinput0/libxcb-xinput-dev. (Closes: #733227) (LP: #1777994) [ Andreas Boll ] * control: Fix VCS urls. -- Timo Aaltonen Thu, 21 Jun 2018 13:52:59 +0300 ** Changed in: libxcb (Ubuntu) Status: New => Fix Released -- 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: Fix Released 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1777994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778844] Re: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash, kdump is not working and system enters into initramfs state
I have managed to test kdump and initramfs with MODULES=dep on an emulated nvme, using qemu. Both worked just fine. The sysfs tree seems reasonable too, in respect to how initramfs finds the necessary modules. So, I would really need the specific details on that failure case, that is, the sysfs tree and all the rest I requested in the previous message. Thank you. Cascardo. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1778844 Title: ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash,kdump is not working and system enters into initramfs state Status in The Ubuntu-power-systems project: Triaged Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: New Status in makedumpfile package in Ubuntu: New Status in initramfs-tools source package in Bionic: New Status in linux source package in Bionic: New Status in makedumpfile source package in Bionic: New Bug description: Problem Description: === After triggering crash ,kdump is not working & system enters into initramfs state Steps to re-create: == >. woo is installed ubuntu180401 kernel root@woo:~# uname -a Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@woo:~# >. Crashkernel value as below root@woo:~# free -h totalusedfree shared buff/cache available Mem: 503G2.0G501G 13M279M 499G Swap: 2.0G 0B2.0G root@woo:~# cat /proc/cmdline root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet crashkernel=8192M > kdump status root@woo:~# kdump-config status current state : ready to kdump root@woo:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.15.0-23-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@woo:~# dmesg | grep Reser [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System RAM: 524288MB) [0.00] cma: Reserved 26224 MiB at 0x20399500 [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. > Triggered crash root@woo:~# echo 1 > /proc/sys/kernel/sysrq root@woo:~# echo c > /proc/sysrq-trigger [ 73.056308] sysrq: SysRq : Trigger a crash [ 73.056357] Unable to handle kernel paging request for data at address 0x [ 73.056459] Faulting instruction address: 0xc07f24c8 [ 73.056543] Oops: Kernel access of bad area, sig: 11 [#1] [ 73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV [ 73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc [ 73.057601] tg3 libahci nvme_core pnv_php [ 73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G OE 4.15.0-23-generic #25-Ubuntu [ 73.057767] NIP: c07f24c8 LR: c07f3568 CTR: c07f24a0 [ 73.057868] REGS: c03f8269f9f0 TRAP: 0300 Tainted: G OE (4.15.0-23-generic) [ 73.057986] MSR: 90009033 CR: 2822 XER: 2004 [ 73.058099] CFAR: c07f3564 DAR: DSISR: 4200 SOFTE: 1 [ 73.058099] GPR00: c07f3568 c03f8269fc70 c16eaf00 0063 [ 73.058099] GPR04: c03fef47ce18 c03fef494368 90009033 31da0058 [ 73.058099] GPR08: 0007 0001 90001003 [ 73.058099] GPR12: c07f24a0 c7a2e400 0e4f
[Touch-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
Hello Markus, or anyone else affected, Accepted console-setup into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/console- setup/1.178ubuntu2.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in console-setup source package in Bionic: Fix Committed Status in gnome-control-center source package in Bionic: Invalid Bug description: [Impact] The keyboard-configuration package provides a tool for configuring the keyboard via /etc/default/keyboard. However, there are desktop GUIs which provide such tools as well, and in the case of gnome-control- center it has another idea of what /etc/default/keyboard should contain. In short: The different tools don't play well together. The proposed upload does not claim to fix all issues with this incompatibility. But one of the annoyances is that a pure upgrade of the keyboard-configuration package may result in a changed keyboard configuration without the user asking for it. The proposed upload does address that particular issue on desktop systems. [Test Case] 1. On an Ubuntu 18.04 system, make sure that the contents of /etc/default/keyboard is 'the g-c-c style', for instance: XKBLAYOUT=se,us BACKSPACE=guess XKBVARIANT=, 2. Reboot. 3. Upgrade to the version of the keyboard-configuration package in bionic-proposed. => Find that /etc/default/keyboard was not changed through the upgrade. 4. Run the command sudo dpkg-reconfigure keyboard-configuration => Find that you are now offered to change your keyboard configuration. [Regression Potential] As a result of this upload, and unlike before, no keyboard configuration will happen behind the scenes on a desktop system due to an upgrade of the keyboard-configuration package. This is the desired change, and I can't think of a case when a user would want the configuration to be changed without having asked for it. [Original description] Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.la
[Touch-packages] [Bug 1782835] Re: d-i step "Configure the keyboard" fails
Hello dann, or anyone else affected, Accepted console-setup into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/console- setup/1.178ubuntu2.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: console-setup (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1782835 Title: d-i step "Configure the keyboard" fails Status in console-setup package in Ubuntu: Fix Committed Status in console-setup source package in Bionic: Fix Committed Bug description: Testing a bionic build of d-i w/ proposed results in a failure. From d-i's /var/log/syslog: Jul 20 20:01:04 main-menu[897]: INFO: Menu item 'di-utils-shell' selected Jul 20 20:03:23 main-menu[897]: INFO: Menu item 'console-setup-udeb' selected Jul 20 20:03:25 main-menu[897]: (process:1567): /var/lib/dpkg/info/console-setup-udeb.postinst: line 52: dpkg-query: not found Jul 20 20:03:25 main-menu[897]: WARNING **: Configuring 'console-setup-udeb' failed with error code 127 Jul 20 20:03:25 main-menu[897]: WARNING **: Menu item 'console-setup-udeb' failed. Jul 20 20:03:41 main-menu[897]: INFO: Menu item 'di-utils-shell' selected Jul 20 20:03:46 kernel: [ 224.155631] random: crng init done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1782835/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
I prepared a ppa build of d-i (ppa:dannf/test) and booted w/ apt- setup/proposed=true. It resolves the issue I was seeing on a HiSilicon D05 system w/ disks attached to an mpt3sas controller. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device Status in The Ubuntu-power-systems project: Triaged Status in debian-installer package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in debian-installer source package in Xenial: New Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: New Status in debian-installer source package in Bionic: New Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Committed Bug description: == Comment: #0 - ABDUL HALEEM - 2018-07-02 03:55:33 == ---Problem Description--- Ubuntu 18.04.01 ppc64el installer does not detect LSI3008 base SAS disks / MD RAID devices Used 20101020ubuntu543 version to install http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ Contact Information = abdha...@in.ibm.com ---uname output--- Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = BostonLC ---boot type--- Network boot Installer fails to detect the LSI SAS disks / RAID MD device ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device ? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? ? ?? ? ? ??? moves; selects; activates buttons To make sure it detects the disks I had to Detect disks-->Guided partitioning--> Guided - use entire disk ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075 ? ? SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume ? ? SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ ? ? ? ?? ? ? ??? IPR had similar issue reported #164932 and fixed with 4.15.0-20, looks installer need a fix for LSI (mpt3sas) devices too == Comment: #2 - SEETEENA THOUFEEK - 2018-07-03 02:01:47 == 164932 - refers LP1751813 == Comment: #3 - SEETEENA THOUFEEK - 2018-07-03 02:02:51 == Jul 2 08:49:52 anna-install: Installing mdadm-udeb Jul 2 08:49:52 disk-detect: No Intel/DDF RAID disks detected. Jul 2 08:49:52 anna-install: Installing dmraid-udeb Jul 2 08:49:52 disk-detect: No Serial ATA RAID disks detected Jul 2 08:49:53 check-missing-firmware: looking at dmesg again, restarting from \[ 330.659712\] Jul 2 08:49:53 check-missing-firmware: timestamp found, truncat
[Touch-packages] [Bug 1782835] Re: d-i step "Configure the keyboard" fails
** Package changed: linux (Ubuntu) => console-setup (Ubuntu) ** Changed in: console-setup (Ubuntu) Importance: Critical => Undecided ** Changed in: console-setup (Ubuntu) Status: Incomplete => New ** Changed in: console-setup (Ubuntu) Assignee: (unassigned) => Adam Conrad (adconrad) ** Changed in: console-setup (Ubuntu) Status: New => Fix Committed ** Changed in: console-setup (Ubuntu Bionic) Assignee: (unassigned) => Adam Conrad (adconrad) ** Changed in: console-setup (Ubuntu Bionic) Status: Incomplete => Confirmed -- 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/1782835 Title: d-i step "Configure the keyboard" fails Status in console-setup package in Ubuntu: Fix Committed Status in console-setup source package in Bionic: Fix Committed Bug description: Testing a bionic build of d-i w/ proposed results in a failure. From d-i's /var/log/syslog: Jul 20 20:01:04 main-menu[897]: INFO: Menu item 'di-utils-shell' selected Jul 20 20:03:23 main-menu[897]: INFO: Menu item 'console-setup-udeb' selected Jul 20 20:03:25 main-menu[897]: (process:1567): /var/lib/dpkg/info/console-setup-udeb.postinst: line 52: dpkg-query: not found Jul 20 20:03:25 main-menu[897]: WARNING **: Configuring 'console-setup-udeb' failed with error code 127 Jul 20 20:03:25 main-menu[897]: WARNING **: Menu item 'console-setup-udeb' failed. Jul 20 20:03:41 main-menu[897]: INFO: Menu item 'di-utils-shell' selected Jul 20 20:03:46 kernel: [ 224.155631] random: crng init done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1782835/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782835] [NEW] d-i step "Configure the keyboard" fails
You have been subscribed to a public bug: Testing a bionic build of d-i w/ proposed results in a failure. >From d-i's /var/log/syslog: Jul 20 20:01:04 main-menu[897]: INFO: Menu item 'di-utils-shell' selected Jul 20 20:03:23 main-menu[897]: INFO: Menu item 'console-setup-udeb' selected Jul 20 20:03:25 main-menu[897]: (process:1567): /var/lib/dpkg/info/console-setup-udeb.postinst: line 52: dpkg-query: not found Jul 20 20:03:25 main-menu[897]: WARNING **: Configuring 'console-setup-udeb' failed with error code 127 Jul 20 20:03:25 main-menu[897]: WARNING **: Menu item 'console-setup-udeb' failed. Jul 20 20:03:41 main-menu[897]: INFO: Menu item 'di-utils-shell' selected Jul 20 20:03:46 kernel: [ 224.155631] random: crng init done ** Affects: console-setup (Ubuntu) Importance: Undecided Assignee: Adam Conrad (adconrad) Status: New ** Affects: console-setup (Ubuntu Bionic) Importance: Undecided Status: Incomplete -- d-i step "Configure the keyboard" fails https://bugs.launchpad.net/bugs/1782835 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769386] Re: Cable network does not get recognized anymore, wifi works
I think I have the same issue on my nettop using "Pegatron RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller". It doesn't work out of the box on neither Ubuntu Server (bionic) nor Arch, but I used to run Ubuntu Server on this hardware around a year ago without any problems. Someone else downgraded their kernel from 4.15 to 4.14 on Arch to solve this issue after updating, with identical hardware. I'm linking some pastes that were requested in the IRC channel. modinfo r8168 (I tried to fix things by installing r8168-dkms) > paste.ubuntu.com/p/2spYWX5t4k/ modinfo r8169 (I was asked to unload r8168 and load r1869) > https://paste.ubuntu.com/p/jg9rbKThWZ/ dhclient -v (it also takes 5 minutes to boot, until it times out) &> https://paste.ubuntu.com/p/D3JpycKrq3/ -- 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/1769386 Title: Cable network does not get recognized anymore, wifi works Status in network-manager package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: ubuntu 16.04 LTS cable does not connect anymore, wifi working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 5 19:27:18 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-30 (217 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.2 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0wifi connected /org/freedesktop/NetworkManager/Devices/1 WiFi-2.4-3569 7103236e-31c4-43d6-871d-14f3cda4b657 /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0f1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1769386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738034] Re: Muted Sound Indicator randomly remains red when no sound is playing
> The issue is that the icon doesn't go back to normal and REMAINS red when the sound is finished playing. That is expected behavior. It turns red only to notify user that volume is muted. It requires immediate action. Once user unmute the volume it will go back to normal. Music may stop playing due to various other reason like pulseaudio error, so sound indicator couldn't possibly cover all scenarios why music has stopped playing. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1738034 Title: Muted Sound Indicator randomly remains red when no sound is playing Status in indicator-sound package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Mute the main Ubuntu volume 2. Play some short sound Expected behavior: Obviously you won't hear the sound. While the sound plays, the indicator should become red; then, when the sound is done playing and nothing else is playing, either immediately or after a very short period (e.g. a couple of seconds), the indicator should go back to its normal color. Observed behavior: Sometimes it behaves as expected, but sometimes it will remain red forever, until you unmute it. It's utterly random. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: indicator-sound 12.10.2+16.04.20160406-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 13 17:09:25 2017 InstallationDate: Installed on 2013-10-11 (1523 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-sound.log: (process:2339): indicator-sound-WARNING **: accounts-service-access.vala:218: unable to sync volume 0,608643 to AccountsService: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface 'com.ubuntu.AccountsService.Sound' (process:2339): indicator-sound-WARNING **: accounts-service-access.vala:218: unable to sync volume 0,848633 to AccountsService: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface 'com.ubuntu.AccountsService.Sound' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1738034/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769386] Re: Cable network does not get recognized anymore, wifi works
** Also affects: archlinux Importance: Undecided Status: New -- 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/1769386 Title: Cable network does not get recognized anymore, wifi works Status in network-manager package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: ubuntu 16.04 LTS cable does not connect anymore, wifi working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 5 19:27:18 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-30 (217 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.2 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0wifi connected /org/freedesktop/NetworkManager/Devices/1 WiFi-2.4-3569 7103236e-31c4-43d6-871d-14f3cda4b657 /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0f1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1769386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782831] [NEW] greeter fails first attempt and then report system inlow-graphics mode; only happens when DiplayLink Docking Station attached
Public bug reported: Ubuntu 16.04 LTS Unity Greeter ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 20 15:32:43 2018 InstallationDate: Installed on 2018-06-15 (34 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1782831 Title: greeter fails first attempt and then report system inlow-graphics mode; only happens when DiplayLink Docking Station attached Status in lightdm package in Ubuntu: New Bug description: Ubuntu 16.04 LTS Unity Greeter ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 20 15:32:43 2018 InstallationDate: Installed on 2018-06-15 (34 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) 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/1782831/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782190] Re: Set default interface font size to 11 for communitheme sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-settings (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1782190 Title: Set default interface font size to 11 for communitheme sessions Status in ubuntu-settings package in Ubuntu: Confirmed Status in ubuntu-settings source package in Bionic: Confirmed Bug description: [Impact] * communitheme snap users see the gnome shell overview window thumbnail labels cutted off * 18.04 users can install the communitheme snap from within gnome- software * To fix this the default font size of the interface needs to be switched to 11 (again) [Test Case] * Install ubuntu * install the communitheme snap * reboot * select the communitheme snap session and login * Open "activities" by clicking "activities" in the GNOME shell's upper left corner or by pressing the super/ubuntu/windows key * Each window thumbnail is labeled with a text which is now cut * This is caused by a bug in gnome-shell which can't handle any other font size than 11 for any other font beside cantarell * install the new ubuntu-settings version * open again activities * check that window thumbnails aren't cut anymore [Regression Potential] * It's affecting only the communitheme session, not available by default and reverting to the same default than ubuntu main session [Other Info] * Gitlab upstream issue: https://gitlab.gnome.org/GNOME/gnome- shell/issues/378 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1782190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782190] Re: Set default interface font size to 11 for communitheme sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1782190 Title: Set default interface font size to 11 for communitheme sessions Status in ubuntu-settings package in Ubuntu: Confirmed Status in ubuntu-settings source package in Bionic: Confirmed Bug description: [Impact] * communitheme snap users see the gnome shell overview window thumbnail labels cutted off * 18.04 users can install the communitheme snap from within gnome- software * To fix this the default font size of the interface needs to be switched to 11 (again) [Test Case] * Install ubuntu * install the communitheme snap * reboot * select the communitheme snap session and login * Open "activities" by clicking "activities" in the GNOME shell's upper left corner or by pressing the super/ubuntu/windows key * Each window thumbnail is labeled with a text which is now cut * This is caused by a bug in gnome-shell which can't handle any other font size than 11 for any other font beside cantarell * install the new ubuntu-settings version * open again activities * check that window thumbnails aren't cut anymore [Regression Potential] * It's affecting only the communitheme session, not available by default and reverting to the same default than ubuntu main session [Other Info] * Gitlab upstream issue: https://gitlab.gnome.org/GNOME/gnome- shell/issues/378 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1782190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782825] [NEW] missing symlink for library
Public bug reported: On bionic, I needed to ln -s /lib/x86_64-linux-gnu/libdevmapper.so.1.02.1 /lib/x86_64-linux- gnu/libdevmapper.so.1.02 in order for some previously built programs (like skopeo) to continue to work. ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1782825 Title: missing symlink for library Status in lvm2 package in Ubuntu: New Bug description: On bionic, I needed to ln -s /lib/x86_64-linux-gnu/libdevmapper.so.1.02.1 /lib/x86_64-linux- gnu/libdevmapper.so.1.02 in order for some previously built programs (like skopeo) to continue to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1782825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782641] Re: Request: Rename "ubuntu-keyring" package to "ubuntu-archive-keyring" for consistency with Debian
Dimitri, thank you for laying out the rationale behind the package name. Since there is good reason for things to be the way they are here, I've opened a bug on the Debian side for them to address the naming inconsistency: https://bugs.debian.org/904152 ** Bug watch added: Debian Bug tracker #904152 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904152 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1782641 Title: Request: Rename "ubuntu-keyring" package to "ubuntu-archive-keyring" for consistency with Debian Status in ubuntu-keyring package in Ubuntu: Opinion Bug description: The package that Ubuntu calls "ubuntu-keyring" is present in Debian as "ubuntu-archive-keyring". Debian has separate "debian-keyring" and "debian-archive-keyring" packages, described as follows: d-k: GnuPG keys of Debian Developers and Maintainers d-a-k: GnuPG archive keys of the Debian archive IMO this is a reasonable distinction, as the keys of developers/maintainers are rarely needed by end users, and the d-k package is significantly larger (on the order of 30 MB). Thus, the current "ubuntu-keyring" package would be better named "ubuntu-archive-keyring", not only so that the equivalent package has the same name in both distros, but also to maintain the same distinction between developer keys and archive keys. (Ubuntu could potentially decide to ship a package containing Ubuntu developer keys in the future, and it would be awkward if this needed to be named e.g. "ubuntu-devel-keyring" or the like.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1782641/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782135] Re: package cups-daemon 2.2.7-1ubuntu2.1 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1782135 Title: package cups-daemon 2.2.7-1ubuntu2.1 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1 Status in cups package in Ubuntu: Confirmed Bug description: na ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups-daemon 2.2.7-1ubuntu2.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: Mon Jul 16 16:34:07 2018 ErrorMessage: installed cups-daemon package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-07-16 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=94749527-c5d4-44b0-a72a-3b0c9dba3cc4 ro quiet splash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=94749527-c5d4-44b0-a72a-3b0c9dba3cc4 ro quiet splash Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: cups Title: package cups-daemon 2.2.7-1ubuntu2.1 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1782135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
** Changed in: systemd (Ubuntu) Status: New => Fix Committed -- 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/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device Status in The Ubuntu-power-systems project: Triaged Status in debian-installer package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in debian-installer source package in Xenial: New Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: New Status in debian-installer source package in Bionic: New Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Committed Bug description: == Comment: #0 - ABDUL HALEEM - 2018-07-02 03:55:33 == ---Problem Description--- Ubuntu 18.04.01 ppc64el installer does not detect LSI3008 base SAS disks / MD RAID devices Used 20101020ubuntu543 version to install http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ Contact Information = abdha...@in.ibm.com ---uname output--- Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = BostonLC ---boot type--- Network boot Installer fails to detect the LSI SAS disks / RAID MD device ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device ? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? ? ?? ? ? ??? moves; selects; activates buttons To make sure it detects the disks I had to Detect disks-->Guided partitioning--> Guided - use entire disk ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075 ? ? SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume ? ? SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ ? ? ? ?? ? ? ??? IPR had similar issue reported #164932 and fixed with 4.15.0-20, looks installer need a fix for LSI (mpt3sas) devices too == Comment: #2 - SEETEENA THOUFEEK - 2018-07-03 02:01:47 == 164932 - refers LP1751813 == Comment: #3 - SEETEENA THOUFEEK - 2018-07-03 02:02:51 == Jul 2 08:49:52 anna-install: Installing mdadm-udeb Jul 2 08:49:52 disk-detect: No Intel/DDF RAID disks detected. Jul 2 08:49:52 anna-install: Installing dmraid-udeb Jul 2 08:49:52 disk-detect: No Serial ATA RAID disks detected Jul 2 08:49:53 check-missing-firmware: looking at dmesg again, restarting from \[ 330.659712\] Jul 2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg accordingly Jul 2 08:49:53 check-missing-firmware: saving timestamp for a later use: Jul 2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping Jul 2 08:4
[Touch-packages] [Bug 1782275] Re: Conflict between resolvconf and systemd-resolved dhclient scripts
This issue can be addressed with a manual action, but first you have to dig into the scripts to diagnose the problem, and really if resolvconf is installed then it should just work. Part of this setup involves disabling systemd-resolved, in favor of a "direct" /etc/resolv.conf, to match the network configuration of other systems at my site. We've also found resolvconf to be a good solution to allow flexibility in how the dynamic resolv.conf file is assembled. There are at least two issues that I can see here: 1. When there is more than one script in /etc/dhcp/dhclient-enter- hooks.d/ that defines the make_resolv_conf() shell function, the last definition is the one that "wins." If the "resolvconf" script is renamed to e.g. "zz-resolvconf", then it works correctly. This may be a case for renaming systemd's "resolved" script to something like "00resolved" (borrowing an idea from /etc/X11/Xsession.d/), since it is always present in an out-of-the-box install. 2. The "resolved" script takes effect if the /lib/systemd/systemd- resolved executable is present, when it should probably also check that systemd-resolved is enabled. Currently, the script runs even if systemd- resolved is not active, effectively turning into a no-op (albeit a no-op that clobbers resolvconf's functionality). That would also fix another use case, where systemd-resolved is disabled and resolvconf is absent. In that scenario, the default make_resolv_conf() function from /sbin/dhclient-script should be used. -- 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/1782275 Title: Conflict between resolvconf and systemd-resolved dhclient scripts Status in resolvconf package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I am setting up an Ubuntu 18.04 (bionic) system with ifupdown instead of netplan, as the latter does not meet my needs. I am using resolvconf to update /etc/resolv.conf from DHCP, as in earlier releases. Unfortunately, I am not seeing /etc/resolv.conf (actually a symlink to /run/resolvconf/resolv.conf) being updated; it is only the boilerplate from /etc/resolvconf/resolv.conf.d/head with no server information appended. (My "base" and "tail" files are empty.) I poked around the scripts in /etc, and believe I have found the problem. When resolvconf is installed, the following two files are present: /etc/dhcp/dhclient-enter-hooks.d/resolvconf /etc/dhcp/dhclient-enter-hooks.d/resolved Both of these scripts define the make_resolv_conf() shell function. What I am seeing is that dhclient runs these two scripts in the (alphabetical) order shown, and as the resolved script runs second, it overwrites the resolvconf version of the shell function with its own. As a result, dhclient does not invoke the appropriate update command for resolvconf, even though the hook script was installed correctly. Normally, I would remove the package that is providing the "resolved" script, but this package is systemd, which cannot be removed. I am not sure which of the two packages (resolvconf or systemd) needs to make an accommodation for the other, but it is clear that the current approach does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1782275/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
Hello bugproxy, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device Status in The Ubuntu-power-systems project: Triaged Status in debian-installer package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in debian-installer source package in Xenial: New Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: New Status in debian-installer source package in Bionic: New Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Committed Bug description: == Comment: #0 - ABDUL HALEEM - 2018-07-02 03:55:33 == ---Problem Description--- Ubuntu 18.04.01 ppc64el installer does not detect LSI3008 base SAS disks / MD RAID devices Used 20101020ubuntu543 version to install http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ Contact Information = abdha...@in.ibm.com ---uname output--- Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = BostonLC ---boot type--- Network boot Installer fails to detect the LSI SAS disks / RAID MD device ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device ? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? ? ?? ? ? ??? moves; selects; activates buttons To make sure it detects the disks I had to Detect disks-->Guided partitioning--> Guided - use entire disk ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075 ? ? SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume ? ? SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ ? ? ? ?
[Touch-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
I've uploaded a fixed systemd to cosmic and bionic for this (xenial will follow when I sort out the best way to backport the fix). dannf should be in a position to test this once a new d-i is built using the new udev-udeb. ** Also affects: debian-installer (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: debian-installer (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Adam Conrad (adconrad) ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Adam Conrad (adconrad) ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Adam Conrad (adconrad) -- 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/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device Status in The Ubuntu-power-systems project: Triaged Status in debian-installer package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in debian-installer source package in Xenial: New Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: New Status in debian-installer source package in Bionic: New Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: New Bug description: == Comment: #0 - ABDUL HALEEM - 2018-07-02 03:55:33 == ---Problem Description--- Ubuntu 18.04.01 ppc64el installer does not detect LSI3008 base SAS disks / MD RAID devices Used 20101020ubuntu543 version to install http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ Contact Information = abdha...@in.ibm.com ---uname output--- Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = BostonLC ---boot type--- Network boot Installer fails to detect the LSI SAS disks / RAID MD device ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device ? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? ? ?? ? ? ??? moves; selects; activates buttons To make sure it detects the disks I had to Detect disks-->Guided partitioning--> Guided - use entire disk ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075 ? ? SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume ? ? SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ ? ? ? ?? ?
[Touch-packages] [Bug 1552792] Re: gnome software leaves dependencies installed
https://github.com/hughsie/PackageKit/pull/253 -- 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/1552792 Title: gnome software leaves dependencies installed Status in GNOME Software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Triaged Status in packagekit package in Ubuntu: Triaged Status in gnome-software source package in Bionic: Triaged Status in packagekit source package in Bionic: Triaged Status in gnome-software source package in Cosmic: Triaged Status in packagekit source package in Cosmic: Triaged Bug description: Using gnome software (or another PackageKit or aptdaemon based UI) to install an application - removal of that package leaves behind dependencies Installing an application with ubuntu software centre only leaves behind config files (seen in synaptic labelled for complete removal). After installing and then removing alarm clock with USC - sudo apt-get autoremove [sudo] password for wolf: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade. After cleaning up and then reinstalling with gnome software, followed by the removal sudo apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED libappindicator1 libindicator7 0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade. After this operation, 184 kB disk space will be freed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 3 16:23:45 2016 InstallationDate: Installed on 2015-10-29 (126 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1755120] Re: Computers unusable following latest update to Ubuntu 16.04LTS. Computer unusable
Hello Mark, Thank you for submitting this bug and reporting a problem with computer unusable under Ubuntu 16.04. You made this bug report some time ago and Ubuntu has been updated since then. Could you confirm that this is no longer a problem and that we can close the ticket? If it is still a problem, are you still interested in finding a solution to this bug? If you are, could you let us know and, run the following (only once): apport-collect 1755120 and upload the updated logs and any other logs that are relevant for this particular issue. Thank you again for helping make Ubuntu better. G ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1755120 Title: Computers unusable following latest update to Ubuntu 16.04LTS. Computer unusable Status in mesa package in Ubuntu: Incomplete Bug description: Desktop ikons have disappeared on both laptop and desktop, so unable to access Firefox, Thunderbird or any other essential software. Unable to shutdown other than by powering off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1755120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690364] Re: text missing in applications
Thanks for the update, Martin. I will close the report now. Have a great day! :) G Closed per reporter’s feedback. ** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/1690364 Title: text missing in applications Status in xorg package in Ubuntu: Invalid Bug description: Sometimes when I signup after sleep mode, there's much text missing in several applications. See screenshots: - E.g. Nautilus: directory names and filenames missing, but file symbols are displayed correctly. Also the texts in the left side bar, in the headline, and in the tab header are missing. - When I hover over my email inbox in thunderbird, the email subjects, addresses, timestamps etc. disappear. This problem is occurring maybe in 30% of all cases after sleep mode. I'm using Ubuntu 16.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: /dev/sda6: clean, 856683/22781952 files, 58594296/9424 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 12 13:49:56 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05be] Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] [1002:6606] (rev ff) (prog-if ff) InstallationDate: Installed on 2016-09-22 (231 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E6540 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=6209d39b-1926-4016-8dcf-38037307eed4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0CYT5F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd12/22/2016:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri May 12 13:44:50 2017 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5562 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1690364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735784] Re: package uuid-runtime 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
Hello Sudatt, Thank you for submitting this bug and reporting a problem with Package operation failed in Ubuntu 16.04. You made this bug report some time ago and Ubuntu has been updated since then. Could you confirm that this is no longer a problem and that we can close the ticket? If it is still a problem, are you still interested in finding a solution to this bug? If you are, could you let us know and, run the following (only once): apport-collect 1735784 and upload the updated logs and any other logs that are relevant for this particular issue. Thank you again for helping make Ubuntu better. G ** Changed in: dpkg (Ubuntu) Status: New => Incomplete ** Changed in: util-linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1735784 Title: package uuid-runtime 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: Incomplete Status in util-linux package in Ubuntu: Incomplete Bug description: it always shows a massage that is : "Package operation failed - this installation or removal of a software package failed" ProblemType: Package DistroRelease: Ubuntu 16.04 Package: uuid-runtime 2.27.1-6ubuntu3.3 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Fri Dec 1 21:14:54 2017 DpkgHistoryLog: Start-Date: 2017-12-01 21:13:48 Commandline: aptdaemon role='role-commit-packages' sender=':1.94' Upgrade: thunderbird-gnome-support:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1), dpkg:amd64 (1.18.4ubuntu1.2, 1.18.4ubuntu1.3), thunderbird-locale-en-us:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1), firefox-locale-en:amd64 (57.0+build4-0ubuntu0.16.04.6, 57.0.1+build2-0ubuntu0.16.04.1), thunderbird:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1), firefox:amd64 (57.0+build4-0ubuntu0.16.04.6, 57.0.1+build2-0ubuntu0.16.04.1), libdpkg-perl:amd64 (1.18.4ubuntu1.2, 1.18.4ubuntu1.3), thunderbird-locale-en:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1), dpkg-dev:amd64 (1.18.4ubuntu1.2, 1.18.4ubuntu1.3) DuplicateSignature: package:uuid-runtime:2.27.1-6ubuntu3.3 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package uuid-runtime (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-08-26 (96 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: util-linux Title: package uuid-runtime 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1735784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1736381] Re: package apport 2.14.1-0ubuntu3.27 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Hello Nilesh, Thank you for submitting this bug and reporting a problem with apt-get upgrade in Ubuntu 14.04. You made this bug report some time ago and Ubuntu has been updated since then. Could you confirm that this is no longer a problem and that we can close the ticket? If it is still a problem, are you still interested in finding a solution to this bug? If you are, could you let us know and, run the following (only once): apport-collect 1736381 and upload the updated logs and any other logs that are relevant for this particular issue. Thank you again for helping make Ubuntu better. G ** Changed in: apport (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1736381 Title: package apport 2.14.1-0ubuntu3.27 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in apport package in Ubuntu: Incomplete Bug description: Hi, We are working on Ubuntu 14.04LTS. We are trying to "sudo apt-get upgrade". In that, we are getting error similar as below: Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: linux-image-4.4.0-98-generic linux-image-extra-4.4.0-98-generic Use 'apt-get autoremove' to remove them. The following packages have been kept back: libvlc-dev libvlc5 vlc vlc-data vlc-nox vlc-plugin-notify The following packages will be upgraded: curl evince evince-common firefox firefox-locale-en idle-python2.7 libcairo-gobject2 libcairo2 libcurl3 libcurl3-gnutls libdvdnav-dev libdvdnav4 libdvdread-dev libdvdread4 libevdocument3-4 libevview3-3 libpython2.7 libpython2.7-minimal libpython2.7-stdlib libpython3.4 libpython3.4-minimal libpython3.4-stdlib libshine3 libssh-4 libxcursor1 libxfont1 python2.7 python2.7-minimal python3.4 python3.4-minimal resolvconf thunderbird thunderbird-gnome-support 33 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. 19 not fully installed or removed. Need to get 98.7 MB of archives. After this operation, 322 kB disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://ppa.launchpad.net/jonathonf/vlc/ubuntu/ trusty/main libcairo2 amd64 1.14.6-1~14.04.york0 [556 kB] Get:2 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libpython3.4 amd64 3.4.3-1ubuntu1~14.04.6 [1,305 kB] Get:3 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main python3.4 amd64 3.4.3-1ubuntu1~14.04.6 [178 kB] Get:4 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libpython3.4-stdlib amd64 3.4.3-1ubuntu1~14.04.6 [1,987 kB] Get:5 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main python3.4-minimal amd64 3.4.3-1ubuntu1~14.04.6 [1,224 kB] Get:6 http://ppa.launchpad.net/jonathonf/vlc/ubuntu/ trusty/main libcairo-gobject2 amd64 1.14.6-1~14.04.york0 [132 kB] Get:7 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libpython3.4-minimal amd64 3.4.3-1ubuntu1~14.04.6 [460 kB] Get:8 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main resolvconf all 1.69ubuntu1.3 [55.3 kB] Get:9 http://ppa.launchpad.net/jonathonf/vlc/ubuntu/ trusty/main libdvdread-dev amd64 5.0.3-1~14.04.york0 [68.4 kB] Get:10 http://ppa.launchpad.net/jonathonf/vlc/ubuntu/ trusty/main libdvdread4 amd64 5.0.3-1~14.04.york0 [54.8 kB] Get:11 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libcurl3-gnutls amd64 7.35.0-1ubuntu2.13 [166 kB] Get:12 http://ppa.launchpad.net/jonathonf/vlc/ubuntu/ trusty/main libdvdnav-dev amd64 5.0.3-1~14.04.york0 [54.2 kB] Get:13 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main curl amd64 7.35.0-1ubuntu2.13 [123 kB] Get:14 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libcurl3 amd64 7.35.0-1ubuntu2.13 [173 kB] Get:15 http://ppa.launchpad.net/jonathonf/vlc/ubuntu/ trusty/main libdvdnav4 amd64 5.0.3-1~14.04.york0 [41.1 kB] Get:16 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main python2.7 amd64 2.7.6-8ubuntu0.4 [196 kB] Get:17 http://ppa.launchpad.net/jonathonf/vlc/ubuntu/ trusty/main libshine3 amd64 3.1.0-4~14.04.york0 [25.3 kB] Get:18 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libpython2.7 amd64 2.7.6-8ubuntu0.4 [1,040 kB] Get:19 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libpython2.7-stdlib amd64 2.7.6-8ubuntu0.4 [1,869 kB] Get:20 http://ppa.launchpad.net/jonathonf/vlc/ubuntu/ trusty/main libssh-4 amd64 0.6.3-4.3~14.04.york0 [120 kB] Get:21 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main python2.7-minimal amd64 2.7.6-8ubuntu0.4 [1,188 kB] Get:22 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libpython2.7-minimal amd64 2.7.6-8ubuntu0.4 [307 kB] Get:23 http://us.archive.ubuntu.com/
[Touch-packages] [Bug 1697929] Re: Memory leak in xorg.
Thanks for the update, Volodymyr. Have a great day! :) G Closed per reporter’s feedback. ** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/1697929 Title: Memory leak in xorg. Status in xorg package in Ubuntu: Invalid Bug description: Seems that xorg has a memory leak. On 28th day of uptime it consumes 13G of virtualy memory on my PC: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 21516 root 20 0 13,340g 8,351g 49036 S 7,3 53,7 3387:19 Xorg xrestop does not show anything suspicious: xrestop - Display: localhost Monitoring 23 clients. XErrors: 0 Pixmaps: 171661K total, Other: 138K total, All: 171800K total res-base Wins GCs Fnts Pxms Misc Pxm mem Other Total PID Identifier 1e0 110 23 34581170K 8K 81178K ? xcompmgr 08031 171 17 26845896K 8K 45904K ? i3 000 1020 15720111K 5K 20116K ? i3 20033 181 19 15718527K 5K 18533K 23441 Thunderbird 0c027 1414 117 3826K 4K 3830K 21872 emacs 1204131 12 3452 1560K 82K 1642K 21822 Terminal 0e0 34039 570K384B570K ? i3bar for output DP2 1c0 2130 1730B 7K 7K ? screensaver 240 2200 1524B 3K 3K 25174 notify-osd 180 3100 1300B 3K 3K ? 280 0100 1060B 2K 2K ? 140 8 3111 114B 2K 2K 31068 chromium-browser 160 4110 450B 2K 2K 31068 Report a bug : Bugs : linux package : 260 4300 498B 1K 1K 25553 Network 2c0 3100 120B384B384B 21027 gnome-screensaver 100 010020B 72B 72B ? 2a0 110000B 48B 48B ? xrestop 1a0 110000B 48B 48B ? 040 110000B 48B 48B ? 220 010000B 24B 24B ? 060 010000B 24B 24B ? 0a0 000000B 0B 0B ? Description: Ubuntu 16.04.2 LTS Release: 16.04 xorg: Installed: 1:7.7+13ubuntu3 Candidate: 1:7.7+13ubuntu3 Version table: *** 1:7.7+13ubuntu3 500 500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lorc 1736 F pulseaudio CurrentDesktop: i3 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6071d270-1c91-42c9-a5e5-fb2326b04098 InstallationDate: Installed on 2016-10-04 (253 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP ProDesk 600 G2 SFF Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic.efi.signed root=UUID=60ffd1b6-b4b8-4a93-a697-cb95f923a535 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 RelatedPackageVersions: linux-restricted-modules-4.4.0-75-generic N/A linux-backports-modules-4.4.0-75-generic N/A linux-firmware1.157.8 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp _MarkForUpload: True dmi.bios.date: 11/01/2016 dmi.bios.vendor: HP dmi.bios.version: N02 Ver. 02.17 dmi.board.name: 805D dmi.board.vendor: HP dmi.board.version: KBC Version 05.22 dmi.chassis.asset.tag: CZC5520SDC dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN02Ver.02.17:bd11/01/2016:svnHP:pnHPProDesk600G2SFF:pvr:rvnHP:rn805D:rvrKBCVersion05.22:cvnHP:ct4:cvr: dmi.product.name: HP ProDesk 600 G2 SFF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1697929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782802] [NEW] ditch ipconfig in favor of dhclient -4 in 18.10
Public bug reported: When adding ipv6 netboot support to initramfs-tools in yakkety/zesty, this was initially attempted with replacing ipconfig with dhclient. As described in LP: #1621507, the use of dhclient for ipv4 dhcp was backed out in favor of ipconfig. So at the moment, we are using both ipconfig from klibc-utils and dhclient from isc-dhcp-client in the initramfs. We want to switch off of klibc-utils completely and use isc-dhcp-client for both ipv4 and ipv6 in initramfs-tools. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1782802 Title: ditch ipconfig in favor of dhclient -4 in 18.10 Status in initramfs-tools package in Ubuntu: New Bug description: When adding ipv6 netboot support to initramfs-tools in yakkety/zesty, this was initially attempted with replacing ipconfig with dhclient. As described in LP: #1621507, the use of dhclient for ipv4 dhcp was backed out in favor of ipconfig. So at the moment, we are using both ipconfig from klibc-utils and dhclient from isc-dhcp-client in the initramfs. We want to switch off of klibc-utils completely and use isc-dhcp- client for both ipv4 and ipv6 in initramfs-tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1782802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1779237] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
J'ai fait comme Dimitri a écrit sudo apt-get install --reinstall hplip hplip-data sudo apt-get installer --réinstall python3 Merci Excelent JeanMa -- 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/1779237 Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: Invalid Bug description: Only Ubuntu Update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jun 28 22:51:28 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-13 (76 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: python3-defaults Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 214786] Re: Apple USB ISO keyboard has incorrectly swapped keys
Error still present in 18.04 (German Apple wired USB keyboard) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/214786 Title: Apple USB ISO keyboard has incorrectly swapped keys Status in Mactel Support: Confirmed Status in linux package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: Since upgrading kernel to version 2.6.24-12.22 two keys are now swapped on my Apple USB aluminium keyboard with danish layout. Now the keys "<" and "½" are swapped and no longer matches the actual print on the keycaps. The error is isolated to the following commit: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu- hardy.git;a=commitdiff;h=efb3031b446d441dca5b10619503ac0bba7f9748 This commit introduced a key swapping for all "ISO" type Apple keyboards. In my case this swapping is incorrect, and generally it seems like a very bad idea to perform hard coded locale specific key mapping in kernel space as this is also done several places in user space. The included patch reverts the behavior to the default that matches the keycap printing. To manage notifications about this bug go to: https://bugs.launchpad.net/mactel-support/+bug/214786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Solution in #123 did not work for me, even with higher sleep time. So I have to switch back to lightdm. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726873] Re: mount.ecryptfs_private can't mount in 17.10
*** This bug is a duplicate of bug 1718658 *** https://bugs.launchpad.net/bugs/1718658 Doing a manual mount like so (used for safely storing private data in the cloud) used to work since Ubuntu 12 or so. However, today after updating from Ubuntu 16.04 LTS to 18.04 LTS, the entire thing wouldn't mount anymore: ``` $ echo mypassphrase | sudo ecryptfs-add-passphrase --fnek - Inserted auth tok with sig [abc] into the user session keyring Inserted auth tok with sig [123] into the user session keyring $ sudo /bin/mount -it ecryptfs "/media/locked" "/media/unlocked" -o ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_sig=abc,ecryptfs_fnek_sig=123 mount: /home/local/Dropbox.unlocked: mount(2) system call failed: No such file or directory. ``` I read the following messages in `/var/log/syslog`: ``` kernel: [ 5608.396634] Could not find key with description: [abc] kernel: [ 5608.396641] Could not find valid key in user session keyring for sig specified in mount option: [abc] ``` Apparently there are different keyrings now. This fixed my script: ``` $ sudo keyctl link @u @s $ sudo /bin/mount -it ecryptfs "/media/locked" "/media/unlocked" -o ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_sig=abc,ecryptfs_fnek_sig=123 ``` For now everything works again, but the thing seems buggy. Ubuntu even dropped the encrypted home because of it. Ecryptfs seems to be eol. Looking for fresh solutions to protect the privacy of my cloud files. -- 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/1726873 Title: mount.ecryptfs_private can't mount in 17.10 Status in ecryptfs-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Hi, I am using several ecryptfs mounts with ecryptfs-add-passphrase and mount.ecryptfs_private, configured in ~/.ecryptfs/xxx.conf and ~/.ecryptfs/xxx.sig, which was working well for years up to 17.04. With 17.10 I can't mount these file systems anymore. ecryptfs-add-passphrase says Inserted auth tok with sig [] into the user session keyring with the correct sig (!). Trying to mount with mount.ecryptfs_private then says mount: No such file or directory although all directories present and correct. the Kernel then says (dmesg): [10149.247972] Could not find key with description: [...] [10149.247994] process_request_key_err: No key [10149.248000] Could not find valid key in user session keyring for sig specified in mount option: [...] [10149.248012] One or more global auth toks could not properly register; rc = [-2] [10149.248019] Error parsing options; rc = [-2] with exactly the same sig! So although ecryptfs-add-passphrase claimed to have added the key to the keyring, the kernel complains that it could not find such a key. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ecryptfs-utils 111-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: LXDE Date: Tue Oct 24 15:31:45 2017 InstallationDate: Installed on 2017-10-24 (0 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) SourcePackage: ecryptfs-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1726873/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726873] Re: mount.ecryptfs_private can't mount in 17.10
*** This bug is a duplicate of bug 1718658 *** https://bugs.launchpad.net/bugs/1718658 Oops sorry, I missed the duplicate warning! -- 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/1726873 Title: mount.ecryptfs_private can't mount in 17.10 Status in ecryptfs-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Hi, I am using several ecryptfs mounts with ecryptfs-add-passphrase and mount.ecryptfs_private, configured in ~/.ecryptfs/xxx.conf and ~/.ecryptfs/xxx.sig, which was working well for years up to 17.04. With 17.10 I can't mount these file systems anymore. ecryptfs-add-passphrase says Inserted auth tok with sig [] into the user session keyring with the correct sig (!). Trying to mount with mount.ecryptfs_private then says mount: No such file or directory although all directories present and correct. the Kernel then says (dmesg): [10149.247972] Could not find key with description: [...] [10149.247994] process_request_key_err: No key [10149.248000] Could not find valid key in user session keyring for sig specified in mount option: [...] [10149.248012] One or more global auth toks could not properly register; rc = [-2] [10149.248019] Error parsing options; rc = [-2] with exactly the same sig! So although ecryptfs-add-passphrase claimed to have added the key to the keyring, the kernel complains that it could not find such a key. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ecryptfs-utils 111-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: LXDE Date: Tue Oct 24 15:31:45 2017 InstallationDate: Installed on 2017-10-24 (0 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) SourcePackage: ecryptfs-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1726873/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
#26 fixed this for me. Doing a manual mount like so (used for safely storing private data in the cloud) used to work since Ubuntu 12 or so. However, today after updating from Ubuntu 16.04 LTS to 18.04 LTS, the entire thing wouldn't mount anymore: ``` $ echo mypassphrase | sudo ecryptfs-add-passphrase --fnek - Inserted auth tok with sig [abc] into the user session keyring Inserted auth tok with sig [123] into the user session keyring $ sudo /bin/mount -it ecryptfs "/media/locked" "/media/unlocked" -o ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_sig=abc,ecryptfs_fnek_sig=123 mount: /home/local/Dropbox.unlocked: mount(2) system call failed: No such file or directory. ``` I read the following messages in `/var/log/syslog`: ``` kernel: [ 5608.396634] Could not find key with description: [abc] kernel: [ 5608.396641] Could not find valid key in user session keyring for sig specified in mount option: [abc] ``` Apparently there are different keyrings now. This fixed my script: ``` $ sudo keyctl link @u @s $ sudo /bin/mount -it ecryptfs "/media/locked" "/media/unlocked" -o ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_sig=abc,ecryptfs_fnek_sig=123 ``` For now everything works again, but the thing seems buggy. Ubuntu even dropped the encrypted home because of it. Ecryptfs seems to be eol. Looking for fresh solutions to protect the privacy of my cloud files. -- 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/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys Status in ecryptfs-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: ecryptfs-mount-private fails to mount the ecryptfs after the 1st reboot after creating the ecryptfs by ecryptfs-setup-private. After the unsucessful attempt dmesg contains: [ 1265.695388] Could not find key with description: [] [ 1265.695393] process_request_key_err: No key [ 1265.695394] Could not find valid key in user session keyring for sig specified in mount option: [] [ 1265.695395] One or more global auth toks could not properly register; rc = [-2] [ 1265.695396] Error parsing options; rc = [-2] Note: The correct key ID has been replaced in the "". I also accidentally found an workaround - just running ecrytpfs- manager and then the ecryptfs-mount-private (it does not ask for password for the second time and mounts the ecryptfs correctly): host:~$ ecryptfs-manager eCryptfs key management menu --- 1. Add passphrase key to keyring 2. Add public key to keyring 3. Generate new public/private keypair 4. Exit Make selection: 4 host:~$ ls Private/ Access-Your-Private-Data.desktop README.txt host:~$ ecryptfs-mount-private host:~$ ls Private/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781608] Re: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
You have a broken third party init script installed named "discagent". You will need to remove it. ** Changed in: util-linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1781608 Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: Invalid Bug description: Was part of a group of packages that apt-get upgrade pulled down. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.4 ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49 Uname: Linux 4.4.0-67-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Jul 13 10:21:56 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-06-26 (17 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.10ubuntu1 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.pam.d.runuser: 2018-07-12T17:51:21.962750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1781608/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1690364] Re: text missing in applications
Hi, Thanks for fixing the issue! I didn't see it the last weeks anymore, so I think you can close the ticket. Best regards Martin Am 20.07.2018 um 02:24 schrieb gf: > Hello Martin, > Thank you for submitting this bug and reporting a problem with text missing > after suspend. You made this bug report some time ago and Ubuntu has been > updated since then. > > Could you confirm that this is no longer a problem and that we can close the > ticket? > If it is still a problem, are you still interested in finding a solution to > this bug? > If you are, could you let us know and, run the following (only once): > apport-collect 1690364 > and upload the updated logs and and any other logs that are relevant for this > particular issue. > > Thank you again for helping make Ubuntu better. > G > > ** 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/1690364 Title: text missing in applications Status in xorg package in Ubuntu: Incomplete Bug description: Sometimes when I signup after sleep mode, there's much text missing in several applications. See screenshots: - E.g. Nautilus: directory names and filenames missing, but file symbols are displayed correctly. Also the texts in the left side bar, in the headline, and in the tab header are missing. - When I hover over my email inbox in thunderbird, the email subjects, addresses, timestamps etc. disappear. This problem is occurring maybe in 30% of all cases after sleep mode. I'm using Ubuntu 16.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: /dev/sda6: clean, 856683/22781952 files, 58594296/9424 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 12 13:49:56 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05be] Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] [1002:6606] (rev ff) (prog-if ff) InstallationDate: Installed on 2016-09-22 (231 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E6540 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=6209d39b-1926-4016-8dcf-38037307eed4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0CYT5F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd12/22/2016:svnDellInc.:pnLatitudeE6540:pvr00:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri May 12 13:44:50 2017 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5562 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1690364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://laun
Re: [Touch-packages] [Bug 1779237] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
Thanks for help Have a nice day ;) 2018-07-20 13:10 GMT+02:00 paul <1779...@bugs.launchpad.net>: > hello > > after this answer > > I did like Dimitri wrote > hello > > Hello > sudo apt-get install --reinstall hplip hplip-data > sudo apt-get install --reinstall python3 > > solve my problem very good > > > Thank you > Paul > > > > > > > Thank Dimitri > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1781849). > https://bugs.launchpad.net/bugs/1779237 > > Title: > package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed > python3 package post-installation script subprocess returned error > exit status 4 > > Status in python3-defaults package in Ubuntu: > Invalid > > Bug description: > Only Ubuntu Update > > ProblemType: Package > DistroRelease: Ubuntu 18.04 > Package: python3 3.6.5-3ubuntu1 > ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 > Uname: Linux 4.15.0-22-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.2 > Architecture: amd64 > Date: Thu Jun 28 22:51:28 2018 > ErrorMessage: installed python3 package post-installation script > subprocess returned error exit status 4 > InstallationDate: Installed on 2018-04-13 (76 days ago) > InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 > (20180228) > Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, > 3.6.5-3ubuntu1 > PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, > 2.7.15~rc1-1 > RelatedPackageVersions: >dpkg 1.19.0.5ubuntu2 >apt 1.6.2 > SourcePackage: python3-defaults > Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: > installed python3 package post-installation script subprocess returned > error exit status 4 > UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+ > subscriptions > -- 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/1779237 Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: Invalid Bug description: Only Ubuntu Update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jun 28 22:51:28 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-13 (76 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: python3-defaults Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738034] Re: Muted Sound Indicator randomly remains red when no sound is playing
Sorry for my deleted comment, since you said "it's most likely THE issue with..." I thought you were referring to some specific issue that you failed to mention. I assume you meant "most likely AN issue with". Anyway, The icon is EXPECTED to become red when a sound plays and the volume is muted. The issue is that the icon doesn't go back to normal and REMAINS red when the sound is finished playing. I find it hard to believe this is an issue with an theme, are you sure it is? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1738034 Title: Muted Sound Indicator randomly remains red when no sound is playing Status in indicator-sound package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: New Bug description: Steps to reproduce: 1. Mute the main Ubuntu volume 2. Play some short sound Expected behavior: Obviously you won't hear the sound. While the sound plays, the indicator should become red; then, when the sound is done playing and nothing else is playing, either immediately or after a very short period (e.g. a couple of seconds), the indicator should go back to its normal color. Observed behavior: Sometimes it behaves as expected, but sometimes it will remain red forever, until you unmute it. It's utterly random. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: indicator-sound 12.10.2+16.04.20160406-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 13 17:09:25 2017 InstallationDate: Installed on 2013-10-11 (1523 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-sound.log: (process:2339): indicator-sound-WARNING **: accounts-service-access.vala:218: unable to sync volume 0,608643 to AccountsService: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface 'com.ubuntu.AccountsService.Sound' (process:2339): indicator-sound-WARNING **: accounts-service-access.vala:218: unable to sync volume 0,848633 to AccountsService: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface 'com.ubuntu.AccountsService.Sound' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1738034/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738034] Re: Muted Sound Indicator randomly remains red when no sound is playing
The icon is EXPECTED to become red when a sound plays and the volume is muted. The issue is that the icon doesn't go back to normal and REMAINS red when the sound is finished playing. I find it hard to believe this is an issue with an icon-theme, but if that is the case, could you please point to where that supposed issue is described? It doesn't make sense to mark this bug as invalid. If it is a duplicate of some other bug, mark it as such, otherwise this is a bug that is not fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1738034 Title: Muted Sound Indicator randomly remains red when no sound is playing Status in indicator-sound package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: New Bug description: Steps to reproduce: 1. Mute the main Ubuntu volume 2. Play some short sound Expected behavior: Obviously you won't hear the sound. While the sound plays, the indicator should become red; then, when the sound is done playing and nothing else is playing, either immediately or after a very short period (e.g. a couple of seconds), the indicator should go back to its normal color. Observed behavior: Sometimes it behaves as expected, but sometimes it will remain red forever, until you unmute it. It's utterly random. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: indicator-sound 12.10.2+16.04.20160406-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 13 17:09:25 2017 InstallationDate: Installed on 2013-10-11 (1523 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-sound.log: (process:2339): indicator-sound-WARNING **: accounts-service-access.vala:218: unable to sync volume 0,608643 to AccountsService: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface 'com.ubuntu.AccountsService.Sound' (process:2339): indicator-sound-WARNING **: accounts-service-access.vala:218: unable to sync volume 0,848633 to AccountsService: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface 'com.ubuntu.AccountsService.Sound' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1738034/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779438] Re: Cannot resolve names using systemd-resolved stub resolver
To revert to using upstream dns servers directly instead of stub, change /etc/resolv.conf to point at /run/systemd/resolve/resolv.conf instead of ../run/systemd/resolve/stub-resolv.conf However, it would be nice to figure out what domain you are trying to resolve, and what is the result of it. Can you e.g. reproduce both queries against resolved dns server and upstream dns server, and capture systemd-resolved logs and/or network traffic with wireshark? -- 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/1779438 Title: Cannot resolve names using systemd-resolved stub resolver Status in systemd package in Ubuntu: Incomplete Bug description: Description: Ubuntu 18.04 LTS Release: 18.04 I am running a clean install of Ubuntu 18.04. This bug was also present for me on a clean install of Ubuntu 17.10 and I had a solution, but it appears to no longer work. What I expect to happen: Ping other hosts on network by name What happened instead: I can't ping other machines on network via name. From my Ubuntu 18.04 machine, I `ping ubuntu-test-1` and `ping ubuntu-test-1.localdomain` but neither work. I can ping by IP address though. The other machines on the network are Ubuntu Server 16.04.3 machines and can ping each other by name also. All machines on network including problem one receive DHCP leases from same server (192.168.20.1) I believe the problem is systemd-resolved stub resolver. `cat /etc/resolv.conf` # This file is managed by man:systemd-resolved(8). Do not edit. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "systemd-resolve --status" to see details about the uplink DNS servers # currently in use. # # Third party programs must not access this file directly, but only through the # symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way, # replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 search localdomain If I change the nameserver line to the IP of my nameserver, not the stub, resolution works. nameserver 192.168.20.1 search localdomain Now I can ping hosts by name. I used to solve this problem like this... `sudo systemctl disable systemd-resolved.service` `echo "nameserver 192.168.20.1" | sudo tee -a /etc/resolvconf/resolv.conf.d/tail` `sudo reboot` But /etc/resolvconf/resolv.conf.d no longer exists, and it's about time this problem was fixed :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765832] Re: Two finger scrolling not working after suspend
*** This bug is a duplicate of bug 1722478 *** https://bugs.launchpad.net/bugs/1722478 ** This bug has been marked a duplicate of bug 1722478 Two-finger scrolling no longer works after resuming from suspend -- 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/1765832 Title: Two finger scrolling not working after suspend Status in xorg package in Ubuntu: Confirmed Bug description: When waking up my laptop, two finger scrolling is not working anymore. Running: $ modprobe -r psmouse $ modprobe psmouse restores the functionality. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 20 08:23:33 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2227] InstallationDate: Installed on 2018-04-10 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) MachineType: LENOVO 20BTS09800 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET26W (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTS09800 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET26W(1.04):bd01/23/2015:svnLENOVO:pn20BTS09800:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS09800:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BTS09800 dmi.product.version: ThinkPad X1 Carbon 3rd 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 N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765832/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782739] [NEW] Boot to Black
Public bug reported: When I boot my new Ubuntu 18.04LTS install on my ASUS flipbook I see the splash screen as expected. The boot continues and it reaches the point where you would expect to see the login screen. I see what appears to be a non-backlighted blank black screen. If I wait until all hard drive activity ceases and then type in my password and press enter the login completes and I am presented a normal Ubuntu desktop. Thank you Gene ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 20 07:16:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:166d] InstallationDate: Installed on 2018-07-20 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. TP550LA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=5b0bd839-3614-4f3d-8536-bc400cd364e5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP550LA.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP550LA.210:bd06/27/2014:svnASUSTeKCOMPUTERINC.:pnTP550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP550LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1782739 Title: Boot to Black Status in xorg package in Ubuntu: New Bug description: When I boot my new Ubuntu 18.04LTS install on my ASUS flipbook I see the splash screen as expected. The boot continues and it reaches the point where you would expect to see the login screen. I see what appears to be a non-backlighted blank black screen. If I wait until all hard drive activity ceases and then type in my password and press enter the login completes and I am presented a normal Ubuntu desktop. Thank you Gene ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 20 07:16:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:166d] InstallationDate: Installed on 2018-07-20 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. TP550LA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=5b0bd839-3614-4f3d-8536-bc400cd364e5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probab
[Touch-packages] [Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state
** Changed in: init-system-helpers (Ubuntu) Status: New => In Progress ** Changed in: init-system-helpers (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: init-system-helpers (Ubuntu) Importance: Undecided => Critical ** Changed in: init-system-helpers (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1778219 Title: unattended-upgrades hangs on shutdown, leaves system in a broken state Status in init-system-helpers package in Ubuntu: In Progress Status in snapd package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: When using unattended-upgrades with "InstallOnShutdown" on Bionic, the package installation on various packages hangs until the systemd ShutdownTimeout (30min) is expired and systemd kills all processes and powers off/reboots the system. This leaves packages in an unconfigured, broken state. At least sometimes this cannot be fixed with a "dpkg --configure -a", but instead requires the user to manually reinstall the package that caused the hang. This appears to be a deadlock, because the hanging commands are always "systemctl stop ..." or "systemctl restart ...", etc.. If I understand this correctly, those systemctl commands block because systemd tries to shutdown the system and tries to satisfy all dependencies for the shutdown targets before those systemctl commands could get executed, which creates a deadlock. Steps to reproduce: - Install 18.04 - activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades - disable bionic-updates in /etc/apt/sources.list (more on that later) - execute "unattended-upgrade --download-only" - reboot the system -> The upgrade on shutdown hangs when configuring the apport package. The hanging command is "systemctl stop apport-forward.socket". The system hangs until the systemd ShutdownTimeout expires and systemd forcefully reboots the system. After the system is rebooted the apport package is in "iUR" state, and needs to be reinstalled to fix this. I disabled the bionic-updates pocket in sources.list, because in the default configuration unattended-updates does not use bionic-updates, and seems to have skipped installation of apport from bionic-security (supposedly because an already newer version of apport was in bionic- updates). If my understanding of why apport initially did not get installed is correct, then this would be another problem, because it would mean that unattended-upgrades potentially does not install all available security updates when bionic-updates is enabled in sources.list (which is the default). The problem can also be reproduced without disabling bionic-updates in sources.list, but instead enabling bionic-updates in /etc/apt/apt.conf.d/50unattended-upgrades. Then, in my case, the upgrade did hang when installing the package snapd (the hanging command was "systemctl stop snapd.autoimport.service snapd.core-fixup.service snapd.service snapd.snap-repair.service snapd.snap-repair.service snapd.socket snapd.system-shutdown.service"). This leads to the same problems as described above. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: unattended-upgrades 1.1ubuntu1 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1778219/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779237] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
hello after this answer I did like Dimitri wrote hello Hello sudo apt-get install --reinstall hplip hplip-data sudo apt-get install --reinstall python3 solve my problem very good Thank you Paul > Thank Dimitri -- 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/1779237 Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: Invalid Bug description: Only Ubuntu Update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jun 28 22:51:28 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-13 (76 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: python3-defaults Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1697929] Re: Memory leak in xorg.
Hello gf, This bug disappeared after one of upgrades. But I'm not certain, what exactly fixed it. I think, it can be closed now. -- 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/1697929 Title: Memory leak in xorg. Status in xorg package in Ubuntu: Incomplete Bug description: Seems that xorg has a memory leak. On 28th day of uptime it consumes 13G of virtualy memory on my PC: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 21516 root 20 0 13,340g 8,351g 49036 S 7,3 53,7 3387:19 Xorg xrestop does not show anything suspicious: xrestop - Display: localhost Monitoring 23 clients. XErrors: 0 Pixmaps: 171661K total, Other: 138K total, All: 171800K total res-base Wins GCs Fnts Pxms Misc Pxm mem Other Total PID Identifier 1e0 110 23 34581170K 8K 81178K ? xcompmgr 08031 171 17 26845896K 8K 45904K ? i3 000 1020 15720111K 5K 20116K ? i3 20033 181 19 15718527K 5K 18533K 23441 Thunderbird 0c027 1414 117 3826K 4K 3830K 21872 emacs 1204131 12 3452 1560K 82K 1642K 21822 Terminal 0e0 34039 570K384B570K ? i3bar for output DP2 1c0 2130 1730B 7K 7K ? screensaver 240 2200 1524B 3K 3K 25174 notify-osd 180 3100 1300B 3K 3K ? 280 0100 1060B 2K 2K ? 140 8 3111 114B 2K 2K 31068 chromium-browser 160 4110 450B 2K 2K 31068 Report a bug : Bugs : linux package : 260 4300 498B 1K 1K 25553 Network 2c0 3100 120B384B384B 21027 gnome-screensaver 100 010020B 72B 72B ? 2a0 110000B 48B 48B ? xrestop 1a0 110000B 48B 48B ? 040 110000B 48B 48B ? 220 010000B 24B 24B ? 060 010000B 24B 24B ? 0a0 000000B 0B 0B ? Description: Ubuntu 16.04.2 LTS Release: 16.04 xorg: Installed: 1:7.7+13ubuntu3 Candidate: 1:7.7+13ubuntu3 Version table: *** 1:7.7+13ubuntu3 500 500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lorc 1736 F pulseaudio CurrentDesktop: i3 DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6071d270-1c91-42c9-a5e5-fb2326b04098 InstallationDate: Installed on 2016-10-04 (253 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP ProDesk 600 G2 SFF Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-75-generic.efi.signed root=UUID=60ffd1b6-b4b8-4a93-a697-cb95f923a535 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 RelatedPackageVersions: linux-restricted-modules-4.4.0-75-generic N/A linux-backports-modules-4.4.0-75-generic N/A linux-firmware1.157.8 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-75-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp _MarkForUpload: True dmi.bios.date: 11/01/2016 dmi.bios.vendor: HP dmi.bios.version: N02 Ver. 02.17 dmi.board.name: 805D dmi.board.vendor: HP dmi.board.version: KBC Version 05.22 dmi.chassis.asset.tag: CZC5520SDC dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN02Ver.02.17:bd11/01/2016:svnHP:pnHPProDesk600G2SFF:pvr:rvnHP:rn805D:rvrKBCVersion05.22:cvnHP:ct4:cvr: dmi.product.name: HP ProDesk 600 G2 SFF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1697929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777415] Re: Local authorization bypass by using suspend mode
Seth, what do you mean by Xfce's screenslocking package? Ubuntu Mate 18.04 does not contain light-locker package by default: http://cdimage.ubuntu.com/ubuntu-mate/releases/18.04/release/ubuntu- mate-18.04-desktop-amd64.manifest What is the screenlocking package for Mate? -- 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/1777415 Title: Local authorization bypass by using suspend mode Status in Unity: New Status in pam package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Version: Ubuntu 16.04.04 LTS Desktop, all packets are updated at 15.06.2018 Affects: access to latest user opened applications, that can contain sensitive information (documents, private information, passwords, etc.) How to reproduce: 1. open some applications (LibreOffice, browsers, editors, ...) 2. go to suspend mode 3. extract hard drive 4. wake up 5. after that can be several behaviors: * Ubuntu show lock screen. Enter ANY password -> access granted. * Ubuntu show lock screen. Enter ANY password, access denied. Fast press the hardware shutdown button -> access granted. * Ubuntu does not show lock screen, only black screen. We can repeat actions like in previous paragraphs To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1777415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735088] Re: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
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/1735088 Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) Status in initramfs-tools package in Ubuntu: Confirmed Bug description: running update-initramfs -u never completes. Any package install that that attempts to update initramfs sit and hangs. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: initramfs-tools 0.125ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Tue Nov 28 23:51:18 2017 ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2016-11-01 (393 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.125ubuntu12 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) 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/1735088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782641] Re: Request: Rename "ubuntu-keyring" package to "ubuntu-archive-keyring" for consistency with Debian
Ubuntu will not ship a keyring with ubuntu uploaders keys. The permission model in ubuntu is very different from debian and is not based on GPG web of trust. In debian, any DD can upload any package, thus debian-keyring make sense to keep track of all the uploader keys. In Ubuntu, launchpad is the only thing that enforces which keys are allowed to upload and they are scoped a lot - only a minority of keys are allowed to upload anything, and vast majority of uploaders can only upload individual packages or subsets of them. I have no idea why debian choose a different name when importing our package =/ If that is of any help, i'm happy to add Provides stanzas to help with discovery. But I very much see no benefit in renaming this key package in Ubuntu, given that we have not changed it since Ubuntu inception. Note that the ubuntu-keyring package ships not only the keyring that is used to validate APT archives, but other signed metadata as well, for example - /pool/ on the ISOs; cdimage checksum files of ubuntu ISOs; cloud images simplestreams metadata; cloud images checksum files; master key for archive key rotation. Thus naming the package (either source, of one of the binaries) as ubuntu-archive-keyring makes no sense, as it validates more than just the APT archive. ** Changed in: ubuntu-keyring (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1782641 Title: Request: Rename "ubuntu-keyring" package to "ubuntu-archive-keyring" for consistency with Debian Status in ubuntu-keyring package in Ubuntu: Opinion Bug description: The package that Ubuntu calls "ubuntu-keyring" is present in Debian as "ubuntu-archive-keyring". Debian has separate "debian-keyring" and "debian-archive-keyring" packages, described as follows: d-k: GnuPG keys of Debian Developers and Maintainers d-a-k: GnuPG archive keys of the Debian archive IMO this is a reasonable distinction, as the keys of developers/maintainers are rarely needed by end users, and the d-k package is significantly larger (on the order of 30 MB). Thus, the current "ubuntu-keyring" package would be better named "ubuntu-archive-keyring", not only so that the equivalent package has the same name in both distros, but also to maintain the same distinction between developer keys and archive keys. (Ubuntu could potentially decide to ship a package containing Ubuntu developer keys in the future, and it would be awkward if this needed to be named e.g. "ubuntu-devel-keyring" or the like.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1782641/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779438] Re: Cannot resolve names using systemd-resolved stub resolver
This is a recent install, so haven't installed much apart from my usual programs, vim, editors, etc... I would expect to be able to ping by hostname without installing additional software such as resolver libraries. Here is my /etc/nsswitch.conf `cat /etc/nsswitch.conf` # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc-reference' and `info' packages installed, try: # `info libc "Name Service Switch"' for information about this file. passwd: compat systemd group: compat systemd shadow: compat gshadow:files hosts: files mdns4_minimal [NOTFOUND=return] dns networks: files protocols: db files services: db files ethers: db files rpc:db files netgroup: nis Do additional libraries need installing from a full base install? -- 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/1779438 Title: Cannot resolve names using systemd-resolved stub resolver Status in systemd package in Ubuntu: Incomplete Bug description: Description: Ubuntu 18.04 LTS Release: 18.04 I am running a clean install of Ubuntu 18.04. This bug was also present for me on a clean install of Ubuntu 17.10 and I had a solution, but it appears to no longer work. What I expect to happen: Ping other hosts on network by name What happened instead: I can't ping other machines on network via name. From my Ubuntu 18.04 machine, I `ping ubuntu-test-1` and `ping ubuntu-test-1.localdomain` but neither work. I can ping by IP address though. The other machines on the network are Ubuntu Server 16.04.3 machines and can ping each other by name also. All machines on network including problem one receive DHCP leases from same server (192.168.20.1) I believe the problem is systemd-resolved stub resolver. `cat /etc/resolv.conf` # This file is managed by man:systemd-resolved(8). Do not edit. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "systemd-resolve --status" to see details about the uplink DNS servers # currently in use. # # Third party programs must not access this file directly, but only through the # symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way, # replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 search localdomain If I change the nameserver line to the IP of my nameserver, not the stub, resolution works. nameserver 192.168.20.1 search localdomain Now I can ping hosts by name. I used to solve this problem like this... `sudo systemctl disable systemd-resolved.service` `echo "nameserver 192.168.20.1" | sudo tee -a /etc/resolvconf/resolv.conf.d/tail` `sudo reboot` But /etc/resolvconf/resolv.conf.d no longer exists, and it's about time this problem was fixed :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782275] Re: Conflict between resolvconf and systemd-resolved dhclient scripts
Given that it is a conffile, you can remove the one you do not need. Why do you want to use resolvconf, instead of resolved? I was expecting for people to have /etc/resolv.conf to point at either /run/systemd/resolve/stub-resolv.conf or /run/systemd/resolve/resolv.conf (as needed) and have nameservers updated via that. -- 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/1782275 Title: Conflict between resolvconf and systemd-resolved dhclient scripts Status in resolvconf package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I am setting up an Ubuntu 18.04 (bionic) system with ifupdown instead of netplan, as the latter does not meet my needs. I am using resolvconf to update /etc/resolv.conf from DHCP, as in earlier releases. Unfortunately, I am not seeing /etc/resolv.conf (actually a symlink to /run/resolvconf/resolv.conf) being updated; it is only the boilerplate from /etc/resolvconf/resolv.conf.d/head with no server information appended. (My "base" and "tail" files are empty.) I poked around the scripts in /etc, and believe I have found the problem. When resolvconf is installed, the following two files are present: /etc/dhcp/dhclient-enter-hooks.d/resolvconf /etc/dhcp/dhclient-enter-hooks.d/resolved Both of these scripts define the make_resolv_conf() shell function. What I am seeing is that dhclient runs these two scripts in the (alphabetical) order shown, and as the resolved script runs second, it overwrites the resolvconf version of the shell function with its own. As a result, dhclient does not invoke the appropriate update command for resolvconf, even though the hook script was installed correctly. Normally, I would remove the package that is providing the "resolved" script, but this package is systemd, which cannot be removed. I am not sure which of the two packages (resolvconf or systemd) needs to make an accommodation for the other, but it is clear that the current approach does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1782275/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot
** Changed in: netplan Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1770082 Title: systemd-networkd not renaming devices on boot Status in netplan: Fix Released Status in cloud-init package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in nplan source package in Xenial: Fix Released Status in netplan.io source package in Bionic: Fix Released Bug description: [Impact] Systems relying on renaming network interfaces at boot and when 'netplan apply' is run. [Test case] - Write a new netplan YAML (adjusting for current system as necessary): network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:de:bd:f6 set-name: myif0 - Run 'netplan apply' - Verify that the device is correctly renamed to 'myif0'. - Reboot. - Make sure the device is correctly renamed to 'myif0'. [Regression potential] Changes in rename logic to add udev rules may otherwise impact applying different settings to the network interfaces. Changes in settings on network interfaces, missing parameters (especially on bonds, bridges) should be investigated as potential regressions. Other failures to apply network settings might also happen if there's a race between applying renames via the udev rules, and using the new names to apply configuration changes to the interfaces. === systemd issue === Renaming devices doesn't seem to work. If I disable all other network configuration and create /etc/systemd/network/10-network.link with: [Match] MACAddress=52:54:00:c1:c9:bb [Link] Name=myiface3 I expect this to cause the device with that MAC address to be renamed to myiface3. However, when I reboot, I instead see: $ ip l 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff The device is not renamed. This link file is pretty much identical to Example 2 in https://www.freedesktop.org/software/systemd/man/systemd.link.html. The renaming does work if I boot with net.ifnames=0, and oddly, it also works if I unbind the device and rebind it as netplan apply does. No setting of NamePolicy seems to help. === Original Bug == 'set-name:' doesn't change the name of a network interface on boot, it only works when you do netplan apply. Say I take this 50-cloud-init.yaml file: # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:de:bd:f6 set-name: ens3 Say I change set-name to 'myiface3' and reboot. I expect that the device will be called myiface3 and brought up fine with dhcp. However, instead I see: $ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff The name has not been changed, and the device has not been brought up. If I run netplan apply however, I see the following: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 3: myiface3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3 valid_lft 3575sec preferred_lft 3575sec inet6 fe80::5054:ff:fede:bdf6/64 scope link valid_lft forever preferred_lft forever So names are successfully changed with netplan apply. This seems to be some udev-related timing or priority issue that I'm still trying to hunt down. This breaks some forms of migration in certain cloud environments. To
[Touch-packages] [Bug 1782709] Re: Updating systemd kills network on bionic
I examined /var/log/dpkg.log. There is no pause in there. The complete upgrade process looks pretty normal to my. So I guess it is just a network configuration issue during the upgrade that prevented my terminal session from getting updated. -- 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/1782709 Title: Updating systemd kills network on bionic Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I do have an ubuntu bionic server installation without a graphical interface. The server has two active network adapters, both connected to the internet. One is used for outgoing internet traffic, the other for incoming. The incoming adapter lives on a public network segment (something like 88.236.133.104/29). I do have multiple servers within this segment. Typically, I update the server regularly, meaning: * ssh to the incoming adapter: ssh 88.236.133.108 * apt-get update * apt-get upgrade * apt-get dist-upgrade * apt-get clean * reboot It used to work ok. BUT: Today, "apt-get upgrade" seem to take really long when updating systemd. After a could of minutes, I realized that the ssh session became inactive. I couldn't type into it, I had to abort it via ~. . * ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108 * ssh via another server within the public network segment worked * ssh 88.236.133.106 -> ssh 88.236.133.108 * After running "netplan apply" everything was fine again Here my netplan configuration (I changed the ip addresses): network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes eno2: dhcp4: no addresses: [88.236.133.108/29] #gateway4: 88.236.133.105 routes: - to: 0.0.0.0/0 via: 88.236.133.105 table: 120 routing-policy: - from: 88.236.133.108/32 table: 120 - to: 88.236.133.108/32 table: 120 Unfortunately, I don't have the console output avalable anymore. Shall I provide additional info? Best regards, Uli --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 20 08:10 seq crw-rw 1 root audio 116, 33 Jul 20 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-14 (5 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM IBM System x -[794582G]- Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/07/2014 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E162AUS-1.20]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E162AUS-1.20]-:bd05/07/2014:svnIBM:pnIBMSystemx-[794582G]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: IBM System x -[794582G]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782709] Re: Updating systemd kills network on bionic
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1782709 Title: Updating systemd kills network on bionic Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I do have an ubuntu bionic server installation without a graphical interface. The server has two active network adapters, both connected to the internet. One is used for outgoing internet traffic, the other for incoming. The incoming adapter lives on a public network segment (something like 88.236.133.104/29). I do have multiple servers within this segment. Typically, I update the server regularly, meaning: * ssh to the incoming adapter: ssh 88.236.133.108 * apt-get update * apt-get upgrade * apt-get dist-upgrade * apt-get clean * reboot It used to work ok. BUT: Today, "apt-get upgrade" seem to take really long when updating systemd. After a could of minutes, I realized that the ssh session became inactive. I couldn't type into it, I had to abort it via ~. . * ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108 * ssh via another server within the public network segment worked * ssh 88.236.133.106 -> ssh 88.236.133.108 * After running "netplan apply" everything was fine again Here my netplan configuration (I changed the ip addresses): network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes eno2: dhcp4: no addresses: [88.236.133.108/29] #gateway4: 88.236.133.105 routes: - to: 0.0.0.0/0 via: 88.236.133.105 table: 120 routing-policy: - from: 88.236.133.108/32 table: 120 - to: 88.236.133.108/32 table: 120 Unfortunately, I don't have the console output avalable anymore. Shall I provide additional info? Best regards, Uli --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 20 08:10 seq crw-rw 1 root audio 116, 33 Jul 20 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-14 (5 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM IBM System x -[794582G]- Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/07/2014 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E162AUS-1.20]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E162AUS-1.20]-:bd05/07/2014:svnIBM:pnIBMSystemx-[794582G]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: IBM System x -[794582G]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp