[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
*** This bug is a duplicate of bug 520546 *** https://bugs.launchpad.net/bugs/520546 The same thing just happened to me after an update. Running `sudo kbd_mode -s` fixed it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in console-setup package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1508146/+subscriptions -- Mailing list: https://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 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot
Yes, I've deleted the failing packages, game servers, debomatic, etc, or in one case masked it so systemd should not try to run it. On Tue, April 16, 2019 11:27 pm, Sebastien Bacher wrote: > see > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+attachmen > t/5256102/+files/SystemdFailedUnits.txt > > -- > You received this bug notification because you are subscribed to the bug > report. https://bugs.launchpad.net/bugs/1824893 > > > Title: > When I type systemctl reboot system reaches Target Reboot but then > does not reboot > > Status in systemd package in Ubuntu: > New > > > Bug description: > This is similar to the bug where systemd used to get stuck in target > Shutdown except that bug affected all my hardware, now it gets stuck > at target Reboot but this only affects my elderly Mac Pro 1,1 and does not > affect my laptop or i7-6700k and i7-6850k based servers. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: systemd 240-6ubuntu5 > ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 > Uname: Linux 5.0.0-8-lowlatency x86_64 > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > CurrentDesktop: MATE > Date: Mon Apr 15 16:30:34 2019 > InstallationDate: Installed on 2018-12-06 (130 days ago) > InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.2) > MachineType: Apple Computer, Inc. MacPro2,1 > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency > root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash > vt.handoff=1 SourcePackage: systemd > SystemdDelta: > [EXTENDED] /lib/systemd/system/ondemand.service â > /lib/systemd/system/ondemand.service.d/ubuntustudio.conf > [EXTENDED] /lib/systemd/system/rc-local.service â > /lib/systemd/system/rc-local.service.d/debian.conf > [EXTENDED] /lib/systemd/system/user@.service â > /lib/systemd/system/user@.service.d/timeout.conf > > > 3 overridden configuration files found. > UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) > dmi.bios.date: 07/02/07 > dmi.bios.vendor: Apple Computer, Inc. > dmi.bios.version: MP21.88Z.007F.B06.0707021348 > dmi.board.asset.tag: Base Board Asset Tag# > dmi.board.name: Mac-F4208DC8 > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag# > dmi.chassis.type: 2 > dmi.chassis.vendor: Apple Computer, Inc. > dmi.chassis.version: Mac-F4208DC8 > dmi.modalias: > dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnA > ppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:c > vnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: > dmi.product.family: MacPro > dmi.product.name: MacPro2,1 > dmi.product.sku: System SKU# > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Computer, Inc. > > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscripti > ons > -- 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/1824893 Title: When I type systemctl reboot system reaches Target Reboot but then does not reboot Status in systemd package in Ubuntu: New Bug description: This is similar to the bug where systemd used to get stuck in target Shutdown except that bug affected all my hardware, now it gets stuck at target Reboot but this only affects my elderly Mac Pro 1,1 and does not affect my laptop or i7-6700k and i7-6850k based servers. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1 Uname: Linux 5.0.0-8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 15 16:30:34 2019 InstallationDate: Installed on 2018-12-06 (130 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Apple Computer, Inc. MacPro2,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/ondemand.service → /lib/systemd/system/ondemand.service.d/ubuntustudio.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago) dmi.bios.date: 07/02/07 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MP21.88Z.007F.B06.0707021348 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F4208DC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F4208DC8 dmi.modalia
[Touch-packages] [Bug 1774419] Re: easy_install command is missing
** Changed in: python-setuptools (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1774419 Title: easy_install command is missing Status in python-setuptools package in Ubuntu: Confirmed Status in python-setuptools package in Debian: New Bug description: Description: Ubuntu 18.04 LTS Release: 18.04 Package: python-setuptools Version: 39.0.1-2 This package installs the easy_install module, but the command is missing: deploy@controller0:~$ which easy_install deploy@controller0:~$ echo $? 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1774419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY
This just happened to me, after an update. Alt+Left logged me out, and Ctrl+Alt+Del restarted the computer, even though I had mapped this combination to another command, and used successfully for weeks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
*** This bug is a duplicate of bug 520546 *** https://bugs.launchpad.net/bugs/520546 I also just had the same issue on KDE Neon after an update. Running `sudo kbd_mode -s` also fixed it for me. Thank you very much, Eric! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in console-setup package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1508146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1816642] Re: SRU of LXC 2.0.11
Did manual testing on LXC 2.0.11 both using it directly and through LXD with pre-existing and new containers. Also tested LXD on top of the updated go-lxc. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1816642 Title: SRU of LXC 2.0.11 Status in golang-gopkg-lxc-go-lxc.v2 package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in golang-gopkg-lxc-go-lxc.v2 source package in Trusty: Triaged Status in lxc source package in Trusty: Triaged Status in golang-gopkg-lxc-go-lxc.v2 source package in Xenial: Fix Released Status in lxc source package in Xenial: Fix Released Bug description: LXC upstream has released a new bugfix release for the LXC 2.0 LTS branch. This is version 2.0.10. Ubuntu never received 2.0.9 as an SRU, so the changelog for both of them can be found below: LXC 2.0.11: - autotools: handle getgrgid_r on bionic - autotools: add memory_utils.h to Makefile.am - change version to 2.0.11 in configure.ac LXC 2.0.10: - tools: allow lxc-attach to undefined containers - utils: move memfd_create() definition - utils: add lxc_cloexec() - utils: add lxc_make_tmpfile() - utils: add lxc_getpagesize() - utils: add lxc_safe_long_long() - utils: parse_byte_size_string() - utils: add lxc_find_next_power2() - namespace: use lxc_getpagesize() - lxc-debian: allow creating `testing` and `unstable` - Call lxc_config_define_load from lxc_execute again - Fix typo in lxc-net script - Add missing lxc_container_put - lxc-debian: don't write C.* locales to /etc/locale.gen - attach: correctly handle namespace inheritance - cgfsng: fix cgroup2 detection - cgroups: enable container without CAP_SYS_ADMIN - lxc-start: remove unnecessary checks - start: close non-needed file descriptors - handler: make name argument const - start: close data socket in parent - monitor: do not log useless warnings - network: reap child in all cases - conf: reap child in all cases - storage: switch to ext4 as default filesystem - tools: fix help output of lxc-create - attach: handle namespace inheritance - cgroups/cgfsng: keep mountpoint intact - cgroups/cgfsng: cgfsns_chown() -> cgfsng_chown() - cgroups/cgfsng: support MS_READONLY with cgroup ns - log: check for i/o error with vsnprintf() - cgroupfs/cgfsng: tweak logging - cgroups/cgfsng: remove is_lxcfs() - cgroups/cgfsng: fix get_controllers() for cgroup2 - cgroupfs/cgfsng: improve cgroup2 handling - config: remove SIGRTMIN+14 as lxc.signal.stop - commands: non-functional changes - console: non-functional changes - console: non-functional changes - lxc-test-unpriv: fix the overlayfs mount error - attach: allow attach with empty conf - tools/lxc_attach: removed api logging - console: fix console info message - Add missing dependency libunistring - cgroups/cgfsng: adapt to new cgroup2 delegation - console: report detach message on demand - lxccontainer: enable daemonized app containers - console: use correct escape sequence check - console: prepare for generic signal handler - console: exit mainloop on SIGTERM - commands: non-functional changes - lxccontainer: non-functional changes - commands: fix state socket implementation - lxc_init: set the control terminal in the child session - lxc-test-unpriv: check user existence before removing it - Fixed typo on lxc.spec.in - conf: move CAP_SYS_* definitions to utils.h - start.c: always switch uid and gid - Use AX_PTHREAD config script to detect pthread api - utils.h: Avoid duplicated sethostname implementation - tools/lxc_cgroup: remove internal logging - tools/lxc_autostart: remove internal logging - tools/lxc_clone: remove internal logging - tools/lxc_console: remove internal logging - tools/lxc_create: remove internal logging - tools/lxc_destroy: remove internal logging - tools/lxc_device: remove internal logging - tools/lxc_execute: removed internal logging - tools/lxc_freeze: remove internal logging - tools/lxc_info: removed internal logging - criu: detect veth name - lxccontainer: various container creation fixes - storage: remove unused declaration - tools/lxc_ls: remove internal logging - tools/lxc_copy: remove internal logging - tools/lxc_monitor: removed internal logging - tools/lxc_snapshot: removed internal logging - tools/lxc_start: removed internal logging - tools/lxc_stop: removed internal logging - tools/lxc_top: removed internal logging - tools/lxc_unfreeze: removed internal logging - tools/lxc_unshare: removed internal logging - tools/lxc_usernsexec: removed internal logging - tools/
[Touch-packages] [Bug 1816642] Re: SRU of LXC 2.0.11
This bug was fixed in the package golang-gopkg-lxc-go-lxc.v2 - 0.0~git20161126.1.82a07a6-0ubuntu1~ubuntu16.04.2 --- golang-gopkg-lxc-go-lxc.v2 (0.0~git20161126.1.82a07a6-0ubuntu1~ubuntu16.04.2) xenial; urgency=medium * Cherry-pick fixes from recent go-lxc (LP: #1816642): - Actually start the container in shutdown test - Make sure the container has a config when calling Execute() -- Stéphane Graber Tue, 09 Apr 2019 14:14:00 -0400 ** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1816642 Title: SRU of LXC 2.0.11 Status in golang-gopkg-lxc-go-lxc.v2 package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in golang-gopkg-lxc-go-lxc.v2 source package in Trusty: Triaged Status in lxc source package in Trusty: Triaged Status in golang-gopkg-lxc-go-lxc.v2 source package in Xenial: Fix Released Status in lxc source package in Xenial: Fix Released Bug description: LXC upstream has released a new bugfix release for the LXC 2.0 LTS branch. This is version 2.0.10. Ubuntu never received 2.0.9 as an SRU, so the changelog for both of them can be found below: LXC 2.0.11: - autotools: handle getgrgid_r on bionic - autotools: add memory_utils.h to Makefile.am - change version to 2.0.11 in configure.ac LXC 2.0.10: - tools: allow lxc-attach to undefined containers - utils: move memfd_create() definition - utils: add lxc_cloexec() - utils: add lxc_make_tmpfile() - utils: add lxc_getpagesize() - utils: add lxc_safe_long_long() - utils: parse_byte_size_string() - utils: add lxc_find_next_power2() - namespace: use lxc_getpagesize() - lxc-debian: allow creating `testing` and `unstable` - Call lxc_config_define_load from lxc_execute again - Fix typo in lxc-net script - Add missing lxc_container_put - lxc-debian: don't write C.* locales to /etc/locale.gen - attach: correctly handle namespace inheritance - cgfsng: fix cgroup2 detection - cgroups: enable container without CAP_SYS_ADMIN - lxc-start: remove unnecessary checks - start: close non-needed file descriptors - handler: make name argument const - start: close data socket in parent - monitor: do not log useless warnings - network: reap child in all cases - conf: reap child in all cases - storage: switch to ext4 as default filesystem - tools: fix help output of lxc-create - attach: handle namespace inheritance - cgroups/cgfsng: keep mountpoint intact - cgroups/cgfsng: cgfsns_chown() -> cgfsng_chown() - cgroups/cgfsng: support MS_READONLY with cgroup ns - log: check for i/o error with vsnprintf() - cgroupfs/cgfsng: tweak logging - cgroups/cgfsng: remove is_lxcfs() - cgroups/cgfsng: fix get_controllers() for cgroup2 - cgroupfs/cgfsng: improve cgroup2 handling - config: remove SIGRTMIN+14 as lxc.signal.stop - commands: non-functional changes - console: non-functional changes - console: non-functional changes - lxc-test-unpriv: fix the overlayfs mount error - attach: allow attach with empty conf - tools/lxc_attach: removed api logging - console: fix console info message - Add missing dependency libunistring - cgroups/cgfsng: adapt to new cgroup2 delegation - console: report detach message on demand - lxccontainer: enable daemonized app containers - console: use correct escape sequence check - console: prepare for generic signal handler - console: exit mainloop on SIGTERM - commands: non-functional changes - lxccontainer: non-functional changes - commands: fix state socket implementation - lxc_init: set the control terminal in the child session - lxc-test-unpriv: check user existence before removing it - Fixed typo on lxc.spec.in - conf: move CAP_SYS_* definitions to utils.h - start.c: always switch uid and gid - Use AX_PTHREAD config script to detect pthread api - utils.h: Avoid duplicated sethostname implementation - tools/lxc_cgroup: remove internal logging - tools/lxc_autostart: remove internal logging - tools/lxc_clone: remove internal logging - tools/lxc_console: remove internal logging - tools/lxc_create: remove internal logging - tools/lxc_destroy: remove internal logging - tools/lxc_device: remove internal logging - tools/lxc_execute: removed internal logging - tools/lxc_freeze: remove internal logging - tools/lxc_info: removed internal logging - criu: detect veth name - lxccontainer: various container creation fixes - storage: remove unused declaration - tools/lxc_ls: remove internal logging - tools/lxc_copy: remove internal logging - tools/lxc_monitor: removed internal logging - tools/lxc_snapshot: removed internal logging - tools/lxc
[Touch-packages] [Bug 1816642] Update Released
The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1816642 Title: SRU of LXC 2.0.11 Status in golang-gopkg-lxc-go-lxc.v2 package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in golang-gopkg-lxc-go-lxc.v2 source package in Trusty: Triaged Status in lxc source package in Trusty: Triaged Status in golang-gopkg-lxc-go-lxc.v2 source package in Xenial: Fix Released Status in lxc source package in Xenial: Fix Released Bug description: LXC upstream has released a new bugfix release for the LXC 2.0 LTS branch. This is version 2.0.10. Ubuntu never received 2.0.9 as an SRU, so the changelog for both of them can be found below: LXC 2.0.11: - autotools: handle getgrgid_r on bionic - autotools: add memory_utils.h to Makefile.am - change version to 2.0.11 in configure.ac LXC 2.0.10: - tools: allow lxc-attach to undefined containers - utils: move memfd_create() definition - utils: add lxc_cloexec() - utils: add lxc_make_tmpfile() - utils: add lxc_getpagesize() - utils: add lxc_safe_long_long() - utils: parse_byte_size_string() - utils: add lxc_find_next_power2() - namespace: use lxc_getpagesize() - lxc-debian: allow creating `testing` and `unstable` - Call lxc_config_define_load from lxc_execute again - Fix typo in lxc-net script - Add missing lxc_container_put - lxc-debian: don't write C.* locales to /etc/locale.gen - attach: correctly handle namespace inheritance - cgfsng: fix cgroup2 detection - cgroups: enable container without CAP_SYS_ADMIN - lxc-start: remove unnecessary checks - start: close non-needed file descriptors - handler: make name argument const - start: close data socket in parent - monitor: do not log useless warnings - network: reap child in all cases - conf: reap child in all cases - storage: switch to ext4 as default filesystem - tools: fix help output of lxc-create - attach: handle namespace inheritance - cgroups/cgfsng: keep mountpoint intact - cgroups/cgfsng: cgfsns_chown() -> cgfsng_chown() - cgroups/cgfsng: support MS_READONLY with cgroup ns - log: check for i/o error with vsnprintf() - cgroupfs/cgfsng: tweak logging - cgroups/cgfsng: remove is_lxcfs() - cgroups/cgfsng: fix get_controllers() for cgroup2 - cgroupfs/cgfsng: improve cgroup2 handling - config: remove SIGRTMIN+14 as lxc.signal.stop - commands: non-functional changes - console: non-functional changes - console: non-functional changes - lxc-test-unpriv: fix the overlayfs mount error - attach: allow attach with empty conf - tools/lxc_attach: removed api logging - console: fix console info message - Add missing dependency libunistring - cgroups/cgfsng: adapt to new cgroup2 delegation - console: report detach message on demand - lxccontainer: enable daemonized app containers - console: use correct escape sequence check - console: prepare for generic signal handler - console: exit mainloop on SIGTERM - commands: non-functional changes - lxccontainer: non-functional changes - commands: fix state socket implementation - lxc_init: set the control terminal in the child session - lxc-test-unpriv: check user existence before removing it - Fixed typo on lxc.spec.in - conf: move CAP_SYS_* definitions to utils.h - start.c: always switch uid and gid - Use AX_PTHREAD config script to detect pthread api - utils.h: Avoid duplicated sethostname implementation - tools/lxc_cgroup: remove internal logging - tools/lxc_autostart: remove internal logging - tools/lxc_clone: remove internal logging - tools/lxc_console: remove internal logging - tools/lxc_create: remove internal logging - tools/lxc_destroy: remove internal logging - tools/lxc_device: remove internal logging - tools/lxc_execute: removed internal logging - tools/lxc_freeze: remove internal logging - tools/lxc_info: removed internal logging - criu: detect veth name - lxccontainer: various container creation fixes - storage: remove unused declaration - tools/lxc_ls: remove internal logging - tools/lxc_copy: remove internal logging - tools/lxc_monitor: removed internal logging - tools/lxc_snapshot: removed internal logging - tools/lxc_start: removed internal logging - tools/lxc_stop: removed internal logging - tools/lxc_top: removed
[Touch-packages] [Bug 1816642] Re: SRU of LXC 2.0.11
This bug was fixed in the package lxc - 2.0.11-0ubuntu1~16.04.3 --- lxc (2.0.11-0ubuntu1~16.04.3) xenial; urgency=medium * Cherry-pick upstream bugfix (fixes regression on attach with uid/gid): - attach: improve id switching - utils: make id switching functions return bool lxc (2.0.11-0ubuntu1~16.04.2) xenial; urgency=medium * Use clean LDFLAGS when building the static init.lxc, otherwise we end up with broken binaries on some architectures. lxc (2.0.11-0ubuntu1~16.04.1) xenial; urgency=medium * New upstream bugfix release (2.0.11) (LP: #1816642) - Security fix for CVE-2018-6556 (affecting 2.0.9+) - Mitigation for CVE-2019-5736 - Full changelog available at: https://discuss.linuxcontainers.org/t/lxc-2-0-11-has-been-released/4238 -- Stéphane Graber Tue, 09 Apr 2019 13:58:10 -0400 ** Changed in: lxc (Ubuntu Xenial) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6556 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-5736 -- 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/1816642 Title: SRU of LXC 2.0.11 Status in golang-gopkg-lxc-go-lxc.v2 package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in golang-gopkg-lxc-go-lxc.v2 source package in Trusty: Triaged Status in lxc source package in Trusty: Triaged Status in golang-gopkg-lxc-go-lxc.v2 source package in Xenial: Fix Released Status in lxc source package in Xenial: Fix Released Bug description: LXC upstream has released a new bugfix release for the LXC 2.0 LTS branch. This is version 2.0.10. Ubuntu never received 2.0.9 as an SRU, so the changelog for both of them can be found below: LXC 2.0.11: - autotools: handle getgrgid_r on bionic - autotools: add memory_utils.h to Makefile.am - change version to 2.0.11 in configure.ac LXC 2.0.10: - tools: allow lxc-attach to undefined containers - utils: move memfd_create() definition - utils: add lxc_cloexec() - utils: add lxc_make_tmpfile() - utils: add lxc_getpagesize() - utils: add lxc_safe_long_long() - utils: parse_byte_size_string() - utils: add lxc_find_next_power2() - namespace: use lxc_getpagesize() - lxc-debian: allow creating `testing` and `unstable` - Call lxc_config_define_load from lxc_execute again - Fix typo in lxc-net script - Add missing lxc_container_put - lxc-debian: don't write C.* locales to /etc/locale.gen - attach: correctly handle namespace inheritance - cgfsng: fix cgroup2 detection - cgroups: enable container without CAP_SYS_ADMIN - lxc-start: remove unnecessary checks - start: close non-needed file descriptors - handler: make name argument const - start: close data socket in parent - monitor: do not log useless warnings - network: reap child in all cases - conf: reap child in all cases - storage: switch to ext4 as default filesystem - tools: fix help output of lxc-create - attach: handle namespace inheritance - cgroups/cgfsng: keep mountpoint intact - cgroups/cgfsng: cgfsns_chown() -> cgfsng_chown() - cgroups/cgfsng: support MS_READONLY with cgroup ns - log: check for i/o error with vsnprintf() - cgroupfs/cgfsng: tweak logging - cgroups/cgfsng: remove is_lxcfs() - cgroups/cgfsng: fix get_controllers() for cgroup2 - cgroupfs/cgfsng: improve cgroup2 handling - config: remove SIGRTMIN+14 as lxc.signal.stop - commands: non-functional changes - console: non-functional changes - console: non-functional changes - lxc-test-unpriv: fix the overlayfs mount error - attach: allow attach with empty conf - tools/lxc_attach: removed api logging - console: fix console info message - Add missing dependency libunistring - cgroups/cgfsng: adapt to new cgroup2 delegation - console: report detach message on demand - lxccontainer: enable daemonized app containers - console: use correct escape sequence check - console: prepare for generic signal handler - console: exit mainloop on SIGTERM - commands: non-functional changes - lxccontainer: non-functional changes - commands: fix state socket implementation - lxc_init: set the control terminal in the child session - lxc-test-unpriv: check user existence before removing it - Fixed typo on lxc.spec.in - conf: move CAP_SYS_* definitions to utils.h - start.c: always switch uid and gid - Use AX_PTHREAD config script to detect pthread api - utils.h: Avoid duplicated sethostname implementation - tools/lxc_cgroup: remove internal logging - tools/lxc_autostart: remove internal logging - tools/lxc_clone: remove internal logging - tools/lxc_console: remove internal logging - tools/lxc_create: remove internal logging - tools/lxc_destroy: remove internal logging
[Touch-packages] [Bug 1825001] Re: Allow archives to send a 4xx response to tell apt to try again later
** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1825001 Title: Allow archives to send a 4xx response to tell apt to try again later Status in apt package in Ubuntu: New Bug description: As part of a broad plan to improve our ability to manage traffic to the archive servers, it would be useful if the archives could return a 4xx response to indicate to apt that they were over capacity and it should try again later, where later could be defined on the client side as several hours, the next day for unattended-upgrades runs, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825000] Re: Add ability for mirrors to distinguish interactive and non-interactive apt runs
** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1825000 Title: Add ability for mirrors to distinguish interactive and non-interactive apt runs Status in apt package in Ubuntu: New Bug description: As part of a larger scale plan to manage traffic to the main archive servers it would be useful if apt could provide a facility for us to identify interactive vs. non-interactive traffic on the server side, ideally via a header of some kind. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825000/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
$ dig phspi05.phs ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> phspi05.phs ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61787 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;phspi05.phs. IN A ;; Query time: 29 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Apr 17 10:08:48 BST 2019 ;; MSG SIZE rcvd: 40 $ dig phspi05.phs @192.168.2.1 ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> phspi05.phs @192.168.2.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21263 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;phspi05.phs. IN A ;; AUTHORITY SECTION: . 3600IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019041700 1800 900 604800 86400 ;; Query time: 20 msec ;; SERVER: 192.168.2.1#53(192.168.2.1) ;; WHEN: Wed Apr 17 10:10:11 BST 2019 ;; MSG SIZE rcvd: 115 Hmm... so that is curious... this is making me think, so I have another local host specified on the router DNS, but it is specified with then host and local domain, i.e. on the router I have: sjr05x 192.168.2.20 sjr05x.phs 192.168.2.20 And dig results: $ dig sjr05x ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> sjr05x ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 15618 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;sjr05x.IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Apr 17 10:15:06 BST 2019 ;; MSG SIZE rcvd: 35 $ dig sjr05x @192.168.2.1 ;; Warning: Message parser reports malformed message packet. ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> sjr05x @192.168.2.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25027 ;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: ddfb8b62c3075f35 (echoed) ;; QUESTION SECTION: ;sjr05x.IN A ;; ADDITIONAL SECTION: sjr05x. 199150 IN A 192.168.2.20 ;; Query time: 7 msec ;; SERVER: 192.168.2.1#53(192.168.2.1) ;; WHEN: Wed Apr 17 10:19:32 BST 2019 ;; MSG SIZE rcvd: 63 $ dig sjr05x.phs ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> sjr05x.phs ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4826 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;sjr05x.phs.IN A ;; ANSWER SECTION: sjr05x.phs. 6899IN A 192.168.2.20 ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Apr 17 10:20:16 BST 2019 ;; MSG SIZE rcvd: 55 $ dig sjr05x.phs @192.168.2.1 ;; Warning: Message parser reports malformed message packet. ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> sjr05x.phs @192.168.2.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52715 ;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: b00c84bd6596 (echoed) ;; QUESTION SECTION: ;sjr05x.phs.IN A ;; ADDITIONAL SECTION: sjr05x.phs. 199217 IN A 192.168.2.20 ;; Query time: 5 msec ;; SERVER: 192.168.2.1#53(192.168.2.1) ;; WHEN: Wed Apr 17 10:20:39 BST 2019 ;; MSG SIZE rcvd: 67 So is it perhaps that my naive expectation that without a domain the host is assumed to be local is not consistently followed by different programs/devices? Also I now realise that my laptop doesn't know what domain it is part of: $ domainname (none) but then neither does my desktop where the lookups work (not using networkmanager), and explicitly setting it seems to have no effect. -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Incomplete Bug description: Mint 19 (Ubuntu Bionic) Laptop so Using NetworkManager, and connecting wirelessly to LAN Upgraded from Mint 18.3 so using resolvconf... Versions: network-manager: 1.10.6-2ubuntu1.1 resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2 systemd: 237-3ubuntu10.15 dns is specified in NetworkMananager as 192.168.2.1 the dns is a router, and has static ips assigned to certain hosts on my lan... $cat resolv.conf nameserver 127.0.0.53 search phs options edns0 $ nsloo
[Touch-packages] [Bug 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces
Is the information provided already enough to change this report's status? I think we have provided details, as well as offered to give even more (thank you Joi!) if required, so it would be great to follow up on this. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1823871 Title: After unattended-upgrade of systemd IP configuration removed from interfaces Status in systemd package in Ubuntu: Incomplete Bug description: Info: Ubuntu Server 18.04 LTS, 4.15.0-43-generic, fresh installation (December, 2018). HP DL380 server I had this issue already twice in the past couple of months. After unattended upgrade of systemd my server's public IP address is removed from the interface. I statically configure the IP address using the interfaces file. I have opted out of the YML based network configuration. This is my apt history log: Start-Date: 2019-04-09 06:15:01 Commandline: /usr/bin/unattended-upgrade Upgrade: systemd-sysv:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:07 Start-Date: 2019-04-09 06:15:12 Commandline: /usr/bin/unattended-upgrade Upgrade: udev:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libudev1:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:56 Start-Date: 2019-04-09 06:15:59 Commandline: /usr/bin/unattended-upgrade Upgrade: libsystemd0:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libpam-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:16:15 After that my server was unavailable from the Internet. When I logged in via out of band management and simply brought down and up the interface everything went back to normal. As said above this is the second time I had this issue. Last time it was unattended upgrades and it was systemd again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
** Changed in: systemd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: New Bug description: Mint 19 (Ubuntu Bionic) Laptop so Using NetworkManager, and connecting wirelessly to LAN Upgraded from Mint 18.3 so using resolvconf... Versions: network-manager: 1.10.6-2ubuntu1.1 resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2 systemd: 237-3ubuntu10.15 dns is specified in NetworkMananager as 192.168.2.1 the dns is a router, and has static ips assigned to certain hosts on my lan... $cat resolv.conf nameserver 127.0.0.53 search phs options edns0 $ nslookup phspi05 Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find phspi05: SERVFAIL If I explicity specify the dns: $ nslookup phspi05 192.168.2.1 Server: 192.168.2.1 Address: 192.168.2.1#53 Non-authoritative answer: Name: phspi05 Address: 192.168.2.35 I get the correct ip address... Same with dig... I would expect that the nameserver set in network-manager would be used From tail of $ systemd-resolve --status Link 2 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.2.1 DNS Domain: phs So the dns address had been picked up from NetworkManager, but apparently is not being used... Thought it might be related to this bug: https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903 So installed the proposed fix, but no change. I also tried removing package resolvconf, again no change... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824998] Re: Zanata is messing up the translations
Thank you for your bug report, is the string in the upstream tarball? Could you explain what is happening exactly, is upstream important from fedora with those errors? Does upstream know about the issue? -- 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/1824998 Title: Zanata is messing up the translations Status in network-manager package in Ubuntu: New Bug description: Hi Today is actually impossible to keep NM translations in good shape since Zanata (a tool used in Fedora and Red Hat) is messing up the translations. Example: https://translations.launchpad.net/ubuntu/disco/+source/network- manager/+pots/networkmanager/es/870/+translate Which literally means: One of the functions of the swimming boat (3) is a function of the boat's control unit. Or translating "master" as "dominate" This is hilarous but also frustrating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1824998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822898] Re: wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i
** Changed in: openssl (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1822898 Title: wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Cosmic: Fix Committed Status in openssl source package in Disco: Fix Released Status in openssl package in Debian: Fix Released Bug description: [Impact] * fetch-url cannot use https protocol (no https preseeds) [Test case] * in d-i, mini.iso, tty try wget https://geoip.ubuntu.com/lookup it should succeed. [Solution] The required openssl.cnf configuration file is missing, needs to simply exists, even if it is empty. [Regression Potential] well, if one cannot download over https / init ssl library in d-i, it's hard to get openssl busted more than that. No code changes on the .deb side of things To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
Hi guys, This bug is still present on latest versions (seahorse 3.30). Why is assigned to chromium-browser package? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed Status in chromium-browser package in Ubuntu: Invalid Status in dbus package in Ubuntu: Triaged Status in flatpak package in Ubuntu: Fix Released Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
> $ dig phspi05.phs @192.168.2.1 ... > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21263 hmm, so, i'm confused now, in the description you said dig works when querying your router directly? I guess that's not the case? It certainly seems like this is not a issue with systemd - your problem appears to be with your router dns configuration. I'll mark this bug as invalid, but let me know if you disagree. > So is it perhaps that my naive expectation that without a domain the host is > assumed to be local is not consistently followed by different > programs/devices? Appending of the "search domains" is done only through the getaddrinfo() (and related) glibc functions. This is the call that uses the /etc/resolv.conf file for configuration to perform its lookup. You can see "man resolv.conf" for specific details on the process, but in most cases it will lookup the hostname you ask for first, and then if that fails it will try looking up the hostname using each 'search' domain you specify. Since modern systems using systemd almost always configure resolv.conf to send all traffic to the local stub resolver (i.e. 127.0.0.53), this in effect means systemd-resolved is responsible for actually talking to all upstream name servers. Note that any program that *does not* use getaddrinfo() completely bypasses this and is free to perform lookups however it wants; dig does just that, by querying *exactly* what you are searching for, to *exactly* the nameserver you specify. You can tell dig to use any search domains specified in /etc/resolv.conf, with the +search parameter; by default it does not use any search domains, and queries only what you ask it for. > Also I now realise that my laptop doesn't know what domain it is part of: > $ domainname > (none) Unless you don't have 'domain' or 'search' defined in /etc/resolv.conf, this doesn't matter for dns resolution. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Invalid Bug description: Mint 19 (Ubuntu Bionic) Laptop so Using NetworkManager, and connecting wirelessly to LAN Upgraded from Mint 18.3 so using resolvconf... Versions: network-manager: 1.10.6-2ubuntu1.1 resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2 systemd: 237-3ubuntu10.15 dns is specified in NetworkMananager as 192.168.2.1 the dns is a router, and has static ips assigned to certain hosts on my lan... $cat resolv.conf nameserver 127.0.0.53 search phs options edns0 $ nslookup phspi05 Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find phspi05: SERVFAIL If I explicity specify the dns: $ nslookup phspi05 192.168.2.1 Server: 192.168.2.1 Address: 192.168.2.1#53 Non-authoritative answer: Name: phspi05 Address: 192.168.2.35 I get the correct ip address... Same with dig... I would expect that the nameserver set in network-manager would be used From tail of $ systemd-resolve --status Link 2 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.2.1 DNS Domain: phs So the dns address had been picked up from NetworkManager, but apparently is not being used... Thought it might be related to this bug: https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903 So installed the proposed fix, but no change. I also tried removing package resolvconf, again no change... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)
This bug is still relevant for Bionic. Any info about possible backport? -- 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/1691908 Title: fstab binds appear as mounts (x-gvfs-hide is being ignored) Status in GLib: Expired Status in glib2.0 package in Ubuntu: Triaged Bug description: glib2 version 2.52.2+1+gb8bd46bc8-1 (possibly the version before it as well, I haven't tested) causes fstab binds to appear as mounts in Nautilus (and in Deepin Dock - Deepin is based on Gnome). Downgrading to glib2 and glib2-docs 2.52.0-1 resolves this behaviour. I first noted this bug behaviour here: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/452049 Details of my particular system and issue with what I tried to resolve it can be found here: https://bbs.archlinux.org/viewtopic.php?pid=1712030#p1712030 1. Not using Ubuntu. Deepin Desktop 15.4 (Gnome based) on Arch Linux. OS: Arch Linux Kernel: x86_64 Linux 4.10.13-1-ARCH Shell: bash 4.4.12 Resolution: 1920x1200 DE: Deepin 15.4 WM: Deepin WM WM Theme: Arc-Darker GTK Theme: Arc-Darker [GTK2/3] Icon Theme: deepin Font: Noto Sans 11 CPU: Intel Core i5-6500 @ 4x 3.6GHz [27.8°C] GPU: GeForce GTX 950 RAM: 2598MiB / 15990MiB 2. 2.52.2+1+gb8bd46bc8-1 (downgrading to 2.52.0-1 removed the problem). 3. Nautilus to list internal physical drives (my SSD and 1TB HDD) only. 4. Nautilus listed my system disk (as expected) but also listed all of my fstab binds as removable drives (Downloads, Music, Pictures, Videos and Documents although this was not listed as "Documents" but instead listed as the HDD label "Farsight"). Adding x-gvfs-hide did not hide those drives. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1691908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** Changed in: mesa (Ubuntu)
Status: New => Invalid
** Description changed:
- https://bugs.freedesktop.org/show_bug.cgi?id=110452
+ https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
totem crashed with signal 5
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
** Description changed:
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
- totem crashed with signal 5
+ Backtrace goes through:
+
+ totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
+ (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
+ (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
+ (MakeContextCurrent) -> Xlib (XError)
+
+ Ubuntu bug doesn't say anything about what's the use-case / when this
+ happens and whether it's reproducible (is it e.g. timing related), it
+ seems just some random crash that Apport collects.
+
+ In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell
that it was given invalid/bad context. Corresponding Mesa code:
+ ---
+if (gc) {
+ /* Attempt to bind the context. We do this before mucking with
+* gc and __glXSetCurrentContext to properly handle our state in
+* case of an error.
+*
+* If an error occurs, set the Null context since we've already
+* blown away our old context. The caller is responsible for
+* figuring out how to handle setting a valid context.
+*/
+ if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
+ __glXSetCurrentContextNull();
+ __glXUnlock();
+ __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
+ False);
+ return GL_FALSE;
+ }
+ ---
+
+ I.e. bug is in what is given to Mesa, not what Mesa does.
+
+ -> NOTOURBUG
+
+
+ To me it looks something that could happen when Totem is exiting, gst-vaapi
is trying to use resources that have already been freed, and X catching that
when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do
CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
** Also affects: gstreamer (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: gstreamer (Ubuntu)
** Also affects: gstreamer-vaapi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
Status in GStreamer:
Unknown
Status in Mesa:
Confirmed
Status in gstreamer-vaapi package in Ubuntu:
New
Status in mesa package in Ubuntu:
Invalid
Status in totem package in Ubuntu:
Co
[Touch-packages] [Bug 1005424] Re: 12.04 regression: Sierra Wireless 3G mini card modem fails to connect
I do not have access to the laptop anymore, and 12.04 is EOL anyway, so this bug report can be closed. ** Changed in: modemmanager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1005424 Title: 12.04 regression: Sierra Wireless 3G mini card modem fails to connect Status in modemmanager package in Ubuntu: Invalid Bug description: I have a Fujitsu Siemens Lifebook P8020 with a build in Sierra Wireless modem. In Ubuntu 10.10 this modem works out of the box, simply by following the 3G modem wizard and selecting my carrier (Sweden/Telia) the modem connects without problem. When I try to connect using the wizard (MM 0.5.2.0) in Ubuntu 12.04 the modem fails to connect. In the syslog I see: (ttyUSB3): device state change: prepare -> failed (reason 'modem- no-carrier') [40 120 25] As far as I can tell the same usb drivers are loaded in both 10.10 and 12.04, and it seems that the system tries to connect to the same usb port too (ttyUSB3) in both versions. So I can't spot anything obvious. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1005424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues #153
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
** Also affects: gstreamer via
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
Importance: Unknown
Status: Unknown
** Description changed:
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
(buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
(CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
(MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this
happens and whether it's reproducible (is it e.g. timing related), it
seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell
that it was given invalid/bad context. Corresponding Mesa code:
---
-if (gc) {
- /* Attempt to bind the context. We do this before mucking with
-* gc and __glXSetCurrentContext to properly handle our state in
-* case of an error.
-*
-* If an error occurs, set the Null context since we've already
-* blown away our old context. The caller is responsible for
-* figuring out how to handle setting a valid context.
-*/
- if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
- __glXSetCurrentContextNull();
- __glXUnlock();
- __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
- False);
- return GL_FALSE;
- }
+ if (gc) {
+ /* Attempt to bind the context. We do this before mucking with
+ * gc and __glXSetCurrentContext to properly handle our state in
+ * case of an error.
+ *
+ * If an error occurs, set the Null context since we've already
+ * blown away our old context. The caller is responsible for
+ * figuring out how to handle setting a valid context.
+ */
+ if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
+ __glXSetCurrentContextNull();
+ __glXUnlock();
+ __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
+ False);
+ return GL_FALSE;
+ }
---
I.e. bug is in what is given to Mesa, not what Mesa does.
-> NOTOURBUG
-
- To me it looks something that could happen when Totem is exiting, gst-vaapi
is trying to use resources that have already been freed, and X catching that
when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do
CommonMakeCurrent().
+ To me it looks something that could happen when Totem is exiting, gst-
+ vaapi is trying to use resources that have already been freed, and X
+ catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
+ ask libglvnd to do CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
Status in GStreamer:
Unknown
Status in Mesa:
Confirmed
Status in gstreamer-vaapi package in Ubuntu:
New
Status in mesa package in Ubuntu:
Invalid
Status in totem package in Ubuntu:
Confirmed
Bug description:
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/proble
[Touch-packages] [Bug 1825021] Re: apt's dpkgpm.cc WriteApportReport function should gather more data
** Tags added: id-5cb602c6889ce851761205ca
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1825021
Title:
apt's dpkgpm.cc WriteApportReport function should gather more data
Status in apt package in Ubuntu:
New
Bug description:
While fixing bug 1813464 it occurred to me that it is not obvious that
the dist-upgrader tarball includes its own copy of invoke-rc.d and
that this has been complicated to debug more than once. The apport
information in that report was gathered by apt's dpkgpm.cc code and I
think we should extend that to gather additional information from the
environment at the time that the package installation failed. For
example the dist-upgrader sets the following:
os.environ["PATH"] = "%s:%s" % (os.getcwd()+"/imported",
os.environ["PATH"])
Gathering path from the environment would have made diagnosing bug
1813464 a lot easier. I tested modifying dpkgpm.cc with the following:
if(const char* env_p = std::getenv("PATH"))
fprintf(report, "EnvPATH: %s\n", env_p);
I then installed the crash-in-postinst package from the daisy-plucker-
seeds PPA and received a crash report with the EnvPATH key and value.
Its worth noting that when apport gathers environment information only
a white listed set of keys is gathered to prevent disclosing
potentially sensitive information. So we should look at what
environment variables the dist-upgrader sets and gather those at a
minimum.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825021/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** Changed in: totem (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
Status in GStreamer:
Unknown
Status in Mesa:
Confirmed
Status in gstreamer-vaapi package in Ubuntu:
New
Status in mesa package in Ubuntu:
Invalid
Status in totem package in Ubuntu:
Invalid
Bug description:
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) ->
gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia
libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
(MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this
happens and whether it's reproducible (is it e.g. timing related), it
seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell
that it was given invalid/bad context. Corresponding Mesa code:
---
if (gc) {
/* Attempt to bind the context. We do this before mucking with
* gc and __glXSetCurrentContext to properly handle our state in
* case of an error.
*
* If an error occurs, set the Null context since we've already
* blown away our old context. The caller is responsible for
* figuring out how to handle setting a valid context.
*/
if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
__glXSetCurrentContextNull();
__glXUnlock();
__glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
False);
return GL_FALSE;
}
---
I.e. bug is in what is given to Mesa, not what Mesa does.
-> NOTOURBUG
To me it looks something that could happen when Totem is exiting, gst-
vaapi is trying to use resources that have already been freed, and X
catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
ask libglvnd to do CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814765] Re: [19.04 FEAT] zone awareness for lsmem / chmem - util-linux
** Tags added: id-5c59ddd4bebcb462311ad26e -- 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/1814765 Title: [19.04 FEAT] zone awareness for lsmem / chmem - util-linux Status in Ubuntu on IBM z Systems: Fix Released Status in util-linux package in Ubuntu: Fix Released Bug description: Description: Kernel version 4.12 will change the default zone for hotplug memory to the zone-normal. To add memory to the zone movable "online_movable" needs to be echoed into the state attribute of a memory segment. Currently chmem always echos "online" to enable a memory segment. This feature adds an option to lsmem and chmem to distinguish between zone-movable and zone-normal. Business Case: Ensure memory hotplug with enhanced upstream functionality Available with util-linux 2.32. Due to integration of 2.33 already in 19.04, this feature is only for completness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1814765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803998] Re: [19.04 FEAT] upgrade binutils >=2.32
** Tags added: id-5bf307a3e162ca3fefea5ae0 -- 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/1803998 Title: [19.04 FEAT] upgrade binutils >=2.32 Status in Ubuntu on IBM z Systems: Fix Released Status in binutils package in Ubuntu: Fix Released Bug description: Upgrade to new version of binutils >= 2.32 Available here: https://www.gnu.org/software/binutils/ LP will be updated, once available upstream! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1803998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY
** Tags added: id-5c51b3a3cb40343530f1abbd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://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 1786574] Re: remove i2c-i801 from blacklist
@AaronMa, after recent updates and new kernel 5.0.0-13-generic , I can't reproduce the issue again. On Apr 17 2019, at 12:25 pm, AaronMa wrote: > @Khairul > > Please try passing "psmouse.synaptics_intertouch=0" in kernel parameter. > If it works, I will send a patch to mainline kernel. > Thanks, > Aaron > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1786574 > > Title: > remove i2c-i801 from blacklist > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: In Progress Status in OEM Priority Project: New Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Xenial: In Progress Status in kmod source package in Bionic: In Progress Status in kmod source package in Cosmic: In Progress Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** Changed in: gstreamer
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
Status in GStreamer:
New
Status in Mesa:
Confirmed
Status in gstreamer-vaapi package in Ubuntu:
New
Status in mesa package in Ubuntu:
Invalid
Status in totem package in Ubuntu:
Invalid
Bug description:
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) ->
gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia
libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
(MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this
happens and whether it's reproducible (is it e.g. timing related), it
seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell
that it was given invalid/bad context. Corresponding Mesa code:
---
if (gc) {
/* Attempt to bind the context. We do this before mucking with
* gc and __glXSetCurrentContext to properly handle our state in
* case of an error.
*
* If an error occurs, set the Null context since we've already
* blown away our old context. The caller is responsible for
* figuring out how to handle setting a valid context.
*/
if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
__glXSetCurrentContextNull();
__glXUnlock();
__glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
False);
return GL_FALSE;
}
---
I.e. bug is in what is given to Mesa, not what Mesa does.
-> NOTOURBUG
To me it looks something that could happen when Totem is exiting, gst-
vaapi is trying to use resources that have already been freed, and X
catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
ask libglvnd to do CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792934] Re: symlink loop detected in path 'usr/share/doc/module-init-tools/changelog.Debian.gz'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kmod (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1792934 Title: symlink loop detected in path 'usr/share/doc/module-init- tools/changelog.Debian.gz' Status in kmod package in Ubuntu: Confirmed Bug description: I ran debsums -ac and it printed this error debsums: Error: symlink loop detected in path 'usr/share/doc /module-init-tools/changelog.Debian.gz'. Please file a bug again module-init-tools. So here I am, filing a bug against module-init-tools. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: module-init-tools 24-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Mon Sep 17 16:13:36 2018 InstallationDate: Installed on 2012-11-02 (2144 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: LC_CTYPE=lt_LT.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kmod UpgradeStatus: Upgraded to bionic on 2018-09-16 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1792934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825188] [NEW] Just upgraded to ubunt 18 and now ulimit -n changes hard and soft limits
Public bug reported: I recently upgraded from Ubuntu 14 to 18 and now I can't use ulimit -n to increase the allowed number of files open! This is a change from my previous version of Ubuntu. Lines from /etc/security/limits.conf jonesdc hardnofile 10 jonesdc softnofile 1 Setting in /etc/sysctl.conf # Max open files (system limit) fs.file-max = 10 When I first open a terminal if I type $ulimit -n 1000 then $ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) 1 pending signals (-i) 30927 max locked memory (kbytes, -l) 16384 max memory size (kbytes, -m) unlimited open files (-n) 1000 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30927 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited Now if I type $ulimit -n 999 and then try again $ulimit -n 1000 bash: ulimit: open files: cannot modify limit: Operation not permitted Looking further, it appears that ulimit -n changes both the hard and soft limits $ulimit -H -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30927 max locked memory (kbytes, -l) 16384 max memory size (kbytes, -m) unlimited open files (-n) 999 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) unlimited cpu time (seconds, -t) unlimited max user processes (-u) 30927 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1825188 Title: Just upgraded to ubunt 18 and now ulimit -n changes hard and soft limits Status in lightdm package in Ubuntu: New Bug description: I recently upgraded from Ubuntu 14 to 18 and now I can't use ulimit -n to increase the allowed number of files open! This is a change from my previous version of Ubuntu. Lines from /etc/security/limits.conf jonesdc hardnofile 10 jonesdc softnofile 1 Setting in /etc/sysctl.conf # Max open files (system limit) fs.file-max = 10 When I first open a terminal if I type $ulimit -n 1000 then $ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) 1 pending signals (-i) 30927 max locked memory (kbytes, -l) 16384 max memory size (kbytes, -m) unlimited open files (-n) 1000 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 30927 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited Now if I type $ulimit -n 999 and then try again $ulimit -n 1000 bash: ulimit: open files: cannot modify limit: Operation not permitted Looking further, it appears that ulimit -n changes both the hard and soft limits $ulimit -H -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 30927 max locked memory (kbytes, -l) 16384 max memory size (kbytes, -m) unlimited open files (-n) 999 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) unlimited cpu time (seconds, -t) unlimited max user processes (-u) 30927 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1825188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More h
[Touch-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** No longer affects: mesa
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
Status in GStreamer:
New
Status in gstreamer-vaapi package in Ubuntu:
New
Status in mesa package in Ubuntu:
Invalid
Status in totem package in Ubuntu:
Invalid
Bug description:
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) ->
gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia
libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
(MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this
happens and whether it's reproducible (is it e.g. timing related), it
seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell
that it was given invalid/bad context. Corresponding Mesa code:
---
if (gc) {
/* Attempt to bind the context. We do this before mucking with
* gc and __glXSetCurrentContext to properly handle our state in
* case of an error.
*
* If an error occurs, set the Null context since we've already
* blown away our old context. The caller is responsible for
* figuring out how to handle setting a valid context.
*/
if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
__glXSetCurrentContextNull();
__glXUnlock();
__glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
False);
return GL_FALSE;
}
---
I.e. bug is in what is given to Mesa, not what Mesa does.
-> NOTOURBUG
To me it looks something that could happen when Totem is exiting, gst-
vaapi is trying to use resources that have already been freed, and X
catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
ask libglvnd to do CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824998] Re: Zanata is messing up the translations
Yes, the string is upstream. Yes, upstream was importing errors from Red Hat translators. I think is related with the Copy Trans feaure of Zanata. I reported this issue upstream a few minutes after reporting in Launchpad and here is his reply: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/160 I also contacted one of the developers of Zanata: Sachin Pathare. https://github.com/orgs/zanata/people Summary: "NetworkManager upstream does not use Zanata. We had a project at zanata.org [1], but that had severe issues, so we are back to po-files and git." "Red Hat uses Zanata internally, but afterwards they get manualy import the plain "po" file in git. Whatever Red Hat translators do, what matters is only what we import. The only upstream location for translations is git (and that's also the place to contribute translations)." ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues #160 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/160 -- 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/1824998 Title: Zanata is messing up the translations Status in network-manager package in Ubuntu: New Bug description: Hi Today is actually impossible to keep NM translations in good shape since Zanata (a tool used in Fedora and Red Hat) is messing up the translations. Example: https://translations.launchpad.net/ubuntu/disco/+source/network- manager/+pots/networkmanager/es/870/+translate Which literally means: One of the functions of the swimming boat (3) is a function of the boat's control unit. Or translating "master" as "dominate" This is hilarous but also frustrating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1824998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825194] [NEW] resolvconf is racy, which leads to broken resolv.conf in parallel calls
Public bug reported: It has been found that simultaneous calls to resolvconf can lead to inconsistent content in resolv.conf. For instance, no nameservers while NetworkManager has one in its record (see LP: #1824395): $ cat /run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN $ cat /run/resolvconf/interface/NetworkManager nameserver 192.168.1.6 nameserver 192.168.1.2 This can happen easily when calling "netplan apply", which can re-start both networkd and NM. resolvconf is called at that point by the "systemd-networkd-resolvconf-update.service" service, and also directly by NetworkManager, which leads to the situation described above. This is not surprising as there is nothing preventing different instances of resolvconf to access the same files. This sort of situation can be reproduced by running in a loop commands like: $ printf "\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd $ printf "nameserver 80.58.61.250\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd Eventually, this leads to a resolv.conf that is not consistent with the last run command. ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Description changed: It has been found that simultaneous calls to resolvconf can lead to inconsistent content in resolv.conf. For instance, no nameservers while NetworkManager has one in its record (see LP: #1824395): $ cat /run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN $ cat /run/resolvconf/interface/NetworkManager nameserver 192.168.1.6 nameserver 192.168.1.2 - This can happen easily when calling "netplan generate", which can re- - start both networkd and NM. resolvconf is called at that point by the + This can happen easily when calling "netplan apply", which can re-start + both networkd and NM. resolvconf is called at that point by the "systemd-networkd-resolvconf-update.service" service, and also directly by NetworkManager, which leads to the situation described above. This is not surprising as there is nothing preventing different instances of resolvconf to access the same files. This sort of situation can be reproduced by running in a loop commands like: $ printf "\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd $ printf "nameserver 80.58.61.250\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd Eventually, this leads to a resolv.conf that is not consistent with the last run command. -- 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/1825194 Title: resolvconf is racy, which leads to broken resolv.conf in parallel calls Status in resolvconf package in Ubuntu: New Bug description: It has been found that simultaneous calls to resolvconf can lead to inconsistent content in resolv.conf. For instance, no nameservers while NetworkManager has one in its record (see LP: #1824395): $ cat /run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN $ cat /run/resolvconf/interface/NetworkManager nameserver 192.168.1.6 nameserver 192.168.1.2 This can happen easily when calling "netplan apply", which can re- start both networkd and NM. resolvconf is called at that point by the "systemd-networkd-resolvconf-update.service" service, and also directly by NetworkManager, which leads to the situation described above. This is not surprising as there is nothing preventing different instances of resolvconf to access the same files. This sort of situation can be reproduced by running in a loop commands like: $ printf "\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd $ printf "nameserver 80.58.61.250\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd Eventually, this leads to a resolv.conf that is not consistent with the last run command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
Thankyou for all the attention to this and the explanations Dan, but now I am also confused... I tend to think that if my desktop is able to successfully lookup the host on the router (as per https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1817903) then I should expect that my laptop on the same lan, should also be able to do so, hence to me it is still a bug... So to clarify for me, if nothing else: If the router dns only has the hostname defined, i.e. phspi05 192.168.2.35 Lookups by the desktop (no NetworkManager, fixed IP) with resolv.conf containing: nameserver 192.168.2.1 nameserver 127.0.0.53 dig phspi05 = success dig phspi05.phs = fail Lookups by the laptop (with NetworkManager, dhcp assigned IP) with resolv.conf containing: nameserver 127.0.0.53 search phs dig phspi05 = fail dig phspi05.phs = fail dig phspi05 @192.168.2.1 = success dig phspi05.phs @192.168.2.1 = fail If I manually edit resolv.conf on the laptop so that it looks like nameserver 192.168.2.1 nameserver 127.0.0.53 search phs dig phspi05 = success So it seems to me that lookups by systemd-resolved are failing to lookup the hostname on the local DNS (even if this is by design) Whatever way I look at it, I have an inconsistency between computers on the same network. If the router has the hostname AND domainname defined: phspi05 192.168.2.35 phspi05.phs 192.168.2.35 then on the desktop dig phspi05 = success dig phspi05.phs = success on laptop dig phspi05 = fails dig phspi05.phs = success I guess I have a workaround to manually edit resolv.conf, and as I don't reboot that often it is not a big issue, but it doesn't feel right somehow. -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Invalid Bug description: Mint 19 (Ubuntu Bionic) Laptop so Using NetworkManager, and connecting wirelessly to LAN Upgraded from Mint 18.3 so using resolvconf... Versions: network-manager: 1.10.6-2ubuntu1.1 resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2 systemd: 237-3ubuntu10.15 dns is specified in NetworkMananager as 192.168.2.1 the dns is a router, and has static ips assigned to certain hosts on my lan... $cat resolv.conf nameserver 127.0.0.53 search phs options edns0 $ nslookup phspi05 Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find phspi05: SERVFAIL If I explicity specify the dns: $ nslookup phspi05 192.168.2.1 Server: 192.168.2.1 Address: 192.168.2.1#53 Non-authoritative answer: Name: phspi05 Address: 192.168.2.35 I get the correct ip address... Same with dig... I would expect that the nameserver set in network-manager would be used From tail of $ systemd-resolve --status Link 2 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.2.1 DNS Domain: phs So the dns address had been picked up from NetworkManager, but apparently is not being used... Thought it might be related to this bug: https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903 So installed the proposed fix, but no change. I also tried removing package resolvconf, again no change... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY
I'm also seeing this behavior in gnome-shell on disco. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825194] Re: resolvconf is racy, which leads to broken resolv.conf in parallel calls
** Patch added: "debdiff.patch" https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+attachment/5256569/+files/debdiff.patch -- 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/1825194 Title: resolvconf is racy, which leads to broken resolv.conf in parallel calls Status in resolvconf package in Ubuntu: New Bug description: It has been found that simultaneous calls to resolvconf can lead to inconsistent content in resolv.conf. For instance, no nameservers while NetworkManager has one in its record (see LP: #1824395): $ cat /run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN $ cat /run/resolvconf/interface/NetworkManager nameserver 192.168.1.6 nameserver 192.168.1.2 This can happen easily when calling "netplan apply", which can re- start both networkd and NM. resolvconf is called at that point by the "systemd-networkd-resolvconf-update.service" service, and also directly by NetworkManager, which leads to the situation described above. This is not surprising as there is nothing preventing different instances of resolvconf to access the same files. This sort of situation can be reproduced by running in a loop commands like: $ printf "\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd $ printf "nameserver 80.58.61.250\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd Eventually, this leads to a resolv.conf that is not consistent with the last run command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825194] Re: resolvconf is racy, which leads to broken resolv.conf in parallel calls
The attachment "debdiff.patch" seems to be a debdiff. The ubuntu- sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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/1825194 Title: resolvconf is racy, which leads to broken resolv.conf in parallel calls Status in resolvconf package in Ubuntu: New Bug description: It has been found that simultaneous calls to resolvconf can lead to inconsistent content in resolv.conf. For instance, no nameservers while NetworkManager has one in its record (see LP: #1824395): $ cat /run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN $ cat /run/resolvconf/interface/NetworkManager nameserver 192.168.1.6 nameserver 192.168.1.2 This can happen easily when calling "netplan apply", which can re- start both networkd and NM. resolvconf is called at that point by the "systemd-networkd-resolvconf-update.service" service, and also directly by NetworkManager, which leads to the situation described above. This is not surprising as there is nothing preventing different instances of resolvconf to access the same files. This sort of situation can be reproduced by running in a loop commands like: $ printf "\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd $ printf "nameserver 80.58.61.250\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd Eventually, this leads to a resolv.conf that is not consistent with the last run command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813464] Re: dist-upgrader tarball contains and uses an ancient version of invoke-rc.d
For the record I did a search of all the packages in the Ubuntu archive (for Bionic, Cosmic, and Disco) which used the new invoke-rc.d argument of "--skip-systemd-native" and only found sasl2-bin. Additionally, I also search all my local bug attachments (foundations-bugs subscribed packages) for issues with invoke-rc.d and didn't find any. Subsequently, I don't think this really needs SRU'ing for Bionic and Cosmic. $ export UST="/home/bdmurray/source-trees/ubuntu-security-tools"; export ARCH=amd64; for comp in main; do ~/source-trees/ubuntu-security-tools/repo-tools/for-archive /mnt/storage/archive-mirror/dists/disco/$comp/binary-$ARCH/Packages.gz /mnt/storage/archive-mirror/ $UST/repo-tools/for-archive-tools/unpack-control-search "skip-systemd-native"; done /mnt/storage/archive-mirror/pool/main/c/cyrus-sasl2/sasl2-bin_2.1.27+dfsg-1_amd64.deb ./postinst:invoke-rc.d --skip-systemd-native saslauthd $_dh_action || exit 1 ./prerm: invoke-rc.d --skip-systemd-native saslauthd stop || exit 1 [ 2:53PM 5093 ] [ bdmurray@bizarro:/mnt/storage/archive-mirror ] $ export UST="/home/bdmurray/source-trees/ubuntu-security-tools"; export ARCH=amd64; for comp in main; do ~/source-trees/ubuntu-security-tools/repo-tools/for-archive /mnt/storage/archive-mirror/dists/cosmic/$comp/binary-$ARCH/Packages.gz /mnt/storage/archive-mirror/ $UST/repo-tools/for-archive-tools/unpack-control-search "skip-systemd-native"; done [ 3:00PM 5094 ] [ bdmurray@bizarro:/mnt/storage/archive-mirror ] $ export UST="/home/bdmurray/source-trees/ubuntu-security-tools"; export ARCH=amd64; for comp in universe multiverse restricted; do ~/source-trees/ubuntu-security-tools/repo-tools/for-archive /mnt/storage/archive-mirror/dists/cosmic/$comp/binary-$ARCH/Packages.gz /mnt/storage/archive-mirror/ $UST/repo-tools/for-archive-tools/unpack-control-search "skip-systemd-native"; done [ 3:16PM 5095 ] [ bdmurray@bizarro:/mnt/storage/archive-mirror ] $ export UST="/home/bdmurray/source-trees/ubuntu-security-tools"; export ARCH=amd64; for comp in main universe multiverse restricted; do ~/source-trees/ubuntu-security-tools/repo-tools/for-archive /mnt/storage/archive-mirror/dists/bionic/$comp/binary-$ARCH/Packages.gz /mnt/storage/archive-mirror/ $UST/repo-tools/for-archive-tools/unpack-control-search "skip-systemd-native"; done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1813464 Title: dist-upgrader tarball contains and uses an ancient version of invoke- rc.d Status in cyrus-sasl2 package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in cyrus-sasl2 source package in Disco: Invalid Status in ubuntu-release-upgrader source package in Disco: Fix Released Bug description: I know that's not a good thing, but i try to upgrade versions by sSh ProblemType: Package DistroRelease: Ubuntu 19.04 Package: sasl2-bin 2.1.27+dfsg-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Sun Jan 27 09:34:34 2019 ErrorMessage: installed sasl2-bin package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.7, Python 3.7.2rc1, python3-minimal, 3.7.1-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.2ubuntu2 apt 1.8.0~beta1 SourcePackage: cyrus-sasl2 Title: package sasl2-bin 2.1.27+dfsg-1 failed to install/upgrade: installed sasl2-bin package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to disco on 2019-01-27 (0 days ago) mtime.conffile..etc.default.saslauthd: 2019-01-14T05:57:07.197338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1813464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812903] Re: Please remove libproxy1-plugin-mozjs/s390x on disco
This is done. libproxy1-plugin-mozjs | 0.4.15-5 | disco/universe | amd64, arm64, armhf, i386, ppc64el ** Changed in: libproxy (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1812903 Title: Please remove libproxy1-plugin-mozjs/s390x on disco Status in libproxy package in Ubuntu: Fix Released Bug description: Please remove the NBS libproxy1-plugiin-mozjs from s390x. It does not show up on https://people.canonical.com/~ubuntu-archive/nbs.html But it does show at https://people.canonical.com/~ubuntu-archive/proposed-migration/disco_uninst.txt The binary package is intentionally not built on s390x because mozjs60 is not available on s390x currently. $ rmadison libproxy1-plugin-mozjs libproxy1-plugin-mozjs | 0.4.15-3 | disco/universe | s390x libproxy1-plugin-mozjs | 0.4.15-5 | disco/universe | amd64, arm64, armhf, i386, ppc64el $ rmadison libproxy libproxy | 0.4.15-2 | cosmic | source libproxy | 0.4.15-5 | disco| source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/1812903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825212] [NEW] [SRU] openssl disco
Public bug reported: [Impact] * openssl has BUF_MEM regression that may affect packages at runtime. * openssl has a regression of failing to initialize SSL context without openssl.cnf file [Test Case] * Compile an old r-cran-openssl and run its autopkgtest against the current & fixed openssl, it should fail and pass respectively * remove openssl.cnf and try to use curl https://www.ubuntu.com it should succeed [Regression Potential] * These are regressions in the 1.1.1 series, witch patches cherrypicked from openssl stable branch and the same patches were uploaded into Debian. * The above two issues may continue to persist ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1825212 Title: [SRU] openssl disco Status in openssl package in Ubuntu: New Bug description: [Impact] * openssl has BUF_MEM regression that may affect packages at runtime. * openssl has a regression of failing to initialize SSL context without openssl.cnf file [Test Case] * Compile an old r-cran-openssl and run its autopkgtest against the current & fixed openssl, it should fail and pass respectively * remove openssl.cnf and try to use curl https://www.ubuntu.com it should succeed [Regression Potential] * These are regressions in the 1.1.1 series, witch patches cherrypicked from openssl stable branch and the same patches were uploaded into Debian. * The above two issues may continue to persist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1825212/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809819] Re: Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument
** Description changed: Ubuntu will not unlock non-root LUKS devices (with the same passphrase) when booting without "splash" kernel argument. Please see the video I've recorded (in VirtualBox) - https://my.nixaid.com/s/epxpwHckGipcB6D + https://my.nixaid.com/s/odG8zEJ2Z75TdHG It feels like systemd-ask-password-plymouth is trying to use the same passphrase to unlock the rest of the LUKS devices, whilst systemd-ask- password-console isn't. Ubuntu 18.04.1 64-bit. /etc/crypttab: sda5_crypt UUID=5ba77327-4680-45d1-ba03-ab1b4fc12abb none luks,discard c4129022-9a34-4eee-9971-0464d92881e0 UUID=c4129022-9a34-4eee-9971-0464d92881e0 none luks luks-b7e017d7-53c4-4503-b376-c62a1d383f17 UUID=b7e017d7-53c4-4503-b376-c62a1d383f17 none luks -- 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/1809819 Title: Ubuntu will not unlock non-root LUKS devices when booting without "splash" kernel argument Status in systemd package in Ubuntu: New Bug description: Ubuntu will not unlock non-root LUKS devices (with the same passphrase) when booting without "splash" kernel argument. Please see the video I've recorded (in VirtualBox) https://my.nixaid.com/s/odG8zEJ2Z75TdHG It feels like systemd-ask-password-plymouth is trying to use the same passphrase to unlock the rest of the LUKS devices, whilst systemd-ask- password-console isn't. Ubuntu 18.04.1 64-bit. /etc/crypttab: sda5_crypt UUID=5ba77327-4680-45d1-ba03-ab1b4fc12abb none luks,discard c4129022-9a34-4eee-9971-0464d92881e0 UUID=c4129022-9a34-4eee-9971-0464d92881e0 none luks luks-b7e017d7-53c4-4503-b376-c62a1d383f17 UUID=b7e017d7-53c4-4503-b376-c62a1d383f17 none luks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1809819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825194] Re: resolvconf is racy, which leads to broken resolv.conf in parallel calls
@Alfonso What's the use case for calling 'netplan apply' in this scenario? Is NM the configured as the netplan renderer? Is there ever a case where "systemd-networkd-resolvconf-update.service" can call resolvconf even though NM is the renderer from the start (i.e. there's no transition from networkd to NM)? I've always contended that mixing two network management services on the same device was asking for trouble... -- 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/1825194 Title: resolvconf is racy, which leads to broken resolv.conf in parallel calls Status in resolvconf package in Ubuntu: New Bug description: It has been found that simultaneous calls to resolvconf can lead to inconsistent content in resolv.conf. For instance, no nameservers while NetworkManager has one in its record (see LP: #1824395): $ cat /run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN $ cat /run/resolvconf/interface/NetworkManager nameserver 192.168.1.6 nameserver 192.168.1.2 This can happen easily when calling "netplan apply", which can re- start both networkd and NM. resolvconf is called at that point by the "systemd-networkd-resolvconf-update.service" service, and also directly by NetworkManager, which leads to the situation described above. This is not surprising as there is nothing preventing different instances of resolvconf to access the same files. This sort of situation can be reproduced by running in a loop commands like: $ printf "\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd $ printf "nameserver 80.58.61.250\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd Eventually, this leads to a resolv.conf that is not consistent with the last run command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues #143
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
** Description changed:
- https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
(DUPLICATE OF
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 )
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
(buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
(CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
(MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this
happens and whether it's reproducible (is it e.g. timing related), it
seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell
that it was given invalid/bad context. Corresponding Mesa code:
---
if (gc) {
/* Attempt to bind the context. We do this before mucking with
* gc and __glXSetCurrentContext to properly handle our state in
* case of an error.
*
* If an error occurs, set the Null context since we've already
* blown away our old context. The caller is responsible for
* figuring out how to handle setting a valid context.
*/
if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
__glXSetCurrentContextNull();
__glXUnlock();
__glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
False);
return GL_FALSE;
}
---
I.e. bug is in what is given to Mesa, not what Mesa does.
-> NOTOURBUG
To me it looks something that could happen when Totem is exiting, gst-
vaapi is trying to use resources that have already been freed, and X
catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
ask libglvnd to do CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
** No longer affects: gstreamer
** Also affects: totem via
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
Importance: Unknown
Status: Unknown
** Description changed:
- https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
(DUPLICATE OF
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 )
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 DUPLICATE
OF:
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
+
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
(buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
(CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
(MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this
happens and whether it's reproducible (is it e.g. timing related), it
seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell
that it was given invalid/bad context. Corresponding Mesa code:
---
if (gc) {
/* Attempt to bind the context. We do this before mucking with
* gc and __glXSetCurrentContext to properly handle our state in
* case of an error.
*
* If an error occurs, set the Null context since we've already
[Touch-packages] [Bug 1656100] Re: Unable to remove signing keys using gnome-software-properties
On Ubuntu 18.04 (Long Term Support release), software-properties is only available up to version 0.96.24.32.7 from bionic-updates and version 0.96.30 is not available. When will this be available for 18.04, since this is the LTS release? -- 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/1656100 Title: Unable to remove signing keys using gnome-software-properties Status in Ubuntu GNOME: Invalid Status in software-properties package in Ubuntu: Fix Released Bug description: I have found that on Ubuntu GNOME 16.10 with GNOME 3.22 that I am unable to remove signing keys in the Authentication tab. If I select a key I wish to remove and click the Remove button, either nothing will happen, or it will ask me for authentication, upon giving it the correct password all that will happen is it will deselect the key I select, but at no point will it actually remove it, which is rather annoying. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: software-properties-gtk 0.96.24.7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jan 12 21:35:55 2017 InstallationDate: Installed on 2017-01-09 (3 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1656100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1020756] Re: GtkTreeView keyboard binding are not intituive
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnucash (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1020756 Title: GtkTreeView keyboard binding are not intituive Status in GTK+: Expired Status in gnucash package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Bug description: Most GUIs, like MacOS X, Microsoft Windows and Qt handle the keyboard bindings for its treeviews in the same way: user can easily expand, collapse and move into tree nodes using only the arrow keys. In Gtk+, however, is quite different. User needs to press "plus" and "minus" key to collapse and expand nodes, leaving Right and Left arrows with essentially null functionality. Well yeah, that keys allow to move horizontally into row cells. Seeing many of the applications written using Gtk+, there are not many cases where user find useful moving horizontally across the row with the keyboard, most GtkTreeView that I see are simple and used only to show information. So I guess the current GtkTreeView behaviour is crazy, not useful in most cases, goes against intuition and against good User Experience. I'm really not familiar with Gtk+ programming but, as user, I find this "bug" extremely annoying in my day to day. So, I make some changes in Gtk+ to enhance (from my point of view) the behavior of GtkTreeView with the keyboard. The attached patch to the 3.4 branch modifies the default GtkTreeView behaviour with the keyboard, expanding nodes with the right arrow and collapsing it with left arrow, selecting parent and child nodes when appropriate: - When user press Left on a collapsed node, Gtk+ select the parent node. - When user press right on an expanded node, Gtk+ select the first child node. Users that want to navigate into cells horizontally (as I can see, a non frecuent use case) will need to press Ctrl+. Users can still move to the parent node with the Backspace key, without collapsing anything. I don't know exactly if this behavior change break some expected behavior to application programmer, I hope not. A last question, Why Gtk+ programmers implemented the current GtkTreeView behavior knowing the big difference with other tested GUIs? Best Regards! To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1020756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770792] Re: Clean up sync blacklist
You've dropped ccsm from the blacklist, but the sole binary package built from ccsm in Debian comes from compiz source in Ubuntu; I think this needs to be retained. You've traded icedove for thunderbird, but why should thunderbird be blacklisted? It's currently maintained in Ubuntu and not merged from Debian but I don't see any reason in principle that it couldn't be. Why are you dropping the blacklist of fbxkb, which was identified in the blacklist file as "obsolete GNOME panel applet"? I am satisfied that the rest of the changes here are correct, however I would want the rationales to be better documented in the commit history. I would ask you to please: - rebase on the current sync-blacklist branch (there is a conflict) - divide the commits up according to rationale (e.g., dropped because package removed from unstable; vs dropped because package is now in Ubuntu again; vs. reshuffling of file contents) - resubmit Or, you can punt this to me to do and I'll apply these changes when I have a chance. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1770792 Title: Clean up sync blacklist Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I am attaching a bzr branch here. Because the sync blacklist is a "junk" bzr repository, Launchpad isn't letting me make a merge proposal for it. I think it makes the blacklist easier to read and use if we get rid of all the old entries. I went through and verified that these removals were removed from Debian. There are a few exceptions (gdm3 and openssl1.0) which didn't need to be blacklisted anymore. I mostly ignored the Mozilla extensions. The Mozilla situation is interesting this year, but I'll save that discussion for later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1770792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770792] Re: Clean up sync blacklist
> Why are you dropping the blacklist of fbxkb, which was identified > in the blacklist file as "obsolete GNOME panel applet"? This is answered by LP: #1811718. But still, please make this rationale apparent in the commit history. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1770792 Title: Clean up sync blacklist Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: I am attaching a bzr branch here. Because the sync blacklist is a "junk" bzr repository, Launchpad isn't letting me make a merge proposal for it. I think it makes the blacklist easier to read and use if we get rid of all the old entries. I went through and verified that these removals were removed from Debian. There are a few exceptions (gdm3 and openssl1.0) which didn't need to be blacklisted anymore. I mostly ignored the Mozilla extensions. The Mozilla situation is interesting this year, but I'll save that discussion for later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1770792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** Project changed: totem => gstreamer
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
Status in GStreamer:
Unknown
Status in gstreamer-vaapi package in Ubuntu:
New
Status in mesa package in Ubuntu:
Invalid
Status in totem package in Ubuntu:
Invalid
Bug description:
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 DUPLICATE
OF:
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) ->
gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia
libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
(MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this
happens and whether it's reproducible (is it e.g. timing related), it
seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell
that it was given invalid/bad context. Corresponding Mesa code:
---
if (gc) {
/* Attempt to bind the context. We do this before mucking with
* gc and __glXSetCurrentContext to properly handle our state in
* case of an error.
*
* If an error occurs, set the Null context since we've already
* blown away our old context. The caller is responsible for
* figuring out how to handle setting a valid context.
*/
if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
__glXSetCurrentContextNull();
__glXUnlock();
__glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
False);
return GL_FALSE;
}
---
I.e. bug is in what is given to Mesa, not what Mesa does.
-> NOTOURBUG
To me it looks something that could happen when Totem is exiting, gst-
vaapi is trying to use resources that have already been freed, and X
catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
ask libglvnd to do CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies
In the time it took to try to port from aptdaemon to packagekit, packagekit has gone dead upstream, and we have been recommended not to port further work to it. Julian is now looking at providing an aptd as part of apt upstream that is fit for purpose. I am unsubscribing ubuntu-archive from this bug. -- 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/1673258 Title: Remove aptdaemon and drop or port its reverse-dependencies Status in aptdaemon package in Ubuntu: New Status in apturl package in Ubuntu: New Status in dell-recovery package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: New Status in lubuntu-software-center package in Ubuntu: Fix Released Status in mythbuntu-control-centre package in Ubuntu: Fix Released Status in sessioninstaller package in Ubuntu: New Status in software-properties package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntu-mate-welcome package in Ubuntu: New Status in update-manager package in Ubuntu: New Status in update-notifier package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: Fix Released Bug description: aptdaemon is abandoned and unmaintained. It has already been dropped from Debian, but there are several reverse dependencies keeping it in Ubuntu. I will add bug tasks for each of those dependencies, which should be ported or dropped themselves. Then we can get rid of aptdaemon too. See this mailing list thread for more details: https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
> So it seems to me that lookups by systemd-resolved > are failing to lookup the hostname on the local DNS > (even if this is by design) yes, this is by design. systemd-resolved never forwards "single label" addresses to upstream nameservers. > If the router has the hostname AND domainname defined: > phspi05 192.168.2.35 > phspi05.phs 192.168.2.35 you don't need the router configured to resolve the "single label" (without .phs) hostname (unless your router doesn't have 'phs' in its resolv.conf search list, and you need to look up the hostname from the router itself). > on laptop > dig phspi05 = fails stop using dig to debug your system. the behavior above is correct (dig *should* fail when querying the local systemd-resolved resolver without using .phs domain suffix). Instead try using a program that uses getaddrinfo(), like nslookup, ping, or even host. e.g.: $ host phspi05 > I guess I have a workaround to manually edit resolv.conf, and as I don't > reboot that often it is not a big issue, but it doesn't feel right somehow. it isn't right, and you don't need to. Just make sure your router delivers your domain as part of its dhcp reply, and you will be fine. Your resolv.conf will contain your local domain in its 'search' and all programs on your system using getaddrinfo() and friends will correctly look up any address with your domain appended. -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Invalid Bug description: Mint 19 (Ubuntu Bionic) Laptop so Using NetworkManager, and connecting wirelessly to LAN Upgraded from Mint 18.3 so using resolvconf... Versions: network-manager: 1.10.6-2ubuntu1.1 resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2 systemd: 237-3ubuntu10.15 dns is specified in NetworkMananager as 192.168.2.1 the dns is a router, and has static ips assigned to certain hosts on my lan... $cat resolv.conf nameserver 127.0.0.53 search phs options edns0 $ nslookup phspi05 Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find phspi05: SERVFAIL If I explicity specify the dns: $ nslookup phspi05 192.168.2.1 Server: 192.168.2.1 Address: 192.168.2.1#53 Non-authoritative answer: Name: phspi05 Address: 192.168.2.35 I get the correct ip address... Same with dig... I would expect that the nameserver set in network-manager would be used From tail of $ systemd-resolve --status Link 2 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.2.1 DNS Domain: phs So the dns address had been picked up from NetworkManager, but apparently is not being used... Thought it might be related to this bug: https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903 So installed the proposed fix, but no change. I also tried removing package resolvconf, again no change... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1816530] Re: DNS servers are not being set in the system correctly when you upgrade from 16.04 to 18.04
> it seems the problem is solved. great! > The question is whether the patch/fix/change is included into that ISO file > which > is used for upgrading the older ubuntu releases to the 18.04? I'm not sure what, if any, the bug was in the first place. If you can reproduce the failure, please feel free to update this bug. ** Changed in: resolvconf (Ubuntu) Status: Incomplete => Invalid ** Changed in: resolvconf (Ubuntu) Assignee: Dan Streetman (ddstreet) => (unassigned) -- 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/1816530 Title: DNS servers are not being set in the system correctly when you upgrade from 16.04 to 18.04 Status in resolvconf package in Ubuntu: Invalid Bug description: I upgraded my 16.04 to 18.04 before the official release. After the upgrade I noticed that I don't have internet access. The wired network and the wifi settings looked good, but the internet didn't work. After the login the system always switched itself into airplane mode. I tethered the network via USB and Bluetooth by my mobile but they also didn't work. I found a useful answer from @andrew-woodhead666: https://answers.launchpad.net/ubuntu/+question/665374 it seems this bug is still not fixed for the upgraded dists in the main release and affects a few dozens of ubuntu users. https://askubuntu.com/questions/1021884/no-internet-after-upgrade-from-16-04-to-18-04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1816530/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1756972] Re: RM: gcc-4.8: no longer used
Removed 2019-02-21: (From Debian) ROM; obsolete GCC version; Debian bug #821336 ** Changed in: gcc-4.8 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1756972 Title: RM: gcc-4.8: no longer used Status in gcc-4.8 package in Ubuntu: Fix Released Bug description: With the latest round of removals for Ubuntu Touch-related packages from bionic, gcc-4.8 no longer has any non-alternative reverse- depends. $ liblist='lib(x32|32|64|sf)?(gomp1|quadmath0|atomic1|itm1|objc4|stdc\+\+6|gfortran3|tsan0)' $ rmadison -s bionic -S gcc-4.8 | grep -E "\b$liblist[[:space:]]" $ reverse-depends src:gcc-4.8 | grep -vE "\b$liblist\)" Reverse-Depends === * gcc-4.8-doc (for gcc-4.8-base) * libboost1.62-dev (for libstdc++-4.8-dev) * libboost1.65-dev (for libstdc++-4.8-dev) * nvidia-cuda-toolkit [amd64 ppc64el] (for gcc-4.8) * nvidia-cuda-toolkit [amd64 ppc64el] (for g++-4.8) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ We should drop it from the archive for 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1756972/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1816530] Re: DNS servers are not being set in the system correctly when you upgrade from 16.04 to 18.04
I don't know whether I find time to install a 16.04 then upgrade it to 18.04, but as you can see, many people were affected. Check the number of the visitors and the comments: https://askubuntu.com/questions/1021884/no-internet-after-upgrade-from-16-04-to-18-04 -- 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/1816530 Title: DNS servers are not being set in the system correctly when you upgrade from 16.04 to 18.04 Status in resolvconf package in Ubuntu: Invalid Bug description: I upgraded my 16.04 to 18.04 before the official release. After the upgrade I noticed that I don't have internet access. The wired network and the wifi settings looked good, but the internet didn't work. After the login the system always switched itself into airplane mode. I tethered the network via USB and Bluetooth by my mobile but they also didn't work. I found a useful answer from @andrew-woodhead666: https://answers.launchpad.net/ubuntu/+question/665374 it seems this bug is still not fixed for the upgraded dists in the main release and affects a few dozens of ubuntu users. https://askubuntu.com/questions/1021884/no-internet-after-upgrade-from-16-04-to-18-04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1816530/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734568] Re: Please remove obsolete Android packages from Ubuntu
Removing packages from disco: android-audiosystem 1.8+13.10.20130807-0ubuntu1 in disco libandroid-audiosystem-asound2 1.8+13.10.20130807-0ubuntu1 in disco armhf libandroid-audiosystem-asound2 1.8+13.10.20130807-0ubuntu1 in disco i386 libwaudio1 1.8+13.10.20130807-0ubuntu1 in disco armhf libwaudio1 1.8+13.10.20130807-0ubuntu1 in disco i386 libwaudio1-dev 1.8+13.10.20130807-0ubuntu1 in disco armhf libwaudio1-dev 1.8+13.10.20130807-0ubuntu1 in disco i386 Comment: Ubuntu-specific, no uploads since 2013, unmaintained; LP: #1734568 1 package successfully removed. ** Changed in: android-audiosystem (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1734568 Title: Please remove obsolete Android packages from Ubuntu Status in android-audiosystem package in Ubuntu: Fix Released Status in android-headers package in Ubuntu: New Status in android-src-vendor package in Ubuntu: Fix Released Status in wpa package in Ubuntu: Triaged Bug description: Ubuntu has a few Android-related packages that were never in Debian and are no longer maintained by anyone. Please remove them from Ubuntu disco. $ reverse-depends src:android-src-vendor No reverse dependencies found $ reverse-depends -b src:android-src-vendor No reverse dependencies found $ reverse-depends src:android-audiosystem No reverse dependencies found $ reverse-depends -b src:android-audiosystem No reverse dependencies found $ reverse-depends src:android-headers No reverse dependencies found $ reverse-depends -b src:android-headers Reverse-Build-Depends = * wpa (for android-headers) WPA source package would need to first drop: - debian/patches/android_hal_fw_path_change.patch: add a DBus method for requesting a firmware change when working with the Android HAL; this is used to set a device in P2P or AP mode; conditional to CONFIG_ANDROID_HAL being enabled. - debian/config/wpasupplicant/linux: enable CONFIG_ANDROID_HAL. - debian/control: Build-Depends on android-headers to get the required wifi headers for the HAL support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-audiosystem/+bug/1734568/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734568] Re: Please remove obsolete Android packages from Ubuntu
Removing packages from disco: android-src-vendor 7-0ubuntu1 in disco android-src-vendor 7-0ubuntu1 in disco amd64 android-src-vendor 7-0ubuntu1 in disco arm64 android-src-vendor 7-0ubuntu1 in disco armhf android-src-vendor 7-0ubuntu1 in disco i386 android-src-vendor 7-0ubuntu1 in disco ppc64el android-src-vendor 7-0ubuntu1 in disco s390x Comment: Ubuntu-specific, no uploads since 2014, unmaintained; LP: #1734568 1 package successfully removed. ** Changed in: android-src-vendor (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1734568 Title: Please remove obsolete Android packages from Ubuntu Status in android-audiosystem package in Ubuntu: Fix Released Status in android-headers package in Ubuntu: New Status in android-src-vendor package in Ubuntu: Fix Released Status in wpa package in Ubuntu: Triaged Bug description: Ubuntu has a few Android-related packages that were never in Debian and are no longer maintained by anyone. Please remove them from Ubuntu disco. $ reverse-depends src:android-src-vendor No reverse dependencies found $ reverse-depends -b src:android-src-vendor No reverse dependencies found $ reverse-depends src:android-audiosystem No reverse dependencies found $ reverse-depends -b src:android-audiosystem No reverse dependencies found $ reverse-depends src:android-headers No reverse dependencies found $ reverse-depends -b src:android-headers Reverse-Build-Depends = * wpa (for android-headers) WPA source package would need to first drop: - debian/patches/android_hal_fw_path_change.patch: add a DBus method for requesting a firmware change when working with the Android HAL; this is used to set a device in P2P or AP mode; conditional to CONFIG_ANDROID_HAL being enabled. - debian/config/wpasupplicant/linux: enable CONFIG_ANDROID_HAL. - debian/control: Build-Depends on android-headers to get the required wifi headers for the HAL support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-audiosystem/+bug/1734568/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734568] Re: Please remove obsolete Android packages from Ubuntu
wpa still has a build-dependency on android-headers. ** Changed in: wpa (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1734568 Title: Please remove obsolete Android packages from Ubuntu Status in android-audiosystem package in Ubuntu: Fix Released Status in android-headers package in Ubuntu: New Status in android-src-vendor package in Ubuntu: Fix Released Status in wpa package in Ubuntu: Triaged Bug description: Ubuntu has a few Android-related packages that were never in Debian and are no longer maintained by anyone. Please remove them from Ubuntu disco. $ reverse-depends src:android-src-vendor No reverse dependencies found $ reverse-depends -b src:android-src-vendor No reverse dependencies found $ reverse-depends src:android-audiosystem No reverse dependencies found $ reverse-depends -b src:android-audiosystem No reverse dependencies found $ reverse-depends src:android-headers No reverse dependencies found $ reverse-depends -b src:android-headers Reverse-Build-Depends = * wpa (for android-headers) WPA source package would need to first drop: - debian/patches/android_hal_fw_path_change.patch: add a DBus method for requesting a firmware change when working with the Android HAL; this is used to set a device in P2P or AP mode; conditional to CONFIG_ANDROID_HAL being enabled. - debian/config/wpasupplicant/linux: enable CONFIG_ANDROID_HAL. - debian/control: Build-Depends on android-headers to get the required wifi headers for the HAL support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-audiosystem/+bug/1734568/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457400] Re: reduce 90s session kill timeout if the session does not shutdown cleanly
I also experienced "A stop job is running for Session c2 ... / 1min 30 s)". Newbies (like me) might need to know that in a fresh install of Ubuntu 16.04, the file /etc/systemd/system.conf has (almost) all lines commented out with a # . So, in addition to changing the number in the line #DefaultTimeoutStopSec=90 , one must also remove the # at the beginning of the line, to uncomment it. Also, before I changed the conf file, I had fast restarts sometimes by logging out before I restarted. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1457400 Title: reduce 90s session kill timeout if the session does not shutdown cleanly Status in lvm2 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently onwards the ubuntu is taking long to shut down nearly 1:30 minutes. I checked the shutdown log messages and I get the follow message. A stop job is running for Session c2 of user * (25s/ 1min 30 s) It count downs till 1:30 minutes and then shutdown the machine. Why is it happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1457400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 486154] Re: System beep broken in Karmic despite heroic efforts to fix it
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-lts-xenial (Ubuntu) Status: New => Confirmed -- 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/486154 Title: System beep broken in Karmic despite heroic efforts to fix it Status in Metacity: New Status in libcanberra package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Confirmed Status in metacity package in Ubuntu: Triaged Status in pulseaudio package in Ubuntu: Invalid Bug description: Between Jaunty and Karmic, a number of changes were made to keep the PC speaker from beeping. As part of this, system bell events are now captured by metacity, which uses libcanberra to play a sound. For users without speakers, this fails to be useful. The current setup makes restoring the old behavior extremely difficult. The absolute show stopper is that metacity traps audible system bell events. This behavior is, as best we can tell, not configurable. The attached patch keeps metacity from capturing system bell events. It also removes the sound playback capability. As Lucid will be using pulse audio's module-x11-bell to play sounds for system bell events, it is not necessary for this capability to be in metacity. Additionally, this removes the discrepancy between metacity's and compiz's handling of system bell events. There are several other difficulties in enabling the system bell: 1) Even if it is taken out of the blacklist, the pcspkr module may not load properly. Another modprobe may be necessary to get it loaded. See bug #398161. 2) Something in Gnome's startup does the equivalent of `xset b off`, so `xset b on` must be run on every login. (Note that bug #280767 keeps you from setting the bell volume with xset.) 3) A number of settings in gnome-terminal and gconf may keep the shell from sounding system bell events. Comments #28, #34, and #50 give more detailed summaries of the various problems. To manage notifications about this bug go to: https://bugs.launchpad.net/metacity/+bug/486154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected
Do you need any other input to get a fix in for this? I've tried a number of different 'model' settings for the ALC256 to try to get this to work to no avail. -- 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/1807138 Title: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Running the command alsamixer allows me to manually increase the sound levels for the headset, and sound plays properly through them. This requires me to disable the auto-mute feature. I haven't rebooted my system yet to see if this is permanent. But the UI doesn't show the heaphones at all and only sends sound through the main speakers of the laptop. ➜ ~ lspci -nnk | grep -i -A7 audio 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 ➜ ~ cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC256 Codec: Intel Kabylake HDMI Using for example pavucontrol allows me to select the headphone, which are marked as unplugged, and I can play audio through them as long as I keep the application open. If I reboot or close pavucontrol, everything is back to the original state and only the speakers work. Additional Information: ➜ ~ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 What I expect to happen: When I plug in my headphones, Ubuntu and the UI should see them and automatically redirect all sound through them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: olivar 8320 F...m pulseaudio /dev/snd/controlC0: olivar 8320 F pulseaudio CurrentDesktop: X-Cinnamon Date: Thu Dec 6 13:02:14 2018 InstallationDate: Installed on 2018-11-21 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: Razer dmi.bios.version: 01.01 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade dmi.product.version: 1.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
Thanks again Dan for taking the time to explain. > stop using dig to debug your system. Sorry thought I was using dig at your request... I was originally using nslookup and ping to find out why I couldn't browse to the server on phspi05 (phspi05 is actually controlling the heating and cooling in my glasshouse) and confusingly to me they give different results, ping often works when nslookup fails (as is currently the case on the desktop) > you don't need the router configured to resolve the "single label" (without > .phs) hostname ... I have managed to telnet into the router: # cat /etc/resolv.conf domain phs nameserver 208.67.222.222 nameserver 212.159.6.10 so clearly the domain is set, but if I remove the single label entry from the router even ping fails from the desktop (but still works on the laptop) and it seems that when providing an address via dhcp (e.g. to the laptop) the router puts both phs09 and phs09.phs in /etc/hosts, so I guess the router needs it... -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Invalid Bug description: Mint 19 (Ubuntu Bionic) Laptop so Using NetworkManager, and connecting wirelessly to LAN Upgraded from Mint 18.3 so using resolvconf... Versions: network-manager: 1.10.6-2ubuntu1.1 resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2 systemd: 237-3ubuntu10.15 dns is specified in NetworkMananager as 192.168.2.1 the dns is a router, and has static ips assigned to certain hosts on my lan... $cat resolv.conf nameserver 127.0.0.53 search phs options edns0 $ nslookup phspi05 Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find phspi05: SERVFAIL If I explicity specify the dns: $ nslookup phspi05 192.168.2.1 Server: 192.168.2.1 Address: 192.168.2.1#53 Non-authoritative answer: Name: phspi05 Address: 192.168.2.35 I get the correct ip address... Same with dig... I would expect that the nameserver set in network-manager would be used From tail of $ systemd-resolve --status Link 2 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.2.1 DNS Domain: phs So the dns address had been picked up from NetworkManager, but apparently is not being used... Thought it might be related to this bug: https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903 So installed the proposed fix, but no change. I also tried removing package resolvconf, again no change... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825194] Re: resolvconf is racy, which leads to broken resolv.conf in parallel calls
** Tags added: disco ** Tags added: rls-ee-incoming -- 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/1825194 Title: resolvconf is racy, which leads to broken resolv.conf in parallel calls Status in resolvconf package in Ubuntu: New Bug description: It has been found that simultaneous calls to resolvconf can lead to inconsistent content in resolv.conf. For instance, no nameservers while NetworkManager has one in its record (see LP: #1824395): $ cat /run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN $ cat /run/resolvconf/interface/NetworkManager nameserver 192.168.1.6 nameserver 192.168.1.2 This can happen easily when calling "netplan apply", which can re- start both networkd and NM. resolvconf is called at that point by the "systemd-networkd-resolvconf-update.service" service, and also directly by NetworkManager, which leads to the situation described above. This is not surprising as there is nothing preventing different instances of resolvconf to access the same files. This sort of situation can be reproduced by running in a loop commands like: $ printf "\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd $ printf "nameserver 80.58.61.250\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd Eventually, this leads to a resolv.conf that is not consistent with the last run command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY
kde neon: (ubuntu 18.04.2 with HWE stack) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()
** Changed in: gstreamer
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
Status in GStreamer:
Fix Released
Status in gstreamer-vaapi package in Ubuntu:
New
Status in mesa package in Ubuntu:
Invalid
Status in totem package in Ubuntu:
Invalid
Bug description:
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 DUPLICATE
OF:
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
---
Backtrace goes through:
totem -> clutter-gst (frame update) -> cogl (pipeline free) ->
gstreamer (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia
libglvd (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
(MakeContextCurrent) -> Xlib (XError)
Ubuntu bug doesn't say anything about what's the use-case / when this
happens and whether it's reproducible (is it e.g. timing related), it
seems just some random crash that Apport collects.
In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell
that it was given invalid/bad context. Corresponding Mesa code:
---
if (gc) {
/* Attempt to bind the context. We do this before mucking with
* gc and __glXSetCurrentContext to properly handle our state in
* case of an error.
*
* If an error occurs, set the Null context since we've already
* blown away our old context. The caller is responsible for
* figuring out how to handle setting a valid context.
*/
if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
__glXSetCurrentContextNull();
__glXUnlock();
__glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
False);
return GL_FALSE;
}
---
I.e. bug is in what is given to Mesa, not what Mesa does.
-> NOTOURBUG
To me it looks something that could happen when Totem is exiting, gst-
vaapi is trying to use resources that have already been freed, and X
catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
ask libglvnd to do CommonMakeCurrent().
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: totem 3.26.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 11:26:51 2018
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2017-05-04 (323 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 5
SourcePackage: totem
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
Title: totem crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
> Sorry thought I was using dig at your request... yes, sorry - dig is useful *but* it does only what you ask it specifically to do (i.e. lookup the specific hostname you ask it for, without appending any search domains to it). this is different from everything else on your system, which uses getaddrinfo(), which will append search domains listed in /etc/resolv.conf. > ping often works when nslookup fails i can't say *exactly* why this is, but I suspect it's because you had two nameservers listed in /etc/resolv.conf; your router (which *will* resolve the hostname without any domain suffix) and your local systemd- resolved resolver (which *will not* resolve the hostname without a domain suffix, since it won't pass the "single label" hostname to your router nameserver). i believe (don't remember the specifics of the glibc internals tho) that getaddrinfo() will do round-robin queries of each nameserver you list in /etc/resolv.conf, so it may be random chance that one thing looks up your host right, and the next request doesn't. > so clearly the domain is set that will let you do "single label" lookups *from your router only*. setting the router's search domain(s) will have *no effect at all* on lookups from any other system. just make sure: -your router's dhcp configuration includes your local subnet domain (i.e. provides it to your dhcp clients) -your router's dnsmasq (or whatever public nameserver program) has your local subnet hosts *including local subnet domain* defined -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Invalid Bug description: Mint 19 (Ubuntu Bionic) Laptop so Using NetworkManager, and connecting wirelessly to LAN Upgraded from Mint 18.3 so using resolvconf... Versions: network-manager: 1.10.6-2ubuntu1.1 resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2 systemd: 237-3ubuntu10.15 dns is specified in NetworkMananager as 192.168.2.1 the dns is a router, and has static ips assigned to certain hosts on my lan... $cat resolv.conf nameserver 127.0.0.53 search phs options edns0 $ nslookup phspi05 Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find phspi05: SERVFAIL If I explicity specify the dns: $ nslookup phspi05 192.168.2.1 Server: 192.168.2.1 Address: 192.168.2.1#53 Non-authoritative answer: Name: phspi05 Address: 192.168.2.35 I get the correct ip address... Same with dig... I would expect that the nameserver set in network-manager would be used From tail of $ systemd-resolve --status Link 2 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.2.1 DNS Domain: phs So the dns address had been picked up from NetworkManager, but apparently is not being used... Thought it might be related to this bug: https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903 So installed the proposed fix, but no change. I also tried removing package resolvconf, again no change... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
> setting the router's search domain(s) will have *no effect at all* on > lookups from any other system well - this does depend on your specific dns nameserver program and configuration; so I shouldn't say this without qualification :) It's possible to have your router's dns use local lookups, in various ways. -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Invalid Bug description: Mint 19 (Ubuntu Bionic) Laptop so Using NetworkManager, and connecting wirelessly to LAN Upgraded from Mint 18.3 so using resolvconf... Versions: network-manager: 1.10.6-2ubuntu1.1 resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2 systemd: 237-3ubuntu10.15 dns is specified in NetworkMananager as 192.168.2.1 the dns is a router, and has static ips assigned to certain hosts on my lan... $cat resolv.conf nameserver 127.0.0.53 search phs options edns0 $ nslookup phspi05 Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find phspi05: SERVFAIL If I explicity specify the dns: $ nslookup phspi05 192.168.2.1 Server: 192.168.2.1 Address: 192.168.2.1#53 Non-authoritative answer: Name: phspi05 Address: 192.168.2.35 I get the correct ip address... Same with dig... I would expect that the nameserver set in network-manager would be used From tail of $ systemd-resolve --status Link 2 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.2.1 DNS Domain: phs So the dns address had been picked up from NetworkManager, but apparently is not being used... Thought it might be related to this bug: https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903 So installed the proposed fix, but no change. I also tried removing package resolvconf, again no change... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies
** Changed in: ubuntu-mate-welcome (Ubuntu) Importance: Undecided => Wishlist ** Changed in: ubuntu-mate-welcome (Ubuntu) Status: New => Opinion -- 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/1673258 Title: Remove aptdaemon and drop or port its reverse-dependencies Status in aptdaemon package in Ubuntu: New Status in apturl package in Ubuntu: New Status in dell-recovery package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: New Status in lubuntu-software-center package in Ubuntu: Fix Released Status in mythbuntu-control-centre package in Ubuntu: Fix Released Status in sessioninstaller package in Ubuntu: New Status in software-properties package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: Fix Released Status in ubuntu-mate-welcome package in Ubuntu: Opinion Status in update-manager package in Ubuntu: New Status in update-notifier package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: Fix Released Bug description: aptdaemon is abandoned and unmaintained. It has already been dropped from Debian, but there are several reverse dependencies keeping it in Ubuntu. I will add bug tasks for each of those dependencies, which should be ported or dropped themselves. Then we can get rid of aptdaemon too. See this mailing list thread for more details: https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824103] Re: aplay record file failed always.
Retest the issue on Yoda2-2, image : Disco-Daily-20190416, it can not reproduce anymore. The test.wav file can record and play normally. When executing commands arecord and aplay, there is no error info feedback also. ** Tags added: cqa-verified -- 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/1824103 Title: aplay record file failed always. Status in pulseaudio package in Ubuntu: Fix Released Bug description: Test machine: ThinkPad X1 Carbon Image: Ubuntu Disco 19.04 CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (family: 0x6, model: 0x8e, stepping: 0xa) GPU: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) BIOS: N23ET55W (1.30 ) Steps: 1. Install image 19.04 2. Login as default user 3. Open a terminal and type "$ arecord abc.wav" 4. Say something and let laptop recorded your words 5. Cancel the record, please press 'Ctrl + C' 6. Please type "$ aplay abc.wav" in terminal Expected result: The voice played smoothly. Actual result: Step 3, u@u-ThinkPad-X1-Carbon-6th:~$ arecord abc.wav Recording WAVE 'abc.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono ^CAborted by signal Interrupt... arecord: pcm_read:2145: read error: Interrupted system call Step 6, u@u-ThinkPad-X1-Carbon-6th:~$ aplay abc.wav ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave aplay: main:828: audio open error: Device or resource busy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1824103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815987] Re: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Still no idea/help on this bug? -- 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/1815987 Title: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS Status in systemd package in Ubuntu: New Bug description: I am using Ubuntu 18.04LTS, fresh install from the summer, and tmpfiles won't launch since November. $ sudo systemctl start systemd-tmpfiles-setup Job for systemd-tmpfiles-setup.service failed because the control process exited with error code. See "systemctl status systemd-tmpfiles-setup.service" and "journalctl -xe" for details. $ sudo systemctl status systemd-tmpfiles-setup ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-02-14 19:48:36 EST; 8s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 28934 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE) Main PID: 28934 (code=exited, status=1/FAILURE) Feb 14 19:48:35 mythserver2018 systemd[1]: Starting Create Volatile Files and Directories... Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Feb 14 19:48:36 mythserver2018 systemd[1]: Failed to start Create Volatile Files and Directories. Looking at /var/lib/colord/icc: kris@mythserver2018:/var/lib/colord/icc$ ls -a . .. kris@mythserver2018:/var/lib/colord/icc$ I have also deleted these directories and rebuilt them, just to be sure - they are NOT symlinked and have no permission issues: kris@mythserver2018:/var/lib/systemd$ ls -l total 28 drwxr-xr-x 2 root root 4096 Feb 9 16:04 catalog drwxr-xr-x 2 root root 4096 Dec 28 07:04 coredump drwxr-xr-x 2 root root 4096 Jul 8 2018 coredumpold drwxr-xr-x 20 root root 4096 Feb 9 16:08 deb-systemd-helper-enabled drwxr-xr-x 2 root root 4096 Nov 14 18:31 deb-systemd-helper-masked -rw--- 1 root root 512 Feb 9 17:34 random-seed drwxr-xr-x 2 root root 4096 Jul 10 2018 timers lrwxrwxrwx 1 root root 27 Jul 8 2018 timesync -> ../private/systemd/timesync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799265] Re: avahi-daemon high cpu, unusable networking
** Changed in: avahi Status: Unknown => New -- 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/1799265 Title: avahi-daemon high cpu, unusable networking Status in Avahi: New Status in avahi package in Ubuntu: Triaged Bug description: Currently running Kubuntu 18.10, Dell XPS 13 9350 Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been consistently hampering network performance and using CPU for long periods of time. When booting machine from off state, avahi-daemon uses an entire CPU at max load for approx 10 minutes. During this time, internet connectivity via wifi is essentially unusable. The wifi connection is good, but it seems that http transactions are cutoff mid-way so no webpage is able to load. When waking from sleep, the avahi-daemon causes similar symptoms, but with less than 1 full cpu usage, and with somewhat less degraded network performance, but still quite unusable. I have never had issues with avahi prior to the 18.10 upgrade, so I am fairly confident the issue is rooted in that change. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: avahi-daemon 0.7-4ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE Date: Mon Oct 22 10:00:34 2018 InstallationDate: Installed on 2017-07-24 (455 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LD_PRELOAD= SHELL=/bin/bash SourcePackage: avahi UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/avahi/+bug/1799265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1409872] Re: avahi-0.6.31 doesn't pass Apple conformance test
** Changed in: avahi
Status: Unknown => New
--
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/1409872
Title:
avahi-0.6.31 doesn't pass Apple conformance test
Status in Avahi:
New
Status in avahi package in Ubuntu:
Confirmed
Bug description:
We are working on to support Apple bonjour conformance test-1.3.0 and
test fails with avahi version 0.6.31 for test case - SRV
PROBING/ANNOUNCEMENTS. This test fails both on IPV4 and IPV6. And the
configured network package - dhcpcd-6.6.4.
After parsing all logs(wireshark, apple PC and linux PC syslogs), and
looks like avahi does not support a particular scenario in which Apple
bonjour conformance test looks for. And also confirmed Apple test is
inline with the RFC 6762 document for a special use-case(resolving SRV
names on power up).
Below is the bug description,
setup:
Apple MAC with Bonjour conformance test - 1.3.0 (latest OS x)
Apple airport (latest version)
Linux device(PC) (ubuntu 14.04)
Configure all above devices to communicate on link local mode.
1) Start avahi bonjour conformance test on APPLE PC and Power ON linux
device with avahi-0.6.31 and with _ssh._tcp.local service file
2) First Linux device sends SRV initial probe message on link and followed by
apple test sends same SRV (Linux device) question on link,
example:(commands on wire shark)
Linux Device sends -> Who has "SSH" SRV QM question?
Apple Bonjour Conformance Test -> Who has "SSH" SRV QM question?
3) Then after this there is no message from Linux device on network and Apple
test expecting new SRV probe message from device.
And so conformance test failed, since device couldn't able to send new
SRV probe message with new name for service "SSH"
4) After parsing log files found that,
avahi-daemon logged service with new name ("SSH #2") in log file and could
not publish/probe SRV message on network.
Linux device syslog messages,
Loading service file /etc/avahi/services/ssh.service
Service name conflict for "SSH" (/etc/avahi/services/ssh.service),
retrying with "SSH #2).
To manage notifications about this bug go to:
https://bugs.launchpad.net/avahi/+bug/1409872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825273] Re: /usr/bin/lxc-start:11:cgfsng_payload_create:lxc_spawn:__lxc_start:lxc_start:do_lxcapi_start
*** This bug is a duplicate of bug 1825155 *** https://bugs.launchpad.net/bugs/1825155 ** This bug has been marked a duplicate of private bug 1825155 -- 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/1825273 Title: /usr/bin/lxc- start:11:cgfsng_payload_create:lxc_spawn:__lxc_start:lxc_start:do_lxcapi_start Status in lxc package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding lxc. This problem was most recently seen with package version 3.0.3-0ubuntu1~18.10.1, the problem page at https://errors.ubuntu.com/problem/8e0f1b9682f08bab5dedd4100e42f59cfe2cc004 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1825273/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825155] Re: lxc-start crashed with SIGSEGV in cgfsng_payload_create()
Also tracking in: https://errors.ubuntu.com/problem/8e0f1b9682f08bab5dedd4100e42f59cfe2cc004 ** Description changed: + https://errors.ubuntu.com/problem/8e0f1b9682f08bab5dedd4100e42f59cfe2cc004 + Steps to reproduce: 1) Prepare creating unprivileged containers as described here: https://linuxcontainers.org/lxc/getting-started/ 2) Create a new container (e.g. "lxc-create -n container -t download" and then "debian", "stretch" and "amd64"). 3) Start the created container in foreground using "lxc-start -n container -F" ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: lxc-utils 3.0.3-0ubuntu1~18.10.1 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: KDE Date: Wed Apr 17 12:03:37 2019 ExecutablePath: /usr/bin/lxc-start InstallationDate: Installed on 2019-04-15 (1 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.18.0-17-generic root=UUID=0739f905-33c9-4de3-9ba9-a63b8d69e5e5 ro quiet splash vt.handoff=1 SegvAnalysis: - Segfault happened at: 0x7f6292c5dbbd:mov(%rax),%r15 - PC (0x7f6292c5dbbd) ok - source "(%rax)" (0x) not located in a known VMA region (needed readable region)! - destination "%r15" ok + Segfault happened at: 0x7f6292c5dbbd:mov(%rax),%r15 + PC (0x7f6292c5dbbd) ok + source "(%rax)" (0x) not located in a known VMA region (needed readable region)! + destination "%r15" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: lxc StacktraceTop: - ?? () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 - __lxc_start () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 - lxc_start () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 - ?? () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 - ?? () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 + ?? () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 + __lxc_start () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 + lxc_start () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 + ?? () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 + ?? () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 Title: lxc-start crashed with SIGSEGV in __lxc_start() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo defaults.conf: - lxc.net.0.type = veth - lxc.net.0.link = lxcbr0 - lxc.net.0.flags = up - lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx + lxc.net.0.type = veth + lxc.net.0.link = lxcbr0 + lxc.net.0.flags = up + lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx mtime.conffile..etc.apport.crashdb.conf: 2019-04-17T11:58:15.556166 ** Information type changed from Private to Public ** Tags added: bionic -- 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/1825155 Title: lxc-start crashed with SIGSEGV in cgfsng_payload_create() Status in lxc package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/8e0f1b9682f08bab5dedd4100e42f59cfe2cc004 Steps to reproduce: 1) Prepare creating unprivileged containers as described here: https://linuxcontainers.org/lxc/getting-started/ 2) Create a new container (e.g. "lxc-create -n container -t download" and then "debian", "stretch" and "amd64"). 3) Start the created container in foreground using "lxc-start -n container -F" ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: lxc-utils 3.0.3-0ubuntu1~18.10.1 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: KDE Date: Wed Apr 17 12:03:37 2019 ExecutablePath: /usr/bin/lxc-start InstallationDate: Installed on 2019-04-15 (1 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.18.0-17-generic root=UUID=0739f905-33c9-4de3-9ba9-a63b8d69e5e5 ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x7f6292c5dbbd:mov(%rax),%r15 PC (0x7f6292c5dbbd) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%r15" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: lxc StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 __lxc_start () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 lxc_start () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 ?? () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 ?? () from /usr/lib/x86_64-linux-gnu/liblxc.so.1 Title: lxc-start crashed with SIGSEGV in __lxc_start() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo defaults.conf: lxc.net.0.type = veth lxc.net.0.
[Touch-packages] [Bug 1825273] [NEW] /usr/bin/lxc-start:11:cgfsng_payload_create:lxc_spawn:__lxc_start:lxc_start:do_lxcapi_start
*** This bug is a duplicate of bug 1825155 *** https://bugs.launchpad.net/bugs/1825155 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding lxc. This problem was most recently seen with package version 3.0.3-0ubuntu1~18.10.1, the problem page at https://errors.ubuntu.com/problem/8e0f1b9682f08bab5dedd4100e42f59cfe2cc004 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic -- 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/1825273 Title: /usr/bin/lxc- start:11:cgfsng_payload_create:lxc_spawn:__lxc_start:lxc_start:do_lxcapi_start Status in lxc package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding lxc. This problem was most recently seen with package version 3.0.3-0ubuntu1~18.10.1, the problem page at https://errors.ubuntu.com/problem/8e0f1b9682f08bab5dedd4100e42f59cfe2cc004 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1825273/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY
Also assigned to xorg-server, because Xorg should be intercepting Alt+KEY. If Xorg fails to do so and somehow the key events get sent to the VT then we get the unwanted VT's interpretation of Alt+KEY. ** Description changed: + WORKAROUND: + + sudo kbd_mode -s + + ORIGINAL DESCRIPTION: + I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Summary changed: - Alt+KEY incorrectly behaves like Ctrl+Alt+KEY + Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed ** Changed in: xorg-server (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769657] Re: update toolchain packages for bionic
** No longer affects: build-essential (Ubuntu) ** Changed in: cross-toolchain-base (Ubuntu) Status: New => Fix Released ** Changed in: cross-toolchain-base-ports (Ubuntu) Status: New => Fix Released ** Changed in: gcc-7 (Ubuntu) Status: New => Fix Released ** Changed in: gcc-7-cross (Ubuntu) Status: New => Fix Released ** Changed in: gcc-7-cross-ports (Ubuntu) Status: New => Fix Released ** Changed in: gcc-8 (Ubuntu) Status: New => Fix Released ** Changed in: gcc-8-cross (Ubuntu) Status: New => Fix Released ** Changed in: gcc-8-cross-ports (Ubuntu) Status: New => Fix Released ** Changed in: gcc-defaults (Ubuntu) Status: New => Fix Released ** Changed in: gcc-defaults-ports (Ubuntu) Status: New => Fix Released -- 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/1769657 Title: update toolchain packages for bionic Status in binutils package in Ubuntu: Fix Released Status in cross-toolchain-base package in Ubuntu: Fix Released Status in cross-toolchain-base-ports package in Ubuntu: Fix Released Status in gcc-7 package in Ubuntu: Fix Released Status in gcc-7-cross package in Ubuntu: Fix Released Status in gcc-7-cross-ports package in Ubuntu: Fix Released Status in gcc-8 package in Ubuntu: Fix Released Status in gcc-8-cross package in Ubuntu: Fix Released Status in gcc-8-cross-ports package in Ubuntu: Fix Released Status in gcc-defaults package in Ubuntu: Fix Released Status in gcc-defaults-ports package in Ubuntu: Fix Released Status in binutils source package in Bionic: Fix Released Status in cross-toolchain-base source package in Bionic: Fix Released Status in cross-toolchain-base-ports source package in Bionic: Fix Released Status in gcc-7 source package in Bionic: Fix Released Status in gcc-7-cross source package in Bionic: Fix Released Status in gcc-7-cross-ports source package in Bionic: Fix Released Status in gcc-8 source package in Bionic: Fix Released Status in gcc-8-cross source package in Bionic: Fix Released Status in gcc-8-cross-ports source package in Bionic: Fix Released Status in gcc-defaults source package in Bionic: Fix Released Status in gcc-defaults-ports source package in Bionic: Fix Released Bug description: I'd like to update the toolchain packages in bionic, to state which we have in cosmic on May 07: - LP: #1771635: binutils updates from the branch - gcc-8, update to the final 8.1.0 release - gcc-7, updates to the gcc-7-branch up to the time of the 8.1.0 release. - gcc-defaults to bump the 8.1 version, and add some provides - build-essential to add cross packages for amd64 and i386 - corresponding gcc-cross packages The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for GCC 8, and update GCC 7 fixes to the date of the corresponding GCC 8 updates. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the GCC test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, a complete archive rebuild (main only) was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, binutils, python3.6 and python3.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. For the cross builds, just make sure that the packages build using the updated sources. Summary of the test rebuilds: file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html No regressions are shown with the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1769657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825194] Re: resolvconf is racy, which leads to broken resolv.conf in parallel calls
I assume this is primarily an issue for UC16, since in UC18 we no longer use resolvconf at all, and have targeted the bug accordingly. Do you want to prepare a corresponding debdiff for xenial, and adjust the bug description to include a complete SRU template per https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ? ** Also affects: resolvconf (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: resolvconf (Ubuntu) Status: New => Fix Committed -- 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/1825194 Title: resolvconf is racy, which leads to broken resolv.conf in parallel calls Status in resolvconf package in Ubuntu: Fix Committed Status in resolvconf source package in Xenial: New Bug description: It has been found that simultaneous calls to resolvconf can lead to inconsistent content in resolv.conf. For instance, no nameservers while NetworkManager has one in its record (see LP: #1824395): $ cat /run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN $ cat /run/resolvconf/interface/NetworkManager nameserver 192.168.1.6 nameserver 192.168.1.2 This can happen easily when calling "netplan apply", which can re- start both networkd and NM. resolvconf is called at that point by the "systemd-networkd-resolvconf-update.service" service, and also directly by NetworkManager, which leads to the situation described above. This is not surprising as there is nothing preventing different instances of resolvconf to access the same files. This sort of situation can be reproduced by running in a loop commands like: $ printf "\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd $ printf "nameserver 80.58.61.250\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd Eventually, this leads to a resolv.conf that is not consistent with the last run command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
Xorg can't do anything about intercepting Alt-key, it's the kernel which takes the shortcut away. Again, as mentioned on https://bugs.launchpad.net/ubuntu/+source /console-setup/+bug/520546/comments/66 « proposed fix: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+attachment/5227480/+files/patch As mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146 , Ubuntu probably wants to apply the attached patch. » Can somebody with t he proper rights do something about this? That patch exists since months now... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825194] Re: resolvconf is racy, which leads to broken resolv.conf in parallel calls
This bug was fixed in the package resolvconf - 1.79ubuntu13 --- resolvconf (1.79ubuntu13) disco; urgency=medium * bin/resolvconf: use flock so resolvconf can be called in parallel safely (LP: #1825194). -- Alfonso Sanchez-Beato (email Canonical) Wed, 17 Apr 2019 16:53:53 +0200 ** Changed in: resolvconf (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1825194 Title: resolvconf is racy, which leads to broken resolv.conf in parallel calls Status in resolvconf package in Ubuntu: Fix Released Status in resolvconf source package in Xenial: New Bug description: It has been found that simultaneous calls to resolvconf can lead to inconsistent content in resolv.conf. For instance, no nameservers while NetworkManager has one in its record (see LP: #1824395): $ cat /run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN $ cat /run/resolvconf/interface/NetworkManager nameserver 192.168.1.6 nameserver 192.168.1.2 This can happen easily when calling "netplan apply", which can re- start both networkd and NM. resolvconf is called at that point by the "systemd-networkd-resolvconf-update.service" service, and also directly by NetworkManager, which leads to the situation described above. This is not surprising as there is nothing preventing different instances of resolvconf to access the same files. This sort of situation can be reproduced by running in a loop commands like: $ printf "\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd $ printf "nameserver 80.58.61.250\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd Eventually, this leads to a resolv.conf that is not consistent with the last run command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
