[Touch-packages] [Bug 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name
** Changed in: oem-priority Importance: Critical => 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/1647283 Title: WiFi being detected as ethernet when race condition on renaming for persistent name Status in HWE Next: Fix Released Status in NetworkManager: Fix Released Status in OEM Priority Project: In Progress Status in OEM Priority Project xenial series: In Progress Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: New Bug description: [Impact] * It is a very bad user experience that the WiFi device is recognized as an Ethernet device making Ubuntu users unable to connect to WiFi network. [Test Case] * Find some laptop that can reduplicate this issue. * Keep rebooting the system until you see this issue. * Usually this issue can be reduplicated within 10 reboot cycles on the right laptop. [Regression Potential] * No trivial regression. [Other Info] * network-manager_1.2.6-0ubuntu0.16.04.2.debdiff (comment #8) is for xenial [Original Bug Description] Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613 Version: NetworkManager 1.4.2 This bug happens after power-on with probability about 1/50. That means we need to reboot about 50 times to get into the buggy situation. "nmcli d" shows the device type is ethernet: DEVICE TYPE STATECONNECTION wlp1s0 ethernet unavailable -- lo loopback unmanaged-- The bug starts from a race condition. But it is not the root cause. I've also attach 2 logs. One is in good situation. Another is in bad situation. This log is generated by applying a "log patch" to network-manager 1.4.2 so we can see more stuff. In the bad situation. The bug starts with race condition. But the race condition is not the root cause. The race condition is: * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared. * Inside the NM, it is still using "wlan0" in "_linktype_get_type()". * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching failed in _linktype_get_type(). * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 disappeared. * And finally, devtype and kind are both NULL, so it returns NM_LINK_TYPE_ETHERNET for wlan0. Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit the type so it is still type ethernet. But from the log, I saw _linktype_get_type() is called several times later and return the correct type (wifi). But just, "nmcli d" still shows type ethernet. I'm wondering if we are missing to update the type in the Object created after renaming and re-detecting the type. fix need landing LP: #1645698 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1647283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1702794] Re: Automatically switch audio devices on connection
It sounds like we might be able to drop module-switch-on-connect in future, as PulseAudio 11.0 solves the same problem by default: https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/ -- 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/1702794 Title: Automatically switch audio devices on connection Status in pulseaudio package in Ubuntu: Fix Released Bug description: This way once a user pairs & connects a bluetooth speaker device pulseaudio will auto switch to it. As it stands now users have to open sound settings & switch manually. It's bad enough that auto discover & connect don't work, (can be scripted thru bluetoothctl), no sense adding to frustration In the ### Automatically load driver modules for Bluetooth hardware section .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.3 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doug 1843 F pulseaudio /dev/snd/controlC0: doug 1843 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 6 20:02:15 2017 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2017-07-04T13:42:27.651527 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1702794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1702606] Re: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: пакет iproute2 не готов к настройке настройка невозможна (текущее состояние: «half-installed»)
[Expired for iproute2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: iproute2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1702606 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: пакет iproute2 не готов к настройке настройка невозможна (текущее состояние: «half-installed») Status in iproute2 package in Ubuntu: Expired Bug description: 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Jul 5 08:04:21 2017 ErrorMessage: пакет iproute2 не готов к настройке настройка невозможна (текущее состояние: «half-installed») InstallationDate: Installed on 2017-07-03 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: пакет iproute2 не готов к настройке настройка невозможна (текущее состояние: «half-installed») UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1702606/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715235] Re: failed to install/upgrade: package coreutils is not ready for configuration cannot configure (current status 'half-installed')
** Summary changed: - package coreutils 8.25-2ubuntu2 [modified: bin/cat bin/chgrp bin/chmod bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false bin/ln bin/ls bin/mkdir bin/mknod bin/mktemp bin/mv bin/pwd bin/readlink bin/rm bin/rmdir bin/sleep bin/stty bin/sync bin/touch bin/true bin/uname bin/vdir usr/bin/[ usr/bin/base64 usr/bin/basename usr/bin/chcon usr/bin/dircolors usr/bin/factor usr/bin/hostid usr/bin/id usr/bin/join usr/bin/link usr/bin/logname usr/bin/md5sum usr/bin/nice usr/bin/nl usr/bin/nohup usr/bin/od usr/bin/pathchk usr/bin/pinky usr/bin/printenv usr/bin/printf usr/bin/seq usr/bin/sha1sum usr/bin/sha384sum usr/bin/shuf usr/bin/stat usr/bin/stdbuf usr/bin/tac usr/bin/tail usr/bin/tee usr/bin/test usr/bin/tr usr/bin/tsort usr/bin/tty usr/bin/unexpand usr/bin/uniq usr/bin/unlink usr/bin/yes usr/lib/x86_64-linux-gnu/coreutils/libstdbuf.so usr/sbin/chroot usr/share/doc/coreutils/changelog.Debian.gz usr/share/man/man1/arch.1.gz usr/share/man/man1/base32.1.gz usr/share/man/man1/b ase64.1.gz usr/share/man/man1/basename.1.gz usr/share/man/man1/cat.1.gz usr/share/man/man1/chcon.1.gz usr/share/man/man1/chgrp.1.gz usr/share/man/man1/chmod.1.gz usr/share/man/man1/chown.1.gz usr/share/man/man1/cksum.1.gz usr/share/man/man1/comm.1.gz usr/share/man/man1/cp.1.gz usr/share/man/man1/csplit.1.gz usr/share/man/man1/cut.1.gz usr/share/man/man1/date.1.gz usr/share/man/man1/dd.1.gz usr/share/man/man1/df.1.gz usr/share/man/man1/dir.1.gz usr/share/man/man1/dircolors.1.gz usr/share/man/man1/dirname.1.gz usr/share/man/man1/du.1.gz usr/share/man/man1/echo.1.gz usr/share/man/man1/env.1.gz usr/share/man/man1/expand.1.gz usr/share/man/man1/expr.1.gz usr/share/man/man1/factor.1.gz usr/share/man/man1/false.1.gz usr/share/man/man1/fmt.1.gz usr/share/man/man1/fold.1.gz usr/share/man/man1/groups.1.gz usr/share/man/man1/head.1.gz usr/share/man/man1/hostid.1.gz usr/share/man/man1/id.1.gz usr/share/man/man1/install.1.gz usr/share/man/man1/join.1.gz usr/share/man/man1/link.1.gz usr/share/man /man1/ln.1.gz usr/share/man/man1/logname.1.gz usr/share/man/man1/ls.1.gz usr/share/man/man1/md5sum.1.gz usr/share/man/man1/mkdir.1.gz usr/share/man/man1/mkfifo.1.gz usr/share/man/man1/mknod.1.gz usr/share/man/man1/mktemp.1.gz usr/share/man/man1/mv.1.gz usr/share/man/man1/nice.1.gz usr/share/man/man1/nl.1.gz usr/share/man/man1/nohup.1.gz usr/share/man/man1/nproc.1.gz usr/share/man/man1/numfmt.1.gz usr/share/man/man1/od.1.gz usr/share/man/man1/paste.1.gz usr/share/man/man1/pathchk.1.gz usr/share/man/man1/pinky.1.gz usr/share/man/man1/pr.1.gz usr/share/man/man1/printenv.1.gz usr/share/man/man1/printf.1.gz usr/share/man/man1/ptx.1.gz usr/share/man/man1/pwd.1.gz usr/share/man/man1/readlink.1.gz usr/share/man/man1/realpath.1.gz usr/share/man/man1/rm.1.gz usr/share/man/man1/rmdir.1.gz usr/share/man/man1/runcon.1.gz usr/share/man/man1/seq.1.gz usr/share/man/man1/sha1sum.1.gz usr/share/man/man1/sha224sum.1.gz usr/share/man/man1/sha256sum.1.gz usr/share/man/man1/sha384sum.1.gz usr/share/man/m an1/sha512sum.1.gz usr/share/man/man1/shred.1.gz usr/share/man/man1/shuf.1.gz usr/share/man/man1/sleep.1.gz usr/share/man/man1/sort.1.gz usr/share/man/man1/split.1.gz usr/share/man/man1/stat.1.gz usr/share/man/man1/stdbuf.1.gz usr/share/man/man1/stty.1.gz usr/share/man/man1/sum.1.gz usr/share/man/man1/sync.1.gz usr/share/man/man1/tac.1.gz usr/share/man/man1/tail.1.gz usr/share/man/man1/tee.1.gz usr/share/man/man1/test.1.gz usr/share/man/man1/timeout.1.gz usr/share/man/man1/touch.1.gz usr/share/man/man1/tr.1.gz usr/share/man/man1/true.1.gz usr/share/man/man1/truncate.1.gz usr/share/man/man1/tsort.1.gz usr/share/man/man1/tty.1.gz usr/share/man/man1/uname.1.gz usr/share/man/man1/unexpand.1.gz usr/share/man/man1/uniq.1.gz usr/share/man/man1/unlink.1.gz usr/share/man/man1/users.1.gz usr/share/man/man1/vdir.1.gz usr/share/man/man1/wc.1.gz usr/share/man/man1/who.1.gz usr/share/man/man1/whoami.1.gz usr/share/man/man1/yes.1.gz usr/share/man/man8/chroot.8.gz] failed to install/upgrade: packag e coreutils is not ready for configuration cannot configure (current status 'half-installed') + failed to install/upgrade: package coreutils is not ready for configuration cannot configure (current status 'half-installed') -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1715235 Title: failed to install/upgrade: package coreutils is not ready for configuration cannot configure (current status 'half-installed') Status in coreutils package in Ubuntu: New Bug description: Update OS or software impossible. Starts but never finished. Impossible to remove some apps. Problem with installing also occured. ProblemType: Package DistroRelease: Ubuntu 16.04 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion:
[Touch-packages] [Bug 1676912] Re: Kernel 4.9+ regression: Suspend - Freezing of tasks failed
I have the same issue on an MSI GS70 running kernel 4.10.0-33. BUT I found a pretty easy workaround: If I turn off wifi in NetworkManager, not only does it always suspend successfully, it suspends very quickly. Thought maybe this would be helpful for others. -- 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/1676912 Title: Kernel 4.9+ regression: Suspend - Freezing of tasks failed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu Gnome 17.04 and since then sometimes my Laptop won't suspend when I close the lid. The power led does not blink like it is supposed to do and when I open the Laptop the lockscreen appears but freezes after a short time, followed by a blackscreen until eventually it reappears and allows me to unlock it. After that certain application can not be started anymore and would freeze if they were running before. These include Chrome, Gedit and Gnome System Monitor for example. Also my Laptop will not connect to my WLAN until I restart it. In syslog I found the line: "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to freeze, wq_busy=0):" According to syslog network-nanaeger whoopsie cups-browsed wpa-supplicant geoclue packagekitd several evolution-related processes goa-daemon gnome-software geary dropbox deja-dup-monitor are responsible. I tried disabling some of them, but it did not solve the problem. Update: I tested different Kernel versions in the last days. So far there were no issues with suspend/resume using Kernel 4.8 and 4.9. The problem is present in 4.10 and 4.11. Update 2: I just encountered this issue with Kernel 4.9. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 28 16:27:34 2017 InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 80J8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B8CN31WW(V2.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paganini dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 3 11 dmi.modalias: dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311: dmi.product.name: 80J8 dmi.product.version: Lenovo Yoga 3 11 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682934] Proposed package upload rejected
An upload of python3.5 to xenial-proposed has been rejected from the upload queue for the following reason: "Bug# 1682934 is missing SRU testcase/impact/regresison potential; all bugs are missing a Zesty upload which is requried before we could release the Xenial update.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1682934 Title: python3 in /usr/local/bin can cause python3 packages to fail to install Status in python2.7 package in Ubuntu: Confirmed Status in python3.5 package in Ubuntu: Fix Released Status in python2.7 source package in Xenial: New Status in python3.5 source package in Xenial: New Status in python2.7 source package in Zesty: New Status in python3.5 source package in Zesty: New Bug description: Got this error while using "Transmageddon Video Transcoder" and again while updating 16.10 to 17.04. Seems to have something to do with needing that Python3 version for Teletext decoding in media that is in transport stream format (.ts). ProblemType: Package DistroRelease: Ubuntu 17.04 Package: python3 3.5.1-4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri Apr 14 19:27:33 2017 ErrorMessage: pre-dependency problem - not installing python3 InstallationDate: Installed on 2015-05-01 (714 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: python3-defaults Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3 UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1682934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1691848] Proposed package upload rejected
An upload of python3.5 to xenial-proposed has been rejected from the upload queue for the following reason: "Bug# 1682934 is missing SRU testcase/impact/regresison potential; all bugs are missing a Zesty upload which is requried before we could release the Xenial update.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1691848 Title: Python not compiled with -fexceptions in ppc64le Status in python2.7 package in Ubuntu: New Status in python3.6 package in Ubuntu: Fix Released Bug description: Pytorch (https://github.com/pytorch/pytorch) is an application that is written in python, C and C++. There's high interoperalibity between code written in these languages therex. The issue is that there are cases when an exception is thrown by C++ code that subsequentely calls some C code before being caught. In ppc64le builds, without the -fexceptions gcc flag, such exceptions are not caught when the execution returns to C++ code from C code. This makes some Pytorch tests fail. Compiling CPython with -fexceptions seems to solve this issue. This was also reported to Debian: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=862925 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: python2.7 2.7.13-2 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic ppc64le .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform' ApportVersion: 2.20.4-0ubuntu4 Architecture: ppc64el Date: Thu May 18 15:35:54 2017 InstallationDate: Installed on 2015-11-05 (560 days ago) InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release ppc64el (20150422) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcLoadAvg: 0.07 0.33 0.43 1/348 20166 ProcSwaps: Filename TypeSizeUsed Priority ProcVersion: Linux version 4.10.0-19-generic (buildd@bos01-ppc64el-009) (gcc version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1) ) #21-Ubuntu SMP Thu Apr 6 17:03:05 UTC 2017 SourcePackage: python2.7 UpgradeStatus: Upgraded to zesty on 2017-04-17 (30 days ago) cpu_cores: Number of cores present = 2 cpu_coreson: Number of cores online = 2 cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1691848/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715278] [NEW] [FFe] LXC 2.1
Public bug reported: LXC upstream just released LXC 2.1. This was meant to happen right before the Ubuntu feature freeze but we ran a bit late due to last minute bugfixes and cleanups. LXC 2.1 is generally backward compatible all the way down to LXC 1.0 and higher, including at the ABI level (new symbols got added but none were changed or removed since LXC 1.0). So getting LXC 2.1 in Ubuntu 17.04 wouldn't require any porting or changes to any downstream software in the archive. This release is meant as a transitional release between the 2.0 and 3.0 series of LXC. A great number of configuration options were changed and a number of tools and commands have now been marked as deprecated. But all this without actually removing any of those, instead LXC 2.1 is issuing warnings and providing tooling to automatically convert the needed configuration files. This will give some time for our users to notice anything that needs updating and get it done before they upgrade to LXC 3.0 and things will stop working until they do those changes then. Detailed on the LXC 2.1 release are here: https://discuss.linuxcontainers.org/t/lxc-2-1-has-been-released/487 We have packages ready to upload to artful and that have been used during development in our various PPAs. We therefore don't expect any significant issues with this hitting the Ubuntu archive. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1715278 Title: [FFe] LXC 2.1 Status in lxc package in Ubuntu: New Bug description: LXC upstream just released LXC 2.1. This was meant to happen right before the Ubuntu feature freeze but we ran a bit late due to last minute bugfixes and cleanups. LXC 2.1 is generally backward compatible all the way down to LXC 1.0 and higher, including at the ABI level (new symbols got added but none were changed or removed since LXC 1.0). So getting LXC 2.1 in Ubuntu 17.04 wouldn't require any porting or changes to any downstream software in the archive. This release is meant as a transitional release between the 2.0 and 3.0 series of LXC. A great number of configuration options were changed and a number of tools and commands have now been marked as deprecated. But all this without actually removing any of those, instead LXC 2.1 is issuing warnings and providing tooling to automatically convert the needed configuration files. This will give some time for our users to notice anything that needs updating and get it done before they upgrade to LXC 3.0 and things will stop working until they do those changes then. Detailed on the LXC 2.1 release are here: https://discuss.linuxcontainers.org/t/lxc-2-1-has-been-released/487 We have packages ready to upload to artful and that have been used during development in our various PPAs. We therefore don't expect any significant issues with this hitting the Ubuntu archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1715278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704508] Re: add-apt-repository traceback when hitting ctrl-c
** Changed in: software-properties (Ubuntu) Status: Confirmed => Triaged ** Changed in: software-properties (Ubuntu) Importance: Undecided => Medium -- 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/1704508 Title: add-apt-repository traceback when hitting ctrl-c Status in software-properties package in Ubuntu: Triaged Bug description: add-apt-repository says to hit ctrl-c to cancel adding a PPA. Then it tracebacks when you do: ubuntu@bysen:~$ sudo add-apt-repository ppa:maas/next This PPA holds new upstream development releases, usually development releases. Currently, it is holding the 2.2 series. More info: https://launchpad.net/~maas/+archive/ubuntu/next Press [ENTER] to continue or ctrl-c to cancel adding it ^CTraceback (most recent call last): File "/usr/bin/add-apt-repository", line 143, in sys.stdin.readline() KeyboardInterrupt I understand why the trace is generated, but this is ugly (users should never see tracebacks for known conditions, IMO). The KeyboardInterrupt exception should be handled properly like any other exception. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: software-properties-common 0.96.20.7 ProcVersionSignature: User Name 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.9 Architecture: amd64 Date: Fri Jul 14 23:17:57 2017 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1704508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699216] Re: Encrypted home support
tsimonq2, I have subscribed ubuntu-release. We have modifications in our PPA that utilize this patch to accountsservice. If the patch to accountsservice is not merged in Ubuntu's version, our version will be overridden when there is another accountsservice release. Since this is a feature that is desired in Ubuntu, I think it would be best to allow for the patch to accountsservice to be merged in for use by others, regardless of the patches to gnome-control-center or gnome- initial-setup. At the moment, we have a safely forked version of these packages that cannot be overridden. The issue with accountservice, is that it cannot be forked, renamed, and then use a Provides Conflicts Replaces. This leaves us in a dangerous place where we may have to revert our changes to add encrypted home to gnome-control-center and gnome-initial-setup. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699216] Re: Encrypted home support
@Jeremy: If you get a Feature Freeze Exception as defined here[1] or an ack from a member of the release team, I'll be happy to get it uploaded for you. I want to upload your patches, I just don't want to break freeze and have to apologize to the release team... sorry. :/ [1] https://wiki.ubuntu.com/FreezeExceptionProcess -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1699216 Title: Encrypted home support Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: In the CreateUser D-bus call, allow the home directory of the new user to be encrypted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715242] Re: avahi-daemon crashed with SIGABRT in avahi_malloc(). https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1679117
*** This bug is a duplicate of bug 1668218 *** https://bugs.launchpad.net/bugs/1668218 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 #1668218, 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/1715242/+attachment/4944985/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1715242/+attachment/4944987/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1715242/+attachment/4944990/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1715242/+attachment/4944991/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1715242/+attachment/4944992/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1715242/+attachment/4944993/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1715242/+attachment/4944994/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1668218 ** 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 avahi in Ubuntu. https://bugs.launchpad.net/bugs/1715242 Title: avahi-daemon crashed with SIGABRT in avahi_malloc(). https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1679117 Status in avahi package in Ubuntu: New Bug description: Seems like this bug has already been reported. I just updated to xubuntu 17.10 and still get this bug. Existing bug report: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1679117 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Tue Sep 5 13:51:24 2017 ExecutablePath: /usr/sbin/avahi-daemon InstallationDate: Installed on 2017-04-21 (137 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: avahi-daemon:\ running\ [hostname.local] ProcEnviron: Signal: 6 SourcePackage: avahi StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 avahi_malloc () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 avahi_time_event_new () from /usr/lib/x86_64-linux-gnu/libavahi-core.so.7 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-core.so.7 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-core.so.7 Title: avahi-daemon crashed with SIGABRT in avahi_malloc() UpgradeStatus: Upgraded to artful on 2017-09-05 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1715242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715235] [NEW] package coreutils 8.25-2ubuntu2 [modified: bin/cat bin/chgrp bin/chmod bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false bin/ln bin/ls bin/mkdir b
Public bug reported: Update OS or software impossible. Starts but never finished. Impossible to remove some apps. Problem with installing also occured. ProblemType: Package DistroRelease: Ubuntu 16.04 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: coreutils: Configure vokoscreen: Remove NULL: ConfigurePending Architecture: amd64 Date: Mon Sep 4 21:31:36 2017 DpkgTerminalLog: dpkg: error processing package coreutils (--configure): package coreutils is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package coreutils is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-01-12 (236 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1715235 Title: package coreutils 8.25-2ubuntu2 [modified: bin/cat bin/chgrp bin/chmod bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false bin/ln bin/ls bin/mkdir bin/mknod bin/mktemp bin/mv bin/pwd bin/readlink bin/rm bin/rmdir bin/sleep bin/stty bin/sync bin/touch bin/true bin/uname bin/vdir usr/bin/[ usr/bin/base64 usr/bin/basename usr/bin/chcon usr/bin/dircolors usr/bin/factor usr/bin/hostid usr/bin/id usr/bin/join usr/bin/link usr/bin/logname usr/bin/md5sum usr/bin/nice usr/bin/nl usr/bin/nohup usr/bin/od usr/bin/pathchk usr/bin/pinky usr/bin/printenv usr/bin/printf usr/bin/seq usr/bin/sha1sum usr/bin/sha384sum usr/bin/shuf usr/bin/stat usr/bin/stdbuf usr/bin/tac usr/bin/tail usr/bin/tee usr/bin/test usr/bin/tr usr/bin/tsort usr/bin/tty usr/bin/unexpand usr/bin/uniq usr/bin/unlink usr/bin/yes usr/lib/x86_64-linux- gnu/coreutils/libstdbuf.so usr/sbin/chroot usr/share/doc/coreutils/changelog.Debian.gz usr/share/man/man1/arch.1.gz usr/share/man/man1/base32.1.gz usr/share/man/man1/base64.1.gz usr/share/man/man1/basename.1.gz usr/share/man/man1/cat.1.gz usr/share/man/man1/chcon.1.gz usr/share/man/man1/chgrp.1.gz usr/share/man/man1/chmod.1.gz usr/share/man/man1/chown.1.gz usr/share/man/man1/cksum.1.gz usr/share/man/man1/comm.1.gz usr/share/man/man1/cp.1.gz usr/share/man/man1/csplit.1.gz usr/share/man/man1/cut.1.gz usr/share/man/man1/date.1.gz usr/share/man/man1/dd.1.gz usr/share/man/man1/df.1.gz usr/share/man/man1/dir.1.gz usr/share/man/man1/dircolors.1.gz usr/share/man/man1/dirname.1.gz usr/share/man/man1/du.1.gz usr/share/man/man1/echo.1.gz usr/share/man/man1/env.1.gz usr/share/man/man1/expand.1.gz usr/share/man/man1/expr.1.gz usr/share/man/man1/factor.1.gz usr/share/man/man1/false.1.gz usr/share/man/man1/fmt.1.gz usr/share/man/man1/fold.1.gz usr/share/man/man1/groups.1.gz usr/share/man/man1/head.1.gz usr/share/man/man1/hostid.1.gz usr/share/man/man1/id.1.gz usr/share/man/man1/install.1.gz usr/share/man/man1/join.1.gz usr/share/man/man1/link.1.gz usr/share/man/man1/ln.1.gz usr/share/man/man1/logname.1.gz usr/share/man/man1/ls.1.gz usr/share/man/man1/md5sum.1.gz usr/share/man/man1/mkdir.1.gz usr/share/man/man1/mkfifo.1.gz usr/share/man/man1/mknod.1.gz usr/share/man/man1/mktemp.1.gz usr/share/man/man1/mv.1.gz usr/share/man/man1/nice.1.gz usr/share/man/man1/nl.1.gz usr/share/man/man1/nohup.1.gz usr/share/man/man1/nproc.1.gz usr/share/man/man1/numfmt.1.gz usr/share/man/man1/od.1.gz usr/share/man/man1/paste.1.gz usr/share/man/man1/pathchk.1.gz usr/share/man/man1/pinky.1.gz usr/share/man/man1/pr.1.gz usr/share/man/man1/printenv.1.gz usr/share/man/man1/printf.1.gz usr/share/man/man1/ptx.1.gz usr/share/man/man1/pwd.1.gz usr/share/man/man1/readlink.1.gz usr/share/man/man1/realpath.1.gz usr/share/man/man1/rm.1.gz usr/share/man/man1/rmdir.1.gz usr/share/man/man1/runcon.1.gz usr/share/man/man1/seq.1.gz usr/share/man/man1/sha1sum.1.gz usr/share/man/man1/sha224sum.1.gz usr/share/man/man1/sha256sum.1.gz usr/share/man/man1/sha384sum.1.gz usr/share/man/man1/sha512sum.1.gz usr/share/man/man1/shred.1.gz usr/share/man/man1/shuf.1.gz usr/share/man/man1/sleep.1.gz usr/share/man/man1/sort.1.gz usr/share/man/man1/split.1.gz usr/share/man/man1/stat.1.gz usr/share/man/man1/stdbuf.1.gz usr/share/man/man1/stty.1.gz usr/share/man/man1/sum.1.gz usr/share/man/man1/sync.1.gz usr/share/man/man1/tac.1.gz usr/share/man/man1/tail.1.gz usr/share/man/man1/tee.1.gz usr/share/man/man1/test.1.gz usr/share/man/man1/timeout.1.gz usr/share/man/man1/touch.1.gz usr/share/man/man1/tr.1.gz
[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record
This has been happening to me lately. I am using 17.04. I have a feeling it might be IPv6 related since we just started using that at work, so it's only affecting me there. Usually I see the following in my syslog: > Sep 5 15:40:46 laptop avahi-daemon[1158]: Withdrawing address record for > 1234:5678:4556::99 on eth0. > Sep 5 15:40:46 laptop avahi-daemon[1158]: Leaving mDNS multicast group on > interface eth0.IPv6 with address 1234:5678:4556::99. -- 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/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713161] Re: package libpam-systemd:amd64 234-2ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Дима, уже поздно, я сделал apt upgrade. А ошибка была после установки gnome-desktop -- 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/1713161 Title: package libpam-systemd:amd64 234-2ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: Incomplete Bug description: i don't know ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libpam-systemd:amd64 234-2ubuntu9 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 Date: Fri Aug 25 21:13:13 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-07-18 (38 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 3.6.1-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 2.7.13-2 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5~rc1~ubuntu1 SourcePackage: systemd Title: package libpam-systemd:amd64 234-2ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to artful on 2017-08-21 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713161/+subscriptions -- Mailing list: https://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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
On my Mint (18.2 and I think I did it on 18.3 too - both Cinnamon) the network-manager downgrade sufficed; I did not need to adjust resolvconf. However, I don't think I was using a 'PPTP tunnel'. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713161] Re: package libpam-systemd:amd64 234-2ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Sorry, i made typpo. I meant: $ sudo dpkg --configure -a -- 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/1713161 Title: package libpam-systemd:amd64 234-2ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: Incomplete Bug description: i don't know ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libpam-systemd:amd64 234-2ubuntu9 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 Date: Fri Aug 25 21:13:13 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-07-18 (38 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 3.6.1-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 2.7.13-2 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5~rc1~ubuntu1 SourcePackage: systemd Title: package libpam-systemd:amd64 234-2ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to artful on 2017-08-21 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
Just an FYI, I have to downgrade both network-manager=1.2.2-0ubuntu0.16.04.4 and resolvconf=1.78ubuntu2. Doing one or the other would not fix the problem on my system (Linux Mint Mate 18.1). I'm using a PPTP tunnel. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
Just downgrade network-manager to 1.2.2-0ubuntu0.16.04.4 until the issue is resolved. Pretty simple. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
@lukas-d: I understand, but perhaps you are thinking that I work for Canonical or that I have the skill to contribute to the network-manager project. Neither of those things are true. I am a frustrated user (with fairly low programming ability). It seems to me that switching to a distribution that is not Ubuntu and is not based on Ubuntu might be an idea, in your circumstances. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696686] Re: ld: Relocation truncated to fit: R_ARM_THM_JUMP24 for relocation to PLT entry
the binutils change is limited to arm32 only. so you have to look for other things causing these "regressions". the linux/armhf failure seems to be unrelated, packaging error? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1696686 Title: ld: Relocation truncated to fit: R_ARM_THM_JUMP24 for relocation to PLT entry Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Xenial: Fix Committed Bug description: SRU acceptance criteria: - the package builds - the newly added tests pass, no regressions to previous builds - needs only testing on armhf, no other changes. Original bug report: When linking large applications, we sometimes see this error. This is affecting the LLVM ARM buildbots. The issue was fixed upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=20608 Could you please backport it to Xenial? I have applied the patch on top of binutils_2.26.1.orig.tar.gz + binutils_2.26.1-1ubuntu1~16.04.3.diff.gz as found here: https://packages.ubuntu.com/xenial-updates/binutils-arm-linux-gnueabihf It applies cleanly (except the ChangeLog) and passes make check. To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1696686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
Pushed MPs for review now. @Paul - if you could test the ppas for your cases in advance as well, that would be great. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: Confirmed Status in ntp source package in Xenial: Confirmed Status in ntp source package in Zesty: Fix Released Status in ntp source package in Artful: Confirmed Status in ntp package in Debian: Fix Released Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/ntp/+git/ntp/+merge/330223 ** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/ntp/+git/ntp/+merge/330224 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: Confirmed Status in ntp source package in Xenial: Confirmed Status in ntp source package in Zesty: Fix Released Status in ntp source package in Artful: Confirmed Status in ntp package in Debian: Fix Released Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
Changed my fix and tests are good now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: Confirmed Status in ntp source package in Xenial: Confirmed Status in ntp source package in Zesty: Fix Released Status in ntp source package in Artful: Confirmed Status in ntp package in Debian: Fix Released Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696981] Re: fixrtc is ineffective when there is no battery for the RTC
@smb the concrete problem this was solving was happening with an armhf device running Ubuntu Core. UC assertions were not validated and a system user could not be created if there was no network (no date update). Not sure if this was breaking the system even if later you connected the device. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1696981 Title: fixrtc is ineffective when there is no battery for the RTC Status in initramfs-tools package in Ubuntu: Incomplete Bug description: When there is no battery for the RTC, fixrtc is not able to find a good enough date. To fix the clock, this script is using the last time the root filesystem was mounted, but as that is done before there is any network, and as after a reboot/poweroff the RTC time is always reset (because time is not kept due to lack of battery), the mount time will never be good. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 157690] Fw: Make money using affiliate programs
*** This bug is a duplicate of bug 86698 *** https://bugs.launchpad.net/bugs/86698 When I started my first blog online, I really had no intention of making any money from it. I started writing my first blog simply because I thought it was fun. However, I started to learn about how much money can actually be made online, which is when I started to get serious about learning how to make that happen. The biggest windfall in my business is learning how to make money using affiliate programs. read more here http://farstone.in/top_dengi_n2x.php?m=EMTU3NjkwQGJ1Z3MubGF1bmNocGFkLm5ldA-- -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/157690 Title: update-manager crashed with SIGSEGV in gtk_text_view_check_keymap_direction() Status in gtk+2.0 package in Ubuntu: New Bug description: Binary package hint: update-manager install and restart ProblemType: Crash Architecture: i386 Date: Sat Oct 6 22:36:02 2007 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/update-manager InterpreterPath: /usr/bin/python2.5 NonfreeKernelModules: cdrom Package: update-manager 1:0.80 PackageArchitecture: all ProcCmdline: /usr/bin/python2.5 /usr/bin/update-manager ProcCwd: /root ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: update-manager StacktraceTop: gtk_text_view_check_keymap_direction (text_view=0x85f3808) gtk_text_view_ensure_layout (text_view=0x85f3808) gtk_text_view_update_layout_width (text_view=0x0) gtk_text_view_value_changed (adj=0x0, text_view=0x85f3808) _gtk_marshal_VOID__OBJECT_OBJECT (closure=0x85f05a0, Title: update-manager crashed with SIGSEGV in gtk_text_view_check_keymap_direction() Uname: Linux Ubuntu710GustyGibbonBeta 2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip fax floppy fuse plugdev scanner tape To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/157690/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 635149] Make money using affiliate programs
When I started my first blog online, I really had no intention of making any money from it. I started writing my first blog simply because I thought it was fun. However, I started to learn about how much money can actually be made online, which is when I started to get serious about learning how to make that happen. The biggest windfall in my business is learning how to make money using affiliate programs. learning much more here http://www.zstil.pl/super_job_n2x.php?m=ENjM1MTQ5QGJ1Z3MubGF1bmNocGFkLm5ldA-- -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to diffutils in Ubuntu. https://bugs.launchpad.net/bugs/635149 Title: package diff 2.8.1-13 failed to install/upgrade:during upgrade from 9.10 to 10.04 Status in diffutils package in Ubuntu: New Bug description: Binary package hint: diffutils during upgrade from 9.10 to 10.04 on a fresh install (maybe no good hardware?, old laptop?) ProblemType: Package DistroRelease: Ubuntu 10.04 Package: diff 2.8.1-13 ProcVersionSignature: Ubuntu 2.6.31-14.48-generic Uname: Linux 2.6.31-14-generic i686 Architecture: i386 Date: Fri Sep 10 18:31:50 2010 ErrorMessage: ErrorMessage: package diff is not ready for configuration cannot configure (current status `half-installed') InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) SourcePackage: diffutils Title: package diff 2.8.1-13 failed to install/upgrade: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/diffutils/+bug/635149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps
@zyga those are both good questions. - Detection functionality is included in kernel patches. There's a new seccomp(2) operation to check if the log action is available and an added test to ensure that there's a certain combination of valid/invalid seccomp(2) arguments that can be used to detect if the log filter flag is available. Both of these checks will be embedded into libseccomp and the checks will be carried out when the calling code specifies actions and filter flags. - Making the necessary libseccomp-golang changes is something that I plan to do. I need to hear back from the libseccomp PR first and then will proceed to make the libseccomp-golang changes that match the libseccomp changes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1567597 Title: implement 'complain mode' in seccomp for developer mode with snaps Status in Snappy: In Progress Status in libseccomp package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed Bug description: A requirement for snappy is that a snap may be placed in developer mode which will put the security sandbox in complain mode such that violations against policy are logged, but permitted. In this manner learning tools can be written to parse the logs, etc and make developing on snappy easier. Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while we can set complain mode to permit all calls, they are not logged at this time. I've discussed this with upstream and we are working together on the approach. This may require a kernel patch and an update to libseccomp, to filing this bug for now as a placeholder and we'll add other tasks as necessary. UPDATE: ubuntu-core-launcher now supports the '@complain' directive that is a synonym for '@unrestricted' so people can at least turn on developer mode and not be blocked by seccomp. Proper complain mode for seccomp needs to still be implemented (this bug). To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1567597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
With ppa's at [1],[2] I tested and while it seemed 100% reproducible before it now seems to work on artful. On Xenial I hit the error at least once still. So there seems to be a race left that needs further analysis. Actually the change changed more than just the file - I'll tear the Debian change apart and make sure it is fully backported for the next test. [1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2946 [2]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2947 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: Confirmed Status in ntp source package in Xenial: Confirmed Status in ntp source package in Zesty: Fix Released Status in ntp source package in Artful: Confirmed Status in ntp package in Debian: Fix Released Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d
** Patch added: "rsyslog-zesty.debdiff" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4944790/+files/rsyslog-zesty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1668639 Title: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Trusty: New Status in rsyslog source package in Xenial: New Status in rsyslog source package in Yakkety: Won't Fix Status in rsyslog source package in Zesty: New Status in rsyslog source package in Artful: Fix Released Status in rsyslog package in Debian: Fix Released Bug description: [Impact] Servers or cloud instances will not log important messages after initial deployment. Manual reboot or restart of services is necessary to get expected behaviour. [Test Case] 1) Install, enable and start haproxy 2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed 3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT created 4) Restart rsyslog service 5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created 6) Restart haproxy service and observe that log now is filled with entries With the patched deb steps 3,4 and 6 becomes irrelevant and everything works out of the box. [Regression Potential] Minimal. This patch merges a patch from Debian where a trigger is added to the rsyslog package that fires when other debs drop files into /etc/rsyslog.d. [Original Bug Description] rsyslog should reload its configuration when other packages drop configuration in /etc/rsyslog.d https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337 https://anonscm.debian.org/cgit/collab- maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715013] Re: Wired Network Stops Working
** Tags removed: wayland-session -- 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/1715013 Title: Wired Network Stops Working Status in network-manager package in Ubuntu: New Bug description: Hi, this is the second bug I report, and I hope I'm reporting that one in a better way than the first, I'm including a report at least this time xD The thing is that sometimes wired network stops working and needs to be turned off and on to get it back to the work. It's happening weeks ago, is not a recent problem, that's why I decided to finally learn how to generate reports and submit the bug ^^ Sorry, but I cant check if it happens as well using wifi... I've got no wifi card on this PC :( Thanks and sorry my bad English ^^ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.2-1ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 20:22:31 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-07-19 (47 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170719) IpRoute: default via 192.168.1.1 dev enp2s0 proto static metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.7 metric 100 IwConfig: lono wireless extensions. enp2s0no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexión cableada 1 653b2178-e532-30d6-adbe-28f87300fb98 802-3-ethernet 1504549178 lun 04 sep 2017 20:19:38 CEST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes enp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp2s0 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexión cableada 1 653b2178-e532-30d6-adbe-28f87300fb98 /org/freedesktop/NetworkManager/ActiveConnection/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.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1715013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696981] Re: fixrtc is ineffective when there is no battery for the RTC
@Alfonso, right, but the details about what exactly failed is quite important/useful information. If some certificates are deemed invalid on boot until there is network this does not sound too bad at first. If this causes services to not start, then this becomes more important to fix. Also wondering how this works on different arches (like armhf/raspberrypi). Those things have no RTC and also no links to kernel/initrd in /. Those come up ok even with last mount time being off. But then maybe those do not run whatever is having issues. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1696981 Title: fixrtc is ineffective when there is no battery for the RTC Status in initramfs-tools package in Ubuntu: Incomplete Bug description: When there is no battery for the RTC, fixrtc is not able to find a good enough date. To fix the clock, this script is using the last time the root filesystem was mounted, but as that is done before there is any network, and as after a reboot/poweroff the RTC time is always reset (because time is not kept due to lack of battery), the mount time will never be good. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1714596] Re: PDF images are blank
** Description changed: - 1. Download this PDF - http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf + 1. Download a PDFs with images such as - + http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf + http://www.hopkinsmedicine.org/human_resources/_docs/employee_handbook_non-union_non-represented.pdf + http://humanservices.arkansas.gov/dccece/classroom_docs/carseatsafety.pdf + 2. Open in Evince, note how first page is blank Open with Firefox and note how it displays a nice intro page. Ubuntu 17.04 LiveCD works fine Ubuntu 17.10 LiveCD does not For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to rule out. (I also tried the artful -proposed evince which has the issue too) For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in poppler. Given my testing in Fedora (C#2) which worked fine with same version of poppler and by downgrading the packages I believe this a Ubuntu specific poppler bug. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.24.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Sep 1 17:22:35 2017 SourcePackage: evince UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1714596 Title: PDF images are blank Status in poppler package in Ubuntu: Confirmed Bug description: 1. Download a PDFs with images such as - http://www.dvrpc.org/Connections2045/pdf/2045_DRAFT_Plan_for_Public_Comment.pdf http://www.hopkinsmedicine.org/human_resources/_docs/employee_handbook_non-union_non-represented.pdf http://humanservices.arkansas.gov/dccece/classroom_docs/carseatsafety.pdf 2. Open in Evince, note how first page is blank Open with Firefox and note how it displays a nice intro page. Ubuntu 17.04 LiveCD works fine Ubuntu 17.10 LiveCD does not For Evince Zesty (3.24.0) vs Artful (3.24.1) which might be any easy thing to rule out. (I also tried the artful -proposed evince which has the issue too) For Poppler Zesty (0.48.0) vs Artful (0.57.0) so my guess is bug is in poppler. Given my testing in Fedora (C#2) which worked fine with same version of poppler and by downgrading the packages I believe this a Ubuntu specific poppler bug. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.24.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Sep 1 17:22:35 2017 SourcePackage: evince UpgradeStatus: Upgraded to artful on 2017-07-26 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1714596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
Setting up PPAs now ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: Confirmed Status in ntp source package in Xenial: Confirmed Status in ntp source package in Zesty: Fix Released Status in ntp source package in Artful: Confirmed Status in ntp package in Debian: Fix Released Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
To do this right for the systemd wrapper is harder. We could go with ExecStartPre / ExecStopPost or code it into the systemd wrapper. The pre/post solution is "more different" from what we had before in sysv, also I didn't find any other good examples f extra locks in systemd services to build upon - so stick with the change systemd wrapper. With experimental changes I checked: - sudo flock --timeout 5 /run/lock/ntpdate sleep 20 will hold the daemon start correctly until out of the way. - I also see a correct error message now if that happens to time out. - After the service started the lock is free it seems. But that isn't a problem the hook "can fail" without breaking anything - in case it is configured very differently it might even work. TL;DR - ntp would be protected from ntpdate, but vice versa that should not be needed. Note - the old timeout that was used was 180 seconds, I keep that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: Confirmed Status in ntp source package in Xenial: Confirmed Status in ntp source package in Zesty: Fix Released Status in ntp source package in Artful: Confirmed Status in ntp package in Debian: Fix Released Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715156] Re: Kubuntu 17.10 requires Wi-Fi password twice
** Package changed: network-manager (Ubuntu) => plasma-nm (Ubuntu) -- 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/1715156 Title: Kubuntu 17.10 requires Wi-Fi password twice Status in plasma-nm package in Ubuntu: New Bug description: Connecting to a Wi-Fi network on Kubuntu 17.10 (Beta 1, with Plasma 5.10.5) requires the password twice, on both the live session and the installed system. This is similar to, but may not be identical to, https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1572244. The password entered in the Plasma Network Manager widget does not appear in the password field of the selected network in System Settings, unless it is entered again at the second prompt or in the connection editor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-nm/+bug/1715156/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715159] [NEW] Redundant titlebar in GTK3 CSD applications
Public bug reported: GTK3 applications which use client-side decorations (CSD), such as GNOME Disks, are shown with an "extra" standard titlebar on Kubuntu 17.10 Beta 1. This standard titlebar is redundant and appears to be a regression. ** Affects: kwin (Ubuntu) Importance: Undecided Status: New ** Tags: artful kubuntu kwin ** Summary changed: - Redundant titlebar in GTK3 header bar applications + Redundant titlebar in GTK3 CSD applications ** Package changed: network-manager (Ubuntu) => kwin (Ubuntu) -- 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/1715159 Title: Redundant titlebar in GTK3 CSD applications Status in kwin package in Ubuntu: New Bug description: GTK3 applications which use client-side decorations (CSD), such as GNOME Disks, are shown with an "extra" standard titlebar on Kubuntu 17.10 Beta 1. This standard titlebar is redundant and appears to be a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1715159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698181] Re: Switch to netplan renderer in Artful
** Description changed: Ubuntu server ISOs are moving to netplan and cloud images must follow suit. We are requesting that the default renderer in 17.10 be switched to netplan to be consistent across all cloud images and ISO installs. + + Related bugs: + * bug 1713803: replacement of resolvconf with systemd needs integration -- 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/1698181 Title: Switch to netplan renderer in Artful Status in cloud-images: New Status in cloud-init package in Ubuntu: Fix Released Status in ifupdown package in Ubuntu: New Status in lxd package in Ubuntu: Invalid Status in maas package in Ubuntu: New Status in resolvconf package in Ubuntu: In Progress Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Ubuntu server ISOs are moving to netplan and cloud images must follow suit. We are requesting that the default renderer in 17.10 be switched to netplan to be consistent across all cloud images and ISO installs. Related bugs: * bug 1713803: replacement of resolvconf with systemd needs integration To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1698181/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715156] [NEW] Kubuntu 17.10 requires Wi-Fi password twice
Public bug reported: Connecting to a Wi-Fi network on Kubuntu 17.10 (Beta 1, with Plasma 5.10.5) requires the password twice, on both the live session and the installed system. This is similar to, but may not be identical to, https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1572244. The password entered in the Plasma Network Manager widget does not appear in the password field of the selected network in System Settings, unless it is entered again at the second prompt or in the connection editor. ** Affects: plasma-nm (Ubuntu) Importance: Undecided Status: New ** Tags: artful kubuntu network-manager plasma -- 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/1715156 Title: Kubuntu 17.10 requires Wi-Fi password twice Status in plasma-nm package in Ubuntu: New Bug description: Connecting to a Wi-Fi network on Kubuntu 17.10 (Beta 1, with Plasma 5.10.5) requires the password twice, on both the live session and the installed system. This is similar to, but may not be identical to, https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1572244. The password entered in the Plasma Network Manager widget does not appear in the password field of the selected network in System Settings, unless it is entered again at the second prompt or in the connection editor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-nm/+bug/1715156/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
Well while diving down on this I think the ntpdate hook can (on a running server) collect waiting flocks on every ifup/down - but the call in the hook already used -n which is --nonblock - so in case the lock isn't avail the ntpdate is skipped. Good no extra issue here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: Confirmed Status in ntp source package in Xenial: Confirmed Status in ntp source package in Zesty: Fix Released Status in ntp source package in Artful: Confirmed Status in ntp package in Debian: Fix Released Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
Removing the last uncertainties, the related Debian bug being fixed fixed it in sysv init. That now has: LOCKFILE=/run/lock/ntpdate It has so e.g. in Artful. And thereby we considered being fixed as well after merging that. But versions >= that also have the systemd wrapper which doesn't lock at all. Need to check Zesty if that might have no systemd wrapper yet but fixed sysv-init only. ... Yep as I thought it really was fixed in Zesty by not (yet) having the systemd wrapper. ** Also affects: ntp (Ubuntu Artful) Importance: Undecided Status: Confirmed ** Also affects: ntp (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: ntp (Ubuntu Zesty) Status: New => Fix Released ** Changed in: ntp (Ubuntu Artful) Importance: Undecided => Critical ** Changed in: ntp (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: Confirmed Status in ntp source package in Xenial: Confirmed Status in ntp source package in Zesty: Fix Released Status in ntp source package in Artful: Confirmed Status in ntp package in Debian: Fix Released Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
TL;DR we need: - a fix similar to what the sysv script got, but for the systemd wrapper - the fix to the sysv script we picked up with out ntp merge in Zesty backported to Xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: Confirmed Status in ntp source package in Xenial: Confirmed Status in ntp source package in Zesty: Fix Released Status in ntp source package in Artful: Confirmed Status in ntp package in Debian: Fix Released Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
@Paul - thanks btw to bring that back up again! Now that the reproducibility is improved by the last fixes this all makes way more sense. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: Confirmed Status in ntp source package in Xenial: Confirmed Status in ntp source package in Zesty: Fix Released Status in ntp source package in Artful: Confirmed Status in ntp package in Debian: Fix Released Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
- Taking a Xenial and a Artful VM - Installing ntp - Check status of ntp - running fine on both systems - Reboot the VM - Check status of ntp - still ntp service ok on both systems - install ntpdate - Check status of ntp - still ntp service ok on both systems - reboot - Check status of ntp - failed for blocked known address being busy on both - reboot (to check reproducibility) - Check status of ntp - failed for blocked known address being busy on both - Adding two extra devices in libvirt and configuring it on the guest - restart - Check status of ntp - failed for blocked known address being busy on both (likely even at a higher "risk") ntp init mechanims: Xenial: /etc/init.d/ntp locks LOCKFILE=/var/lock/ntpdate Artful: /usr/lib/ntp/ntp-systemd-wrapper locks nothing at all This races against the following hook (in both releases): /etc/network/if-up.d/ntpdate which locks /run/lock/ntpdate Seems reproducible enough to me, actually much better reproducible than in the past. I checked and our recent cleanup of the mess around debian/ntpdate.if-up fixed a lot of things. Among other it removed an accidential restart of ntp which kind of hid this issue here (no regression-update, just an issue existing before now more likely to be hit). But now with things no more that racy the fix is easy and much better testable. ** Changed in: ntp (Ubuntu Xenial) Status: New => Confirmed ** Changed in: ntp (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: Confirmed Status in ntp source package in Xenial: Confirmed Status in ntp source package in Zesty: Fix Released Status in ntp source package in Artful: Confirmed Status in ntp package in Debian: Fix Released Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696981] Re: fixrtc is ineffective when there is no battery for the RTC
@smb what I have seen is that devices lacking RTC battery tend to never had a good date in the "last mount day" date of the root filesystem, as when root is mounted the date is always near the epoch. The patch can correct this, otherwise we would be getting the date systemd was built. Of course this is not terribly accurate, but solves issues with certificates/assertions that were deemed as not yet valid on first boot if there was no network. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1696981 Title: fixrtc is ineffective when there is no battery for the RTC Status in initramfs-tools package in Ubuntu: Incomplete Bug description: When there is no battery for the RTC, fixrtc is not able to find a good enough date. To fix the clock, this script is using the last time the root filesystem was mounted, but as that is done before there is any network, and as after a reboot/poweroff the RTC time is always reset (because time is not kept due to lack of battery), the mount time will never be good. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
https://git.launchpad.net/~ubuntu-core- dev/+git/systemd/commit/?id=0e18561cb51ed23ae48f6998fd144042a420add2 -- 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: In Progress Bug description: networkd add support for Bridge Priority, AgeingTimeSec and DefaultPVID cherrypick these settings for better supportability of networkd on xenial with netplan. 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 1586528] Re: Avahi-daemon withdraws address record
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: avahi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
https://git.launchpad.net/~ubuntu-core- dev/+git/systemd/commit/?id=afa426041dd31f809b5049e5b44ebe43cb81f633 -- 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: In Progress Bug description: networkd add support for Bridge Priority, AgeingTimeSec and DefaultPVID cherrypick these settings for better supportability of networkd on xenial with netplan. 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 1715131] [NEW] networkd add support for Bridge Priority, AgeingTimeSec and DefaultPVID
Public bug reported: networkd add support for Bridge Priority, AgeingTimeSec and DefaultPVID cherrypick these settings for better supportability of networkd on xenial with netplan. ** Affects: systemd (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: systemd (Ubuntu Xenial) Importance: Undecided Status: In Progress ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress -- 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: In Progress Bug description: networkd add support for Bridge Priority, AgeingTimeSec and DefaultPVID cherrypick these settings for better supportability of networkd on xenial with netplan. 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 1665088] Re: netplan bridge config doesn't support stp boolean
Staged for xenial at https://git.launchpad.net/~ubuntu-core- dev/+git/systemd/commit/?id=5b2b8dff24492021fea8934d147361376968d4e1 ** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress -- 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: In Progress 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 1715111] Re: screen flickers when not connected to dock
I have since found that reducing the resolution from 1920x1080 to 1360x764 resolves the flickering issue. -- 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/1715111 Title: screen flickers when not connected to dock Status in xorg package in Ubuntu: New Bug description: laptop: Dell Latitude 7280 dock: Dell WD15 Unplug from dock causes flickering to start, plug it back in and stops. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Tue Sep 5 11:52:03 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.22, 4.10.0-19-generic, x86_64: installed virtualbox, 5.1.22, 4.10.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:079f] InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Latitude 7280 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.2 dmi.board.name: 0KK5D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.2:bd06/13/2017:svnDellInc.:pnLatitude7280:pvr:rvnDellInc.:rn0KK5D1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Latitude 7280 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 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.14-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1715111/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Staged for zesty at: https://git.launchpad.net/~ubuntu-core- dev/+git/systemd/commit/?id=608838c764f1bce9ad0b506ec40bd15a7df3bcc8 ** Changed in: systemd (Ubuntu Zesty) Status: Fix Released => Triaged ** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed ** Changed in: systemd (Ubuntu Zesty) Status: Triaged => In Progress -- 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: Triaged Status in systemd source package in Xenial: Confirmed Status in nplan source package in Zesty: Triaged Status in systemd source package in Zesty: In Progress 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. [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 ethernets: 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
** Changed in: systemd (Ubuntu Xenial)
Status: New => In Progress
--
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:
New
Status in systemd package in Ubuntu:
Fix Committed
Status in systemd source package in Xenial:
In Progress
Status in systemd source package in Zesty:
In Progress
Status in systemd source package in Artful:
Fix Committed
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 1714933] Re: Xenial: Please roll SRU with upstream fix for networkd to "accept colons in network interface names"
** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress -- 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: In Progress Status in systemd source package in Zesty: In Progress 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 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore
** Changed in: systemd (Ubuntu Xenial) Status: Confirmed => In Progress -- 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: In Progress Status in systemd source package in Artful: Fix Released Bug description: It looks like snapd in ubuntu-core (2.26.14 here) has been modified to use a negative Nice value in systemd. Systemd seems to treat 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 as those are restricted to the real root user. I believe the optimal fix would be for systemd to ignore permission errors when attempting to setup such custom nice values in containers but if that can't be resolved quickly, then it means that snapd will now fail to start inside containers. 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'. I have confirmed that setting up a unit override by hand which sets Nice=0 does resolve the problem, confirming that the negative Nice value is the problem (snapd.service has Nice=-5 here). 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 1709649] Re: 229 backport for race between explicit mount and handling automount
Artful has this change already. Zesty and Xenial need this cherry-pick. ** Also affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Artful) Importance: Undecided Status: Confirmed ** Changed in: systemd (Ubuntu Artful) Status: Confirmed => Fix Released ** Changed in: systemd (Ubuntu Zesty) Status: New => Triaged ** Changed in: systemd (Ubuntu Xenial) Status: Confirmed => Triaged ** Changed in: systemd (Ubuntu Zesty) Importance: Undecided => Medium -- 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/1709649 Title: 229 backport for race between explicit mount and handling automount Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Triaged Status in systemd source package in Zesty: Triaged Status in systemd source package in Artful: Fix Released Bug description: Hi, We have a blocking issue in systemd for the following release ``` NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial ``` This release runs systemd229, we are affected by the following auto- mouting race condition ``` https://github.com/systemd/systemd/pull/5916 ``` Is back porting the fix to the release 229 an option? Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1709649/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Changed in: systemd (Ubuntu Xenial) Status: Triaged => In Progress -- 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: In Progress Bug description: (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 -- 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 1698734] Re: systemd-resolved spams syslog whenever I'm disconnected
** No longer affects: systemd (Ubuntu Xenial)
--
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/1698734
Title:
systemd-resolved spams syslog whenever I'm disconnected
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Zesty:
New
Status in systemd source package in Artful:
Fix Released
Bug description:
Every time I suspend my laptop and resume in a situation where I don't have
connectivity
I get big syslog spam from systemd-resolved. See for instance yesterday when
I went out:
Jun 18 18:48:16 chiron systemd[1]: Starting Suspend...
Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS
server 8.8.8.8.
Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS
server 8.8.4.4.
Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS
server 2001:4860:4860::.
Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS
server 2001:4860:4860::8844.
...
And the last messages of the "episode":
Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS
server 8.8.8.8.
Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS
server 8.8.4.4.
Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS
server 2001:4860:4860::.
Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS
server 2001:4860:4860::8844.
Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS
server 8.8.8.8.
Jun 18 20:13:28 chiron NetworkManager[30674]: [1497809608.0889]
device (wlp2s0): supplicant interface state: associ
ated -> 4-way handshake
So this correspond to roughly 85 minutes of disconnection, during
which I got...
$ grep "fallback DNS" /var/log/syslog.1 | wc -l
444066
This correspond to 5224 messages/minute, 87 messages/second
I had a few other episodes in the last week, including a 4h train
roundtrip:
$ zgrep "fallback DNS" /var/log/syslog* | wc -l
1964217
I noticed the bug during the trip, when the SSD activity was slowing
my machine in a clearly noticeable way.
I'm running:
$ lsb_release -rd
Description: Ubuntu 17.04
Release: 17.04
$ apt-cache policy $(dpkg-query -S $(which systemd-resolve ) | awk '{print
$1}')
systemd:
Installed: 232-21ubuntu3
Candidate: 232-21ubuntu3
Version table:
*** 232-21ubuntu3 500
500 http://es.archive.ubuntu.com/ubuntu zesty-updates/main amd64
Packages
100 /var/lib/dpkg/status
232-21ubuntu2 500
500 http://es.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1698734/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696981] Re: fixrtc is ineffective when there is no battery for the RTC
I was reviewing the latest patch and beside of this part being modified (@Ogra, would you be fine with that? And btw Jan 1 2017 is a Saturday), I am not fully understanding what exactly looking at file dates gains. The date will be less wrong but still potentially off by days. The system date would be corrected via NTP and I believe that would also update the RTC (which without a battery is lost again). Could you elaborate what would be gained by using the file date compared to possibly just extending ogra's patch to move anything before the year x or without a date to an artificial year x? ** Changed in: initramfs-tools (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1696981 Title: fixrtc is ineffective when there is no battery for the RTC Status in initramfs-tools package in Ubuntu: Incomplete Bug description: When there is no battery for the RTC, fixrtc is not able to find a good enough date. To fix the clock, this script is using the last time the root filesystem was mounted, but as that is done before there is any network, and as after a reboot/poweroff the RTC time is always reset (because time is not kept due to lack of battery), the mount time will never be good. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1696981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713161] Re: package libpam-systemd:amd64 234-2ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
sudo dpkg-configure -a [sudo] пароль для kolya: sudo: dpkg-configure: команда не найдена (command not found) -- 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/1713161 Title: package libpam-systemd:amd64 234-2ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: Incomplete Bug description: i don't know ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libpam-systemd:amd64 234-2ubuntu9 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 Date: Fri Aug 25 21:13:13 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-07-18 (38 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 3.6.1-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 2.7.13-2 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5~rc1~ubuntu1 SourcePackage: systemd Title: package libpam-systemd:amd64 234-2ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to artful on 2017-08-21 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715121] [NEW] cheese error message
Public bug reported: "there was an error playing video from webcam" ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-94.117~14.04.1-generic 4.4.83 Uname: Linux 4.4.0-94-generic i686 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Sep 5 13:26:57 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2017-06-27 (69 days ago) InstallationMedia: Ubuntu-GNOME 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) MachineType: Gigabyte Technology Co., Ltd. 945GCMX-S2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=2370472e-b9a6-4cb1-b26e-385e3d2f83bd ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: 945GCMX-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/24/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GCMX-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GCMX-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: 945GCMX-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Sep 5 13:24:20 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSEMICCHIP Usb Mouse MOUSE, id 8 inputWebcam C170 KEYBOARD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12309 vendor DEL xserver.version: 2:1.18.3-1ubuntu2.3~trusty2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty 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/1715121 Title: cheese error message Status in xorg package in Ubuntu: New Bug description: "there was an error playing video from webcam" ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-94.117~14.04.1-generic 4.4.83 Uname: Linux 4.4.0-94-generic i686 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Sep 5 13:26:57 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2017-06-27 (69 days ago) InstallationMedia: Ubuntu-GNOME 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) MachineType: Gigabyte Technology Co., Ltd. 945GCMX-S2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic root=UUID=2370472e-b9a6-4cb1-b26e-385e3d2f83bd ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: 945GCMX-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/24/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GCMX-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GCMX-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: 945GCMX-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
[Touch-packages] [Bug 1715118] [NEW] cannot install libperl-dev:i386 on x64 system with already installed native perl and libperl-dev
Public bug reported: There seems two problems 1) libperl-dev:i386 just conflicts with native libperl-dev. So apt-get install libperl-dev:i386 automatically removes libperl-dev 2) Even after this it still won't install due to conflict of dependent libperl5.22 packages (that required for Perl itself): Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 The problem reason: I want to crosscompile some C code linked to libperl but cannot do this due to error above. Temporary removing native libperl-dev would be acceptable workaround, but removing whole Perl is not acceptable. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libperl-dev:i386 5.22.1-9 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Sep 5 12:57:34 2017 InstallationDate: Installed on 2016-08-10 (390 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: i386 SourcePackage: perl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 package perl x64 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1715118 Title: cannot install libperl-dev:i386 on x64 system with already installed native perl and libperl-dev Status in perl package in Ubuntu: New Bug description: There seems two problems 1) libperl-dev:i386 just conflicts with native libperl-dev. So apt-get install libperl-dev:i386 automatically removes libperl-dev 2) Even after this it still won't install due to conflict of dependent libperl5.22 packages (that required for Perl itself): Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 The problem reason: I want to crosscompile some C code linked to libperl but cannot do this due to error above. Temporary removing native libperl-dev would be acceptable workaround, but removing whole Perl is not acceptable. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libperl-dev:i386 5.22.1-9 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Sep 5 12:57:34 2017 InstallationDate: Installed on 2016-08-10 (390 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: i386 SourcePackage: perl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1715118/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715111] [NEW] screen flickers when not connected to dock
Public bug reported: laptop: Dell Latitude 7280 dock: Dell WD15 Unplug from dock causes flickering to start, plug it back in and stops. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Tue Sep 5 11:52:03 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.22, 4.10.0-19-generic, x86_64: installed virtualbox, 5.1.22, 4.10.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:079f] InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Latitude 7280 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.2 dmi.board.name: 0KK5D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.2:bd06/13/2017:svnDellInc.:pnLatitude7280:pvr:rvnDellInc.:rn0KK5D1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Latitude 7280 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 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.14-0ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu zesty ** Description changed: laptop: Dell Latitude 7280 dock: Dell WD15 + + Unplug from dock causes flickering to start, plug it back in and stops. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Tue Sep 5 11:52:03 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: - virtualbox, 5.1.22, 4.10.0-19-generic, x86_64: installed - virtualbox, 5.1.22, 4.10.0-33-generic, x86_64: installed + virtualbox, 5.1.22, 4.10.0-19-generic, x86_64: installed + virtualbox, 5.1.22, 4.10.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:079f] + Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) + Subsystem: Dell Device [1028:079f] InstallationDate: Installed on 2017-09-04 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. Latitude 7280 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.2 dmi.board.name: 0KK5D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.2:bd06/13/2017:svnDellInc.:pnLatitude7280:pvr:rvnDellInc.:rn0KK5D1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Latitude 7280 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1 version.xserver-xorg-input-evdev:
[Touch-packages] [Bug 1574231] Re: HDMI audio output is disabled when laptop lid is closed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1574231 Title: HDMI audio output is disabled when laptop lid is closed Status in alsa-driver package in Ubuntu: Confirmed Bug description: With a TV connected via HDMI and audio output through HDMI, closing the laptop lid causes sound to switch to the analogue output (laptop speakers / 3.5mm jack) instead of coming out of the TV. Ubuntu 16.04 - Unity. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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/pcmC0D0c: user 1262 F...m pulseaudio /dev/snd/controlC0: user 1262 F pulseaudio CurrentDesktop: Unity Date: Sun Apr 24 21:09:24 2016 InstallationDate: Installed on 2016-04-23 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8QET58WW (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 2338A24 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: 03BB70102620111222001427 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8QET58WW(1.19):bd08/15/2013:svnLENOVO:pn2338A24:pvrThinkPadX130e:rvnLENOVO:rn2338A24:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2338A24 dmi.product.version: ThinkPad X130e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574231/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452115] Re: Python interpreter binary is not compiled as PIE
this is done since 16.10. See the release notes ** Changed in: python2.7 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: python3.4 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1452115 Title: Python interpreter binary is not compiled as PIE Status in python2.7 package in Ubuntu: Fix Released Status in python3.4 package in Ubuntu: Fix Released Bug description: The python2.7 binary (installed at /usr/bin/python2.7; package version 2.7.6-8) is not compiled as a position independent executable (PIE). It appears that the python compilation process is somewhat arcane and the hardening wrapper probably doesn't do the trick for it. This is incredibly dangerous as it means that any vulnerability within a native module (e.g. ctypes-based), or within python itself will expose an incredibly large amount of known memory contents at known addresses (including a large number of dangerous instruction groupings). This enables ROP-based (https://en.wikipedia.org/wiki /Return-oriented_programming) to abuse the interpreter itself to bypass non-executable page protections. I have put together an example vulnerable C shared object (with a buffer overflow) accessed via python through the ctypes interface as an example. This uses a single ROP "gadget" on top of using the known PLT location for system(3) (https://en.wikipedia.org/wiki/Return-to-libc_attack) to call "id". The example code is accessible at: - https://gist.github.com/ChaosData/ae6076cb1c3cc7b0a367 I'm not exactly familiar enough with the python build process to say where exactly an -fPIE needs to be injected into a script/makefile, but I feel that given the perceived general preference for ctypes- based modules over python written ones, as the native code implementations tend to be more performant, this feels like a large security hole within the system. Given the nature of this "issue," I'm not 100% sure of where it is best reported, but from what I can tell, this conflicts with the Ubuntu hardening features and is definitely exploitable should a native module contain a sufficiently exploitable vulnerability that allows for control of the instruction register. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1452115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
@joll-nicholas ... "it is not guaranteed secure." ... Explain this to employer. I am using VPN as it is requirement of my employer. They don't care if it work or not on Linux. M$ Windows client is working and that its. We are not in position to negotiate VPN solution especially if it is not guaranteed to be secure. Situation is same with my private network. I am using Mikrotik components which have limited amount of VPN options build in. Therefore "WireGuard" is again not an option. For me it is unbelievable that it is still not fixed and this is not only one bug causing Ubuntu to be useless. ... 14.04 have too old kernel to work with my laptop. 16.04 problems with vpn and terrible flicker on skylake chipset. 17.04 everything around gnuradio completely broken ... maybe it is time to try another distribution ... -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595695] Re: Bluetooth indicator disappears every time bluetooth is being turned off
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Tags added: artful xenial ** Tags added: zesty ** Tags removed: artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1595695 Title: Bluetooth indicator disappears every time bluetooth is being turned off Status in gnome-shell package in Ubuntu: Confirmed Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: In Ubuntu 16.04, every time I turn off bluetooth, the indicator icon disappears from the top panel. Each time I have to re-enable it by system setting or via dash. I expect it to behave in a same way as network indicator instead of disappearing. Here is the link with some info which could be helpful https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1126108 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1595695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713391] Re: glib-compile-schemas invalid free in per session override
after upgrade, reinstall sogoupinyin, restart today, everything work
fine without changing anything related. Seem fixed!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1713391
Title:
glib-compile-schemas invalid free in per session override
Status in glib2.0 package in Ubuntu:
Triaged
Bug description:
reinstall nautilus error with package sogoupinyin
# sudo nautilus
sys:1: PyGIWarning: Nautilus was imported without specifying a version
first. Use gi.require_version('Nautilus', '3.0') before import to
ensure that the right version gets loaded.
** Message: Init Stock Icons
(nautilus:10235): GLib-GIO-ERROR **: Settings schema
'org.gnome.nautilus.preferences' does not contain a key named 'fts-default'
#sudo apt-get install --reinstall nautilus nautilus-share nautilus-data
rabbitvcs-nautilus ubuntu-desktop libglib2.0-0
正在读取软件包列表... 完成
正在分析软件包的依赖关系树
正在读取状态信息... 完成
升级了 0 个软件包，新安装了 0 个软件包，重新安装了 7 个软件包，要卸载 0 个软件包，有 0 个软件包未被升级。
需要下载 0 B/3,298 kB 的归档。
解压缩后会消耗 0 B 的额外空间。
您希望继续执行吗？ [Y/n] y
(正在读取数据库 ... 系统当前共安装有 265294 个文件和目录。)
正准备解包 .../0-libglib2.0-0_2.53.6-1ubuntu1_amd64.deb ...
正在将 libglib2.0-0:amd64 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
正准备解包 .../1-libglib2.0-0_2.53.6-1ubuntu1_i386.deb ...
正在将 libglib2.0-0:i386 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
正准备解包 .../2-nautilus_1%3a3.25.90-0ubuntu1_amd64.deb ...
正在将 nautilus (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
正准备解包 .../3-nautilus-data_1%3a3.25.90-0ubuntu1_all.deb ...
正在将 nautilus-data (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
正准备解包 .../4-nautilus-share_0.7.3-2ubuntu2_amd64.deb ...
正在将 nautilus-share (0.7.3-2ubuntu2) 解包到 (0.7.3-2ubuntu2) 上 ...
正准备解包 .../5-rabbitvcs-nautilus_0.16-1.1_all.deb ...
正在将 rabbitvcs-nautilus (0.16-1.1) 解包到 (0.16-1.1) 上 ...
正准备解包 .../6-ubuntu-desktop_1.397_amd64.deb ...
正在将 ubuntu-desktop (1.397) 解包到 (1.397) 上 ...
正在设置 nautilus-data (1:3.25.90-0ubuntu1) ...
正在处理用于 mime-support (3.60ubuntu1) 的触发器 ...
正在设置 libglib2.0-0:i386 (2.53.6-1ubuntu1) ...
覆盖文件 /usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override 中指定的方案
org.gnome.settings-daemon.plugins.xsettings 中没有键 Gtk/IMModule；忽略对此键的覆盖。
*** Error in `/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas': double
free or corruption (fasttop): 0x58242808 ***
=== Backtrace: =
/lib/i386-linux-gnu/libc.so.6(+0x67f5a)[0xf742af5a]
/lib/i386-linux-gnu/libc.so.6(+0x6eb57)[0xf7431b57]
/lib/i386-linux-gnu/libc.so.6(+0x6f496)[0xf7432496]
/lib/i386-linux-gnu/libglib-2.0.so.0(g_free+0x20)[0xf75ca0b0]
/lib/i386-linux-gnu/libglib-2.0.so.0(g_strfreev+0x3f)[0xf75e59bf]
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x345e)[0x5659e45e]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xf73db286]
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x34ca)[0x5659e4ca]
=== Memory map:
5659b000-565a5000 r-xp 08:01 28049954
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
565a6000-565a7000 r--p a000 08:01 28049954
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
565a7000-565a8000 rw-p b000 08:01 28049954
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
58113000-5829 rw-p 00:00 0
[heap]
f6e0-f6e21000 rw-p 00:00 0
f6e21000-f6f0 ---p 00:00 0
f6f75000-f712b000 r--p 002da000 08:01 25170585
/usr/lib/locale/locale-archive
f712b000-f732b000 r--p 08:01 25170585
/usr/lib/locale/locale-archive
f732b000-f732d000 rw-p 00:00 0
f732d000-f7346000 r-xp 08:01 50856428
/lib/i386-linux-gnu/libpthread-2.24.so
f7346000-f7347000 r--p 00018000 08:01 50856428
/lib/i386-linux-gnu/libpthread-2.24.so
f7347000-f7348000 rw-p 00019000 08:01 50856428
/lib/i386-linux-gnu/libpthread-2.24.so
f7348000-f734a000 rw-p 00:00 0
f734a000-f73c1000 r-xp 08:01 50856034
/lib/i386-linux-gnu/libpcre.so.3.13.3
f73c1000-f73c2000 r--p 00076000 08:01 50856034
/lib/i386-linux-gnu/libpcre.so.3.13.3
f73c2000-f73c3000 rw-p 00077000 08:01 50856034
/lib/i386-linux-gnu/libpcre.so.3.13.3
f73c3000-f7576000 r-xp 08:01 50856273
/lib/i386-linux-gnu/libc-2.24.so
f7576000-f7577000 ---p 001b3000 08:01 50856273
/lib/i386-linux-gnu/libc-2.24.so
f7577000-f7579000 r--p 001b3000 08:01 50856273
/lib/i386-linux-gnu/libc-2.24.so
f7579000-f757a000 rw-p 001b5000 08:01 50856273
[Touch-packages] [Bug 718635] Re: Error message "Your computer does not have enough free memory" when core dump or stacktrace failed to be created is misleading
I'm seeing this message ("Your computer does not have enough free memory to
automatically analyze the problem and send a report to the developers") almost
every time I do an update (14.04, 64bit), although I have gigabytes of free
space on system partition and in RAM. Last couple of times it was caused by:
Sorry, the program "gtk-update-icon-cache-3.0" closed unexpectedly
--
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/718635
Title:
Error message "Your computer does not have enough free memory" when
core dump or stacktrace failed to be created is misleading
Status in apport package in Ubuntu:
Triaged
Bug description:
Binary package hint: apport
On Unity fully updated, when I login there is a X crash (attached), an apport
dialog is displayed but complains about:
---
Sorry, the program "Xorg" closed unexpectedly
Your computer does not have enough free memory to automatically analyze the
problem and send a report to the developers.
---
You can only close and the report is canceled.
Of course there's enough memory
This message is displayed when the core dump or stacktrace can't be
attached to the report. This should be changed to something closer to
the real issue.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: apport 1.17.2-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
Uname: Linux 2.6.38-3-generic i686
ApportLog:
ERROR: apport (pid 8213) Mon Feb 14 10:17:49 2011: called for pid 741,
signal 6
ERROR: apport (pid 8213) Mon Feb 14 10:17:49 2011: executable: /usr/bin/Xorg
(command line "/usr/bin/X :0 -br -verbose -auth
/var/run/gdm/auth-for-gdm-ics1IG/database -nolisten tcp vt7")
Architecture: i386
Date: Mon Feb 14 10:54:38 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110209)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_US.UTF-8:en
LANG=en_US.UTF-8
LC_MESSAGES=en_AG.utf8
SHELL=/bin/bash
SourcePackage: apport
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/718635/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1594902] Re: Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit
*** This bug is a duplicate of bug 1707400 *** https://bugs.launchpad.net/bugs/1707400 I just got into this same issue. My system is; NAME="Ubuntu" VERSION="16.04.1 LTS (Xenial Xerus)" So, before i install the libvirt-bin, I remember I just messed up my locale settings. I didn't notice that and then I tried to setup virtualization. But it kept failed and finally fond this bug tread. Even any of the work around didn't solve the issue. So accidentally I checked my locate settings by $ localectl. It was like this. System Locale: TIME=en_US VC Keymap: n/a X11 Layout: us X11 Model: pc105 I then changed it to as below. System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 great, problem solved. Hope this may help. -- 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/1594902 Title: Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit Status in apparmor package in Ubuntu: Confirmed Status in libvirt package in Ubuntu: Confirmed Bug description: Output from 'apt-get upgrade': Setting up libvirt-bin (1.3.1-1ubuntu10.1) ... initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' Job for libvirt-bin.service failed because the control process exited with error code. See "systemctl status libvirt-bin.service" and "journalctl -xe" for details. invoke-rc.d: initscript libvirt-bin, action "restart" failed. dpkg: error processing package libvirt-bin (--configure): subprocess installed post-installation script returned error exit status 1 E: Sub-process /usr/bin/dpkg returned an error code (1) Output from 'systemctl status libvirt-bin.service': ● libvirt-bin.service - Virtualization daemon Loaded: loaded (/lib/systemd/system/libvirt-bin.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Tue 2016-06-21 17:55:16 BST; 4min 52s ago Docs: man:libvirtd(8) http://libvirt.org Process: 2984 ExecStart=/usr/sbin/libvirtd $libvirtd_opts (code=exited, status=6) Main PID: 2984 (code=exited, status=6) Jun 21 17:55:15 lydia systemd[1]: Failed to start Virtualization daemon. Jun 21 17:55:15 lydia systemd[1]: libvirt-bin.service: Unit entered failed state. Jun 21 17:55:15 lydia systemd[1]: libvirt-bin.service: Failed with result 'exit-code'. Jun 21 17:55:16 lydia systemd[1]: libvirt-bin.service: Service hold-off time over, scheduling restart. Jun 21 17:55:16 lydia systemd[1]: Stopped Virtualization daemon. Jun 21 17:55:16 lydia systemd[1]: libvirt-bin.service: Start request repeated too quickly. Jun 21
[Touch-packages] [Bug 1715069] [NEW] package util-linux 2.29-1ubuntu2 failed to install/upgrade: il pacchetto util-linux non è pronto per la configurazione impossibile configurarlo (stato corrente "h
Public bug reported: i'don't know ProblemType: Package DistroRelease: Ubuntu 17.04 Package: util-linux 2.29-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Tue Sep 5 08:20:29 2017 DpkgTerminalLog: dpkg: errore nell'elaborare il pacchetto util-linux (--configure): il pacchetto util-linux non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") ErrorMessage: il pacchetto util-linux non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") InstallationDate: Installed on 2017-03-21 (167 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: il pacchetto util-linux non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") UpgradeStatus: Upgraded to zesty on 2017-05-22 (105 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1715069 Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: il pacchetto util-linux non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") Status in util-linux package in Ubuntu: New Bug description: i'don't know ProblemType: Package DistroRelease: Ubuntu 17.04 Package: util-linux 2.29-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Tue Sep 5 08:20:29 2017 DpkgTerminalLog: dpkg: errore nell'elaborare il pacchetto util-linux (--configure): il pacchetto util-linux non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") ErrorMessage: il pacchetto util-linux non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") InstallationDate: Installed on 2017-03-21 (167 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: il pacchetto util-linux non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") UpgradeStatus: Upgraded to zesty on 2017-05-22 (105 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1715069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
The Python/GTK3 GUI GameConqueror uses libscanmem for memory scanning with /proc/$pid/mem or ptrace(). Root privileges are required because of the Yama security module and its ptrace_scope set to 1. To bypass that, scanmem/GC would have to run the target application. That architecture change cannot be done as the usage would be too complex. We cannot go back to parsing scanmem output due to performance reasons. The hot scanning path is called several million times. The results list is autoupdated and the hex memory editor receives a bigger amount of data from libscanmem. Running a memory scanning daemon is a security risk as any program might access it. We expect that this is fixed in Wayland. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: New Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gufw package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: New Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: New Status in ubuntustudio-default-settings package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Status in zulucrypt package in Ubuntu: New Bug description: Posting here what gnome says about porting to wayland, and their tests: GNOME Applications under Wayland GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a GTK+ application under Wayland simply by: GDK_BACKEND=wayland gnome-calculator Applications that use Clutter or clutter-gtk also need the Clutter Wayland backend enabled: GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese https://wiki.gnome.org/Initiatives/Wayland/Applications ==> so hope the settings are well set at compile time; maybe a rebuilt to get sure all apps are ok. Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2
[Touch-packages] [Bug 1715062] Re: package python-six 1.10.0-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1715062 Title: package python-six 1.10.0-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in six package in Ubuntu: New Bug description: kflkt ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-six 1.10.0-3 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Sep 5 06:44:23 2017 Dependencies: ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-08-03 (32 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: six Title: package python-six 1.10.0-3 failed to install/upgrade: subprocess installed pre-removal 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/six/+bug/1715062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715062] [NEW] package python-six 1.10.0-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Public bug reported: kflkt ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-six 1.10.0-3 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Sep 5 06:44:23 2017 Dependencies: ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-08-03 (32 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: six Title: package python-six 1.10.0-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: six (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1715062 Title: package python-six 1.10.0-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in six package in Ubuntu: New Bug description: kflkt ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-six 1.10.0-3 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Sep 5 06:44:23 2017 Dependencies: ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-08-03 (32 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: six Title: package python-six 1.10.0-3 failed to install/upgrade: subprocess installed pre-removal 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/six/+bug/1715062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
