[Touch-packages] [Bug 1720400] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render
Ditto here for PJSingh5000. I had added a google account as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1720400 Title: /usr/bin/gnome-control- center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render Status in GTK+: Confirmed Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.26.0-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1720400/+subscriptions -- Mailing list: https://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 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)
I think Andres has access to the GMAAS, would appreciate if he could verify the fix there. If not, let me know and I can try it. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1711760 Title: [2.3] resolv.conf is not set (during commissioning or testing) Status in MAAS: Fix Committed Status in cloud-init package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: In Progress Bug description: === Begin SRU Template === [Impact] Without this fix applied, dns settings provided to the dhcp response in the initramfs are not reflected in the "real root". Thus dns resolution does not work. Of most interest was the MAAS use case of the 'root=http://<>/squashfs' use case. MAAS 2.3 uses this for the installation environment and also the rescue environment. [Test Case] There are two tests for this. a.) local/non-MAAS test Download the test case attached. Run it and follow the instructions. Login to the guest (ubuntu:password), and inspect /etc/resolv.conf without the fix there would be no data in /etc/resolv.conf. With the fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com' b.) MAAS test. For the full maas test, you need to build a image stream for maas with the fix included in the squashfs image and then import that stream to maas and use the rescue environment and verify dns. This process is beyond the scope of the SRU template, but is described partially in http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README [Regression Potential] Regression potential should be very low. There are gates in the code to make sure that this code is inactive other than when it is explicitly enabled. net-interface-handler will exit without doing anything unless: a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf and these files have non-empty values for a variable mentioned above. (These files are written by the initramfs code when 'ip=' is seen). b.) this is not a container. b.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface) if open-iscsi has written this file due to open-iscsi root, then it will handle this functionality. resolvconf will get out of the way. c.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns' This lowers the scope of changes in runtime to cases with where either the new flag is seen or cloud-config-url is passed. The MAAS use case will contain this flag. [Other Info] === End SRU Template === Using MAAS 2.3, during commissioning (and likely in the rest of the ephemeral environment) we have noticed that resolv.conf is not set with the DNS server. That said, during the commissioning process, MAAS does not send any metadata to cloud-init to configure the network, rather, we expect the image to boot from the network via DHCP. So, cloud-init writes: ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg # 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} auto lo iface lo inet loopback # control-manual ens3 iface ens3 inet dhcp broadcast 192.168.122.255 dns-nameservers 192.168.122.2 gateway 192.168.122.1 netmask 255.255.255.0 Which correctly includes the DNS server. However: ubuntu@manual:~$ ping google.com ping: unknown host google.com If restart the interfacE: ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3 ifdown: interface ens3 not configured Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/ens3/52:54:00:ea:57:31 Sending on LPF/ens3/52:54:00:ea:57:31 Sending on Socket/fallback DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354) DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354) DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 (xid=0x5403eb14) DHCPOFFER of 192.168.122.195 from 192.168.122.2 DHCPACK of 192.168.122.195 from 192.168.122.2 Restarting ntp (via systemctl): ntp.service. bound to 192.168.122.195 -- renewal in 290 seconds. ubuntu@manual:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.122.2 search maas ubuntu@manual:~$ ping google.com PING google.com (216.58.192.46) 56(84) bytes of
[Touch-packages] [Bug 1725651] Re: package passwd 1:4.2-3.2ubuntu1.17.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurat
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1725651 Title: package passwd 1:4.2-3.2ubuntu1.17.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in shadow package in Ubuntu: New Bug description: hello ProblemType: Package DistroRelease: Ubuntu 17.04 Package: passwd 1:4.2-3.2ubuntu1.17.04.2 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri Jun 2 13:42:41 2017 DpkgTerminalLog: dpkg: error processing package passwd (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-02 (171 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: shadow Title: package passwd 1:4.2-3.2ubuntu1.17.04.2 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/shadow/+bug/1725651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726627] [NEW] Pulse audio sink changes from HDMI when starting new Xsession for game
Public bug reported: I have speakers built into my monitor and if I am using 'alsa_output .pci-_02_00.1.hdmi-stereo-extra1' as my default sink, audio plays correctly. I have set up a .desktop file to launch a game in a new xsession using the following: /usr/bin/xinit /usr/bin/wine /mnt/1tb/WoW/WoW.exe -- :3 vt8 If I run this script, pulseaudio changes the sink to 'alsa_output.pci- _00_1b.0.iec958-stereo' automatically, so I get no audio from my application via my monitor. If I hook a device to the s/pdif port I do get the audio. I am a member of the 'audio' group and this worked properly in 17.04 but has broken after a clean install of 17.10. $ pacmd list-sinks | grep name: name: <-what I want to stay as default name: <-what the sink switches to when starting a second X session. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sbarcomb 1993 F pulseaudio /dev/snd/controlC0: sbarcomb 1993 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 18:48:48 2017 InstallationDate: Installed on 2017-10-19 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: GP104 High Definition Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: Sound works for a while, then breaks Title: [hostname-R4, Nvidia GPU 83 HDMI/DP, Digital Out, HDMI] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2013 dmi.bios.vendor: Alienware dmi.bios.version: A11 dmi.board.name: 07JNH0 dmi.board.vendor: Alienware dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: 00 dmi.modalias: dmi:bvnAlienware:bvrA11:bd11/26/2013:svnAlienware:pnAurora-R4:pvr00:rvnAlienware:rn07JNH0:rvrA02:cvnAlienware:ct3:cvr00: dmi.product.family: 0 dmi.product.name: Aurora-R4 dmi.product.version: 00 dmi.sys.vendor: Alienware ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1726627 Title: Pulse audio sink changes from HDMI when starting new Xsession for game Status in alsa-driver package in Ubuntu: New Bug description: I have speakers built into my monitor and if I am using 'alsa_output .pci-_02_00.1.hdmi-stereo-extra1' as my default sink, audio plays correctly. I have set up a .desktop file to launch a game in a new xsession using the following: /usr/bin/xinit /usr/bin/wine /mnt/1tb/WoW/WoW.exe -- :3 vt8 If I run this script, pulseaudio changes the sink to 'alsa_output.pci- _00_1b.0.iec958-stereo' automatically, so I get no audio from my application via my monitor. If I hook a device to the s/pdif port I do get the audio. I am a member of the 'audio' group and this worked properly in 17.04 but has broken after a clean install of 17.10. $ pacmd list-sinks | grep name: name: <-what I want to stay as default name: <-what the sink switches to when starting a second X session. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sbarcomb 1993 F pulseaudio /dev/snd/controlC0: sbarcomb 1993 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 18:48:48 2017 InstallationDate: Installed on 2017-10-19 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: GP104 High Definition Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: Sound works for a while, then breaks Title: [hostname-R4, Nvidia GPU 83 HDMI/DP, Digital Out, HDMI] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2013 dmi.bios.vendor: Alienware dmi.bios.version: A11 dmi.board.name: 07JNH0
[Touch-packages] [Bug 1726634] [NEW] the sound laptop speaker is not working and it sound interface isnt showing in "sound" app. sound works perfectly in other users
Public bug reported: the sound laptop speaker is not working and it sound interface isnt showing in "sound" app. sound works perfectly in other users ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximum2935 F chrome maximum7304 F AudioThread CurrentDesktop: Unity Date: Mon Oct 23 19:05:32 2017 InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.asset.tag: MAXIMUM dmi.board.name: 05GRXT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: MAXIMUM dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd01/04/2017:svnDellInc.:pnLatitudeE5530non-vPro:pvr01:rvnDellInc.:rn05GRXT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5530 non-vPro dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1726634 Title: the sound laptop speaker is not working and it sound interface isnt showing in "sound" app. sound works perfectly in other users Status in pulseaudio package in Ubuntu: New Bug description: the sound laptop speaker is not working and it sound interface isnt showing in "sound" app. sound works perfectly in other users ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximum2935 F chrome maximum7304 F AudioThread CurrentDesktop: Unity Date: Mon Oct 23 19:05:32 2017 InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.asset.tag: MAXIMUM dmi.board.name: 05GRXT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: MAXIMUM dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd01/04/2017:svnDellInc.:pnLatitudeE5530non-vPro:pvr01:rvnDellInc.:rn05GRXT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5530 non-vPro dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1726634/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725933] Re: package libunity9 7.1.4+17.10.20170605-0ubuntu1 failed to install/upgrade: tentata sovrascrittura di "/usr/bin/unity-scope-loader" (condiviso), diverso da altre ista
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1725933 Title: package libunity9 7.1.4+17.10.20170605-0ubuntu1 failed to install/upgrade: tentata sovrascrittura di "/usr/bin/unity-scope- loader" (condiviso), diverso da altre istanze del pacchetto libunity9:i386 Status in libunity package in Ubuntu: New Bug description: bug ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libunity9 7.1.4+17.10.20170605-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 11:39:29 2017 ErrorMessage: tentata sovrascrittura di "/usr/bin/unity-scope-loader" (condiviso), diverso da altre istanze del pacchetto libunity9:i386 InstallationDate: Installed on 2017-10-12 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011) 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 SourcePackage: libunity Title: package libunity9 7.1.4+17.10.20170605-0ubuntu1 failed to install/upgrade: tentata sovrascrittura di "/usr/bin/unity-scope-loader" (condiviso), diverso da altre istanze del pacchetto libunity9:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1725933/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726013] Re: systemd-resolved crashed with SIGABRT in log_assert_failed_realm()
*** This bug is a duplicate of bug 1714792 *** https://bugs.launchpad.net/bugs/1714792 ** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1726013 Title: systemd-resolved crashed with SIGABRT in log_assert_failed_realm() Status in systemd package in Ubuntu: New Bug description: Appairs error messge at startup ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sun Oct 22 09:44:22 2017 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2017-10-22 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. N552VX ProcCmdline: /lib/systemd/systemd-resolved ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=457b2a84-bb47-47c1-ae79-2e76186547a7 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: log_assert_failed_realm () from /lib/systemd/libsystemd-shared-234.so ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-234.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-234.so SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-resolved crashed with SIGABRT in log_assert_failed_realm() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N552VX.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N552VX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN552VX.300:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnN552VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN552VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N552VX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
I added a comment about this new fix on https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1608495. One thing I wanted to add here, for the first time shutdown completed successfully. In fact, I was a little startled when it happened. :-) It powered off at the end of shutdown, instead of hanging at the "Reached target Shutdown" message. One question: Does this mean that Ubuntu 18.04 will use mdadm by default during installation instead of dmraid? I really hope so. It's a real pain to do it manually. -- 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/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." Status in systemd package in Ubuntu: Confirmed Bug description: I'm booting a fully patched 16.04 from an Intel Rapid Storage Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode). If the RAID volume is recovering or resyncing for whatever reason, then `sudo systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to consistently get that). However, once the recovery/resync is complete and clean, the reboot and poweroff commands above hang forever after "Reached target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in the bug #1464917) does not help. [EDIT]Actually, the shutdown also hangs from time to time during a resync. But I've never seen it succeed once the resync is complete.[/EDIT] Then, if the server has been forcibly restarted with the power button, the Intel Matrix Storage Manager indicates a "Normal" status for the RAID1 volume, but Ubuntu then resyncs the volume anyway: [1.223649] md: bind [1.228426] md: bind [1.230030] md: bind [1.230738] md: bind [1.232985] usbcore: registered new interface driver usbhid [1.233494] usbhid: USB HID core driver [1.234022] md: raid1 personality registered for level 1 [1.234876] md/raid1:md126: not clean -- starting background reconstruction [1.234956] input: CHESEN USB Keyboard as /devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5 [1.236273] md/raid1:md126: active with 2 out of 2 mirrors [1.236797] md126: detected capacity change from 0 to 1000202043392 [1.246271] md: md126 switched to read-write mode. [1.246834] md: resync of RAID array md126 [1.247325] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [1.247503] md126: p1 p2 p3 p4 [1.248269] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. [1.248774] md: using 128k window, over a total of 976759940k. Note that the pain of "resync upon every (re)boot" cannot even be a bit relieved thanks to bitmaps because mdadm does not support them for IMSM containers: $ sudo mdadm --grow --bitmap=internal /dev/md126 mdadm: Cannot add bitmaps to sub-arrays yet I also get this in syslog during boot when the individual drives are detected, but this seems to be harmless: May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental /dev/sdb --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental /dev/sda --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed with exit code 1. During a resync, `sudo sh -c 'echo idle > /sys/block/md126/md/sync_action'` actually stops it as expected, but it restarts immediately though nothing seems to have triggered it: May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted. May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of md126. May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126 May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a total of 976759940k. May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 from checkpoint. May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device /dev/md/Volume0 I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 > /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is unusable on this machine at this point because Ctrl+Alt+F9 brings tty9
[Touch-packages] [Bug 1726647] [NEW] crash reports still sent to LP on artful
Public bug reported: /etc/apport/crashdb.conf was not modified to stop sending crash reports to Launchpad for Ubuntu 17.10, since it was released they should only be going to errors.ubuntu.com. The problem_types field needs to change to ['Bug', 'Package']. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 17:43:06 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1741 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1726647 Title: crash reports still sent to LP on artful Status in apport package in Ubuntu: New Bug description: /etc/apport/crashdb.conf was not modified to stop sending crash reports to Launchpad for Ubuntu 17.10, since it was released they should only be going to errors.ubuntu.com. The problem_types field needs to change to ['Bug', 'Package']. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 17:43:06 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1741 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1726647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)
@Mark, I do have access (just tested). I'll give it a try tomorrow! Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1711760 Title: [2.3] resolv.conf is not set (during commissioning or testing) Status in MAAS: Fix Committed Status in cloud-init package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: In Progress Bug description: === Begin SRU Template === [Impact] Without this fix applied, dns settings provided to the dhcp response in the initramfs are not reflected in the "real root". Thus dns resolution does not work. Of most interest was the MAAS use case of the 'root=http://<>/squashfs' use case. MAAS 2.3 uses this for the installation environment and also the rescue environment. [Test Case] There are two tests for this. a.) local/non-MAAS test Download the test case attached. Run it and follow the instructions. Login to the guest (ubuntu:password), and inspect /etc/resolv.conf without the fix there would be no data in /etc/resolv.conf. With the fix you should see 'nameserver 10.0.2.2' and 'search mydomain.com bar.com' b.) MAAS test. For the full maas test, you need to build a image stream for maas with the fix included in the squashfs image and then import that stream to maas and use the rescue environment and verify dns. This process is beyond the scope of the SRU template, but is described partially in http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/view/head:/README [Regression Potential] Regression potential should be very low. There are gates in the code to make sure that this code is inactive other than when it is explicitly enabled. net-interface-handler will exit without doing anything unless: a.) there exist files /run/net-$INTERFACE.conf or /run/net6-$INTERFACE.conf and these files have non-empty values for a variable mentioned above. (These files are written by the initramfs code when 'ip=' is seen). b.) this is not a container. b.) there is no OPENISCSI_MARKER file (/run/initramfs/open-iscsi.interface) if open-iscsi has written this file due to open-iscsi root, then it will handle this functionality. resolvconf will get out of the way. c.) /proc/cmdline contains cloud-config-url=* or 'rc-initrd-dns' This lowers the scope of changes in runtime to cases with where either the new flag is seen or cloud-config-url is passed. The MAAS use case will contain this flag. [Other Info] === End SRU Template === Using MAAS 2.3, during commissioning (and likely in the rest of the ephemeral environment) we have noticed that resolv.conf is not set with the DNS server. That said, during the commissioning process, MAAS does not send any metadata to cloud-init to configure the network, rather, we expect the image to boot from the network via DHCP. So, cloud-init writes: ubuntu@manual:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg # 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} auto lo iface lo inet loopback # control-manual ens3 iface ens3 inet dhcp broadcast 192.168.122.255 dns-nameservers 192.168.122.2 gateway 192.168.122.1 netmask 255.255.255.0 Which correctly includes the DNS server. However: ubuntu@manual:~$ ping google.com ping: unknown host google.com If restart the interfacE: ubuntu@manual:~$ sudo ifdown ens3 && sudo ifup ens3 ifdown: interface ens3 not configured Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/ens3/52:54:00:ea:57:31 Sending on LPF/ens3/52:54:00:ea:57:31 Sending on Socket/fallback DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 3 (xid=0x14eb0354) DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 4 (xid=0x14eb0354) DHCPREQUEST of 192.168.122.195 on ens3 to 255.255.255.255 port 67 (xid=0x5403eb14) DHCPOFFER of 192.168.122.195 from 192.168.122.2 DHCPACK of 192.168.122.195 from 192.168.122.2 Restarting ntp (via systemctl): ntp.service. bound to 192.168.122.195 -- renewal in 290 seconds. ubuntu@manual:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.122.2 search maas ubuntu@manual:~$ ping google.com PING google.com (216.58.192.46) 56(84) bytes of data. 64 bytes from mia07s46-in-f14.1e100.net (216.58.192.46):
[Touch-packages] [Bug 1556419] Re: nf_conntrack: automatic helper assignment is deprecated
Hello, I just started seeing this on Ubuntu 17.10. ** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1556419 Title: nf_conntrack: automatic helper assignment is deprecated Status in iptables package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Get this logged into journalctl (since a moment): kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-13-generic 4.4.0-13.29 ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem1942 F pulseaudio /dev/snd/pcmC0D0p: oem1942 F...m pulseaudio /dev/snd/controlC0: oem1942 F pulseaudio CurrentDesktop: GNOME Date: Sat Mar 12 14:52:09 2016 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-13-generic N/A linux-backports-modules-4.4.0-13-generic N/A linux-firmware1.156 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1556419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556419] Re: nf_conntrack: automatic helper assignment is deprecated
nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based firewall rule not found. Use the iptables CT target to attach helpers instead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1556419 Title: nf_conntrack: automatic helper assignment is deprecated Status in iptables package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Get this logged into journalctl (since a moment): kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-13-generic 4.4.0-13.29 ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem1942 F pulseaudio /dev/snd/pcmC0D0p: oem1942 F...m pulseaudio /dev/snd/controlC0: oem1942 F pulseaudio CurrentDesktop: GNOME Date: Sat Mar 12 14:52:09 2016 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-13-generic N/A linux-backports-modules-4.4.0-13-generic N/A linux-firmware1.156 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1556419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716184] Re: failure of xrandr to find any outputs
** Description changed: I have a very new Lenovo X1 Yoga 2nd edition, with oled display. The exact model is 20JECTO1WW. The BIOS is N1NET27W. I am running a vanilla Ubuntu 16.04 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial uname -a Linux gjs-yoga 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Until recently things worked quite well. But on August 26 I got an update from Ubuntu and things began to decay. In particular, I can no longer display except on the built-in display: For example, xrandr cannot find any outputs, even though this laptop has a (working) HDMI output port. xrandr --verbose xrandr: Failed to get size of gamma for output default Screen 0: minimum 2560 x 1440, current 2560 x 1440, maximum 2560 x 1440 default connected primary 2560x1440+0+0 (0x272) normal (normal) 0mm x 0mm - Identifier: 0x271 - Timestamp: 33974 - Subpixel: unknown - Clones: - CRTC: 0 - CRTCs: 0 - Transform: 1.00 0.00 0.00 - 0.00 1.00 0.00 - 0.00 0.00 1.00 - filter: - _GNOME_FLASHBACK_PRESENTATION_OUTPUT: 0 - 2560x1440 (0x272) 342.835MHz *current - h: width 2560 start0 end0 total 2560 skew0 clock 133.92KHz - v: height 1440 start0 end0 total 1440 clock 93.00Hz + Identifier: 0x271 + Timestamp: 33974 + Subpixel: unknown + Clones: + CRTC: 0 + CRTCs: 0 + Transform: 1.00 0.00 0.00 + 0.00 1.00 0.00 + 0.00 0.00 1.00 + filter: + _GNOME_FLASHBACK_PRESENTATION_OUTPUT: 0 + 2560x1440 (0x272) 342.835MHz *current + h: width 2560 start0 end0 total 2560 skew0 clock 133.92KHz + v: height 1440 start0 end0 total 1440 clock 93.00Hz Notice there are no (even disconnected) outputs other than default. Another symptom is that system restart always turns off the power rather than rebooting. I looked at the manifest of the update that seems to have caused trouble and the only - suspicious entry is a microcode update from Intel. + suspicious entry is a microcode update from Intel. Here is the entry from the apt history log: Start-Date: 2017-08-26 17:54:05 Commandline: aptdaemon role='role-commit-packages' sender=':1.87' Upgrade: intel-microcode:amd64 (3.20151106.1, 3.20170707.1~ubuntu16.04.0), I hope that someone knows what is the problem here. I am stumped. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Uname: Linux 4.11.0-14-generic x86_64 .tmp.unity_support_test.1: - + ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 BootLog: - + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Sep 9 18:54:56 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Device [17aa:224e] + Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Device [17aa:224e] InstallationDate: Installed on 2017-07-27 (44 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd - Bus 001 Device 004: ID 056a:5087 Wacom Co., Ltd - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd + Bus 001 Device 004: ID 056a:5087 Wacom Co., Ltd + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20JECTO1WW ProcEnviron: - LANGUAGE=en_US - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-14-generic root=/dev/mapper/ubuntu--vg-root ro nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET27W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JECTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO
[Touch-packages] [Bug 1716184] Re: failure of xrandr to find any outputs
I got the bios upgraded, but the problem has not gone away. I hope someone would look into this problem. The machine is usable, but I cannot access any display output except default, as described in the the original bug report. I can demonstrate that the hardware is correctly working by changing the bios setting to boot using the hdmi display, but then the laptop screen does not work and xrandr does not find it. The current machine state is as follows: # dmidecode 3.0 Getting SMBIOS data from sysfs. SMBIOS 3.0.0 present. Table at 0x4F0E8000. Handle 0x, DMI type 222, 14 bytes OEM-specific Type Header and Data: DE 0E 00 00 01 99 00 03 10 01 20 02 30 03 Strings: Memory Init Complete End of DXE Phase BIOS Boot Complete Handle 0x0001, DMI type 14, 8 bytes Group Associations Name: Intel(R) Silicon View Technology Items: 1 0x () Handle 0x0002, DMI type 134, 13 bytes OEM-specific Type Header and Data: 86 0D 02 00 17 07 17 20 00 00 00 00 00 Handle 0x0003, DMI type 16, 23 bytes Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 16 GB Error Information Handle: Not Provided Number Of Devices: 2 Handle 0x0004, DMI type 17, 40 bytes Memory Device Array Handle: 0x0003 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 8192 MB Form Factor: Row Of Chips Set: None Locator: ChannelA-DIMM0 Bank Locator: BANK 0 Type: LPDDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 2133 MHz Manufacturer: Micron Serial Number: Asset Tag: None Part Number: MT52L1G32D4PG-093 Rank: 2 Configured Clock Speed: 2133 MHz Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: 1.2 V Handle 0x0005, DMI type 17, 40 bytes Memory Device Array Handle: 0x0003 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 8192 MB Form Factor: Row Of Chips Set: None Locator: ChannelB-DIMM0 Bank Locator: BANK 2 Type: LPDDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 2133 MHz Manufacturer: Micron Serial Number: Asset Tag: None Part Number: MT52L1G32D4PG-093 Rank: 2 Configured Clock Speed: 2133 MHz Minimum Voltage: Unknown Maximum Voltage: Unknown Configured Voltage: 1.2 V Handle 0x0006, DMI type 19, 31 bytes Memory Array Mapped Address Starting Address: 0x000 Ending Address: 0x003 Range Size: 16 GB Physical Array Handle: 0x0003 Partition Width: 2 Handle 0x0007, DMI type 7, 19 bytes Cache Information Socket Designation: L1 Cache Configuration: Enabled, Not Socketed, Level 1 Operational Mode: Write Back Location: Internal Installed Size: 128 kB Maximum Size: 128 kB Supported SRAM Types: Synchronous Installed SRAM Type: Synchronous Speed: Unknown Error Correction Type: Parity System Type: Unified Associativity: 8-way Set-associative Handle 0x0008, DMI type 7, 19 bytes Cache Information Socket Designation: L2 Cache Configuration: Enabled, Not Socketed, Level 2 Operational Mode: Write Back Location: Internal Installed Size: 512 kB Maximum Size: 512 kB Supported SRAM Types: Synchronous Installed SRAM Type: Synchronous Speed: Unknown Error Correction Type: Single-bit ECC System Type: Unified Associativity: 4-way Set-associative Handle 0x0009, DMI type 7, 19 bytes Cache Information Socket Designation: L3 Cache Configuration: Enabled, Not Socketed, Level 3 Operational Mode: Write Back Location: Internal Installed Size: 4096 kB Maximum Size: 4096 kB Supported SRAM Types: Synchronous Installed SRAM Type: Synchronous Speed: Unknown Error Correction Type: Multi-bit ECC System Type: Unified Associativity: 16-way Set-associative Handle 0x000A, DMI type 4, 48 bytes Processor Information Socket Designation: U3E1 Type: Central Processor Family: Core i7 Manufacturer: Intel(R) Corporation ID: E9 06 08 00 FF FB EB BF Signature: Type 0, Family 6, Model 142, Stepping 9 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension)
[Touch-packages] [Bug 1726555] [NEW] Use mainstream theme solution for gnome-terminal, drop patch
You have been subscribed to a public bug: Ubuntu adds a patch called "0001-Add-style-classes-and-CSS-names-to- some-of-our-widge.patch" to gnome-terminal, and in turn Ambiance and Radiance themes' apps/gnome-terminal.css relies on this to get the desired look for the notebook widget. Beginning with gnome-terminal 3.20.3 / 3.22.1 this should no longer be necessary. It's just an additional burden to carry this patch, plus an unnecessary complication for those who wish to manually compile gnome- terminal for whatever reason. gnome-terminal.css should ideally be modified to use the CSS names provided by mainstream gnome-terminal, and once done, the gnome-terminal patch can be dropped. Upstream references: https://bugzilla.gnome.org/show_bug.cgi?id=765590 https://bugzilla.gnome.org/show_bug.cgi?id=772134#c6 https://bugzilla.gnome.org/show_bug.cgi?id=788044 ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: artful -- Use mainstream theme solution for gnome-terminal, drop patch https://bugs.launchpad.net/bugs/1726555 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes 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 1726571] [NEW] cpu fan speed freezes
Public bug reported: cpu fan speed always freezes at 525RPM ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.24 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Oct 23 22:24:18 2017 InstallationDate: Installed on 2015-08-06 (809 days ago) InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530 Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 2550W1E ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=81f09e4c-e8db-48d1-9083-0ef6bfbec68f ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 81ET48WW (1.24 ) dmi.board.name: 2550W1E dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr81ET48WW(1.24):bd12/10/2010:svnLENOVO:pn2550W1E:pvrThinkPadL512:rvnLENOVO:rn2550W1E:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2550W1E dmi.product.version: ThinkPad L512 dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug qiana third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1726571 Title: cpu fan speed freezes Status in systemd package in Ubuntu: New Bug description: cpu fan speed always freezes at 525RPM ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.24 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Oct 23 22:24:18 2017 InstallationDate: Installed on 2015-08-06 (809 days ago) InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530 Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 2550W1E ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=81f09e4c-e8db-48d1-9083-0ef6bfbec68f ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 81ET48WW (1.24 ) dmi.board.name: 2550W1E dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr81ET48WW(1.24):bd12/10/2010:svnLENOVO:pn2550W1E:pvrThinkPadL512:rvnLENOVO:rn2550W1E:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2550W1E dmi.product.version: ThinkPad L512 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Trying the above fix does not work for 17.10. This is highly unfortunate. -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Confirmed Status in network-manager source package in Zesty: Confirmed Status in network-manager source package in Artful: Confirmed Bug description: [Impact] * NetworkManager incorrectly handles dns-priority of the VPN-like connections, which leads to leaking DNS queries outside of the VPN into the general internet. * Upstream has resolved this issue in master and 1.8 to correctly configure any dns backends with negative dns-priority settings. [Test Case] #FIXME# * detailed instructions how to reproduce the bug * these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. #FIXME# [Regression Potential] * If this issue is changed DNS resolution will change, for certain queries, to go via VPN rather than general internet. And therefore, one may get new/different results or even loose access to resolve/access certain parts of the interent depending on what the DNS server on VPN chooses to respond to. [Other Info] * Original bug report I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1175608] [NEW] Thumbnails too small in 'open file' dialog nautilus
You have been subscribed to a public bug: When trying to upload image files to e.g. websites like marktplaats.nl (kind of ebay) I get very, very small image thumbnails. There seems no way to enlarge these thumbnails. All options only work if Nautilus is used stand alone, but not with the open file dialog that is being used to upload files. I have attached a screen dump just to show what I mean. ** Affects: nautilus Importance: Wishlist Status: In Progress ** Affects: gtk+3.0 (Ubuntu) Importance: Wishlist Status: Triaged -- Thumbnails too small in 'open file' dialog nautilus https://bugs.launchpad.net/bugs/1175608 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 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 1723272] Re: apport-bug unable to init server, dumps core
@nrbrtx Yeah, Launchpad has had some timeout issue for over a week now. However ... This bug isn't a duplicate of bug 1713313. That bug is filed against Wayland in general, and odds on it won't get fixed because this feature/misfeature is intentional in Wayland's architecture. Other distros are sticking to it. See https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/1713313/comments/44 This bug is filed against apport-bug itself, which is where changes will need to be made if/when bug 1713313 is Wontfixed. -- 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/1723272 Title: apport-bug unable to init server, dumps core Status in apport package in Ubuntu: Confirmed Bug description: After upgrading to 17.10, apport-bug fails with the follow error: # apport-bug No protocol specified Unable to init server: Could not connect: Connection refused No protocol specified Unable to init server: Could not connect: Connection refused Segmentation fault (core dumped) Calling apport-cli directly works just fine. The problem seems to be a general Xwayland permission issue, since nothing can connect to the display server if sudo/su is used: $ sudo xclock No protocol specified Error: Can't open display: :0 $ xauth list xauth: file /home/user/.Xauthority does not exist If that's the way things are going to be in Ubuntu from now on, we need to make apport-bug a bit smarter in the way it decides whether to use the GUI version or not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashReports: 640:0:119:7137742:2017-10-13 09:46:22.546417474 +1100:2017-10-13 09:46:23.546417474 +1100:/var/crash/_usr_share_apport_apport-gtk.0.crash Date: Fri Oct 13 09:49:17 2017 InstallationDate: Installed on 2016-12-02 (313 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all ProcEnviron: LANG=en_AU.UTF-8 SHELL=/bin/bash TERM=xterm-256color LANGUAGE=en_AU:en PATH=(custom, no user) SourcePackage: apport UpgradeStatus: Upgraded to artful on 2017-10-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1723272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720400] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render
Also happens after adding a Microsoft account. I just upgraded from 16.04 to 17.10. It is a bit annoying but the added Accounts are working well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1720400 Title: /usr/bin/gnome-control- center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render Status in GTK+: Confirmed Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.26.0-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1720400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726555] Re: Use mainstream theme solution for gnome-terminal, drop patch
** Package changed: light-themes (Ubuntu) => ubuntu-themes (Ubuntu) -- 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/1726555 Title: Use mainstream theme solution for gnome-terminal, drop patch Status in gnome-terminal package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: Ubuntu adds a patch called "0001-Add-style-classes-and-CSS-names-to- some-of-our-widge.patch" to gnome-terminal, and in turn Ambiance and Radiance themes' apps/gnome-terminal.css relies on this to get the desired look for the notebook widget. Beginning with gnome-terminal 3.20.3 / 3.22.1 this should no longer be necessary. It's just an additional burden to carry this patch, plus an unnecessary complication for those who wish to manually compile gnome- terminal for whatever reason. gnome-terminal.css should ideally be modified to use the CSS names provided by mainstream gnome-terminal, and once done, the gnome- terminal patch can be dropped. Upstream references: https://bugzilla.gnome.org/show_bug.cgi?id=765590 https://bugzilla.gnome.org/show_bug.cgi?id=772134#c6 https://bugzilla.gnome.org/show_bug.cgi?id=788044 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1726555/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
This bug was fixed in the package cracklib2 - 2.9.2-3ubuntu1 --- cracklib2 (2.9.2-3ubuntu1) zesty; urgency=medium * Migrate triggers to interest-noawait to avoid trigger-cycles (Closes: #859307, LP: #1681231) -- Brian MurrayFri, 20 Oct 2017 16:52:55 -0700 ** Changed in: cracklib2 (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1681231 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Confirmed Status in cracklib2 package in Ubuntu: Fix Released Status in cracklib2 source package in Trusty: Incomplete Status in cracklib2 source package in Xenial: Fix Committed Status in cracklib2 source package in Yakkety: Won't Fix Status in cracklib2 source package in Zesty: Fix Released Status in cracklib2 package in Debian: Fix Released Bug description: [Impact] Upgrading cracklib-runtime is not working for some systems due to trigger cycles. This is making distribution upgrades challenging. [Test Case] While we haven't been able to replicate this directly the following tests will confirm that there are no regressions. Test A -- 1) Install cracklib-runtime from -proposed. 2) Reinstall dictionaries-common and verify that the trigger is called Test B -- 1) With the version of cracklib-runtime from -proposed installed, confirm that a distribution upgrade to next supported release succeeds. Test C -- 1) Test a release upgrade from an affected release (Trusty, Xenial) to the next supported release (Xenial, Zesty) with -proposed enabled. To do this upgrade you'll need to edit /etc/apt/sources.list to the target release and run 'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed. [Regression Potential] It's possible that upgrades will break hence all the regression tests in the Test Case. Original Description This seems to be the same problem as described in bug #1636262, only this time it happened during upgrade from 16.10 to 17.04. The setup process (do-release-upgrade -d) aborted and I had to finish it manually. ProblemType: PackageDistroRelease: Ubuntu 17.04 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sun Apr 9 17:09:37 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-26 (257 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1681231/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
On an Ubuntu 16.04 system I installed the version of cracklib-runtime from -proposed and performed the following tests: Test A -- 1) Install cracklib-runtime from -proposed. 2) Reinstall dictionaries-common and verify that the trigger is called Test B -- 1) With the version of cracklib-runtime from -proposed installed, confirm that a distribution upgrade to next supported release succeeds. Both of them succeeded. The apt-term.log of the distribution upgrade: Preparing to unpack .../cracklib-runtime_2.9.2-3_amd64.deb ...^M Unpacking cracklib-runtime (2.9.2-3) over (2.9.2-1ubuntu1) ...^M -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1681231 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Confirmed Status in cracklib2 package in Ubuntu: Fix Released Status in cracklib2 source package in Trusty: Incomplete Status in cracklib2 source package in Xenial: Fix Committed Status in cracklib2 source package in Yakkety: Won't Fix Status in cracklib2 source package in Zesty: Fix Released Status in cracklib2 package in Debian: Fix Released Bug description: [Impact] Upgrading cracklib-runtime is not working for some systems due to trigger cycles. This is making distribution upgrades challenging. [Test Case] While we haven't been able to replicate this directly the following tests will confirm that there are no regressions. Test A -- 1) Install cracklib-runtime from -proposed. 2) Reinstall dictionaries-common and verify that the trigger is called Test B -- 1) With the version of cracklib-runtime from -proposed installed, confirm that a distribution upgrade to next supported release succeeds. Test C -- 1) Test a release upgrade from an affected release (Trusty, Xenial) to the next supported release (Xenial, Zesty) with -proposed enabled. To do this upgrade you'll need to edit /etc/apt/sources.list to the target release and run 'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed. [Regression Potential] It's possible that upgrades will break hence all the regression tests in the Test Case. Original Description This seems to be the same problem as described in bug #1636262, only this time it happened during upgrade from 16.10 to 17.04. The setup process (do-release-upgrade -d) aborted and I had to finish it manually. ProblemType: PackageDistroRelease: Ubuntu 17.04 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sun Apr 9 17:09:37 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-26 (257 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1681231/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725980] Re: package libheimntlm0-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall
Thanks for filing this bug in Ubuntu. Could you please try these commands and see if they help solve the problem: sudo apt update sudo apt install --reinstall libheimntlm0-heimdal:i386 sudo apt -f install Please let us know how it goes. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1725980 Title: package libheimntlm0-heimdal:i386 1.7~git20150920+dfsg- 4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in heimdal package in Ubuntu: New Bug description: not updated ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libheimntlm0-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 Date: Sun Oct 22 09:37:53 2017 DuplicateSignature: package:libheimntlm0-heimdal:i386:1.7~git20150920+dfsg-4ubuntu1.16.04.1 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package libheimntlm0-heimdal:i386 (--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-03-06 (229 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: heimdal Title: package libheimntlm0-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 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/heimdal/+bug/1725980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
On an Ubuntu 14.04 system I edited my sources.list file to have -proposed enabled and modified all trusty entries to xenial. After which I ran 'sudo apt-get dist-upgrade' and successfully upgraded to Ubuntu 16.04 with -proposed enabled and the new version of cracklib-runtime being installed. >From /var/log/apt-term.log: Preparing to unpack .../cracklib-runtime_2.9.2-1ubuntu1_amd64.deb ... Unpacking cracklib-runtime (2.9.2-1ubuntu1) over (2.9.1-1build1) ... Setting up cracklib-runtime (2.9.2-1ubuntu1) ... Setting to v-done for xenial. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1681231 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Confirmed Status in cracklib2 package in Ubuntu: Fix Released Status in cracklib2 source package in Trusty: Incomplete Status in cracklib2 source package in Xenial: Fix Committed Status in cracklib2 source package in Yakkety: Won't Fix Status in cracklib2 source package in Zesty: Fix Released Status in cracklib2 package in Debian: Fix Released Bug description: [Impact] Upgrading cracklib-runtime is not working for some systems due to trigger cycles. This is making distribution upgrades challenging. [Test Case] While we haven't been able to replicate this directly the following tests will confirm that there are no regressions. Test A -- 1) Install cracklib-runtime from -proposed. 2) Reinstall dictionaries-common and verify that the trigger is called Test B -- 1) With the version of cracklib-runtime from -proposed installed, confirm that a distribution upgrade to next supported release succeeds. Test C -- 1) Test a release upgrade from an affected release (Trusty, Xenial) to the next supported release (Xenial, Zesty) with -proposed enabled. To do this upgrade you'll need to edit /etc/apt/sources.list to the target release and run 'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed. [Regression Potential] It's possible that upgrades will break hence all the regression tests in the Test Case. Original Description This seems to be the same problem as described in bug #1636262, only this time it happened during upgrade from 16.10 to 17.04. The setup process (do-release-upgrade -d) aborted and I had to finish it manually. ProblemType: PackageDistroRelease: Ubuntu 17.04 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sun Apr 9 17:09:37 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-26 (257 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1681231/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
On an Ubuntu 16.04 system I edited my sources.list file to have -proposed enabled and modify all xenial entries to zesty. After which I ran 'sudo apt-get dist-upgrade' and successfully upgraded to Ubuntu 17.04 with -proposed enabled and the new version of cracklib-runtime being installed. bdmurray@clean-xenial-amd64:~$ apt-cache policy cracklib-runtime cracklib-runtime: Installed: 2.9.2-3ubuntu1 Candidate: 2.9.2-3ubuntu1 Version table: *** 2.9.2-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu zesty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2.9.2-3 500 500 http://192.168.10.7/ubuntu zesty/main amd64 Packages ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1681231 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Confirmed Status in cracklib2 package in Ubuntu: Fix Released Status in cracklib2 source package in Trusty: Incomplete Status in cracklib2 source package in Xenial: Fix Committed Status in cracklib2 source package in Yakkety: Won't Fix Status in cracklib2 source package in Zesty: Fix Committed Status in cracklib2 package in Debian: Fix Released Bug description: [Impact] Upgrading cracklib-runtime is not working for some systems due to trigger cycles. This is making distribution upgrades challenging. [Test Case] While we haven't been able to replicate this directly the following tests will confirm that there are no regressions. Test A -- 1) Install cracklib-runtime from -proposed. 2) Reinstall dictionaries-common and verify that the trigger is called Test B -- 1) With the version of cracklib-runtime from -proposed installed, confirm that a distribution upgrade to next supported release succeeds. Test C -- 1) Test a release upgrade from an affected release (Trusty, Xenial) to the next supported release (Xenial, Zesty) with -proposed enabled. To do this upgrade you'll need to edit /etc/apt/sources.list to the target release and run 'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed. [Regression Potential] It's possible that upgrades will break hence all the regression tests in the Test Case. Original Description This seems to be the same problem as described in bug #1636262, only this time it happened during upgrade from 16.10 to 17.04. The setup process (do-release-upgrade -d) aborted and I had to finish it manually. ProblemType: PackageDistroRelease: Ubuntu 17.04 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sun Apr 9 17:09:37 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-26 (257 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1681231/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725850] Re: systemd-journald crashed with SIGABRT in journal_file_rotate_suggested()
the error is "systemd-journald.service: Watchdog timeout (limit 3min)!" which seems to match https://github.com/systemd/systemd/issues/1353 ** Information type changed from Private to Public ** Bug watch added: github.com/systemd/systemd/issues #1353 https://github.com/systemd/systemd/issues/1353 -- 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/1725850 Title: systemd-journald crashed with SIGABRT in journal_file_rotate_suggested() Status in systemd package in Ubuntu: New Bug description: System was in sleep mode, I logged back in and this system error was waiting for me. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 09:34:50 2017 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Alienware Alienware X51 R3 ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: journal_file_rotate_suggested () from /lib/systemd/libsystemd-shared-234.so ?? () ?? () ?? () ?? () SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-journald crashed with SIGABRT in journal_file_rotate_suggested() UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago) UserGroups: dmi.bios.date: 09/11/2015 dmi.bios.vendor: Alienware dmi.bios.version: 1.1.0 dmi.board.name: 026CD3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.modalias: dmi:bvnAlienware:bvr1.1.0:bd09/11/2015:svnAlienware:pnAlienwareX51R3:pvr:rvnAlienware:rn026CD3:rvrA00:cvnAlienware:ct3:cvr: dmi.product.name: Alienware X51 R3 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725850/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725865] Re: Network shows Cable Unplugged
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low -- 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/1725865 Title: Network shows Cable Unplugged Status in network-manager package in Ubuntu: New Bug description: This was working perfectly on 17.04, but after installing 17.10 from scratch, the wired network is not detected. It simply shows as Cable Unplugged when in fact there is the same cable still connected directly to the router. This same computer has Windows 10 and it detects the network correctly. I also tested Fedora and it detected the network correctly (The wired one). I am currently using only the Wireless connection because of this. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 17:59:31 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp9s0 proto static metric 600 169.254.0.0/16 dev wlp9s0 scope link metric 1000 192.168.1.0/24 dev wlp9s0 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: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp9s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Linux ecb8e125-48ff-4994-94c8-bdf3731334ce /org/freedesktop/NetworkManager/ActiveConnection/13 enp0s31f6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1725865/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726595] [NEW] Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10
Public bug reported: OBSERVED BEHAVIOR: Matlab stays in busy state when using some functions like "plot" or even "exit", while executing through a ssh tunnel with X11 forwarding. REPRODUCE THE BUG: You need matlab (my version is R2017a) to reproduce the bug. I suspect any version >= 2014b would reproduce the bug (HG2 framework), and maybe any version. 1. Connect to self (or from other machine) with X forwarding: $ ssh -X user@localhost 2. Launch matlab $ matlab & 3. Plot something >> plot(1,1) ADDITIONAL INFORMATION - Normal behavior would be appearance of a new window and a single point at position (1,1). - No ressources seem to be used. - Opening a figure alone is possible. (>> figure). Opening other windows from the graphical user interface is possible - Opening Matlab without the java machine seems to work, but matlab relies heavily on java. At least "exit" which doesn't work with java, works without java. - Providing Matlab with open-jdk version 1.8.0_144 didn't change anything. - This used to work perfectly for as long as I have been using Ubuntu (since 2012). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: openssh-client 1:7.5p1-10 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Oct 23 17:44:23 2017 ExecutablePath: /usr/bin/ssh InstallationDate: Installed on 2017-08-25 (59 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.0.2g 1 Mar 2016 SourcePackage: openssh UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago) modified.conffile..etc.ssh.ssh_config: [modified] mtime.conffile..etc.ssh.ssh_config: 2017-10-23T16:25:50.569560 ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1726595 Title: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10 Status in openssh package in Ubuntu: New Bug description: OBSERVED BEHAVIOR: Matlab stays in busy state when using some functions like "plot" or even "exit", while executing through a ssh tunnel with X11 forwarding. REPRODUCE THE BUG: You need matlab (my version is R2017a) to reproduce the bug. I suspect any version >= 2014b would reproduce the bug (HG2 framework), and maybe any version. 1. Connect to self (or from other machine) with X forwarding: $ ssh -X user@localhost 2. Launch matlab $ matlab & 3. Plot something >> plot(1,1) ADDITIONAL INFORMATION - Normal behavior would be appearance of a new window and a single point at position (1,1). - No ressources seem to be used. - Opening a figure alone is possible. (>> figure). Opening other windows from the graphical user interface is possible - Opening Matlab without the java machine seems to work, but matlab relies heavily on java. At least "exit" which doesn't work with java, works without java. - Providing Matlab with open-jdk version 1.8.0_144 didn't change anything. - This used to work perfectly for as long as I have been using Ubuntu (since 2012). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: openssh-client 1:7.5p1-10 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Oct 23 17:44:23 2017 ExecutablePath: /usr/bin/ssh InstallationDate: Installed on 2017-08-25 (59 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.0.2g 1 Mar 2016 SourcePackage: openssh UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago) modified.conffile..etc.ssh.ssh_config: [modified] mtime.conffile..etc.ssh.ssh_config: 2017-10-23T16:25:50.569560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1726595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1681231] Update Released
The verification of the Stable Release Update for cracklib2 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1681231 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in apt package in Ubuntu: Confirmed Status in cracklib2 package in Ubuntu: Fix Released Status in cracklib2 source package in Trusty: Incomplete Status in cracklib2 source package in Xenial: Fix Committed Status in cracklib2 source package in Yakkety: Won't Fix Status in cracklib2 source package in Zesty: Fix Released Status in cracklib2 package in Debian: Fix Released Bug description: [Impact] Upgrading cracklib-runtime is not working for some systems due to trigger cycles. This is making distribution upgrades challenging. [Test Case] While we haven't been able to replicate this directly the following tests will confirm that there are no regressions. Test A -- 1) Install cracklib-runtime from -proposed. 2) Reinstall dictionaries-common and verify that the trigger is called Test B -- 1) With the version of cracklib-runtime from -proposed installed, confirm that a distribution upgrade to next supported release succeeds. Test C -- 1) Test a release upgrade from an affected release (Trusty, Xenial) to the next supported release (Xenial, Zesty) with -proposed enabled. To do this upgrade you'll need to edit /etc/apt/sources.list to the target release and run 'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed. [Regression Potential] It's possible that upgrades will break hence all the regression tests in the Test Case. Original Description This seems to be the same problem as described in bug #1636262, only this time it happened during upgrade from 16.10 to 17.04. The setup process (do-release-upgrade -d) aborted and I had to finish it manually. ProblemType: PackageDistroRelease: Ubuntu 17.04 Package: cracklib-runtime 2.9.2-3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sun Apr 9 17:09:37 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-26 (257 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.4SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1681231/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1723272] Re: apport-bug unable to init server, dumps core
Thanks for reporting. It's already known - see bug 1713313. Please mark as duplicate (I got timeout issue). ** Changed in: apport (Ubuntu) Status: New => Confirmed -- 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/1723272 Title: apport-bug unable to init server, dumps core Status in apport package in Ubuntu: Confirmed Bug description: After upgrading to 17.10, apport-bug fails with the follow error: # apport-bug No protocol specified Unable to init server: Could not connect: Connection refused No protocol specified Unable to init server: Could not connect: Connection refused Segmentation fault (core dumped) Calling apport-cli directly works just fine. The problem seems to be a general Xwayland permission issue, since nothing can connect to the display server if sudo/su is used: $ sudo xclock No protocol specified Error: Can't open display: :0 $ xauth list xauth: file /home/user/.Xauthority does not exist If that's the way things are going to be in Ubuntu from now on, we need to make apport-bug a bit smarter in the way it decides whether to use the GUI version or not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashReports: 640:0:119:7137742:2017-10-13 09:46:22.546417474 +1100:2017-10-13 09:46:23.546417474 +1100:/var/crash/_usr_share_apport_apport-gtk.0.crash Date: Fri Oct 13 09:49:17 2017 InstallationDate: Installed on 2016-12-02 (313 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all ProcEnviron: LANG=en_AU.UTF-8 SHELL=/bin/bash TERM=xterm-256color LANGUAGE=en_AU:en PATH=(custom, no user) SourcePackage: apport UpgradeStatus: Upgraded to artful on 2017-10-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1723272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1175608] Re: Thumbnails too small in 'open file' dialog nautilus
** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1175608 Title: Thumbnails too small in 'open file' dialog nautilus Status in Nautilus: In Progress Status in gtk+3.0 package in Ubuntu: Triaged Bug description: When trying to upload image files to e.g. websites like marktplaats.nl (kind of ebay) I get very, very small image thumbnails. There seems no way to enlarge these thumbnails. All options only work if Nautilus is used stand alone, but not with the open file dialog that is being used to upload files. I have attached a screen dump just to show what I mean. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1175608/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725847] Re: libstdc++-4.8-dev:amd64 4.8.5-4ubuntu6 configured without _GLIBCXX_USE_C99
Ah, I get it now. g++-4.8 is part of universe in artful, meaning "Community supported", not officially supported by Canonical. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1725847 Title: libstdc++-4.8-dev:amd64 4.8.5-4ubuntu6 configured without _GLIBCXX_USE_C99 Status in gcc-4.8 package in Ubuntu: Won't Fix Bug description: Test program compiled on Artful Aardvark Ubuntu 17.10. $ which g++-4.8 /usr/bin/g++-4.8 $ /usr/bin/g++-4.8 --version g++-4.8 (Ubuntu 4.8.5-4ubuntu6) 4.8.5 Copyright (C) 2015 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ /usr/bin/g++-4.8 -std=c++11 -x c++ - < #include int main() { std::cout << std::to_string(0) << '\n'; return 0; } EOF Expected result compile without errors, output 0 Actual result : In function ‘int main()’: :5:16: error: ‘to_string’ is not a member of ‘std’ Supposed cause _GLIBCXX_USE_C99 is not set in /usr/include/x86_64-linux-gnu/c++/4.8/bits/c++config.h in package libstdc++-4.8-dev:amd64 (4.8.5-4ubuntu6) Further information Test program compiles and runs on Zesty Zapus with package libstdc++-4.8-dev:amd64 (4.8.5-4ubuntu4). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1725847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726609] Re: gdebi crashed with apt.cache.LockFailedException in _fetch_archives(): Failed to lock /var/cache/apt/archives/lock
*** This bug is a duplicate of bug 1303147 *** https://bugs.launchpad.net/bugs/1303147 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1303147, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** Changed in: gdebi (Ubuntu) Importance: Undecided => Medium ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726609/+attachment/4989402/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726609/+attachment/4989403/+files/ProcStatus.txt ** This bug has been marked a duplicate of private bug 1303147 ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1726609 Title: gdebi crashed with apt.cache.LockFailedException in _fetch_archives(): Failed to lock /var/cache/apt/archives/lock Status in gdebi package in Ubuntu: New Bug description: installing dropbox ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gdebi-core 0.9.5.7+nmu1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Mon Oct 23 17:37:34 2017 ExecutablePath: /usr/share/gdebi/gdebi InstallationDate: Installed on 2017-10-22 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gdebi dropbox_2015.10.28_amd64.deb ProcEnviron: LANG=en_US.UTF-8 TERM=xterm-256color LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/bin/gdebi', 'dropbox_2015.10.28_amd64.deb'] PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SourcePackage: gdebi Title: gdebi crashed with apt.cache.LockFailedException in _fetch_archives(): Failed to lock /var/cache/apt/archives/lock UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1726609/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726614] Re: evolution-addressbook-factory-subprocess crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
*** This bug is a duplicate of bug 1724277 *** https://bugs.launchpad.net/bugs/1724277 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1724277, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726614/+attachment/4989449/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726614/+attachment/4989451/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726614/+attachment/4989454/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726614/+attachment/4989455/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726614/+attachment/4989456/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726614/+attachment/4989457/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726614/+attachment/4989458/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1724277 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1726614 Title: evolution-addressbook-factory-subprocess crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() Status in evolution-data-server package in Ubuntu: New Bug description: Probably coming from a background process ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: evolution-data-server 3.26.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 22:55:52 2017 ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory-subprocess InstallationDate: Installed on 2017-09-22 (30 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory-subprocess --factory google --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx5547x3 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/5547/3 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: evolution-data-server StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: evolution-addressbook-factory-subprocess crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1726614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573693] Re: Microphone is not working
I've a Lenovo Flex 3, and the mic does not work with a fresh install of Ubuntu 17.10. I had to instal PulseAudioVolumeControl and move the 'From Left' setting all the way left, and keep the 'From Right' setting higher in order for it to work. But then Chrome autoadjusts the internal mic volume when I do any conferencing in the browser. See: https://askubuntu.com/questions/967674/how-do-i-stop-audiopulsevolumecontrol-auto-adjusting-itself-so-my-mic-works Here Chrome blames Ubuntu: https://bugs.chromium.org/p/chromium/issues/detail?id=435112=2=0=100==ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified== -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1573693 Title: Microphone is not working Status in pulseaudio package in Ubuntu: Confirmed Bug description: Microphone is not working on ASUS X552L laptop. Just installed latest ubuntu version 16.04 LTS After installed Skype, tried a test call, sound was very low volume. Tried to adjust microphone volume with the slider, mic went dead for good, no sound at all. tried to reinstall alsa package apt-get remove --purge alsa-base pulseaudio and install it again, nothing works. Did not work on older ubuntu version either. Description: Ubuntu 16.04 LTS Release: 16.04 alsa-base: Telepítve: 1.0.25+dfsg-0ubuntu5 Jelölt:1.0.25+dfsg-0ubuntu5 Verziótáblázat: *** 1.0.25+dfsg-0ubuntu5 500 500 http://hu.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://hu.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status pulseaudio: Telepítve: 1:8.0-0ubuntu3 Jelölt:1:8.0-0ubuntu3 Verziótáblázat: *** 1:8.0-0ubuntu3 500 500 http://hu.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: irma 1425 F pulseaudio /dev/snd/pcmC1D0c: irma 1425 F...m pulseaudio /dev/snd/controlC1: irma 1425 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 22 18:17:49 2016 InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.509 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.509:bd06/26/2014:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1573693/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720517] Re: Software and Updates /Other Software greys out when clicking on "Canonical Partners"
encountered it after an update to 17.10 as well. My workaround for now is to start software-properties-gtk using gksu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1720517 Title: Software and Updates /Other Software greys out when clicking on "Canonical Partners" Status in software-properties package in Ubuntu: Confirmed Bug description: "Other Software" only works after having clicked on "Ubuntu Software", "Updates", etc and changing some settings on those pages. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.16 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 30 10:44:47 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2017-09-29 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 3.6.2-1ubuntu4 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1720517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1511439] Re: webbrowser-app apparmor policy fails to load on desktop
In ubuntu 17.10, apparmor.service did not start because video.d, audio.d and graphics.d could not be loaded. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1511439 Title: webbrowser-app apparmor policy fails to load on desktop Status in Canonical System Image: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: $ sudo apparmor_parser -r /etc/apparmor.d/usr.bin.webbrowser-app AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open '/usr/share/apparmor/hardware/graphics.d' $ $ sudo aa-status|grep webbrowser $ This was tested on xenial but affects wily too if it is shipping the policy. The problem is that apparmor-easyprof-ubuntu normally ships these directories, but it is not installed by default on the desktop image. I suggest shipping these empty directories via the webbrowser-app's packaging: - /usr/share/apparmor/hardware/audio.d - /usr/share/apparmor/hardware/graphics.d - /usr/share/apparmor/hardware/video.d To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1511439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)
Thanks for your testing. Yes, we already have PulseAudio 11 planned for inclusion in Ubuntu 18.04. It would have been included in Ubuntu 17.10, but PulseAudio 11.0 was released too late in the cycle. ** Tags added: pulse11 ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1725863 Title: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04) Status in linux package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: New Bug description: Every so many seconds / minutes the Wireless headset Logitech G930 simply drops connection. It always reconnects but when doing a recording, a meeting, listening to music or a movie it simply drops the connection for 1 to 3 second. This happens several times an hour. If it helps, it was not happening in 17.04 (Never happened in more than 200+ hours of using the headset). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyrex 1288 F pulseaudio /dev/snd/controlC2: cyrex 1288 F pulseaudio /dev/snd/controlC0: cyrex 1288 F pulseaudio Date: Sat Oct 21 17:55:42 2017 InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726320] Re: suggested and destructive colours are too bright
Ubuntu purple! :) ** Also affects: ubuntu-themes Importance: Undecided Status: New -- 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/1726320 Title: suggested and destructive colours are too bright Status in Ubuntu theme: New Status in ubuntu-themes package in Ubuntu: New Bug description: IMO, so feel free to close this if you disagree, the suggested and destructive (green and red) colours that are used in GTK UIs are too bright. Attached is a screenshot from Marco that shows them both. (It's a faked up example, usually you don't see them together like that.) They draw the eye too much I think. It should be a hint for where you might or might not want to click, but not something that grabs your attention. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1726320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726318] Re: Destructive actions on headerbar aren't properly themed
** Also affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-themes (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1726318 Title: Destructive actions on headerbar aren't properly themed Status in Ubuntu theme: In Progress Status in ubuntu-themes package in Ubuntu: In Progress Bug description: [ Impact ] On simple scan (for example) there's a .destructive-action button in the headerbar and it's not drawn as red unless the button is hovered, clicked or unfocused. It also uses inconsistent gradients [ Test case ] 1. Run gnome-scan 2. Start a scan session (or use the inspector to set the "Stop" button as visible) 3. Expect it to be red in all the cases (focused, pressed, unfocused, hovered) [ Regression Potential] Destructive buttons in headerbar could be broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1726318/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
It continues... bug 1726608 -- 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/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726634] Re: the sound laptop speaker is not working and it sound interface isnt showing in "sound" app. sound works perfectly in other users
It looks like you're logging in as root, is that correct? ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1726634 Title: the sound laptop speaker is not working and it sound interface isnt showing in "sound" app. sound works perfectly in other users Status in pulseaudio package in Ubuntu: Incomplete Bug description: the sound laptop speaker is not working and it sound interface isnt showing in "sound" app. sound works perfectly in other users ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: maximum2935 F chrome maximum7304 F AudioThread CurrentDesktop: Unity Date: Mon Oct 23 19:05:32 2017 InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.) No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.asset.tag: MAXIMUM dmi.board.name: 05GRXT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: MAXIMUM dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd01/04/2017:svnDellInc.:pnLatitudeE5530non-vPro:pvr01:rvnDellInc.:rn05GRXT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5530 non-vPro dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1726634/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725055] Re: pptp vpn cannot be easily connected in gnome network manager and gnome control center
If that could be the case, I updated the bug report to NetworkManager component of GNOME instead. https://bugzilla.gnome.org/show_bug.cgi?id=789341 ** Attachment added: "Selection_008.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725055/+attachment/4990011/+files/Selection_008.png -- 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/1725055 Title: pptp vpn cannot be easily connected in gnome network manager and gnome control center Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in network-manager-applet package in Ubuntu: New Bug description: I tried to reactivate a VPN (for PPTP) several times again and again using PPTP, and it is just that it just suddenly turns off every time I try to turn on. There is no process ongoing for PPTP. I tried to use an OpenVPN plugin for VPN, it works depending on the VPN server. I depend on VPN a lot especially on FreeVPN PPTP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 07:48:21 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1725055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725064] Re: nautilus lacks file search in the gnome activities screen
I wish that the effect here in Ubuntu 7.10 GNOME Shell search is the same as this when it is integrated in the files. I upgraded to Ubuntu 7.10 expecting for this. ** Attachment added: "Selection_009.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1725064/+attachment/4990022/+files/Selection_009.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1725064 Title: nautilus lacks file search in the gnome activities screen Status in gnome-desktop package in Ubuntu: New Status in nautilus package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: I used to search a file and access it immediately using Ubuntu 16.04 LTS and some other distributions of GNOME. However, this time, almost only folders are shown in the file search. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 08:23:44 2017 InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1725064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725064] Re: nautilus lacks file search in the gnome activities screen
I got this instead though... ** Attachment added: "Screenshot from 2017-10-24 11-20-30.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1725064/+attachment/4990023/+files/Screenshot%20from%202017-10-24%2011-20-30.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1725064 Title: nautilus lacks file search in the gnome activities screen Status in gnome-desktop package in Ubuntu: New Status in nautilus package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: I used to search a file and access it immediately using Ubuntu 16.04 LTS and some other distributions of GNOME. However, this time, almost only folders are shown in the file search. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 08:23:44 2017 InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1725064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726340] [NEW] Please add 'dkms' to the dependency list
Public bug reported: Fresh netboot install I have lost too much time fighting against stupid issues after the first installation reboot: - third party apps not listed into the menu - graphic issue - ... and finally have glanced at missing 'important' packages, like 'dkms, tweaks, dconf' ... not everyone knows about such url: http://www.omgubuntu.co.uk/2017/10 /things-to-do-after-installing-ubuntu-17-10 at least, if you do not add those to the 'recommended' list, then add them to the missing 'suggest' one. Make our Ubuntu great again. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 23 11:49:08 2017 SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Description changed: Fresh netboot install I have lost too much time fighting against stupid issues after the first installation reboot: - third party apps not listed into the menu - graphic issue - ... - and finally have thinked to glance at missing 'important' packages, like - 'dkms, tweaks, dconf' ... + and finally have glanced at missing 'important' packages, like 'dkms, + tweaks, dconf' ... not everyone knows about such url: http://www.omgubuntu.co.uk/2017/10 /things-to-do-after-installing-ubuntu-17-10 at least, if you do not add those to the 'recommended' list, then add them to the missing 'suggest' one. Make our Ubuntu great again. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 23 11:49:08 2017 SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1726340 Title: Please add 'dkms' to the dependency list Status in ubuntu-meta package in Ubuntu: New Bug description: Fresh netboot install I have lost too much time fighting against stupid issues after the first installation reboot: - third party apps not listed into the menu - graphic issue - ... and finally have glanced at missing 'important' packages, like 'dkms, tweaks, dconf' ... not everyone knows about such url: http://www.omgubuntu.co.uk/2017/10 /things-to-do-after-installing-ubuntu-17-10 at least, if you do not add those to the 'recommended' list, then add them to the missing 'suggest' one. Make our Ubuntu great again. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 23 11:49:08 2017 SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1726340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
Fwiw, I reported a RFE upstream to warn if networkd is used and promote_secondaries is unset (https://github.com/systemd/systemd/issues/7163) ** Bug watch added: github.com/systemd/systemd/issues #7163 https://github.com/systemd/systemd/issues/7163 -- 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/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore Status in Snappy: Fix Committed Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: New Status in systemd source package in Zesty: New Status in systemd source package in Artful: In Progress Bug description: [Impact] * networkd fails to renew a lease, specifically it fails to change IPv4 address via DHCP renew/rebind. * networkd relies on a kernel feature to promote secondary IPv4 address to primary, upon primary address lease expiry. * this sysctl tunable was not enabled by default in systemd. [Test Case] Add a device, and assign two IPv4 addresses. First one, with a short lease time. Second one, with a different ip and a longer lease time. Second one should be treated as secondary ip address, and upon expiry of the first one, should be promoted and become primary ip address. The below scripted instructions simulate this: sudo ip link add name testleases type dummy sudo ip address add 192.0.2.10/27 dev testleases \ valid_lft 5 preferred_lft 5 sudo ip address add 192.0.2.11/27 dev testleases \ valid_lft 11 preferred_lft 11 ip address list dev testleases | \ grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \ && echo ok || echo not ok ip address list dev testleases | \ grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \ && echo ok || echo not ok sleep 6 ip address list dev testleases | \ grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \ && echo ok || echo not ok sudo ip link del dev testleases [Regression Potential] * This changes the default kernel behaviour, previously upon expiry of the primary address, secondary addresses were removed as well. Which is imho silly. * comparing networkd renewal with isc-dhcp renewal the semantics are quite different. Upon acquiring new ip address, isc-dhcp would instantly flush existing ip address, and add a new one. Networkd add the new address as secondary, and waits for old one to expire first before promoting / switching to using the new ip address. IMHO kernel should have an API to promote secondary ip address to a primary one. * This update also applies other safe-looking options, which are currently also already applied via sysctls shipped in other packages # Source route verification net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 # Do not accept source routing net.ipv4.conf.default.accept_source_route = 0 net.ipv4.conf.all.accept_source_route = 0 # Enable hard and soft link protection fs.protected_hardlinks = 1 fs.protected_symlinks = 1 * This update also applies the following upstream/bufferbloat.net recommended setting # Fair Queue CoDel packet scheduler to fight bufferbloat net.core.default_qdisc = fq_codel * [~racb] There are complex network setups out there, such as HA with corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this fix were SRU'd, will all of these things in the wild cope with this sysctl change? [Other Info] * Original bug report Hi there, we found a replicable issue that involves the Ubuntu Core networking and causes complete loss of connectivity. We run a custom board with ubuntu core: the architecure is amrhf. We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: other platform was been tested. It shows that it is a snap core problem which interests networkd: we use the default network stack based on networkd + netplan. Below steps to replicate the issue. 1)Setup a dhcp server for lease of about some minutes (i.e 10 minutes). 2)Boot the board and wait for get an ip from dhcp server 3)Before the lease expires, set a reservation for a different ip address Depending on lease duration before the lease expires( for 10 minute we have 2 minutes before ), networkd configure the new address in addition to the previous one. When the lease expire both ip address ( the prevoius and the new one ) disappear from the interested network interface. Depending on lease duration before the second lease expires ( for 10 minure we have 2 minutes before ) networkd configure only the new ip address on the network interface and the ping toward an outside host work properly. During the test the dhcp server records correctly leases and their duration. We check directly from console the network
Re: [Touch-packages] [Bug 1726010] Re: systemd-journald crashed with SIGABRT in journal_file_find_data_object_with_hash()
*** This bug is a duplicate of bug 1690935 *** https://bugs.launchpad.net/bugs/1690935 Thank you. I am not an expert in ubuntu or linux distribution at all. So if this bugs are already duplicate, I´m sending my apologies. BR 2017-10-22 10:55 GMT-03:00 Apport retracing service < 1726...@bugs.launchpad.net>: > *** This bug is a duplicate of bug 1690935 *** > https://bugs.launchpad.net/bugs/1690935 > > Thank you for taking the time to report this crash and helping to make > this software better. This particular crash has already been reported > and is a duplicate of bug #1690935, so is being marked as such. Please > look at the other bug report to see if there is any missing information > that you can provide, or to see if there is a workaround for the bug. > Additionally, any further discussion regarding the bug should occur in > the other report. Please continue to report any other bugs you may > find. > > ** Attachment removed: "CoreDump.gz" >https://bugs.launchpad.net/bugs/1726010/+attachment/ > 4985015/+files/CoreDump.gz > > ** Attachment removed: "Disassembly.txt" >https://bugs.launchpad.net/bugs/1726010/+attachment/ > 4985018/+files/Disassembly.txt > > ** Attachment removed: "ProcMaps.txt" >https://bugs.launchpad.net/bugs/1726010/+attachment/ > 4985025/+files/ProcMaps.txt > > ** Attachment removed: "ProcStatus.txt" >https://bugs.launchpad.net/bugs/1726010/+attachment/ > 4985027/+files/ProcStatus.txt > > ** Attachment removed: "Registers.txt" >https://bugs.launchpad.net/bugs/1726010/+attachment/ > 4985028/+files/Registers.txt > > ** Attachment removed: "Stacktrace.txt" >https://bugs.launchpad.net/bugs/1726010/+attachment/ > 4985029/+files/Stacktrace.txt > > ** Attachment removed: "ThreadStacktrace.txt" >https://bugs.launchpad.net/bugs/1726010/+attachment/4985030/+files/ > ThreadStacktrace.txt > > ** This bug has been marked a duplicate of private bug 1690935 > > ** Information type changed from Private to Public > > ** Tags removed: need-amd64-retrace > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1726010 > > Title: > systemd-journald crashed with SIGABRT in > journal_file_find_data_object_with_hash() > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/ > 1726010/+subscriptions > -- Gonzalo Vazquez Ing. Químico -- 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/1726010 Title: systemd-journald crashed with SIGABRT in journal_file_find_data_object_with_hash() Status in systemd package in Ubuntu: New Bug description: I was opening a firefox sheet and all was freezed ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sun Oct 22 10:19:55 2017 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=es_AR.UTF-8 LANGUAGE=es_AR:es PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: journal_file_find_data_object_with_hash () from /lib/systemd/libsystemd-shared-234.so ?? () from /lib/systemd/libsystemd-shared-234.so journal_file_append_entry () from /lib/systemd/libsystemd-shared-234.so ?? () ?? () SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-journald crashed with SIGABRT in journal_file_find_data_object_with_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/24/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: V7.5 dmi.board.name: MS-7246 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 2.1 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrV7.5:bd05/24/2007:svn:pn:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7246:rvr2.1:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726350] Re: unattended-upgrade crashed with apt.cache.LockFailedException in _fetch_archives(): Failed to lock /var/cache/apt/archives/lock
** Tags removed: need-duplicate-check ** Changed in: unattended-upgrades (Ubuntu) Importance: Undecided => Medium -- 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/1726350 Title: unattended-upgrade crashed with apt.cache.LockFailedException in _fetch_archives(): Failed to lock /var/cache/apt/archives/lock Status in unattended-upgrades package in Ubuntu: New Bug description: I am unable to tell you how this happened, I just saw the application which reports bugs logo in the task bar. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: unattended-upgrades 0.98ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 06:25:37 2017 ExecutablePath: /usr/bin/unattended-upgrade InstallationDate: Installed on 2017-03-23 (213 days ago) InstallationMedia: budgie-remix 16.10 "Budgie-remix" - amd64 (20161013) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/unattended-upgrade Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/bin/unattended-upgrade'] PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SourcePackage: unattended-upgrades Title: unattended-upgrade crashed with apt.cache.LockFailedException in _fetch_archives(): Failed to lock /var/cache/apt/archives/lock UpgradeStatus: Upgraded to artful on 2017-10-20 (2 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1726350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726350] [NEW] unattended-upgrade crashed with apt.cache.LockFailedException in _fetch_archives(): Failed to lock /var/cache/apt/archives/lock
Public bug reported: I am unable to tell you how this happened, I just saw the application which reports bugs logo in the task bar. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: unattended-upgrades 0.98ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 06:25:37 2017 ExecutablePath: /usr/bin/unattended-upgrade InstallationDate: Installed on 2017-03-23 (213 days ago) InstallationMedia: budgie-remix 16.10 "Budgie-remix" - amd64 (20161013) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/unattended-upgrade Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/bin/unattended-upgrade'] PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SourcePackage: unattended-upgrades Title: unattended-upgrade crashed with apt.cache.LockFailedException in _fetch_archives(): Failed to lock /var/cache/apt/archives/lock UpgradeStatus: Upgraded to artful on 2017-10-20 (2 days ago) UserGroups: ** Affects: unattended-upgrades (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash artful ** Information type changed from Private to Public -- 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/1726350 Title: unattended-upgrade crashed with apt.cache.LockFailedException in _fetch_archives(): Failed to lock /var/cache/apt/archives/lock Status in unattended-upgrades package in Ubuntu: New Bug description: I am unable to tell you how this happened, I just saw the application which reports bugs logo in the task bar. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: unattended-upgrades 0.98ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sat Oct 21 06:25:37 2017 ExecutablePath: /usr/bin/unattended-upgrade InstallationDate: Installed on 2017-03-23 (213 days ago) InstallationMedia: budgie-remix 16.10 "Budgie-remix" - amd64 (20161013) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/unattended-upgrade Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/bin/unattended-upgrade'] PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SourcePackage: unattended-upgrades Title: unattended-upgrade crashed with apt.cache.LockFailedException in _fetch_archives(): Failed to lock /var/cache/apt/archives/lock UpgradeStatus: Upgraded to artful on 2017-10-20 (2 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1726350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1469890] Re: Could not get the Network Manager state
*** This bug is a duplicate of bug 1594715 *** https://bugs.launchpad.net/bugs/1594715 ** This bug has been marked a duplicate of bug 1594715 wifi does not work roughly half of the times -- 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/1469890 Title: Could not get the Network Manager state Status in network-manager package in Ubuntu: Confirmed Bug description: During boot my laptop behaves weird. Sometimes there are no network connection for the first 60 seconds after desktop is loaded. But on some days, they come quickly, connections are build before desktop is loaded. Had a look in the journal and found these lines interesting: Jun 30 09:07:31 M2 whoopsie[756]: [09:07:31] Could not get the Network Manager state: Jun 30 09:07:31 M2 whoopsie[756]: [09:07:31] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files Any clues? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1469890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725055] Re: pptp vpn cannot be easily connected in gnome network manager and gnome control center
I think this error report had a similar problem, the bug report said it is not GNOME problem: https://bugzilla.gnome.org/show_bug.cgi?id=773163 On the other hand, I created this same bug report to GNOME: https://bugzilla.gnome.org/show_bug.cgi?id=789341 with a video to express clearly what the problem I'm having. ** Attachment added: "vokoscreen-2017-10-23_17-35-49.mkv" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725055/+attachment/4987642/+files/vokoscreen-2017-10-23_17-35-49.mkv -- 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/1725055 Title: pptp vpn cannot be easily connected in gnome network manager and gnome control center Status in gnome-control-center package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in network-manager-applet package in Ubuntu: New Bug description: I tried to reactivate a VPN (for PPTP) several times again and again using PPTP, and it is just that it just suddenly turns off every time I try to turn on. There is no process ongoing for PPTP. I tried to use an OpenVPN plugin for VPN, it works depending on the VPN server. I depend on VPN a lot especially on FreeVPN PPTP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 07:48:21 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
Packages uploaded to https://launchpad.net/~snappy-hwe- team/+archive/ubuntu/stacks-overlay and built for xenial. The versions are the same as for artful, plus additional patches for Dell modems in the modem-manager source package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: New Bug description: We would like to upgrade xenial to 1.6 series so it supports the same modems as the modem-manager snap, specifically some new Sierra modems (HL8548 and others from HL series, popular in IoT devices). These are the packages that would need to be updated: libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap libqmi: 1.12.6-1 in xenial, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10
If you need further information, please let me know. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1725840 Title: resolvconf not correctly configured after update from 17.04 to 17.10 Status in resolvconf package in Ubuntu: New Bug description: After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS lookup on my wireless network connection did not work any more. As it seems, the file /etc/resolv.conf was static and contained wrong data assigned by the NetworkManager. When I changed the file content manually to nameserver 127.0.0.53 DNS lookup worked fine. After reboot, however, I had to repeat this operation since NetworkManager seems to have replaced the file content. Finally, I found a solution. Running sudo dpkg-reconfigure resolvconf the file /etc/resolv.conf was replaced by the link /etc/resolv.conf -> ../run/resolvconf/resolv.conf Now, the wireless network seems to work properly. Hence, there must be some kind of bug during the update process from Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured properly. Best regards, Artur ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: resolvconf 1.79ubuntu8 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 23:17:38 2017 InstallationDate: Installed on 2013-10-18 (1463 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726309] [NEW] avahi-daemon[590]: chroot.c: open() failed: No such file or directory
Public bug reported: Get that error on a fresh mini.iso install [uArtful 3] ~ > journalctl | grep avahi avahi-daemon[581]: Found user 'avahi' (UID 116) and group 'avahi' (GID 122). avahi-daemon[581]: Successfully dropped root privileges. avahi-daemon[581]: avahi-daemon 0.6.32 starting up. avahi-daemon[581]: Successfully called chroot(). avahi-daemon[581]: Successfully dropped remaining capabilities. avahi-daemon[590]: chroot.c: open() failed: No such file or directory avahi-daemon[581]: Failed to open /etc/resolv.conf: Invalid argument avahi-daemon[581]: No service file found in /etc/avahi/services. avahi-daemon[581]: Network interface enumeration completed. avahi-daemon[581]: Server startup complete. Host name is uArtful.local. Local service cookie is 2251384537. avahi-daemon[581]: Joining mDNS multicast group on interface enp2s0.IPv4 with address 192.168.1.2. avahi-daemon[581]: New relevant interface enp2s0.IPv4 for mDNS. avahi-daemon[581]: Registering new address record for 192.168.1.2 on enp2s0.IPv4. avahi-daemon[581]: Joining mDNS multicast group on interface enp2s0.IPv6 with address fe80::7285:c2ff:fe23:9b4c. avahi-daemon[581]: New relevant interface enp2s0.IPv6 for mDNS. avahi-daemon[581]: Registering new address record for fe80::7285:c2ff:fe23:9b4c on enp2s0.*. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 23 10:47:44 2017 SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: avahi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1726309 Title: avahi-daemon[590]: chroot.c: open() failed: No such file or directory Status in avahi package in Ubuntu: New Bug description: Get that error on a fresh mini.iso install [uArtful 3] ~ > journalctl | grep avahi avahi-daemon[581]: Found user 'avahi' (UID 116) and group 'avahi' (GID 122). avahi-daemon[581]: Successfully dropped root privileges. avahi-daemon[581]: avahi-daemon 0.6.32 starting up. avahi-daemon[581]: Successfully called chroot(). avahi-daemon[581]: Successfully dropped remaining capabilities. avahi-daemon[590]: chroot.c: open() failed: No such file or directory avahi-daemon[581]: Failed to open /etc/resolv.conf: Invalid argument avahi-daemon[581]: No service file found in /etc/avahi/services. avahi-daemon[581]: Network interface enumeration completed. avahi-daemon[581]: Server startup complete. Host name is uArtful.local. Local service cookie is 2251384537. avahi-daemon[581]: Joining mDNS multicast group on interface enp2s0.IPv4 with address 192.168.1.2. avahi-daemon[581]: New relevant interface enp2s0.IPv4 for mDNS. avahi-daemon[581]: Registering new address record for 192.168.1.2 on enp2s0.IPv4. avahi-daemon[581]: Joining mDNS multicast group on interface enp2s0.IPv6 with address fe80::7285:c2ff:fe23:9b4c. avahi-daemon[581]: New relevant interface enp2s0.IPv6 for mDNS. avahi-daemon[581]: Registering new address record for fe80::7285:c2ff:fe23:9b4c on enp2s0.*. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 23 10:47:44 2017 SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1726309/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725455] Re: UI login invisible / UI hanging when Dual 4K monitor via Displayport MST is connected (Lenovo Ultra Dock)
Update: I did a full 17.10 reinstall as last attempt. I can confirm the following symptoms: - When both 4k displays are connected to the docking (displayport MST), UI login screen is already hanging (see earlier screenshot) - When 1 x 4K display is connected it works. When connecting 2nd display after login (using Wayland), the UI is completely hanging ** Summary changed: - Dual 4K monitor via Displayport MST not working (Lenovo Ultra Dock) + UI login invisible / UI hanging when Dual 4K monitor via Displayport MST is connected (Lenovo Ultra Dock) -- 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/1725455 Title: UI login invisible / UI hanging when Dual 4K monitor via Displayport MST is connected (Lenovo Ultra Dock) Status in xorg package in Ubuntu: New Bug description: I am experiencing serious issues after upgrading to Ubuntu 17.10 (coming from 17.04 with Gnome, kernel 4.13). I have 2 x 4K (Asus PB279Q) monitors, connected to a Lenovo Ultra Dock (containing 2 x Displayport via MST), where the Lenovo T550 is connected onto it. Both monitors were working perfectly fine at 30Hz simultaneously in an extended desktop, 4K resolution in my old setup with Gnome for over half a year (since kernel 4.10 blink issues on 4K were solved, i used this setup since then). However after upgrading to 17.10 using the new Gnome interface: When the laptop is connected to the Lenovo Ultra Dock (to work on both monitors), the system is hanging and becoming unresponsive. The mouse pointer is freezing and the only way is to do a hard-reboot. I have checked the monitor settings, it's displayed at 60Hz when active, and it appears I am never able to use both monitors simultaneously. When I get 1 monitor working (disconnecting the 2nd monitor from the MST port), after rebooting it works fine. I tried to put settings of the 4K manually on 30Hz, reconnecting, but the system hangs again. I have tried several combinations. It results in a blank (purple) screen and hanging mouse (see attachment). I tried also with the installation-iso to run a fresh 17.10 and tried the same, the symptoms are similar. I suspect that must be an issue with the Displayport MST on dual 4K setups in the new 17.10. When I connect 1 x 4K monitor to the rear displayport of the Lenovo Ultra Dock (there are 2 for MST on the rear, so I disconnected the other) *and* when I connect the other 4K monitor on the separate displayport of the T550 itself instead, it works 100% fine! Shortly: based on my knowledge that must definitely be some issue with the MST displayport functionality itself, that is unable to recognize/identify both 4K monitors when connected to the dock's both displayport connections? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.13.4-041304-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 21:10:50 2017 DistUpgraded: 2017-10-19 21:54:53,162 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2225] Subsystem: Lenovo GM108M [GeForce 940M] [17aa:2225] InstallationDate: Installed on 2017-04-16 (186 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.4-041304-generic root=UUID=9fcc7f4c-35c0-4297-9c98-4dac9acee798 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET42W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CKCTO1WW:pvrThinkPadT550:rvnLENOVO:rn20CKCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CKCTO1WW dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core
[Touch-packages] [Bug 1725055] Re: pptp vpn cannot be easily connected in gnome network manager and gnome control center
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/1725055 Title: pptp vpn cannot be easily connected in gnome network manager and gnome control center Status in gnome-control-center package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in network-manager-applet package in Ubuntu: New Bug description: I tried to reactivate a VPN (for PPTP) several times again and again using PPTP, and it is just that it just suddenly turns off every time I try to turn on. There is no process ongoing for PPTP. I tried to use an OpenVPN plugin for VPN, it works depending on the VPN server. I depend on VPN a lot especially on FreeVPN PPTP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 07:48:21 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721102] Re: Thin line at the left of Simple Scan's "Scan" headerbar button
** Description changed: - There is a thin colored line (green or red) at the left of rounded - button, for example in simple-scan in the screenshot attached (I didn't - find any other app affected ATM) + [Impact] + There is a thin colored line (green or red) at the left of rounded button, for example in simple-scan in the screenshot attached (I didn't find any other app affected ATM) + + [Test case] + 1. Run simple scan + 2. Expect "Scan" button background color to fill all the space. + + 4. Start scanning and expect the same for "Stop" button too ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170930-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 3 20:16:32 2017 InstallationDate: Installed on 2013-09-03 (1490 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) PackageArchitecture: all ProcEnviron: - TERM=screen-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=screen-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1721102 Title: Thin line at the left of Simple Scan's "Scan" headerbar button Status in Ubuntu theme: In Progress Status in ubuntu-themes package in Ubuntu: In Progress Bug description: [Impact] There is a thin colored line (green or red) at the left of rounded button, for example in simple-scan in the screenshot attached (I didn't find any other app affected ATM) [Test case] 1. Run simple scan 2. Expect "Scan" button background color to fill all the space. 4. Start scanning and expect the same for "Stop" button too ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170930-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 3 20:16:32 2017 InstallationDate: Installed on 2013-09-03 (1490 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1721102/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725055] Re: pptp vpn cannot be easily connected in gnome network manager and gnome control center
I think this error report had a similar problem, the bug report said it is not GNOME problem: https://bugzilla.gnome.org/show_bug.cgi?id=773163 On the other hand, I created this same bug report to GNOME: https://bugzilla.gnome.org/show_bug.cgi?id=789341 with a video to express clearly what the problem I'm having. ** Bug watch added: GNOME Bug Tracker #773163 https://bugzilla.gnome.org/show_bug.cgi?id=773163 ** Bug watch added: GNOME Bug Tracker #789341 https://bugzilla.gnome.org/show_bug.cgi?id=789341 -- 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/1725055 Title: pptp vpn cannot be easily connected in gnome network manager and gnome control center Status in gnome-control-center package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in network-manager-applet package in Ubuntu: New Bug description: I tried to reactivate a VPN (for PPTP) several times again and again using PPTP, and it is just that it just suddenly turns off every time I try to turn on. There is no process ongoing for PPTP. I tried to use an OpenVPN plugin for VPN, it works depending on the VPN server. I depend on VPN a lot especially on FreeVPN PPTP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 07:48:21 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726187] Re: After 17.04 -> 17.10 upgrade, wifi often freezes
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- 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/1726187 Title: After 17.04 -> 17.10 upgrade, wifi often freezes Status in network-manager package in Ubuntu: New Bug description: (might be incorrect package) About once every few hours, my wifi locks up until I use "turn off + turn on" in the network control - upper right corner drop down. This has started happening after the upgrade from 17.04 to 17.10. The wireless signal is very strong, and it remains strong even after lock up. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 20:41:31 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-13 (192 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) IpRoute: default via 192.168.2.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.2.0/24 dev wlp58s0 proto kernel scope link src 192.168.2.131 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to artful on 2017-10-19 (3 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/3 docker0 c1be4834-7fc1-4167-8509-90e5d1946c14 /org/freedesktop/NetworkManager/ActiveConnection/2 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 pups4bf35394-3e64-4dbe-b1b2-5d1953df7058 /org/freedesktop/NetworkManager/ActiveConnection/14 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1726187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726304] Re: systemd-udevd crashed with SIGABRT in __libc_open64()
*** This bug is a duplicate of bug 1715782 *** https://bugs.launchpad.net/bugs/1715782 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1715782, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726304/+attachment/4987467/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726304/+attachment/4987470/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726304/+attachment/4987477/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726304/+attachment/4987479/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726304/+attachment/4987480/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726304/+attachment/4987481/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726304/+attachment/4987482/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1715782 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1726304 Title: systemd-udevd crashed with SIGABRT in __libc_open64() Status in systemd package in Ubuntu: New Bug description: Crash after booting system ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Mon Oct 23 09:31:18 2017 ExecutablePath: /lib/systemd/systemd-udevd InstallationDate: Installed on 2017-09-30 (22 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: Dell Inc. Vostro 3300 ProcCmdline: /lib/systemd/systemd-udevd ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=1345678b-e284-4b31-9df4-636dd0b03a1b ro quiet splash acpi_osi=Linux Signal: 6 SourcePackage: systemd StacktraceTop: __libc_open64 (file=0x558833571240 "/dev/sdb", oflag=657408) at ../sysdeps/unix/sysv/linux/open64.c:46 ?? () ?? () ?? () ?? () Title: systemd-udevd crashed with SIGABRT in __libc_open64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/08/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 07JC8T dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd04/08/2014:svnDellInc.:pnVostro3300:pvrA12:rvnDellInc.:rn07JC8T:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Vostro 3300 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726320] [NEW] suggested and destructive colours are too bright
Public bug reported: IMO, so feel free to close this if you disagree, the suggested and destructive (green and red) colours that are used in GTK UIs are too bright. Attached is a screenshot from Marco that shows them both. (It's a faked up example, usually you don't see them together like that.) They draw the eye too much I think. It should be a hint for where you might or might not want to click, but not something that grabs your attention. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Attachment added: "colours.png" https://bugs.launchpad.net/bugs/1726320/+attachment/4987564/+files/colours.png -- 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/1726320 Title: suggested and destructive colours are too bright Status in ubuntu-themes package in Ubuntu: New Bug description: IMO, so feel free to close this if you disagree, the suggested and destructive (green and red) colours that are used in GTK UIs are too bright. Attached is a screenshot from Marco that shows them both. (It's a faked up example, usually you don't see them together like that.) They draw the eye too much I think. It should be a hint for where you might or might not want to click, but not something that grabs your attention. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1726320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726333] [NEW] Mouse Cursor not available under Wayland
Public bug reported: Sorry for this being filed under xorg, but I do not get "Wayland" offered. After logging in to Ubuntu 17.10 in Wayland, the mouse cursor flickers shortly and then is gone. In XOrg session all is fine. I had no issues with the cursor in the artful beta release - I was using the beta release of Ubuntu 17.10 7 to 10 days before the final release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Oct 23 11:39:45 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:3801] InstallationDate: Installed on 2017-10-12 (10 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 80VF ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=a5819d75-73ad-458c-8bde-fd93b2f7d230 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2JCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Agera 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 910-13IKB dmi.modalias: dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80VF dmi.product.version: Lenovo YOGA 910-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 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 artful 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/1726333 Title: Mouse Cursor not available under Wayland Status in xorg package in Ubuntu: New Bug description: Sorry for this being filed under xorg, but I do not get "Wayland" offered. After logging in to Ubuntu 17.10 in Wayland, the mouse cursor flickers shortly and then is gone. In XOrg session all is fine. I had no issues with the cursor in the artful beta release - I was using the beta release of Ubuntu 17.10 7 to 10 days before the final release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Oct 23 11:39:45 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:3801] InstallationDate: Installed on 2017-10-12 (10 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 80VF ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=a5819d75-73ad-458c-8bde-fd93b2f7d230 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2JCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Agera 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 910-13IKB dmi.modalias: dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80VF dmi.product.version: Lenovo YOGA 910-13IKB dmi.sys.vendor: LENOVO
[Touch-packages] [Bug 1725976] Re: Sometimes need to login 2 times after resume from suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1725976 Title: Sometimes need to login 2 times after resume from suspend Status in lightdm package in Ubuntu: Confirmed Bug description: I'm on Xubuntu 17.10 About 50% of resume from suspend requires me to login 2 times instead of just once. I press shift to resume from suspend. The login prompt comes - I login. Sometimes, I get logged in. Other times, the login prompt comes again. login manager : lightdm Been using 17.10 pre-releases (and taking daily updates) since about 20 days. The problem has been around since day one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1725976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619844] Re: [Xenial] shutdown/reboot hangs at "Reached target Shutdown"
Just a quick clarification, first boot/shutdown will still not be clean, but subsequent ones (those that are booted with the updated mdadm package) should be clean. -- 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/1619844 Title: [Xenial] shutdown/reboot hangs at "Reached target Shutdown" Status in systemd package in Ubuntu: Confirmed Bug description: I tried getting more information in the debug-shell but I was unsuccessful in doing so. I was able to switch to the debug shell via ctrl+alt+f9 but I couldn't actually type anything in. I could switch back to the stuck shutdown screen via ctrl+alt+f1, and hitting NumLock would turn the light on my keyboard on and off, but I couldn't do anything else. I captured a journal of the stuck reboot. Interestingly, the journal shows a few more lines after "Reached target Shutdown", which is as far as I get on my screen. This system was installed with Xenial 16.04.1 (never been upgraded) and has had this problem since the very first boot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Sep 3 00:33:19 2016 InstallationDate: Installed on 2016-08-17 (16 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=5f709fed-48c9-4830-87be-acd13f263eb1 ro SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/mariadb.service → /etc/systemd/system/mariadb.service.d/migrated-from-my.cnf-settings.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-404:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1619844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
Just a quick clarification, first boot/shutdown will still not be clean, but subsequent ones (those that are booted with the updated mdadm package) should be clean. -- 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/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." Status in systemd package in Ubuntu: Confirmed Bug description: I'm booting a fully patched 16.04 from an Intel Rapid Storage Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode). If the RAID volume is recovering or resyncing for whatever reason, then `sudo systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to consistently get that). However, once the recovery/resync is complete and clean, the reboot and poweroff commands above hang forever after "Reached target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in the bug #1464917) does not help. [EDIT]Actually, the shutdown also hangs from time to time during a resync. But I've never seen it succeed once the resync is complete.[/EDIT] Then, if the server has been forcibly restarted with the power button, the Intel Matrix Storage Manager indicates a "Normal" status for the RAID1 volume, but Ubuntu then resyncs the volume anyway: [1.223649] md: bind [1.228426] md: bind [1.230030] md: bind [1.230738] md: bind [1.232985] usbcore: registered new interface driver usbhid [1.233494] usbhid: USB HID core driver [1.234022] md: raid1 personality registered for level 1 [1.234876] md/raid1:md126: not clean -- starting background reconstruction [1.234956] input: CHESEN USB Keyboard as /devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5 [1.236273] md/raid1:md126: active with 2 out of 2 mirrors [1.236797] md126: detected capacity change from 0 to 1000202043392 [1.246271] md: md126 switched to read-write mode. [1.246834] md: resync of RAID array md126 [1.247325] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [1.247503] md126: p1 p2 p3 p4 [1.248269] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. [1.248774] md: using 128k window, over a total of 976759940k. Note that the pain of "resync upon every (re)boot" cannot even be a bit relieved thanks to bitmaps because mdadm does not support them for IMSM containers: $ sudo mdadm --grow --bitmap=internal /dev/md126 mdadm: Cannot add bitmaps to sub-arrays yet I also get this in syslog during boot when the individual drives are detected, but this seems to be harmless: May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental /dev/sdb --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental /dev/sda --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed with exit code 1. During a resync, `sudo sh -c 'echo idle > /sys/block/md126/md/sync_action'` actually stops it as expected, but it restarts immediately though nothing seems to have triggered it: May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted. May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of md126. May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126 May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a total of 976759940k. May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 from checkpoint. May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device /dev/md/Volume0 I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 > /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without any keyboard. [EDIT]But I can still switch back to tty1.[/EDIT] I have also tried with much lower values for vm.dirty_background_ratio and vm.dirty_ratio, but to no avail. Linux 4.6.0-040600-generic_4.6.0-040600.201605151930_amd64 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ did not help either. More
[Touch-packages] [Bug 1467173] Re: poweroff or reboot hangs
Just a quick clarification, first boot/shutdown will still not be clean, but subsequent ones (those that are booted with the updated mdadm package) should be clean. -- 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/1467173 Title: poweroff or reboot hangs Status in systemd package in Ubuntu: Incomplete Bug description: After the upgrade to 15.04, poweroff or reboot hangs, the last message is quotaoff.sh[PID]... done It hangs if executed by clicking from the menu, as well as with the 'poweroff', 'reboot', or 'halt' commands from the terminal. In debug console, in the journalctl -f output, this one error can be seen Failed umounting /tmp and the last messages before the freeze are like Starting Final Step Starting Power-Off Shutting Down I can still switch vt, but cannot type. After some time, kernel writes: info: task systemd-shutdow:1 blocked for more than 120 seconds. ctrl-alt-del does nothing. the only ways to bring server down seem to be alt-sysrq or powerbutton. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 20 22:17:59 2015 InstallationDate: Installed on 2011-09-16 (1373 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/vg00-lv_ubuntu_root ro SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-06-19 (1 days ago) dmi.bios.date: 02/23/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2102:bd02/23/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1467173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710313] Re: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1
Looks like somehow 'python-configparser' is no longer installed on your desktop; try resolving using: sudo apt install python-configparser python-minimal uses configparser, but has no direct depends which I find a little odd. ** Package changed: python-decorator (Ubuntu) => python-defaults (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-decorator in Ubuntu. https://bugs.launchpad.net/bugs/1710313 Title: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 Status in python-defaults package in Ubuntu: New Bug description: I can't enter the desktop system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-decorator 4.0.6-1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Aug 11 23:44:37 2017 Dependencies: ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1 InstallationDate: Installed on 2017-08-10 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: python-decorator Title: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1710313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710313] Re: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1
Re-assigning to python-defaults (which provides python-minimal). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1710313 Title: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 Status in python-defaults package in Ubuntu: New Bug description: I can't enter the desktop system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-decorator 4.0.6-1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Aug 11 23:44:37 2017 Dependencies: ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1 InstallationDate: Installed on 2017-08-10 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: python-decorator Title: package python-decorator 4.0.6-1 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1710313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1594715] Re: wifi does not work roughly half of the times
Got this bug today's boot: # cat /var/log/syslog | grep "Oct 23" | grep -i "network\|dnsmasq\|whoopsie" Oct 23 13:39:36 localhost systemd[1]: Reached target Network (Pre). Oct 23 13:39:36 localhost systemd[1]: Starting Raise network interfaces... Oct 23 13:39:36 localhost systemd[1]: Started Raise network interfaces. Oct 23 13:39:36 localhost systemd[1]: Reached target Network. Oct 23 13:39:36 localhost systemd[1]: Reached target Network is Online. Oct 23 13:39:36 localhost kernel: [2.547112] FUJITSU Extended Socket Network Device Driver - version 1.0 - Copyright (c) 2015 FUJITSU LIMITED Oct 23 13:39:36 localhost avahi-daemon[1174]: Network interface enumeration completed. Oct 23 13:39:36 localhost systemd[1]: Starting Anonymizing overlay network for TCP... Oct 23 13:39:36 localhost systemd[1]: Starting Anonymizing overlay network for TCP (multi-instance-master)... Oct 23 13:39:36 localhost systemd[1]: Started Anonymizing overlay network for TCP (multi-instance-master). Oct 23 13:39:36 localhost whoopsie[1204]: [13:39:36] Using lock path: /var/lock/whoopsie/lock Oct 23 13:39:36 localhost whoopsie[1204]: [13:39:36] Could not get the Network Manager state: Oct 23 13:39:36 localhost whoopsie[1204]: [13:39:36] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files Oct 23 13:39:37 localhost systemd[1]: Failed to start Anonymizing overlay network for TCP. Oct 23 13:39:37 localhost systemd[1]: Stopped Anonymizing overlay network for TCP. Oct 23 13:39:37 localhost systemd[1]: Starting Anonymizing overlay network for TCP... Oct 23 13:39:39 localhost systemd[1]: Failed to start Anonymizing overlay network for TCP. Oct 23 13:39:39 localhost systemd[1]: Stopped Anonymizing overlay network for TCP. Oct 23 13:39:39 localhost systemd[1]: Starting Anonymizing overlay network for TCP... Oct 23 13:39:40 localhost systemd[1]: Failed to start Anonymizing overlay network for TCP. Oct 23 13:39:40 localhost systemd[1]: Stopped Anonymizing overlay network for TCP. Oct 23 13:39:40 localhost systemd[1]: Starting Anonymizing overlay network for TCP... Oct 23 13:39:41 localhost systemd[1]: Failed to start Anonymizing overlay network for TCP. Oct 23 13:39:41 localhost systemd[1]: Stopped Anonymizing overlay network for TCP. Oct 23 13:39:41 localhost systemd[1]: Starting Anonymizing overlay network for TCP... Oct 23 13:39:42 localhost systemd[1]: Failed to start Anonymizing overlay network for TCP. Oct 23 13:39:42 localhost systemd[1]: Stopped Anonymizing overlay network for TCP. Oct 23 13:39:42 localhost systemd[1]: Failed to start Anonymizing overlay network for TCP. Oct 23 13:39:48 localhost dnsmasq[2228]: started, version 2.75 cachesize 150 Oct 23 13:39:48 localhost dnsmasq[2228]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify Oct 23 13:39:48 localhost dnsmasq-dhcp[2228]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h Oct 23 13:39:48 localhost dnsmasq-dhcp[2228]: DHCP, sockets bound exclusively to interface virbr0 Oct 23 13:39:48 localhost dnsmasq[2228]: no servers found in /etc/resolv.conf, will retry Oct 23 13:39:48 localhost dnsmasq[2228]: read /etc/hosts - 7 addresses Oct 23 13:39:48 localhost dnsmasq[2228]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses Oct 23 13:39:48 localhost dnsmasq-dhcp[2228]: read /var/lib/libvirt/dnsmasq/default.hostsfile Oct 23 13:39:58 localhost blueman-mechanism: loading Network I have already disabled `dnsmasq` in /etc/NetworkManager/NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono #dns=dnsmasq [ifupdown] managed=false NetworkManager is a great tool for Wi-Fi and Ethernet configuration, I'm using laptop, not server. This bug is CRITICAL. Please fix it. ** Summary changed: - wifi does not work roughly half of the times + wifi and/or ethernet does not work roughly half of the times -- 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/1594715 Title: wifi and/or ethernet does not work roughly half of the times Status in network-manager package in Ubuntu: Confirmed Bug description: After booting, roughly half of the times, wifi doesn't work: The nm- applet menu looks as if no wifi would exist. Instead, it lists the a non-existing cable network device called "Marvell 88W8897 [AVASTAR] 802.11ac Wireless". (The network manager seems to be trying to connect to that device, but fails.) After doing /etc/init.d/network-manager restart the wifi device is always recognized properly, so I guess it's something happening in the wrong order during booting. (Alternatively, unloading and reloading the kernel module mwifiex_pcie also always helps.) The problem did not exist in ubuntu 15.10. Some more information: $
[Touch-packages] [Bug 1691901] Update Released
The verification of the Stable Release Update for base-files has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1691901 Title: [SRU] 50-motd-news costs 5 seconds every login on firewalled systems Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Zesty: Fix Released Status in base-files source package in Artful: Fix Released Bug description: I noticed quite a long time to login to some of my systems via ssh (or scp). Investigating lead me to find out that the '50-motd-news' file (/etc/update-motd.d/50-motd-news) was the primary cost. In line 108 [1] it does something like: curl --connect-timeout "5" --max-time "5" -A "..." -o - https://motd.ubuntu.com The systems I'm seeing this on are in a lab and do not have access to https://motd.ubuntu.com. The way the lab is configured, they just end up timing out. So every scp or ssh connection or other path to trigger update-motd will cost 5 seconds. === SRU === [ IMPACT ] This bug affects Ubuntu 17.04 systems which cannot reach the internet (more specifically, https://motd.ubuntu.com). There is a bug in the implementation of /etc/update-motd.d/50-news whereby the failure of the curl fetch of the motd news causes a 5-second delay. This should not be the case. By design, the motd is fetched in the background, by a systemd timer, and refreshed every ~12 hours, also in the background. On login, the script should just cat the cache file. If the cache file isn't found, then it will try to fetch a new motd. In the firewalled system case, the background fetch failed, AND didn't create an empty file. The fix as attached simply ensures that an empty file is created if the curl fetch fails. This eliminates the login delay and solves the bug. Every 12 hours, the curl will be retried, quietly in the background, so if the curl failure happened for temporary reasons, it'll recover, gracefully, eventually. [ TEST CASE ] You can either test this on a firewalled system. Or, if you can hack an entry in your local /etc/hosts for motd.ubuntu.com for an invalid IP address. Without the fix, you'll experience a 5 second delay on login. With the fix, you'll login immediately. Failure case: $ lxc launch ubuntu:17.04 LP1691901 $ lxc exec LP1691901 bash # ssh-import-id kirkland # echo 192.168.0.0 motd.ubuntu.com >> /etc/hosts # rm -f /var/cache/motd-news # exit $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true real0m5.333s user0m0.016s sys 0m0.000s Apply the fix. $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true real0m0.316s user0m0.008s sys 0m0.008s [ REGRESSION ] This is a simple, safe fix with minimal regression potential: diff -Nru base-files-9.6ubuntu13/update-motd.d/50-motd-news base-files-9.6ubuntu13.2/update-motd.d/50-motd-news --- base-files-9.6ubuntu13/update-motd.d/50-motd-news 2017-02-15 13:54:04.0 -0600 +++ base-files-9.6ubuntu13.2/update-motd.d/50-motd-news 2017-06-29 10:43:05.0 -0500 @@ -51,9 +51,13 @@ # If we're not forcing an update, and we have a cached motd-news file, # then just print it and exit as quickly as possible, for login performance. # Note that systemd should keep this cache file up to date, asynchronously -if [ "$FORCED" != "1" ] && [ -r $CACHE ]; then - echo - safe_print $CACHE +if [ "$FORCED" != "1" ]; then + if [ -r $CACHE ]; then + echo + safe_print $CACHE + else + : > $CACHE + fi exit 0 fi @@ -111,7 +115,9 @@ safe_print "$NEWS" # Try to update the cache safe_print "$NEWS" 2>/dev/null >$CACHE || true - fi + else + : > "$CACHE" + fi done rm -f "$NEWS" "$NEWS.err" exit 0 -- [1] https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: base-files 9.6ubuntu13 ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri May 19 01:11:30 2017 Ec2AMI: ami-004f Ec2AMIManifest: FIXME Ec2AvailabilityZone:
[Touch-packages] [Bug 1469890] Re: Could not get the Network Manager state
*** This bug is a duplicate of bug 1706195 *** https://bugs.launchpad.net/bugs/1706195 ** This bug is no longer a duplicate of bug 1594715 wifi and/or ethernet does not work roughly half of the times ** This bug has been marked a duplicate of bug 1706195 whoopsie can start before network-manager during boot -- 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/1469890 Title: Could not get the Network Manager state Status in network-manager package in Ubuntu: Confirmed Bug description: During boot my laptop behaves weird. Sometimes there are no network connection for the first 60 seconds after desktop is loaded. But on some days, they come quickly, connections are build before desktop is loaded. Had a look in the journal and found these lines interesting: Jun 30 09:07:31 M2 whoopsie[756]: [09:07:31] Could not get the Network Manager state: Jun 30 09:07:31 M2 whoopsie[756]: [09:07:31] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files Any clues? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1469890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715131] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1715131 Title: networkd add support for Bridge Priority, AgeingTimeSec and DefaultPVID Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Bug description: [Impact] Newer releases of networkd support more optional settings for Bridge Priority, AgeingTimeSec and DefaultPVID. https://www.freedesktop.org/software/systemd/man/systemd.netdev.html#AgeingTimeSec= https://www.freedesktop.org/software/systemd/man/systemd.netdev.html#Priority= https://www.freedesktop.org/software/systemd/man/systemd.netdev.html#DefaultPVID= Backporting these features to xenial, allows to use/set these options via netplan for any releases as for example deployed by MAAS. [Fix] cherrypick these settings for better supportability of networkd on xenial with netplan. [Testcase] 1) Create .netdev bridge device 2) Specify Priority, AgeingTimeSec, DefaultPVID settings in the [Bridge] section 3) Verify that there are no parsing errors in journalctl from systemd-netword 4) Verify with `ip` command that the bridge device got created 5) Verify in sysfs that the settings requested have been applied to the device [Regression] These stanazas are optional, and will be ignored by older networkd if for example users start using them, and downgrade networkd to the one in release pocket. It is future compatible settings that will not cause upgrade issues, nor could result in failure to create the bridge device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1715131/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713536] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1713536 Title: udev: boot script does not trigger subsystem coldplug Status in Ubuntu on IBM z Systems: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Zesty: Fix Committed Status in systemd source package in Artful: Fix Released Bug description: [Impact] subsystems udev rules are not processed on boot, thus resulting in missing devices on boot / before rootfs is mounted. [Solution] trigger udev subsystems and devices, in the initramfs, in that order. [Testcase] Boot s390x system with chzdev configured devices, and cio_ignore=all kernel command line parameter. The chzdev configured devices should still be discovered on boot. [Original Bug report] The udev initramfs-tools boot script does not trigger subsystem "add" uevents. As a result, udev rules that listen to subsystem "add" events are never activated. This problem exists on at least Ubuntu 16.04 and 17.10. On s390, this results in a boot failure if the kernel is configured to start with an active device black list (kernel parameter cio_ignore=all,!condev). An example for an affected udev rule looks like this: ACTION=="add", SUBSYSTEM=="subsystem", KERNEL=="ccw", RUN{program}+="/bin/sh -c 'echo free 0009,ec30,ec32,f5f0-f5f2 > /proc/cio_ignore'" A proposed fix would be: Modify /usr/share/initramfs-tools/scripts/init-top/udev: Replace line udevadm trigger --action=add with udevadm trigger --type=subsystems --action=add udevadm trigger --type=devices --action=add This would also be consistent with the steps that the systemd udev coldplug unit file performs (see /lib/systemd/system/systemd-udev- trigger.service). [Regression Potential] More udev rules will be now triggered, earlier, during initramfs stage of boot rather than post-pivot-root. However, this is inline with current rootfs behaviour and thus should not regress behaviour - simply some rules will get triggered earlier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1713536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726068] Re: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status
** Tags added: id-59558f621454c20af30afa36 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1726068 Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in software-properties package in Ubuntu: Triaged Bug description: error message on start up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 .proc.sys.kernel.moksbstate_disabled: 0 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Oct 22 12:33:48 2017 DpkgHistoryLog: Start-Date: 2017-10-22 12:31:01 Commandline: aptdaemon role='role-commit-packages' sender=':1.94' Install: linux-image-generic:amd64 (4.4.0.97.102, automatic), libcuda1-387:amd64 (387.12-0ubuntu0~gpu16.04.1, automatic), linux-image-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), linux-image-extra-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), nvidia-prime:amd64 (0.8.2, automatic), libxnvctrl0:amd64 (384.90-0ubuntu0~gpu16.04.1, automatic), lib32gcc1:amd64 (1:6.0.1-0ubuntu1, automatic), libc6-i386:amd64 (2.23-0ubuntu9, automatic), screen-resolution-extra:amd64 (0.17.1, automatic), ocl-icd-libopencl1:amd64 (2.2.8-1, automatic), libjansson4:amd64 (2.7-3, automatic), bbswitch-dkms:amd64 (0.8-3ubuntu1, automatic), linux-generic:amd64 (4.4.0.97.102), nvidia-opencl-icd-387:amd64 (387.12-0ubuntu0~gpu16.04.1, automatic), nvidia-387:amd64 (387.12-0ubuntu0~gpu16.04.1), nvidia-settings:amd64 (384.90-0ubuntu0~gpu16.04.1, automatic) EFITables: Oct 22 12:34:32 crs-Ubuntu kernel: efi: EFI v2.40 by American Megatrends Oct 22 12:34:32 crs-Ubuntu kernel: efi: ESRT=0x77e72f98 ACPI=0x77591000 ACPI 2.0=0x77591000 SMBIOS=0x77e71000 SMBIOS 3.0=0x77e7 Oct 22 12:34:32 crs-Ubuntu kernel: esrt: Reserving ESRT space from 0x77e72f98 to 0x77e72fd0. Oct 22 12:34:32 crs-Ubuntu kernel: Secure boot enabled ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-16 (159 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SecureBoot: 6 0 0 0 1 SourcePackage: shim-signed Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1726068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1714933] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1714933 Title: Xenial: Please roll SRU with upstream fix for networkd to "accept colons in network interface names" Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Zesty: Fix Committed Status in systemd source package in Artful: Fix Released Bug description: [Impact] networkd cannot manage interface names with ':' in them. As used commonly, by convention, by other tools. [Fix] Update networkd validation routines and test-suites to accept network interface names with ':' in it. [Testcase] Create an inteface with ':' in its name and use it anywhere where systemd validates ifname. E.g. Socket BindToDevice definition, nspawn network zone info, Label= in [Address] section in networkd. [Regression Potential] This fix will change validation routines, and thus commands or settings that were previously rejected or ignored will now take effect. Specifically Label= settings in networkd may lead to networking conflicts. The justification for this change is that networkd should really use the sensible ':' ifnames that the user is requesting systemd to use. [Original Bug Reprot] PR: https://github.com/systemd/systemd/pull/5117 issue: https://github.com/systemd/systemd/issues/4057 Before the networkd from 231 was backported, it was possible to use interface alias names that contained a colon, e.g. eth0:1. This is commonly used to make legacy tools like "ifconfig" work, because they *expect* a colon in the interface name. Martin told me to file a bug for this. Merging networkd from 231 lead to a regression where valid configs were not accepted anymore after the backport. Please merge that fix for the regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1714933/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1714933] Re: Xenial: Please roll SRU with upstream fix for networkd to "accept colons in network interface names"
This bug was fixed in the package systemd - 229-4ubuntu20 --- systemd (229-4ubuntu20) xenial; urgency=medium * resolved: recognize DNS names with more than one trailing dot as invalid (LP: #160) * Ignore failures to set Nice priority on services in containers. (LP: #1709536) * networkd: accept `:' in ifnames in systemd/networkd. (LP: #1714933) * initramfs-tools: trigger udevadm add actions with subsystems first. (LP: #1713536) * networkd: Add support to set STP value on a bridge. (LP: #1665088) * networkd: add support for AgeingTImeSec, Priority and DefaultPVID settings. (LP: #1715131) - Drop cherrypick of uint16 config parser, superseeded by above commit. * networkd: add support to set ActiveSlave and PrimarySlave. (LP: #1709135) - networkd: add support to configure ARP, depedency of Primary/ActiveSlave. -- Dimitri John LedkovTue, 05 Sep 2017 14:01:51 +0100 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1714933 Title: Xenial: Please roll SRU with upstream fix for networkd to "accept colons in network interface names" Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Zesty: Fix Committed Status in systemd source package in Artful: Fix Released Bug description: [Impact] networkd cannot manage interface names with ':' in them. As used commonly, by convention, by other tools. [Fix] Update networkd validation routines and test-suites to accept network interface names with ':' in it. [Testcase] Create an inteface with ':' in its name and use it anywhere where systemd validates ifname. E.g. Socket BindToDevice definition, nspawn network zone info, Label= in [Address] section in networkd. [Regression Potential] This fix will change validation routines, and thus commands or settings that were previously rejected or ignored will now take effect. Specifically Label= settings in networkd may lead to networking conflicts. The justification for this change is that networkd should really use the sensible ':' ifnames that the user is requesting systemd to use. [Original Bug Reprot] PR: https://github.com/systemd/systemd/pull/5117 issue: https://github.com/systemd/systemd/issues/4057 Before the networkd from 231 was backported, it was possible to use interface alias names that contained a colon, e.g. eth0:1. This is commonly used to make legacy tools like "ifconfig" work, because they *expect* a colon in the interface name. Martin told me to file a bug for this. Merging networkd from 231 lead to a regression where valid configs were not accepted anymore after the backport. Please merge that fix for the regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1714933/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
Hello, as part of https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1722491 there is currently mdadm update available from xenial-proposed and zesty-proposed that might resolve this issue. To test that solution please perform the following: 1) Install mdadm from xenial-proposed/zesty-proposed - See https://wiki.ubuntu.com/Testing/EnableProposed - Or download & install packages from xenial https://launchpad.net/ubuntu/+source/mdadm/3.4-4ubuntu0.1/+build/13596415 zesty https://launchpad.net/ubuntu/+source/mdadm/3.3-2ubuntu7.5/+build/13596431 2) $ sudo apt install dracut-core 3) $ sudo systemctl enable mdadm-shutdown.service 4) $ sudo systemctl start mdadm-shutdown.service After this the expectation is for shutdown/reboots to perform clean a shutdown, maintaining the raid array in a synced state, such that it comes up clean. Please let me know if above resolves shutdown/reboot issues for you. Regards, Dimitri. -- 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/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." Status in systemd package in Ubuntu: Confirmed Bug description: I'm booting a fully patched 16.04 from an Intel Rapid Storage Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode). If the RAID volume is recovering or resyncing for whatever reason, then `sudo systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to consistently get that). However, once the recovery/resync is complete and clean, the reboot and poweroff commands above hang forever after "Reached target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in the bug #1464917) does not help. [EDIT]Actually, the shutdown also hangs from time to time during a resync. But I've never seen it succeed once the resync is complete.[/EDIT] Then, if the server has been forcibly restarted with the power button, the Intel Matrix Storage Manager indicates a "Normal" status for the RAID1 volume, but Ubuntu then resyncs the volume anyway: [1.223649] md: bind [1.228426] md: bind [1.230030] md: bind [1.230738] md: bind [1.232985] usbcore: registered new interface driver usbhid [1.233494] usbhid: USB HID core driver [1.234022] md: raid1 personality registered for level 1 [1.234876] md/raid1:md126: not clean -- starting background reconstruction [1.234956] input: CHESEN USB Keyboard as /devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5 [1.236273] md/raid1:md126: active with 2 out of 2 mirrors [1.236797] md126: detected capacity change from 0 to 1000202043392 [1.246271] md: md126 switched to read-write mode. [1.246834] md: resync of RAID array md126 [1.247325] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [1.247503] md126: p1 p2 p3 p4 [1.248269] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. [1.248774] md: using 128k window, over a total of 976759940k. Note that the pain of "resync upon every (re)boot" cannot even be a bit relieved thanks to bitmaps because mdadm does not support them for IMSM containers: $ sudo mdadm --grow --bitmap=internal /dev/md126 mdadm: Cannot add bitmaps to sub-arrays yet I also get this in syslog during boot when the individual drives are detected, but this seems to be harmless: May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental /dev/sdb --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental /dev/sda --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed with exit code 1. During a resync, `sudo sh -c 'echo idle > /sys/block/md126/md/sync_action'` actually stops it as expected, but it restarts immediately though nothing seems to have triggered it: May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted. May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of md126. May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126 May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a total of 976759940k. May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126
[Touch-packages] [Bug 1619844] Re: [Xenial] shutdown/reboot hangs at "Reached target Shutdown"
It depends on what sort of raid modes are in place. If you are not using raid (e.g. RAID1) as provided by your motherboard firmware, and only use individual devices, it is best to disable raid settings in the bios and use regular acpi setting. I have to do this for example on latest generation of Dell XPS laptops that use "raid" mode on a single nvme drive with OS support drivers that are not available for linux. Otherwise if you do use RAID controllers with mdadm, e.g. Intel Matrix RAID, DDF, etc. as part of https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1722491 there is currently mdadm update available from xenial-proposed and zesty-proposed that might resolve this issue. To test that solution please perform the following: 1) Install mdadm from xenial-proposed/zesty-proposed - See https://wiki.ubuntu.com/Testing/EnableProposed - Or download & install packages from xenial https://launchpad.net/ubuntu/+source/mdadm/3.4-4ubuntu0.1/+build/13596415 zesty https://launchpad.net/ubuntu/+source/mdadm/3.3-2ubuntu7.5/+build/13596431 2) $ sudo apt install dracut-core 3) $ sudo systemctl enable mdadm-shutdown.service 4) $ sudo systemctl start mdadm-shutdown.service After this the expectation is for shutdown/reboots to perform clean a shutdown, maintaining the raid array in a synced state, such that it comes up clean. Please let me know if above resolves shutdown/reboot issues for you. Regards, Dimitri. -- 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/1619844 Title: [Xenial] shutdown/reboot hangs at "Reached target Shutdown" Status in systemd package in Ubuntu: Confirmed Bug description: I tried getting more information in the debug-shell but I was unsuccessful in doing so. I was able to switch to the debug shell via ctrl+alt+f9 but I couldn't actually type anything in. I could switch back to the stuck shutdown screen via ctrl+alt+f1, and hitting NumLock would turn the light on my keyboard on and off, but I couldn't do anything else. I captured a journal of the stuck reboot. Interestingly, the journal shows a few more lines after "Reached target Shutdown", which is as far as I get on my screen. This system was installed with Xenial 16.04.1 (never been upgraded) and has had this problem since the very first boot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Sep 3 00:33:19 2016 InstallationDate: Installed on 2016-08-17 (16 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=5f709fed-48c9-4830-87be-acd13f263eb1 ro SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/mariadb.service → /etc/systemd/system/mariadb.service.d/migrated-from-my.cnf-settings.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-404:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1619844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582986] Re: NetworkManager service does not start during bootup
This bug should have CRITICAL Importance as other bug 1594715. -- 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/1582986 Title: NetworkManager service does not start during bootup Status in network-manager package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 4.4.0-22 systemd 229-4 network-manager 1.1.93 network-manager-gnome 1.2.0 Multiple services and targets are deleted by systemd to "break ordering cycle" (cf. boot.log), but NetworkManager is the only one of them (network.target,rpcbind,sysinit.target,open-iscsi.service,remote- fs-pre.target,iscsid.service,zfs-fuse.service - cf. their respective logs) which is not started after bootup: sudo systemctl status NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: inactive (dead) May 18 05:00:10 samsung-ubuntu systemd[1]: NetworkManager.service: Job NetworkManager.service/verify-active deleted to break ordering cycle starting with network.target/start Attachments: --- - journalctl -l -b0 --system _COMM=systemd > boot.log - systemctl -l status rpcbind > rpcbind.log - systemctl -l status network.target > network.target.txt - systemctl -l status remote-fs-pre.target > remote-fs-pre.target.log - systemctl -l status sysinit.target > sysinit.target.log - systemctl -l status zfs-fuse.service > zfs-fuse.service.log - systemctl -l status open-iscsi.service > open-iscsi.service.log - systemctl -l status iscsid.service > iscsid.service.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1594715] Re: wifi and/or ethernet does not work roughly half of the times
I purger `whoopsie` package and reinstalled it with `apport-noui` for precise logging at next time. -- 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/1594715 Title: wifi and/or ethernet does not work roughly half of the times Status in network-manager package in Ubuntu: Confirmed Bug description: After booting, roughly half of the times, wifi doesn't work: The nm- applet menu looks as if no wifi would exist. Instead, it lists the a non-existing cable network device called "Marvell 88W8897 [AVASTAR] 802.11ac Wireless". (The network manager seems to be trying to connect to that device, but fails.) After doing /etc/init.d/network-manager restart the wifi device is always recognized properly, so I guess it's something happening in the wrong order during booting. (Alternatively, unloading and reloading the kernel module mwifiex_pcie also always helps.) The problem did not exist in ubuntu 15.10. Some more information: $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 When the bug is there: $ nmcli d show wlp1s0 GENERAL.DEVICE: wlp1s0 GENERAL.TYPE: ethernet GENERAL.HWADDR: 50:1A:C5:E8:2F:09 GENERAL.MTU:1500 GENERAL.STATE: 70 (connecting (getting IP configuration)) GENERAL.CONNECTION: Kabelnetzwerkverbindung 2 GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/7 WIRED-PROPERTIES.CARRIER: on $ ifconfig -a loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:3380 errors:0 dropped:0 overruns:0 frame:0 TX packets:3380 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:251184 (251.1 KB) TX bytes:251184 (251.1 KB) wlp1s0Link encap:Ethernet HWaddr 50:1a:c5:e8:2f:09 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) After restarting the network manager: immi@flunder:~$ nmcli d show wlp1s0 GENERAL.DEVICE: wlp1s0 GENERAL.TYPE: wifi GENERAL.HWADDR: 50:1A:C5:E8:2F:09 GENERAL.MTU:0 GENERAL.STATE: 100 (connected) GENERAL.CONNECTION: virginmedia4709476 GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/8 IP4.ADDRESS[1]: 192.168.0.3/24 IP4.GATEWAY:192.168.0.1 IP4.ROUTE[1]: dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000 IP4.DNS[1]: 194.168.4.100 IP4.DNS[2]: 194.168.8.100 IP6.ADDRESS[1]: fe80::521a:c5ff:fee8:2f09/64 IP6.GATEWAY: (...) wlp1s0Link encap:Ethernet HWaddr 50:1a:c5:e8:2f:09 inet6 addr: fe80::521a:c5ff:fee8:2f09/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:304 (304.0 B) TX bytes:680 (680.0 B) $ dmesg (...) [7.850180] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready [7.850263] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready [7.859773] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready [7.869408] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready (...) I'm happy to try to fix the bug myself, but I could need some help: I don't know how to change booting order or something like that. I could also temporarily insert some commands into /etc/init.d /network-manager printing some status information about the wifi, but I don't know how to get such status information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 21 09:35:14 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-11-19 (579 days ago) InstallationMedia: Ubuntu 14.10
[Touch-packages] [Bug 1488880] Re: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
*** This bug is a duplicate of bug 1594715 *** https://bugs.launchpad.net/bugs/1594715 ** This bug has been marked a duplicate of bug 1594715 wifi and/or ethernet does not work roughly half of the times -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/140 Title: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files Status in whoopsie package in Ubuntu: Confirmed Bug description: Get that error logged into journalctl: NetworkManager[766]: NetworkManager (version 0.9.10.0) is starting... NetworkManager[766]: Read config: /etc/NetworkManager/NetworkManager.conf NetworkManager[766]: WEXT support is enabled whoopsie[769]: [07:02:35] Using lock path: /var/lock/whoopsie/lock whoopsie[769]: [07:02:35] Could not get the Network Manager state: whoopsie[769]: [07:02:35] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files NetworkManager[766]: DNS: loaded plugin dnsmasq NetworkManager[766]: init! sudo systemctl status whoopsie.service ● whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since mer. 2015-08-26 07:02:29 CEST; 4h 17min ago Main PID: 769 (whoopsie) CGroup: /system.slice/whoopsie.service └─769 /usr/bin/whoopsie -f systemd[1]: Started crash report submission daemon. whoopsie[769]: [07:02:35] Using lock path: /var/lock/whoopsie/lock whoopsie[769]: [07:02:35] Could not get the Network Manager state: whoopsie[769]: [07:02:35] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedeskt...e files whoopsie[769]: [07:02:38] offline whoopsie[769]: [07:02:57] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/0 whoopsie[769]: [07:02:57] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/0 whoopsie[769]: [07:02:57] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/0 whoopsie[769]: [07:02:57] online ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: whoopsie 0.2.48 ProcVersionSignature: Ubuntu 4.2.0-6.6-generic 4.2.0-rc8 Uname: Linux 4.2.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.18-0ubuntu7 Architecture: i386 Date: Wed Aug 26 11:29:55 2015 ExecutablePath: /usr/bin/whoopsie RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726333] Re: Mouse Cursor not available under Wayland
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- 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/1726333 Title: Mouse Cursor not available under Wayland Status in gnome-shell package in Ubuntu: New Bug description: Sorry for this being filed under xorg, but I do not get "Wayland" offered. After logging in to Ubuntu 17.10 in Wayland, the mouse cursor flickers shortly and then is gone. In XOrg session all is fine. I had no issues with the cursor in the artful beta release - I was using the beta release of Ubuntu 17.10 7 to 10 days before the final release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Oct 23 11:39:45 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:3801] InstallationDate: Installed on 2017-10-12 (10 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 80VF ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=a5819d75-73ad-458c-8bde-fd93b2f7d230 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2JCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Agera 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 910-13IKB dmi.modalias: dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80VF dmi.product.version: Lenovo YOGA 910-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 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/gnome-shell/+bug/1726333/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later
@Doug, thanks for testing, I've managed to track down a bug in the kernel, I'll try to get a fix merged before 4.14 final, also I have apparmor userspace fixes building in the apparmor ppa and will post those up for further test once they are done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1721278 Title: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later Status in apparmor package in Ubuntu: Confirmed Status in apparmor source package in Xenial: Confirmed Status in apparmor source package in Zesty: Confirmed Status in apparmor source package in Artful: Confirmed Bug description: With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor 2.10.95-0ubuntu2.7, in the system log each second the error message below is printed to. ``` […] [Mi Okt 4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" […] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later
Rocko: thanks for the patch, just so people know this is a work around patch which adjusts policy instead of fixing the bug in the parser. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1721278 Title: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later Status in apparmor package in Ubuntu: Confirmed Status in apparmor source package in Xenial: Confirmed Status in apparmor source package in Zesty: Confirmed Status in apparmor source package in Artful: Confirmed Bug description: With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor 2.10.95-0ubuntu2.7, in the system log each second the error message below is printed to. ``` […] [Mi Okt 4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" […] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1691901] Re: [SRU] 50-motd-news costs 5 seconds every login on firewalled systems
This bug was fixed in the package base-files - 9.6ubuntu13.1 --- base-files (9.6ubuntu13.1) zesty-proposed; urgency=medium * update-motd.d/50-news: Fix LP: #1691901 - when the curl fails (perhaps due to a firewall issue), we should create an empty cache file, so that subsequent runs are not penalized; ensure that we *only* print when we're not forced -- Dustin KirklandThu, 29 Jun 2017 09:22:56 -0500 ** Changed in: base-files (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1691901 Title: [SRU] 50-motd-news costs 5 seconds every login on firewalled systems Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Zesty: Fix Released Status in base-files source package in Artful: Fix Released Bug description: I noticed quite a long time to login to some of my systems via ssh (or scp). Investigating lead me to find out that the '50-motd-news' file (/etc/update-motd.d/50-motd-news) was the primary cost. In line 108 [1] it does something like: curl --connect-timeout "5" --max-time "5" -A "..." -o - https://motd.ubuntu.com The systems I'm seeing this on are in a lab and do not have access to https://motd.ubuntu.com. The way the lab is configured, they just end up timing out. So every scp or ssh connection or other path to trigger update-motd will cost 5 seconds. === SRU === [ IMPACT ] This bug affects Ubuntu 17.04 systems which cannot reach the internet (more specifically, https://motd.ubuntu.com). There is a bug in the implementation of /etc/update-motd.d/50-news whereby the failure of the curl fetch of the motd news causes a 5-second delay. This should not be the case. By design, the motd is fetched in the background, by a systemd timer, and refreshed every ~12 hours, also in the background. On login, the script should just cat the cache file. If the cache file isn't found, then it will try to fetch a new motd. In the firewalled system case, the background fetch failed, AND didn't create an empty file. The fix as attached simply ensures that an empty file is created if the curl fetch fails. This eliminates the login delay and solves the bug. Every 12 hours, the curl will be retried, quietly in the background, so if the curl failure happened for temporary reasons, it'll recover, gracefully, eventually. [ TEST CASE ] You can either test this on a firewalled system. Or, if you can hack an entry in your local /etc/hosts for motd.ubuntu.com for an invalid IP address. Without the fix, you'll experience a 5 second delay on login. With the fix, you'll login immediately. Failure case: $ lxc launch ubuntu:17.04 LP1691901 $ lxc exec LP1691901 bash # ssh-import-id kirkland # echo 192.168.0.0 motd.ubuntu.com >> /etc/hosts # rm -f /var/cache/motd-news # exit $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true real0m5.333s user0m0.016s sys 0m0.000s Apply the fix. $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true real0m0.316s user0m0.008s sys 0m0.008s [ REGRESSION ] This is a simple, safe fix with minimal regression potential: diff -Nru base-files-9.6ubuntu13/update-motd.d/50-motd-news base-files-9.6ubuntu13.2/update-motd.d/50-motd-news --- base-files-9.6ubuntu13/update-motd.d/50-motd-news 2017-02-15 13:54:04.0 -0600 +++ base-files-9.6ubuntu13.2/update-motd.d/50-motd-news 2017-06-29 10:43:05.0 -0500 @@ -51,9 +51,13 @@ # If we're not forcing an update, and we have a cached motd-news file, # then just print it and exit as quickly as possible, for login performance. # Note that systemd should keep this cache file up to date, asynchronously -if [ "$FORCED" != "1" ] && [ -r $CACHE ]; then - echo - safe_print $CACHE +if [ "$FORCED" != "1" ]; then + if [ -r $CACHE ]; then + echo + safe_print $CACHE + else + : > $CACHE + fi exit 0 fi @@ -111,7 +115,9 @@ safe_print "$NEWS" # Try to update the cache safe_print "$NEWS" 2>/dev/null >$CACHE || true - fi + else + : > "$CACHE" + fi done rm -f "$NEWS" "$NEWS.err" exit 0 -- [1] https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: base-files 9.6ubuntu13 ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri May 19
[Touch-packages] [Bug 1725055] Re: pptp vpn cannot be easily connected in gnome network manager and gnome control center
The issue might not be in gnome-control-center but their interface could at least communicate what the error is or that there is an error to the user ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Also affects: gnome-control-center via https://bugzilla.gnome.org/show_bug.cgi?id=789341 Importance: Unknown Status: Unknown -- 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/1725055 Title: pptp vpn cannot be easily connected in gnome network manager and gnome control center Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in network-manager-applet package in Ubuntu: New Bug description: I tried to reactivate a VPN (for PPTP) several times again and again using PPTP, and it is just that it just suddenly turns off every time I try to turn on. There is no process ongoing for PPTP. I tried to use an OpenVPN plugin for VPN, it works depending on the VPN server. I depend on VPN a lot especially on FreeVPN PPTP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 07:48:21 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1725055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709536] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1709536 Title: snapd 2.26.14 on ubuntu-core won't start in containers anymore Status in Snap Layer: New Status in snapd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Artful: Fix Released Bug description: [Impact] Systemd treats a failure to apply the requested Nice value as critical to unit startup. Unprivileged LXD containers do not allow the use of negative nice values. snapd will fail to start inside containers now that snapd uses a negative Nice value. Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, code=exited, status=201/NICE Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state. Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 'exit-code'. The fix is for systemd to ignore permission errors when attempting to setup such custom nice values in containers. I have confirmed that setting up a unit override by hand which sets Nice = 0 does resolve the problem. [Test Case] Boot a Xenial image in lxd: $ lxc launch xenial x1 $ lxc exec x1 -- systemctl --state=failed Observe failures for snapd : ● snapd.service loaded failed failed Snappy daemon ● snapd.socket loaded failed failed Socket activation for snapp Install updated systemd from -proposed and get status: (lxc exec reboot; lxc exec systemctl status) State: running Jobs: 0 queued Failed: 0 units [Regression Potential] Services will now run with a Nice value other than what was specified in the unit if it cannot be changed for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/layer-snap/+bug/1709536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore
This bug was fixed in the package systemd - 229-4ubuntu20 --- systemd (229-4ubuntu20) xenial; urgency=medium * resolved: recognize DNS names with more than one trailing dot as invalid (LP: #160) * Ignore failures to set Nice priority on services in containers. (LP: #1709536) * networkd: accept `:' in ifnames in systemd/networkd. (LP: #1714933) * initramfs-tools: trigger udevadm add actions with subsystems first. (LP: #1713536) * networkd: Add support to set STP value on a bridge. (LP: #1665088) * networkd: add support for AgeingTImeSec, Priority and DefaultPVID settings. (LP: #1715131) - Drop cherrypick of uint16 config parser, superseeded by above commit. * networkd: add support to set ActiveSlave and PrimarySlave. (LP: #1709135) - networkd: add support to configure ARP, depedency of Primary/ActiveSlave. -- Dimitri John LedkovTue, 05 Sep 2017 14:01:51 +0100 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1709536 Title: snapd 2.26.14 on ubuntu-core won't start in containers anymore Status in Snap Layer: New Status in snapd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Artful: Fix Released Bug description: [Impact] Systemd treats a failure to apply the requested Nice value as critical to unit startup. Unprivileged LXD containers do not allow the use of negative nice values. snapd will fail to start inside containers now that snapd uses a negative Nice value. Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, code=exited, status=201/NICE Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state. Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 'exit-code'. The fix is for systemd to ignore permission errors when attempting to setup such custom nice values in containers. I have confirmed that setting up a unit override by hand which sets Nice = 0 does resolve the problem. [Test Case] Boot a Xenial image in lxd: $ lxc launch xenial x1 $ lxc exec x1 -- systemctl --state=failed Observe failures for snapd : ● snapd.service loaded failed failed Snappy daemon ● snapd.socket loaded failed failed Socket activation for snapp Install updated systemd from -proposed and get status: (lxc exec reboot; lxc exec systemctl status) State: running Jobs: 0 queued Failed: 0 units [Regression Potential] Services will now run with a Nice value other than what was specified in the unit if it cannot be changed for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/layer-snap/+bug/1709536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715131] Re: networkd add support for Bridge Priority, AgeingTimeSec and DefaultPVID
This bug was fixed in the package systemd - 229-4ubuntu20 --- systemd (229-4ubuntu20) xenial; urgency=medium * resolved: recognize DNS names with more than one trailing dot as invalid (LP: #160) * Ignore failures to set Nice priority on services in containers. (LP: #1709536) * networkd: accept `:' in ifnames in systemd/networkd. (LP: #1714933) * initramfs-tools: trigger udevadm add actions with subsystems first. (LP: #1713536) * networkd: Add support to set STP value on a bridge. (LP: #1665088) * networkd: add support for AgeingTImeSec, Priority and DefaultPVID settings. (LP: #1715131) - Drop cherrypick of uint16 config parser, superseeded by above commit. * networkd: add support to set ActiveSlave and PrimarySlave. (LP: #1709135) - networkd: add support to configure ARP, depedency of Primary/ActiveSlave. -- Dimitri John LedkovTue, 05 Sep 2017 14:01:51 +0100 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1715131 Title: networkd add support for Bridge Priority, AgeingTimeSec and DefaultPVID Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Bug description: [Impact] Newer releases of networkd support more optional settings for Bridge Priority, AgeingTimeSec and DefaultPVID. https://www.freedesktop.org/software/systemd/man/systemd.netdev.html#AgeingTimeSec= https://www.freedesktop.org/software/systemd/man/systemd.netdev.html#Priority= https://www.freedesktop.org/software/systemd/man/systemd.netdev.html#DefaultPVID= Backporting these features to xenial, allows to use/set these options via netplan for any releases as for example deployed by MAAS. [Fix] cherrypick these settings for better supportability of networkd on xenial with netplan. [Testcase] 1) Create .netdev bridge device 2) Specify Priority, AgeingTimeSec, DefaultPVID settings in the [Bridge] section 3) Verify that there are no parsing errors in journalctl from systemd-netword 4) Verify with `ip` command that the bridge device got created 5) Verify in sysfs that the settings requested have been applied to the device [Regression] These stanazas are optional, and will be ignored by older networkd if for example users start using them, and downgrade networkd to the one in release pocket. It is future compatible settings that will not cause upgrade issues, nor could result in failure to create the bridge device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1715131/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709135] Re: add bond primary parameter
This bug was fixed in the package systemd - 229-4ubuntu20 --- systemd (229-4ubuntu20) xenial; urgency=medium * resolved: recognize DNS names with more than one trailing dot as invalid (LP: #160) * Ignore failures to set Nice priority on services in containers. (LP: #1709536) * networkd: accept `:' in ifnames in systemd/networkd. (LP: #1714933) * initramfs-tools: trigger udevadm add actions with subsystems first. (LP: #1713536) * networkd: Add support to set STP value on a bridge. (LP: #1665088) * networkd: add support for AgeingTImeSec, Priority and DefaultPVID settings. (LP: #1715131) - Drop cherrypick of uint16 config parser, superseeded by above commit. * networkd: add support to set ActiveSlave and PrimarySlave. (LP: #1709135) - networkd: add support to configure ARP, depedency of Primary/ActiveSlave. -- Dimitri John LedkovTue, 05 Sep 2017 14:01:51 +0100 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1709135 Title: add bond primary parameter Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Released Status in nplan source package in Zesty: Fix Committed Status in systemd source package in Zesty: Fix Committed Status in nplan source package in Artful: Fix Released Status in systemd source package in Artful: Fix Released Bug description: [Impact] Some complex bond configurations require setting a "primary" interface for the bond, or setting this greatly improves performance on the network bond. [Test case] See below for a configuration example. 1) Apply configuration on a system with netplan. 2) Run 'netplan apply' 3) Validate that netplan apply does not return with an error 4) Validate that netplan properly sets the "primary_slave" value on the bond. This can be verified by looking at /sys/class/net//bonding/primary_slave. 5) Validate that there are no parsing errors from systemd-networkd in the journalctl [Regression potential] If existing configuration fails to be parsed, or lack of primary interface breaks configuration for existing bonds, this would be a regression caused by this update. --- ifenslave/eni support a bond parameter: bond-primary which accepts an interface name that can be used to tell the kernel bonding driver which interface it should preferred in active-backup (and other modes). This config option is missing in netplan. % cat bond-primary.yaml network: version: 2 ethernets: eth0: match: driver: virtio ens4: match: driver: e1000 bonds: bond0: parameters: mode: active-backup mii-monitor-interval: 100 primary: e1000 dhcp4: true % ./generate -r `pwd`/target Error in network definition /home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 column 8: unknown key primary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1709135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713536] Re: udev: boot script does not trigger subsystem coldplug
This bug was fixed in the package systemd - 229-4ubuntu20 --- systemd (229-4ubuntu20) xenial; urgency=medium * resolved: recognize DNS names with more than one trailing dot as invalid (LP: #160) * Ignore failures to set Nice priority on services in containers. (LP: #1709536) * networkd: accept `:' in ifnames in systemd/networkd. (LP: #1714933) * initramfs-tools: trigger udevadm add actions with subsystems first. (LP: #1713536) * networkd: Add support to set STP value on a bridge. (LP: #1665088) * networkd: add support for AgeingTImeSec, Priority and DefaultPVID settings. (LP: #1715131) - Drop cherrypick of uint16 config parser, superseeded by above commit. * networkd: add support to set ActiveSlave and PrimarySlave. (LP: #1709135) - networkd: add support to configure ARP, depedency of Primary/ActiveSlave. -- Dimitri John LedkovTue, 05 Sep 2017 14:01:51 +0100 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1713536 Title: udev: boot script does not trigger subsystem coldplug Status in Ubuntu on IBM z Systems: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Zesty: Fix Committed Status in systemd source package in Artful: Fix Released Bug description: [Impact] subsystems udev rules are not processed on boot, thus resulting in missing devices on boot / before rootfs is mounted. [Solution] trigger udev subsystems and devices, in the initramfs, in that order. [Testcase] Boot s390x system with chzdev configured devices, and cio_ignore=all kernel command line parameter. The chzdev configured devices should still be discovered on boot. [Original Bug report] The udev initramfs-tools boot script does not trigger subsystem "add" uevents. As a result, udev rules that listen to subsystem "add" events are never activated. This problem exists on at least Ubuntu 16.04 and 17.10. On s390, this results in a boot failure if the kernel is configured to start with an active device black list (kernel parameter cio_ignore=all,!condev). An example for an affected udev rule looks like this: ACTION=="add", SUBSYSTEM=="subsystem", KERNEL=="ccw", RUN{program}+="/bin/sh -c 'echo free 0009,ec30,ec32,f5f0-f5f2 > /proc/cio_ignore'" A proposed fix would be: Modify /usr/share/initramfs-tools/scripts/init-top/udev: Replace line udevadm trigger --action=add with udevadm trigger --type=subsystems --action=add udevadm trigger --type=devices --action=add This would also be consistent with the steps that the systemd udev coldplug unit file performs (see /lib/systemd/system/systemd-udev- trigger.service). [Regression Potential] More udev rules will be now triggered, earlier, during initramfs stage of boot rather than post-pivot-root. However, this is inline with current rootfs behaviour and thus should not regress behaviour - simply some rules will get triggered earlier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1713536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709135] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1709135 Title: add bond primary parameter Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Released Status in nplan source package in Zesty: Fix Committed Status in systemd source package in Zesty: Fix Committed Status in nplan source package in Artful: Fix Released Status in systemd source package in Artful: Fix Released Bug description: [Impact] Some complex bond configurations require setting a "primary" interface for the bond, or setting this greatly improves performance on the network bond. [Test case] See below for a configuration example. 1) Apply configuration on a system with netplan. 2) Run 'netplan apply' 3) Validate that netplan apply does not return with an error 4) Validate that netplan properly sets the "primary_slave" value on the bond. This can be verified by looking at /sys/class/net//bonding/primary_slave. 5) Validate that there are no parsing errors from systemd-networkd in the journalctl [Regression potential] If existing configuration fails to be parsed, or lack of primary interface breaks configuration for existing bonds, this would be a regression caused by this update. --- ifenslave/eni support a bond parameter: bond-primary which accepts an interface name that can be used to tell the kernel bonding driver which interface it should preferred in active-backup (and other modes). This config option is missing in netplan. % cat bond-primary.yaml network: version: 2 ethernets: eth0: match: driver: virtio ens4: match: driver: e1000 bonds: bond0: parameters: mode: active-backup mii-monitor-interval: 100 primary: e1000 dhcp4: true % ./generate -r `pwd`/target Error in network definition /home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 column 8: unknown key primary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1709135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1665088] Re: netplan bridge config doesn't support stp boolean
This bug was fixed in the package systemd - 229-4ubuntu20 --- systemd (229-4ubuntu20) xenial; urgency=medium * resolved: recognize DNS names with more than one trailing dot as invalid (LP: #160) * Ignore failures to set Nice priority on services in containers. (LP: #1709536) * networkd: accept `:' in ifnames in systemd/networkd. (LP: #1714933) * initramfs-tools: trigger udevadm add actions with subsystems first. (LP: #1713536) * networkd: Add support to set STP value on a bridge. (LP: #1665088) * networkd: add support for AgeingTImeSec, Priority and DefaultPVID settings. (LP: #1715131) - Drop cherrypick of uint16 config parser, superseeded by above commit. * networkd: add support to set ActiveSlave and PrimarySlave. (LP: #1709135) - networkd: add support to configure ARP, depedency of Primary/ActiveSlave. -- Dimitri John LedkovTue, 05 Sep 2017 14:01:51 +0100 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1665088 Title: netplan bridge config doesn't support stp boolean Status in netplan: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Released Status in systemd source package in Xenial: Fix Released Status in nplan source package in Yakkety: Fix Released Status in nplan source package in Zesty: Fix Released Status in systemd source package in Zesty: Fix Released Bug description: [Impact] Users of netplan may wish to specify a custom MTU value for a device. [Test case] - Run nplan integration tests on the release - Validate that netplan generate && netplan apply alone, without config, behave as expected (no result) - Validate that netplan generate && netplan apply with minimal config writes /run/NetworkManager/conf.d/10-globally-managed-devices.conf - Validate that netplan generate && netplan apply works with any existing configuation. - Use the config below; ensure behavior is as expected (STP value is set on the interface; adjust device names as appropriate). There should be no errors at applying the requested configuration. - Use the config below with the 'stp' key; the device should be brought up and include the default value set for the kernel. [Regression potential] STP default value should continue to be used for the bridge configured using netplan if STP is unset in configuration. --- networkd supports setting STP value in Bridge type netdevs, but netplan does not accept the key. root@ubuntu:/etc/netplan# apt-cache policy nplan nplan: Installed: 0.18 Candidate: 0.18 Version table: *** 0.18 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:/etc/netplan# lsb_release -rd Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 root@ubuntu:/etc/netplan# cat 52-bridge.yaml network: ethernets: eth0: addresses: - 10.11.12.13/24 match: macaddress: '52:54:00:12:34:00' set-name: foobar0 eth1: match: macaddress: '52:54:00:12:34:02' set-name: eth1 eth2: match: macaddress: '52:54:00:12:34:04' set-name: eth2 bridges: br0: addresses: - 192.168.14.2/24 interfaces: - eth1 - eth2 parameters: ageing-time: 250 priority: 22 forward-delay: 1 hello-time: 1 max-age: 10 path-cost: eth1: 50 eth2: 75 stp: true version: 2 root@ubuntu:/etc/netplan# netplan generate Error in network definition //etc/netplan/52-bridge.yaml line 24 column 16: unknown key stp To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1665088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1600000] Re: libnss-resolve treats two trailing dots on a domain name incorrectly
This bug was fixed in the package systemd - 229-4ubuntu20 --- systemd (229-4ubuntu20) xenial; urgency=medium * resolved: recognize DNS names with more than one trailing dot as invalid (LP: #160) * Ignore failures to set Nice priority on services in containers. (LP: #1709536) * networkd: accept `:' in ifnames in systemd/networkd. (LP: #1714933) * initramfs-tools: trigger udevadm add actions with subsystems first. (LP: #1713536) * networkd: Add support to set STP value on a bridge. (LP: #1665088) * networkd: add support for AgeingTImeSec, Priority and DefaultPVID settings. (LP: #1715131) - Drop cherrypick of uint16 config parser, superseeded by above commit. * networkd: add support to set ActiveSlave and PrimarySlave. (LP: #1709135) - networkd: add support to configure ARP, depedency of Primary/ActiveSlave. -- Dimitri John LedkovTue, 05 Sep 2017 14:01:51 +0100 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/160 Title: libnss-resolve treats two trailing dots on a domain name incorrectly Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Bug description: [Impact] libnss-resolve is an optional component not used by default in xenial. However it treats doubledot incorrectly, meaning it gets resolved when it shouldn't. [Fix] Cherrypick upstream patch to resolve this issue. [Testcase] * Enable resolve nss module * attempt resolving www.gnu.org.. * It should fail to resolve (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org.. 208.118.235.148 STREAM wildebeest.gnu.org 208.118.235.148 DGRAM 208.118.235.148 RAW (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ resolve dns/ dns/' /etc/nsswitch.conf (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org.. (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ dns/ resolve dns/' /etc/nsswitch.conf (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org.. 208.118.235.148 STREAM wildebeest.gnu.org 208.118.235.148 DGRAM 208.118.235.148 RAW (base)adconrad@nosferatu:~$ This is responsible for the new regression in glibc: -- FAIL: posix/tst-getaddrinfo5 original exit status 1 resolving "localhost." worked, proceeding to test resolving "localhost.." failed, test passed resolving "www.gnu.org." worked, proceeding to test resolving "www.gnu.org.." worked, test failed -- [Regression potential] Minimal, since this component is not used by default. However, systems that have this enabled exhibit standards non-compliant behavior. It is not expected for anybody to depend on this broken behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1600000] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/160 Title: libnss-resolve treats two trailing dots on a domain name incorrectly Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Bug description: [Impact] libnss-resolve is an optional component not used by default in xenial. However it treats doubledot incorrectly, meaning it gets resolved when it shouldn't. [Fix] Cherrypick upstream patch to resolve this issue. [Testcase] * Enable resolve nss module * attempt resolving www.gnu.org.. * It should fail to resolve (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org.. 208.118.235.148 STREAM wildebeest.gnu.org 208.118.235.148 DGRAM 208.118.235.148 RAW (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ resolve dns/ dns/' /etc/nsswitch.conf (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org.. (base)adconrad@nosferatu:~$ sudo sed -i -e 's/ dns/ resolve dns/' /etc/nsswitch.conf (base)adconrad@nosferatu:~$ getent ahostsv4 www.gnu.org.. 208.118.235.148 STREAM wildebeest.gnu.org 208.118.235.148 DGRAM 208.118.235.148 RAW (base)adconrad@nosferatu:~$ This is responsible for the new regression in glibc: -- FAIL: posix/tst-getaddrinfo5 original exit status 1 resolving "localhost." worked, proceeding to test resolving "localhost.." failed, test passed resolving "www.gnu.org." worked, proceeding to test resolving "www.gnu.org.." worked, test failed -- [Regression potential] Minimal, since this component is not used by default. However, systems that have this enabled exhibit standards non-compliant behavior. It is not expected for anybody to depend on this broken behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1467173] Re: poweroff or reboot hangs
Can you still reproduce this with 16.04 xenial? Do you use hardware/fakeraid as provided by your motherboard? E.g. Intel Matrix Raid? as part of https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1722491 there is currently mdadm update available from xenial-proposed and zesty-proposed that might resolve this issue. To test that solution please perform the following: 1) Install mdadm from xenial-proposed/zesty-proposed - See https://wiki.ubuntu.com/Testing/EnableProposed - Or download & install packages from xenial https://launchpad.net/ubuntu/+source/mdadm/3.4-4ubuntu0.1/+build/13596415 zesty https://launchpad.net/ubuntu/+source/mdadm/3.3-2ubuntu7.5/+build/13596431 2) $ sudo apt install dracut-core 3) $ sudo systemctl enable mdadm-shutdown.service 4) $ sudo systemctl start mdadm-shutdown.service After this the expectation is for shutdown/reboots to perform clean a shutdown, maintaining the raid array in a synced state, such that it comes up clean. Please let me know if above resolves shutdown/reboot issues for you. Regards, Dimitri. ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete -- 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/1467173 Title: poweroff or reboot hangs Status in systemd package in Ubuntu: Incomplete Bug description: After the upgrade to 15.04, poweroff or reboot hangs, the last message is quotaoff.sh[PID]... done It hangs if executed by clicking from the menu, as well as with the 'poweroff', 'reboot', or 'halt' commands from the terminal. In debug console, in the journalctl -f output, this one error can be seen Failed umounting /tmp and the last messages before the freeze are like Starting Final Step Starting Power-Off Shutting Down I can still switch vt, but cannot type. After some time, kernel writes: info: task systemd-shutdow:1 blocked for more than 120 seconds. ctrl-alt-del does nothing. the only ways to bring server down seem to be alt-sysrq or powerbutton. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 20 22:17:59 2015 InstallationDate: Installed on 2011-09-16 (1373 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/vg00-lv_ubuntu_root ro SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-06-19 (1 days ago) dmi.bios.date: 02/23/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2102:bd02/23/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1467173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726377] Re: evolution-addressbook-factory-subprocess crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
*** This bug is a duplicate of bug 1724277 *** https://bugs.launchpad.net/bugs/1724277 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1724277, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726377/+attachment/4987876/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726377/+attachment/4987878/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726377/+attachment/4987881/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726377/+attachment/4987882/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726377/+attachment/4987883/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726377/+attachment/4987884/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726377/+attachment/4987885/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1724277 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1726377 Title: evolution-addressbook-factory-subprocess crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() Status in evolution-data-server package in Ubuntu: New Bug description: crash when I started my computer ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: evolution-data-server 3.26.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Oct 23 14:26:25 2017 ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory-subprocess ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory-subprocess --factory google --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx13737x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/13737/2 ProcEnviron: LANG=fr_FR.UTF-8 LANGUAGE=fr:en PATH=(custom, user) SHELL=/bin/zsh XDG_RUNTIME_DIR= Signal: 6 SourcePackage: evolution-data-server StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: evolution-addressbook-factory-subprocess crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) UserGroups: adm cdrom dialout dip docker libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1726377/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726395] [NEW] gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell DE
Public bug reported: gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell Desktop Environment. It's 5 years old software (latest release 2012-10-16) and is needed only for old GNOME flashback (fallback) session. Gnome-screensaver shouldn't be running on GNOME Shell - users can't unlock the screen because of important bugs in gnome-screensaver, see bug #1716278 and bug #1699670 (Gnome screensaver lock always responses "incorrect password" when last active window's language is not the language of the password) for example. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1726395 Title: gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell DE Status in ubuntu-meta package in Ubuntu: New Bug description: gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell Desktop Environment. It's 5 years old software (latest release 2012-10-16) and is needed only for old GNOME flashback (fallback) session. Gnome-screensaver shouldn't be running on GNOME Shell - users can't unlock the screen because of important bugs in gnome-screensaver, see bug #1716278 and bug #1699670 (Gnome screensaver lock always responses "incorrect password" when last active window's language is not the language of the password) for example. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1726395/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp