[Touch-packages] [Bug 1849859] Re: smb printing fails
This bug was fixed in the package system-config-printer - 1.5.12-0ubuntu1 --- system-config-printer (1.5.12-0ubuntu1) focal; urgency=medium * New upstream release - The most important change is about samba printers - the workgroup is now required in device URI and samba authentication works only when an user sets username and password during print queue creation for now (LP: #1849859). * Removed 0003-Use-ValueError-instead-of-ImportError-to-catch-excep.patch, 0004-Fix-constructing-the-auth-dialog.patch, 0005-Require-proper-version-of-GDK-and-GTK-in-scp-dbus-se.patch, 0006-Set-programe-name-for-scp-dbus-service-as-well.patch, 40_temporary-fix-for-error-pop-up-window-for-ipp-2.x-attributes.patch, define-classes-for-Secret-only-when-libsecret-is-installe.patch: Included upstream. * Refreshed 03_install_layout.patch * 40-udev-configure-printer-add-checks-for-null.patch, 43-fix-abrt-in-udev-configure-printer.patch: Fixed crashers in udev-configure-printer (Upstream issue #161). -- Till Kamppeter Mon, 24 Feb 2020 22:15:11 +0100 ** Changed in: system-config-printer (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Fix Released Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions -- Mailing list: https://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 1861408] Re: firefox apparmor messages
On Mon, Feb 24, 2020 at 06:48:33AM -, dinar qurbanov wrote:
> after firefox restart these appeared:
>
> Feb 24 09:30:04 dinar-HP-Pavilion-g7-Notebook-PC kernel: [ 141.932834]
> audit: type=1400 audit(1582525804.452:27): apparmor="DENIED"
> operation="open" profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
> name="/proc/1888/uid_map" pid=1888 comm=495043204C61756E6368202331
This file is a necessary part of the Firefox sandbox code. If you deny
this but allow the syscalls and privileges that start the sandbox, you're
going to see some very unusual results.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1861408
Title:
firefox apparmor messages
Status in apparmor package in Ubuntu:
New
Status in firefox package in Ubuntu:
New
Bug description:
firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
19.3.
i see there is newer ubuntu version in
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
, 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
apparmor.
i have not found a page for firefox bugs in linux mint sites, so i
belive i should report here. but i have also asked about that in linux
mint's irc and then github.
i have enabled apparmor for firefox and see these types of messages in
syslog:
Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")
Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5525.077960] audit: type=1400 audit(1580226276.440:27):
apparmor="DENIED" operation="capable"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
comm="firefox" capability=21 capname="sys_admin"
Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/RealtimeKit1"
interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
name="org.freedesktop.RealtimeKit1" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/Private/RemoteVolumeMonitor"
interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
mask="send" name=":1.35" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="ListMounts2" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="LookupMount" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
pid=15948 comm="/usr/lib/firefox/firefox "
label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/hostname1"
interface="org.freedesktop.DBus.Properties" member="GetAll"
mask="send" name=":1.120" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
peer_label="unconfined"
Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
member="Change" mask="send" name="ca.desrt.dconf" pid=15948
label="/usr/li
[Touch-packages] [Bug 1864526] Re: Display ghosting when dragging icons or opening menus
** Package changed: xorg (Ubuntu) => lxqt-session (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1864526 Title: Display ghosting when dragging icons or opening menus Status in lxqt-session package in Ubuntu: New Bug description: Display ghosting when dragging icons or opening menus. Have tested several machines and this only occurring on Intel NUC 8i3BEK - and only when installing or using FOCAL Lubuntu 20.04 . This also is occurring in the Live sessions before install. I have tested Lubuntu Eoan 19.01 and Lubuntu Bionic 18.04.04 on this machine and cannot reproduce the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: LXQt Date: Mon Feb 24 18:23:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics 655 [8086:3ea5] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 655 [8086:2074] InstallationDate: Installed on 2020-02-24 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200224) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard Bus 001 Device 002: ID 2188:0ae1 USB OPTICAL MOUSE Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=11c10d68-db79-4d45-9bbe-8357e125b46b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0073.2019.0618.1409 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-307 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0073.2019.0618.1409:bd06/18/2019:svnIntel(R)ClientSystems:pnNUC8i3BEK:pvrJ72748-306:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-307:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: BE dmi.product.name: NUC8i3BEK dmi.product.sku: BOXNUC8i3BEK dmi.product.version: J72748-306 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1864526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864253] Re: Pulseaudio sink/source selection, weird behaviour.
** Also affects: pulseaudio via https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/814 Importance: Unknown Status: Unknown ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- 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/1864253 Title: Pulseaudio sink/source selection, weird behaviour. Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: New Bug description: I have a Laptop connected to an USB-C dock. By default the docks analog audio output is chosen as the default pulse audio sink. I want that the analog output of the Laptop is the default, hence I configured this in /etc/pulse/default.py This does not work and journalctl informs me that the device chosen by me (alsa_output.pci-_00_1f.3.analog-stereo) does not exist, see attached output from journalctl. I have followed Workaround 1 here https://wiki.debian.org/BluetoothUser/a2dp to prevent pulseaudio getting started in gdm to prevent device capture. This does not work, the device does still not exist. Restarting pulseaudio sometimes, but not always sets the configured default sink. Furthermore plugging in the headphones in the Laptops analog input switches audio to the dock. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: findus 3055 F pulseaudio /dev/snd/controlC1: findus 3055 F pulseaudio /dev/snd/controlC0: findus 3055 F pulseaudio /dev/snd/pcmC0D0p: findus 3055 F...m pulseaudio CurrentDesktop: i3 Date: Fri Feb 21 22:19:04 2020 InstallationDate: Installed on 2019-06-13 (253 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET80W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S0UB00 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET80W(1.58):bd11/26/2019:svnLENOVO:pn20N3S0UB00:pvrThinkPadT490:rvnLENOVO:rn20N3S0UB00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S0UB00 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-02-21T20:38:20.081439 mtime.conffile..etc.pulse.default.pa: 2020-02-21T19:27:57.386938 mtime.conffile..etc.pulse.system.pa: 2020-02-21T15:23:09.470494 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1864253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev
** Merge proposal linked: https://code.launchpad.net/~smoser/cloud-initramfs-tools/+git/cloud-initramfs-tools/+merge/379774 -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev
The fix is in cloud-utils upstream now. Still to do: a.) review/merge cloud-initramfs-tools pull request https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-utils/+merge/379177 b.) upload cloud-initramfs-tools to focal c.) upload cloud-utils to focal d.) any SRU the order of 'b' and 'c' are not *terribly* important, because I do not think that there are many users of 'growroot' at this point. That said... the change to cloud-utils *does* break cloud-initramfs-tools so they should be done in that order. I personally do not really want to babysit these getting in. Can someone else sign up for that? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev
** Changed in: cloud-initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in cloud-utils package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev
** Merge proposal linked: https://code.launchpad.net/~raharper/cloud-utils/+git/cloud-utils/+merge/379177 ** Changed in: cloud-utils Status: New => Fix Committed ** Also affects: cloud-utils (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-utils (Ubuntu) Status: New => Confirmed ** Also affects: cloud-initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1834875 Title: cloud-init growpart race with udev Status in cloud-init: Incomplete Status in cloud-utils: Fix Committed Status in cloud-initramfs-tools package in Ubuntu: New Status in cloud-utils package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/zoneminder/+git/zoneminder/+merge/379771 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: Fix Released Status in asterisk package in Ubuntu: Fix Released Status in clickhouse package in Ubuntu: Fix Committed Status in cppdb package in Ubuntu: Fix Released Status in dballe package in Ubuntu: Fix Released Status in gambas3 package in Ubuntu: Fix Released Status in gearmand package in Ubuntu: Fix Released Status in gerbera package in Ubuntu: Fix Released Status in gnokii package in Ubuntu: Fix Released Status in gnunet package in Ubuntu: Fix Released Status in hoel package in Ubuntu: Fix Released Status in isc-kea package in Ubuntu: Fix Released Status in jabberd2 package in Ubuntu: Fix Released Status in kannel package in Ubuntu: Fix Released Status in libgda5 package in Ubuntu: Fix Released Status in libodb-mysql package in Ubuntu: Fix Released Status in lyricue package in Ubuntu: Fix Released Status in motion package in Ubuntu: Fix Released Status in mysql-8.0 package in Ubuntu: Fix Released Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: Fix Released Status in opendnssec package in Ubuntu: Fix Released Status in opensmtpd-extras package in Ubuntu: Fix Released Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: Fix Released Status in pvpgn package in Ubuntu: Fix Released Status in qt4-x11 package in Ubuntu: Fix Released Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: Fix Released Status in tntdb package in Ubuntu: Fix Released Status in voms-mysql-plugin package in Ubuntu: Fix Released Status in vtk7 package in Ubuntu: Fix Released Status in w1retap package in Ubuntu: Fix Released Status in zoneminder package in Ubuntu: In Progress Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed
Indeed. It offers python3 version 3.7.5-1ubuntu1 as a solution which is not appropriate as python3 version 3.8.0-3 is already installed and does not provide a `python` command. The python-is-python3 solution sounds like a sensible way forward. There be dragons, I suspect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1863532 Title: Invoking "python" brings inappropriate response from command-not-found when python3 installed Status in command-not-found package in Ubuntu: Triaged Status in python3-defaults package in Ubuntu: Triaged Status in command-not-found source package in Focal: Triaged Status in python3-defaults source package in Focal: Triaged Bug description: Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't have python 2.7 installed, but have python 3 installed as per default. Please see ascii-cast at https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 . Running `python` brings up text from command-not-found which suggests installing `python3` as a solution to the missing command. `python3` is already installed, is a later version than the one indicated by command-not-found and does not supply a binary or symlink named `python`. $ apt policy python python: Installed: (none) Candidate: (none) Version table: 2.7.17-1 -1 100 /var/lib/dpkg/status $ apt policy python3 python3: Installed: 3.8.0-3 Candidate: 3.8.0-3 Version table: *** 3.8.0-3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ apt policy command-not-found command-not-found: Installed: 19.10.0 Candidate: 19.10.0 Version table: *** 19.10.0 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status I don't know whether this is a bug in python3 or command-not-found (the latter of which doesn't seem to have been updated for 20.04 yet). i don't know if it is intentional that `python3` will not provide a binary or symlink named `python`. if that is the case, the output of `command-not-found` should be updated to reflect that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3 3.8.0-3 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: MATE Date: Mon Feb 17 01:35:16 2020 InstallationDate: Installed on 2019-10-11 (128 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2) SourcePackage: python3-defaults UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed
Indeed. It offers python3 version 3.7.5-1ubuntu1 as a solution which is not appropriate as python3 version 3.8.0-3 is already installed and does not provide a `python` command. The python-is-python3 solution sounds like a sensible way forward. There be dragons, I suspect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1863532 Title: Invoking "python" brings inappropriate response from command-not-found when python3 installed Status in command-not-found package in Ubuntu: Triaged Status in python3-defaults package in Ubuntu: Triaged Status in command-not-found source package in Focal: Triaged Status in python3-defaults source package in Focal: Triaged Bug description: Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't have python 2.7 installed, but have python 3 installed as per default. Please see ascii-cast at https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 . Running `python` brings up text from command-not-found which suggests installing `python3` as a solution to the missing command. `python3` is already installed, is a later version than the one indicated by command-not-found and does not supply a binary or symlink named `python`. $ apt policy python python: Installed: (none) Candidate: (none) Version table: 2.7.17-1 -1 100 /var/lib/dpkg/status $ apt policy python3 python3: Installed: 3.8.0-3 Candidate: 3.8.0-3 Version table: *** 3.8.0-3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ apt policy command-not-found command-not-found: Installed: 19.10.0 Candidate: 19.10.0 Version table: *** 19.10.0 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status I don't know whether this is a bug in python3 or command-not-found (the latter of which doesn't seem to have been updated for 20.04 yet). i don't know if it is intentional that `python3` will not provide a binary or symlink named `python`. if that is the case, the output of `command-not-found` should be updated to reflect that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3 3.8.0-3 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: MATE Date: Mon Feb 17 01:35:16 2020 InstallationDate: Installed on 2019-10-11 (128 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2) SourcePackage: python3-defaults UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed
The asciicinema stuff has disappeared but I presume this is the output: $ python Command 'python' not found, but can be installed with: sudo apt install python3 # version 3.7.5-1ubuntu1, or sudo apt install python # version 2.7.17-1 sudo apt install python-minimal # version 2.7.17-1 You also have python3 installed, you can run 'python3' instead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1863532 Title: Invoking "python" brings inappropriate response from command-not-found when python3 installed Status in command-not-found package in Ubuntu: Triaged Status in python3-defaults package in Ubuntu: Triaged Status in command-not-found source package in Focal: Triaged Status in python3-defaults source package in Focal: Triaged Bug description: Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't have python 2.7 installed, but have python 3 installed as per default. Please see ascii-cast at https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 . Running `python` brings up text from command-not-found which suggests installing `python3` as a solution to the missing command. `python3` is already installed, is a later version than the one indicated by command-not-found and does not supply a binary or symlink named `python`. $ apt policy python python: Installed: (none) Candidate: (none) Version table: 2.7.17-1 -1 100 /var/lib/dpkg/status $ apt policy python3 python3: Installed: 3.8.0-3 Candidate: 3.8.0-3 Version table: *** 3.8.0-3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ apt policy command-not-found command-not-found: Installed: 19.10.0 Candidate: 19.10.0 Version table: *** 19.10.0 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status I don't know whether this is a bug in python3 or command-not-found (the latter of which doesn't seem to have been updated for 20.04 yet). i don't know if it is intentional that `python3` will not provide a binary or symlink named `python`. if that is the case, the output of `command-not-found` should be updated to reflect that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3 3.8.0-3 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: MATE Date: Mon Feb 17 01:35:16 2020 InstallationDate: Installed on 2019-10-11 (128 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2) SourcePackage: python3-defaults UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864562] [NEW] For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event
Public bug reported: If the keypress event contains GDK_HYPER_MASK as a modifier, gtk_im_context_filter_keypress() returns true, reporting that the IM handled the event, even though it did not, therefore it should return false. Background: We are working on modifying Gnome-Terminal / libvte-2.91.so.0 to enable Terminal-bespoke remapping of modifier keys. This is to facilitate OS X users to migrate to Ubuntu. (Discussion here: #220. Background and unsuccessful alternative approaches detailed here: https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/README.md). When we replace GDK_CONTROL_MASK by GDK_HYPER_MASK, the input method (ibus) reports that it handled the event that had Hyper as the modifier. When we use export GTK_IM_MODULE=xim, the Hyper modifier is passed as expected. We believe that this is a bug in ibus XOR gtk. Unfortunately I'm not sure whether this is an issue in ibus or gtk, so I'm reporting it in both places (as well as upstream). Apologies for the inconvenience caused by this. Many thanks for looking at this. I'll track updates here https://gitlab.gnome.org/GNOME/gnome-terminal/issues/220 and here https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/Building%20a%20Gnome-Hyper-Terminal.md so that people compinging Gnonme Terminal are aware of the status. Many thanks! ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1864562 Title: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event Status in gtk+3.0 package in Ubuntu: New Bug description: If the keypress event contains GDK_HYPER_MASK as a modifier, gtk_im_context_filter_keypress() returns true, reporting that the IM handled the event, even though it did not, therefore it should return false. Background: We are working on modifying Gnome-Terminal / libvte-2.91.so.0 to enable Terminal-bespoke remapping of modifier keys. This is to facilitate OS X users to migrate to Ubuntu. (Discussion here: #220. Background and unsuccessful alternative approaches detailed here: https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/README.md). When we replace GDK_CONTROL_MASK by GDK_HYPER_MASK, the input method (ibus) reports that it handled the event that had Hyper as the modifier. When we use export GTK_IM_MODULE=xim, the Hyper modifier is passed as expected. We believe that this is a bug in ibus XOR gtk. Unfortunately I'm not sure whether this is an issue in ibus or gtk, so I'm reporting it in both places (as well as upstream). Apologies for the inconvenience caused by this. Many thanks for looking at this. I'll track updates here https://gitlab.gnome.org/GNOME/gnome-terminal/issues/220 and here https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/Building%20a%20Gnome-Hyper-Terminal.md so that people compinging Gnonme Terminal are aware of the status. Many thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1864562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864558] Re: Printer adds automatically at boot with notification or if printer deleted
Thank you for your bug report, the notification problem has already been reported, see e.g bug #1725955 but it sounds like a cups(-browsed) issue if a deleted printer is automatically added back as configured... ** Package changed: gnome-control-center (Ubuntu) => gnome-settings- daemon (Ubuntu) ** Package changed: gnome-settings-daemon (Ubuntu) => cups (Ubuntu) ** Changed in: cups (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1864558 Title: Printer adds automatically at boot with notification or if printer deleted Status in cups package in Ubuntu: New Bug description: When booting 20.04 I get a notification on the logon screen each time advising that my wireless printer has been setup. If I remove the printer via settings, then as soon as it's removed, it gets re-added and I see the same notification as I do on the logon screen about the printer having been setup. I've attached a screenshot of this notification. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 21:49:43 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1864558/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864561] [NEW] For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event
Public bug reported: If the keypress event contains GDK_HYPER_MASK as a modifier, gtk_im_context_filter_keypress() returns true, reporting that the IM handled the event, even though it did not, therefore it should return false. Background: We are working on modifying Gnome-Terminal / libvte-2.91.so.0 to enable Terminal-bespoke remapping of modifier keys. This is to facilitate OS X users to migrate to Ubuntu. (Discussion here: #220. Background and unsuccessful alternative approaches detailed here: https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/README.md). When we replace GDK_CONTROL_MASK by GDK_HYPER_MASK, the input method (ibus) reports that it handled the event that had Hyper as the modifier. When we use export GTK_IM_MODULE=xim, the Hyper modifier is passed as expected. We believe that this is a bug in ibus XOR gtk. Unfortunately I'm not sure whether this is an issue in ibus or gtk, so I'm reporting it in both places (as well as upstream). Apologies for the inconvenience caused by this. Many thanks for looking at this. I'll track updates here https://gitlab.gnome.org/GNOME/gnome-terminal/issues/220 and here https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/Building%20a%20Gnome-Hyper-Terminal.md so that people compinging Gnonme Terminal are aware of the status. Many thanks! ** Affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1864561 Title: For GDK_HYPER_MASK, gtk_im_context_filter_keypress() falsely reports that IM handled the event Status in ibus package in Ubuntu: New Bug description: If the keypress event contains GDK_HYPER_MASK as a modifier, gtk_im_context_filter_keypress() returns true, reporting that the IM handled the event, even though it did not, therefore it should return false. Background: We are working on modifying Gnome-Terminal / libvte-2.91.so.0 to enable Terminal-bespoke remapping of modifier keys. This is to facilitate OS X users to migrate to Ubuntu. (Discussion here: #220. Background and unsuccessful alternative approaches detailed here: https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/README.md). When we replace GDK_CONTROL_MASK by GDK_HYPER_MASK, the input method (ibus) reports that it handled the event that had Hyper as the modifier. When we use export GTK_IM_MODULE=xim, the Hyper modifier is passed as expected. We believe that this is a bug in ibus XOR gtk. Unfortunately I'm not sure whether this is an issue in ibus or gtk, so I'm reporting it in both places (as well as upstream). Apologies for the inconvenience caused by this. Many thanks for looking at this. I'll track updates here https://gitlab.gnome.org/GNOME/gnome-terminal/issues/220 and here https://github.com/bjohas/Ubuntu-keyboard-map-like-OS-X/blob/master/Building%20a%20Gnome-Hyper-Terminal.md so that people compinging Gnonme Terminal are aware of the status. Many thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1864561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864558] [NEW] Printer adds automatically at boot with notification or if printer deleted
You have been subscribed to a public bug: When booting 20.04 I get a notification on the logon screen each time advising that my wireless printer has been setup. If I remove the printer via settings, then as soon as it's removed, it gets re-added and I see the same notification as I do on the logon screen about the printer having been setup. I've attached a screenshot of this notification. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 21:49:43 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cups (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug focal -- Printer adds automatically at boot with notification or if printer deleted https://bugs.launchpad.net/bugs/1864558 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758529] Re: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno
On both bionic and eoan I installed postgres packages from Landscape with both the current version and the proposed version of Landscape client. Errors were seen with the current version and they were gone in the proposed version. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1758529 Title: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno Status in Landscape Client: Fix Committed Status in landscape-client package in Ubuntu: Fix Released Status in python-apt package in Ubuntu: Invalid Status in landscape-client source package in Bionic: Fix Committed Status in python-apt source package in Bionic: Invalid Status in landscape-client source package in Disco: Won't Fix Status in python-apt source package in Disco: Invalid Status in landscape-client source package in Eoan: Fix Committed Status in python-apt source package in Eoan: Invalid Bug description: [Impact] * landscape-package-changer will output stack traces when executed with python3. This adds noise in the logs and confuse apport into thinking there was a crash, even though the error does not affect functionality. * The activity log for package operations will also show errors. * The patch overrides python-apt reporting of progress, as landscape-package-changer is never executed from a terminal. [Test Case] * register landscape-client and wait for packages to be reported. * trigger a package installation from the landscape server. * check /var/log/landscape/manager.log for Package changer warnings [Regression Potential] * The change is trivially simple. * The changed code path is only used by python-apt progress reporting. Since landscape-package-changer does not rely on it and is able to continue, other errors would likely have the same fate: that is crashing the progress reporting thread and continuing. [Original Description] Crash in the background ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: landscape-client 18.01-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Mar 24 07:05:34 2018 ExecutablePath: /usr/bin/landscape-package-changer InstallationDate: Installed on 2015-07-04 (994 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.6 ProcCmdline: /usr/bin/python3 /usr/bin/landscape-package-changer --quiet ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonArgs: ['/usr/bin/landscape-package-changer', '--quiet'] PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 SourcePackage: landscape-client Title: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno Traceback: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apt/progress/text.py", line 164, in pulse not os.isatty(self._file.fileno())): io.UnsupportedOperation: fileno UpgradeStatus: Upgraded to bionic on 2018-03-15 (8 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1758529/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848202] Autopkgtest regression report (glib2.0/2.62.3-2~ubuntu19.10.1)
All autopkgtests for the newly accepted glib2.0 (2.62.3-2~ubuntu19.10.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: tracker/2.3.0-1 (armhf) snapd-glib/1.49-0ubuntu1.19.10.0 (armhf) sbd/1.4.0-18-g5e3283c-1ubuntu1 (amd64) gvfs/1.42.1-1ubuntu1 (arm64) glib2.0/2.62.3-2~ubuntu19.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1848202 Title: Use after free in gdbus leads to eds segfaults Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution-data-server. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/b1f62616406e36e521fd1fb1d2be4ac2fe9a2cda 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/. [ Fix ] This bug was fixed upstream in 2.62.2 (see the links below). That update is being issues to eoan. [ QA ] Under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME, we don't need to explicitly test that this bug is fixed. Nevertheless, to verify this bug please give the desktop a good workout. Ideally install the SRU and use your machine as you would normally for a variety of tasks. Make sure there are no regressions. [ Regression potential ] 1) The changes involve mutexes and stuff, which is error prone. 2) It's GLib, a core library, so any bad regressions will be really serious for the desktop as a whole. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1848202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844853] Autopkgtest regression report (glib2.0/2.62.3-2~ubuntu19.10.1)
All autopkgtests for the newly accepted glib2.0 (2.62.3-2~ubuntu19.10.1) for
eoan have finished running.
The following regressions have been reported in tests triggered by the package:
tracker/2.3.0-1 (armhf)
snapd-glib/1.49-0ubuntu1.19.10.0 (armhf)
sbd/1.4.0-18-g5e3283c-1ubuntu1 (amd64)
gvfs/1.42.1-1ubuntu1 (arm64)
glib2.0/2.62.3-2~ubuntu19.10.1 (i386)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#glib2.0
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1844853
Title:
IBus no longer works in Qt applications after upgrade
Status in GLib:
Fix Released
Status in ibus:
Fix Released
Status in glib2.0 package in Ubuntu:
Fix Released
Status in ibus package in Ubuntu:
Fix Released
Status in glib2.0 source package in Xenial:
Fix Committed
Status in glib2.0 source package in Bionic:
Fix Committed
Status in glib2.0 source package in Disco:
Fix Committed
Status in glib2.0 source package in Eoan:
Fix Committed
Status in glib2.0 source package in Focal:
Fix Released
Status in ibus source package in Focal:
Fix Released
Status in glib2.0 package in Debian:
Fix Released
Bug description:
[Impact]
IBus was broken for Qt applications as a regression due to the fix of
CVE-2019-14822. As a result the IBus patch was disabled temporarily,
which fixed IBus from a usability POV.
The real fix has been made in glib2.0, and the updates in -proposed
will allow the IBus patch to be re-enabled.
[Test Case]
* On a standard Ubuntu {eoan,disco,bionic,xenial} installation
- Upgrade the glib2.0 packages from
{eoan,disco,bionic,xenial}-proposed
- Upgrade the ibus packages from
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
- Install some IBus input method, e.g. ibus-libpinyin
- Install some Qt application, e.g. Kate
* Relogin (maybe reboot)
* Add the input method to the input sources
* Open the Qt app and try to input something using the IBus IM
=> Find that the transliteration works as expected
[Regression Potential]
The applicable patches origin from glib upstream:
https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
Consequently the changes have been reviewed by the glib maintainer, but also
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.
[Original description]
Kubuntu Release 18.04.3 LTS
Expected behavior:
ibus continues working as before after applying security update
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.
Observed behavior:
ibus is not usable anymore in Qt applications.
After updating ibus and the related packages ibus-gtk, ibus-gtk3,
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using
shift-space no longer changes the selected input method and even when i switch
to the mozc input method in a gtk application, i can not use it in any Qt
applications.
When starting qtconfig in a terminal, I also get the following message:
Bus::open: Connect ibus failed!
IBusInputContext::createInputContext: no connection to ibus-daemon
This bug was not present in version 1.5.17-3ubuntu5 and I also
confirmed that downgrading the packages to version 1.5.17-3ubuntu4
restores ibus functionality in Qt applications.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ibus 1.5.17-3ubuntu5.1
ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Sep 21 07:58:56 2019
InstallationDate: Installed on 2019-06-28 (84 days ago)
InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850932] Autopkgtest regression report (glib2.0/2.62.3-2~ubuntu19.10.1)
All autopkgtests for the newly accepted glib2.0 (2.62.3-2~ubuntu19.10.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: tracker/2.3.0-1 (armhf) snapd-glib/1.49-0ubuntu1.19.10.0 (armhf) sbd/1.4.0-18-g5e3283c-1ubuntu1 (amd64) gvfs/1.42.1-1ubuntu1 (arm64) glib2.0/2.62.3-2~ubuntu19.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1850932 Title: [SRU] Backport 2.62.4-1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] I'm creating this bug report to have a place to describe the proposed backport of glib2.0 2.62.4-1 from focal. One purpose of this backport is to fix bug #1844853. But there are several other changes. Here's the diff of NEWS: +Overview of changes in GLib 2.62.4 +== + +* Apply recursion depth limits to variants in D-Bus messages (!1290) + +* Bugs fixed: + - #1938 GDateTime doesn't support leap seconds + - !1240 Backport !1233 “gdatetime: Handle leap seconds in ISO8601 dates” +to glib-2-62 + - !1257 Backport !1232 “kqueue: Do not return early from _kqsub_cancel” +to glib-2-62 + - !1266 Backport !1265 “build: don't check for protected visibility” to +glib-2-62 + - !1276 Backport !1274 “trash portal: Don't follow symlinks” to glib-2-62 + - !1290 Backport !1201 “gdbusmessage: Limit recursion of variants in +D-Bus messages” to glib-2-62 + +Overview of changes in GLib 2.62.3 +== + +* Use `poll()` in `g_spawn_sync()` rather than `select()`, which is subject to + FD limits (#954) + +* Fix undefined behaviour with `g_utf8_find_prev_char()` (#1917) + +* Bugs fixed: + - #954 The g_spawn_sync() function uses select() which has limitations + - #1318 rare failure in gdbus-peer test: invalid uninstantiatable type '(null)' in cast to 'GDBusServer' + - #1897 glib 2.62.0 fails test 'test_writev_no_vectors' wih gcc7 + - #1903 use-after-free in mimeapps test causes intermittent segfault during testing + - #1916 objcopy not used from cross-compilation file in GIO tests + - #1917 Test utf8-pointer fails with static build, LTO, optimisations, and new GCC + - !1174 Backport !1164 “use-after-free fix in mimeapps test” to glib-2-62 + - !1184 Backport !1173 “gvariant: Limit recursion in g_variant_parse()” to glib-2-62 + - !1194 Backport !1176, !1183, !1188, !1191 to `glib-2-62` + - !1203 Backport !1192, !1193, !1197 Fixes for gdbus-peer tests to glib-2-62 + - !1207 Backport !1206 “goption: Relax assertion to avoid being broken by kdeinit5” to glib-2-62 + - !1215 [2.62] gdbus-peer: Specifically listen on 127.0.0.1 + - !1219 Backport !1218 “gdb: Fix GHashTable pretty printer off-by-one error” + - !1222 Backport !1221 “Add NOTE_REVOKE to the list of the monitoring events” to glib-2-62 + - !1228 Backport !1199 “gunicode: Fix UB in gutf8.c and utf8-pointer test” to glib-2-62 + + +Overview of changes in GLib 2.62.2 +== + +* Bugs fixed: + - #1896 Use after free when calling g_dbus_connection_flush_sync() in a dedicated thread + - !1154 Backport !1152 “gwinhttpvfs: Handle g_get_prgname() returning NULL” to glib-2-62 + - !1156 Backport !1146 Solaris fixes to glib-2-62 This release can be considered to be tested under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME There are patches from the upstream master branch rather than this stable release: + Add-a-test-for-GDBusServer-authentication.patch + gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch + gdbus-server-auth-test-Include-gcredentialsprivate.h.patch + Make-ld-executable-configurable.patch They are sensible backports which I hope are appropriate for SRU. [ QA ] The testsuite fixes will verify themselves during the build and autopkgtest. For the rest of the fixes, please exercise the desktop thoroughly. Log in, log out, run many applications and make sure there are no regressions. [ Regression potential ] test fixes> Build failures or autopkgtest failures. GLib is a central desktop library. Regressions could break any part of the desktop - so QA is important, the SRU exception notwithstanding. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1850932/+subscriptions -- Mailing list: https://launchpad.n
[Touch-packages] [Bug 1850932] Re: [SRU] Backport 2.62.4-1
Hello Iain, or anyone else affected, Accepted glib2.0 into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.62.4-1~ubuntu19.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: glib2.0 (Ubuntu Eoan) Status: In Progress => Fix Committed -- 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/1850932 Title: [SRU] Backport 2.62.4-1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] I'm creating this bug report to have a place to describe the proposed backport of glib2.0 2.62.4-1 from focal. One purpose of this backport is to fix bug #1844853. But there are several other changes. Here's the diff of NEWS: +Overview of changes in GLib 2.62.4 +== + +* Apply recursion depth limits to variants in D-Bus messages (!1290) + +* Bugs fixed: + - #1938 GDateTime doesn't support leap seconds + - !1240 Backport !1233 “gdatetime: Handle leap seconds in ISO8601 dates” +to glib-2-62 + - !1257 Backport !1232 “kqueue: Do not return early from _kqsub_cancel” +to glib-2-62 + - !1266 Backport !1265 “build: don't check for protected visibility” to +glib-2-62 + - !1276 Backport !1274 “trash portal: Don't follow symlinks” to glib-2-62 + - !1290 Backport !1201 “gdbusmessage: Limit recursion of variants in +D-Bus messages” to glib-2-62 + +Overview of changes in GLib 2.62.3 +== + +* Use `poll()` in `g_spawn_sync()` rather than `select()`, which is subject to + FD limits (#954) + +* Fix undefined behaviour with `g_utf8_find_prev_char()` (#1917) + +* Bugs fixed: + - #954 The g_spawn_sync() function uses select() which has limitations + - #1318 rare failure in gdbus-peer test: invalid uninstantiatable type '(null)' in cast to 'GDBusServer' + - #1897 glib 2.62.0 fails test 'test_writev_no_vectors' wih gcc7 + - #1903 use-after-free in mimeapps test causes intermittent segfault during testing + - #1916 objcopy not used from cross-compilation file in GIO tests + - #1917 Test utf8-pointer fails with static build, LTO, optimisations, and new GCC + - !1174 Backport !1164 “use-after-free fix in mimeapps test” to glib-2-62 + - !1184 Backport !1173 “gvariant: Limit recursion in g_variant_parse()” to glib-2-62 + - !1194 Backport !1176, !1183, !1188, !1191 to `glib-2-62` + - !1203 Backport !1192, !1193, !1197 Fixes for gdbus-peer tests to glib-2-62 + - !1207 Backport !1206 “goption: Relax assertion to avoid being broken by kdeinit5” to glib-2-62 + - !1215 [2.62] gdbus-peer: Specifically listen on 127.0.0.1 + - !1219 Backport !1218 “gdb: Fix GHashTable pretty printer off-by-one error” + - !1222 Backport !1221 “Add NOTE_REVOKE to the list of the monitoring events” to glib-2-62 + - !1228 Backport !1199 “gunicode: Fix UB in gutf8.c and utf8-pointer test” to glib-2-62 + + +Overview of changes in GLib 2.62.2 +== + +* Bugs fixed: + - #1896 Use after free when calling g_dbus_connection_flush_sync() in a dedicated thread + - !1154 Backport !1152 “gwinhttpvfs: Handle g_get_prgname() returning NULL” to glib-2-62 + - !1156 Backport !1146 Solaris fixes to glib-2-62 This release can be considered to be tested under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME There are patches from the upstream master branch rather than this stable release: + Add-a-test-for-GDBusServer-authentication.patch + gdbus-server-auth-test-Create-temporary-directory-for-Uni.patch + gdbus-server-auth-test-Include-gcredentialsprivate.h.patch + Make-ld-executable-configurable.patch They are sensible backports which I hope are appropriate for SRU. [ QA ] The testsuite fixes will verify themselves during th
[Touch-packages] [Bug 1844853] Please test proposed package
Hello Adam, or anyone else affected,
Accepted glib2.0 into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/glib2.0/2.62.4-1~ubuntu19.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1844853
Title:
IBus no longer works in Qt applications after upgrade
Status in GLib:
Fix Released
Status in ibus:
Fix Released
Status in glib2.0 package in Ubuntu:
Fix Released
Status in ibus package in Ubuntu:
Fix Released
Status in glib2.0 source package in Xenial:
Fix Committed
Status in glib2.0 source package in Bionic:
Fix Committed
Status in glib2.0 source package in Disco:
Fix Committed
Status in glib2.0 source package in Eoan:
Fix Committed
Status in glib2.0 source package in Focal:
Fix Released
Status in ibus source package in Focal:
Fix Released
Status in glib2.0 package in Debian:
Fix Released
Bug description:
[Impact]
IBus was broken for Qt applications as a regression due to the fix of
CVE-2019-14822. As a result the IBus patch was disabled temporarily,
which fixed IBus from a usability POV.
The real fix has been made in glib2.0, and the updates in -proposed
will allow the IBus patch to be re-enabled.
[Test Case]
* On a standard Ubuntu {eoan,disco,bionic,xenial} installation
- Upgrade the glib2.0 packages from
{eoan,disco,bionic,xenial}-proposed
- Upgrade the ibus packages from
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
- Install some IBus input method, e.g. ibus-libpinyin
- Install some Qt application, e.g. Kate
* Relogin (maybe reboot)
* Add the input method to the input sources
* Open the Qt app and try to input something using the IBus IM
=> Find that the transliteration works as expected
[Regression Potential]
The applicable patches origin from glib upstream:
https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
Consequently the changes have been reviewed by the glib maintainer, but also
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.
[Original description]
Kubuntu Release 18.04.3 LTS
Expected behavior:
ibus continues working as before after applying security update
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.
Observed behavior:
ibus is not usable anymore in Qt applications.
After updating ibus and the related packages ibus-gtk, ibus-gtk3,
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using
shift-space no longer changes the selected input method and even when i switch
to the mozc input method in a gtk application, i can not use it in any Qt
applications.
When starting qtconfig in a terminal, I also get the following message:
Bus::open: Connect ibus failed!
IBusInputContext::createInputContext: no connection to ibus-daemon
This bug was not present in version 1.5.17-3ubuntu5 and I also
confirmed that downgrading the packages to version 1.5.17-3ubuntu4
restores ibus functionality in Qt applications.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ibus 1.5.17-3ubuntu5.1
ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Sep 21 07:58:56 2019
InstallationDate: Installed on 2019-06-28 (84 days ago)
InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+subscriptions
--
Mailing
[Touch-packages] [Bug 1848202] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted glib2.0 into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.62.4-1~ubuntu19.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1848202 Title: Use after free in gdbus leads to eds segfaults Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution-data-server. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/b1f62616406e36e521fd1fb1d2be4ac2fe9a2cda 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/. [ Fix ] This bug was fixed upstream in 2.62.2 (see the links below). That update is being issues to eoan. [ QA ] Under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME, we don't need to explicitly test that this bug is fixed. Nevertheless, to verify this bug please give the desktop a good workout. Ideally install the SRU and use your machine as you would normally for a variety of tasks. Make sure there are no regressions. [ Regression potential ] 1) The changes involve mutexes and stuff, which is error prone. 2) It's GLib, a core library, so any bad regressions will be really serious for the desktop as a whole. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1848202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758529] Re: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1758529 Title: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno Status in Landscape Client: Fix Committed Status in landscape-client package in Ubuntu: Fix Released Status in python-apt package in Ubuntu: Invalid Status in landscape-client source package in Bionic: Fix Committed Status in python-apt source package in Bionic: Invalid Status in landscape-client source package in Disco: Won't Fix Status in python-apt source package in Disco: Invalid Status in landscape-client source package in Eoan: Fix Committed Status in python-apt source package in Eoan: Invalid Bug description: [Impact] * landscape-package-changer will output stack traces when executed with python3. This adds noise in the logs and confuse apport into thinking there was a crash, even though the error does not affect functionality. * The activity log for package operations will also show errors. * The patch overrides python-apt reporting of progress, as landscape-package-changer is never executed from a terminal. [Test Case] * register landscape-client and wait for packages to be reported. * trigger a package installation from the landscape server. * check /var/log/landscape/manager.log for Package changer warnings [Regression Potential] * The change is trivially simple. * The changed code path is only used by python-apt progress reporting. Since landscape-package-changer does not rely on it and is able to continue, other errors would likely have the same fate: that is crashing the progress reporting thread and continuing. [Original Description] Crash in the background ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: landscape-client 18.01-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Mar 24 07:05:34 2018 ExecutablePath: /usr/bin/landscape-package-changer InstallationDate: Installed on 2015-07-04 (994 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.6 ProcCmdline: /usr/bin/python3 /usr/bin/landscape-package-changer --quiet ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonArgs: ['/usr/bin/landscape-package-changer', '--quiet'] PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 SourcePackage: landscape-client Title: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno Traceback: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apt/progress/text.py", line 164, in pulse not os.isatty(self._file.fileno())): io.UnsupportedOperation: fileno UpgradeStatus: Upgraded to bionic on 2018-03-15 (8 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1758529/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed
The solution for this will be for us to provide a python-is-python3 package, not installed by default, which command-not-found will then offer. This will NOT be managed as an alternative. ** Changed in: python3-defaults (Ubuntu Focal) Status: Confirmed => Triaged ** Changed in: command-not-found (Ubuntu Focal) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1863532 Title: Invoking "python" brings inappropriate response from command-not-found when python3 installed Status in command-not-found package in Ubuntu: Triaged Status in python3-defaults package in Ubuntu: Triaged Status in command-not-found source package in Focal: Triaged Status in python3-defaults source package in Focal: Triaged Bug description: Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't have python 2.7 installed, but have python 3 installed as per default. Please see ascii-cast at https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 . Running `python` brings up text from command-not-found which suggests installing `python3` as a solution to the missing command. `python3` is already installed, is a later version than the one indicated by command-not-found and does not supply a binary or symlink named `python`. $ apt policy python python: Installed: (none) Candidate: (none) Version table: 2.7.17-1 -1 100 /var/lib/dpkg/status $ apt policy python3 python3: Installed: 3.8.0-3 Candidate: 3.8.0-3 Version table: *** 3.8.0-3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ apt policy command-not-found command-not-found: Installed: 19.10.0 Candidate: 19.10.0 Version table: *** 19.10.0 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status I don't know whether this is a bug in python3 or command-not-found (the latter of which doesn't seem to have been updated for 20.04 yet). i don't know if it is intentional that `python3` will not provide a binary or symlink named `python`. if that is the case, the output of `command-not-found` should be updated to reflect that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: python3 3.8.0-3 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: MATE Date: Mon Feb 17 01:35:16 2020 InstallationDate: Installed on 2019-10-11 (128 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2) SourcePackage: python3-defaults UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864526] Re: Display ghosting when dragging icons or opening menus
Further to my initial report -- I have also tested with another monitor Dell U3419W with the same results. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1864526 Title: Display ghosting when dragging icons or opening menus Status in xorg package in Ubuntu: New Bug description: Display ghosting when dragging icons or opening menus. Have tested several machines and this only occurring on Intel NUC 8i3BEK - and only when installing or using FOCAL Lubuntu 20.04 . This also is occurring in the Live sessions before install. I have tested Lubuntu Eoan 19.01 and Lubuntu Bionic 18.04.04 on this machine and cannot reproduce the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: LXQt Date: Mon Feb 24 18:23:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics 655 [8086:3ea5] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 655 [8086:2074] InstallationDate: Installed on 2020-02-24 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200224) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard Bus 001 Device 002: ID 2188:0ae1 USB OPTICAL MOUSE Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=11c10d68-db79-4d45-9bbe-8357e125b46b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0073.2019.0618.1409 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-307 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0073.2019.0618.1409:bd06/18/2019:svnIntel(R)ClientSystems:pnNUC8i3BEK:pvrJ72748-306:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-307:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: BE dmi.product.name: NUC8i3BEK dmi.product.sku: BOXNUC8i3BEK dmi.product.version: J72748-306 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1864526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864526] Re: Display ghosting when dragging icons or opening menus
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1864526 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1864526 Title: Display ghosting when dragging icons or opening menus Status in xorg package in Ubuntu: New Bug description: Display ghosting when dragging icons or opening menus. Have tested several machines and this only occurring on Intel NUC 8i3BEK - and only when installing or using FOCAL Lubuntu 20.04 . This also is occurring in the Live sessions before install. I have tested Lubuntu Eoan 19.01 and Lubuntu Bionic 18.04.04 on this machine and cannot reproduce the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: LXQt Date: Mon Feb 24 18:23:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics 655 [8086:3ea5] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 655 [8086:2074] InstallationDate: Installed on 2020-02-24 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200224) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard Bus 001 Device 002: ID 2188:0ae1 USB OPTICAL MOUSE Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=11c10d68-db79-4d45-9bbe-8357e125b46b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0073.2019.0618.1409 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-307 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0073.2019.0618.1409:bd06/18/2019:svnIntel(R)ClientSystems:pnNUC8i3BEK:pvrJ72748-306:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-307:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: BE dmi.product.name: NUC8i3BEK dmi.product.sku: BOXNUC8i3BEK dmi.product.version: J72748-306 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1864526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864526] [NEW] Display ghosting when dragging icons or opening menus
Public bug reported: Display ghosting when dragging icons or opening menus. Have tested several machines and this only occurring on Intel NUC 8i3BEK - and only when installing or using FOCAL Lubuntu 20.04 . This also is occurring in the Live sessions before install. I have tested Lubuntu Eoan 19.01 and Lubuntu Bionic 18.04.04 on this machine and cannot reproduce the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: LXQt Date: Mon Feb 24 18:23:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics 655 [8086:3ea5] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 655 [8086:2074] InstallationDate: Installed on 2020-02-24 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200224) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard Bus 001 Device 002: ID 2188:0ae1 USB OPTICAL MOUSE Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=11c10d68-db79-4d45-9bbe-8357e125b46b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0073.2019.0618.1409 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-307 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0073.2019.0618.1409:bd06/18/2019:svnIntel(R)ClientSystems:pnNUC8i3BEK:pvrJ72748-306:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-307:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: BE dmi.product.name: NUC8i3BEK dmi.product.sku: BOXNUC8i3BEK dmi.product.version: J72748-306 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal reproducible ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1864526 Title: Display ghosting when dragging icons or opening menus Status in xorg package in Ubuntu: New Bug description: Display ghosting when dragging icons or opening menus. Have tested several machines and this only occurring on Intel NUC 8i3BEK - and only when installing or using FOCAL Lubuntu 20.04 . This also is occurring in the Live sessions before install. I have tested Lubuntu Eoan 19.01 and Lubuntu Bionic 18.04.04 on this machine and cannot reproduce the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: LXQt Date: Mon Feb 24 18:23:21 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics 655 [8086:3ea5] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 655 [8086:2074] InstallationDate: Installed on 2020-02-24 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200224) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard Bus 001 Device 002: ID 2188:0ae1 USB OPTICAL MOUSE Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5
[Touch-packages] [Bug 1864505] Re: wifi service stops periodically
** Package changed: ubuntu => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1864505 Title: wifi service stops periodically Status in network-manager package in Ubuntu: New Bug description: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1864505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1025418] Re: Using ProxyCommand w/a non-existant host results in infinite spawns.
> A fix has been provided upstream. I believe the Ubuntu community should pick up from here and packages the fix. That looks like it's for the specialist ProxyJump directive though, and not the more general ProxyCommand? Please could you link to the upstream discussion? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1025418 Title: Using ProxyCommand w/a non-existant host results in infinite spawns. Status in openssh package in Ubuntu: Invalid Bug description: Version: OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012 Package: openssh-client Today we discovered a possible bug in the OpenSSH-Client package (openssh) that happens when you enable ProxyCommand with a non- existant hostname. This bug is easily replicated with the default example in /etc/ssh/ssh_config. If one uncomments that line and then for example tries to push via Git SSH you end up with SSH spawning over and over and over again as seein the attached screenshot. I have flagged this as a security bug (but ultimately it's up to ya'll if it is) because any user can do this and take down any server quite easily by adding add a bad ProxyCommand to their ~/.ssh/config. I was able to take out one of my personal servers (which happens to be a pretty big server) within a few minutes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1025418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861472] Re: upgrade from fresh bionic to focal needlessly prompts user
** Changed in: openssh (Ubuntu) Status: Triaged => Fix Committed ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Colin Watson (cjwatson) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1861472 Title: upgrade from fresh bionic to focal needlessly prompts user Status in openssh package in Ubuntu: Fix Committed Status in openssh package in Debian: Fix Released Bug description: Upgrading from a fresh 18.04 LTS install to focal unexpectedly prompts for how to handle a change to /etc/ssh/sshd_config To reproduce the issue: lxc launch ubuntu:18.04 u18 lxc exec u18 -- bash # within container do-release-upgrade -d # select restart services when prompted Eventually you'll be prompted to accept changes to /etc/ssh/sshd_config or not because of "local changes". Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.1p1-5 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Fri Jan 31 03:37:55 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: openssh UpgradeStatus: Upgraded to focal on 2020-01-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1861472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701298] Re: ssh_config should include /etc/ssh/ssh_config.d/* by default
** Changed in: openssh (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Colin Watson (cjwatson) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1701298 Title: ssh_config should include /etc/ssh/ssh_config.d/* by default Status in openssh package in Ubuntu: Fix Committed Bug description: It is not currently possible to deploy packages with system-specific SSH configuration settings without modifying the ssh_config file. Ideally the default ssh_config file would simply contain: Include /etc/ssh/ssh_config.d/* as this would allow packages to deploy such settings without tampering with the main ssh_config file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1701298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864505] [NEW] wifi service stops periodically
You have been subscribed to a public bug: I reported this previously, although the bug is different this time; previously I could restart the service effectively with "sudo service network-manager restart", however this time I have to turn on airplane mode and then turn it off again on my laptop in order to get Wi-Fi working again. Sometime after my original logging of the bug, the intermittent service failure stopped. Unfortunately I did not keep track of which update the problem disappeared after. For months the service was rock-solid without any failures, until the update last week 18/Feb/2020 and since then I've had to restart the service multiple times daily, very much the same as when I originally logged the bug. Not sure if I should attach more info and what? Thanks original bug post: https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/1822587 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 17:58:37 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-30 (1304 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.104 metric 600 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2019-10-26 (120 days ago) nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlp3s0f0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 HUAWEI-B315-D7CD 01a82e09-44b7-4509-af07-4bf05f76759a /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0f1 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- wifi service stops periodically https://bugs.launchpad.net/bugs/1864505 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863447] Re: openssh outdated by 8.2
** Changed in: openssh (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1863447 Title: openssh outdated by 8.2 Status in openssh package in Ubuntu: Fix Committed Bug description: Hi, yeah, it's not yet a bug, but it will become a (security) bug within lifetime of 20.04 if not 'fixed'. Currently openssh for Ubuntu 20.04 is still on 8.1p1, while upstream the version 8.2 has just been released: https://lists.mindrot.org/pipermail/openssh-unix- announce/2020-February/000138.html It comes with important security updates, e.g. not accepting SHA-1 for key generation/signature anymore, and using FIDO2/U2F-tokens as a second factor. Especially the latter significantly improves security and helps against stealing keys and hijacking machines. It would be important (and nice) to have these improvements of security in Ubuntu 20.04. It might not yet be seen as a security vulnerability, but it will probably become one soon. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848064] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report
** Description changed: + [Impact] + whoopsie-upload-all is not collecting data for existing crash reports which are not owned by root if /proc/sys/fs/protected_regular is set to 1. Subsequently, the crash reports are incomplete and not getting uploaded to the Error Tracker therefore Ubuntu developers may be missing out on important crash reports. + + [Test Case] + 1) Confirm /proc/sys/fs/protected_regular is set to 1. + 2) Run an application as your user and cause it to crash. (kill -11 $APP) + 3) Confirm there is a crash report in /var/crash + 4) Run 'sudo /usr/share/apport/whoopsie-upload-all' + 5) Observe the Traceback in this bug report is produced by whoopsie-upload-all. + + With the version of apport from -proposed the Traceback will not occur + and a .uploaded file will be created for the corresponding .crash file. + + [Regression Potential] + Not all systems may have /proc/sys/fs/protected_regular set to 1, so we should also test the case where /proc/sys/fs/protected_regular is set to 0. This can be done by manually changing the value and running through the test case above and confirming that a .uploaded file is created for the .crash file. + The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/d9f09f3b3e7aa8ab77434ef30f33416a856971ae 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/. ** Description changed: [Impact] whoopsie-upload-all is not collecting data for existing crash reports which are not owned by root if /proc/sys/fs/protected_regular is set to 1. Subsequently, the crash reports are incomplete and not getting uploaded to the Error Tracker therefore Ubuntu developers may be missing out on important crash reports. [Test Case] 1) Confirm /proc/sys/fs/protected_regular is set to 1. 2) Run an application as your user and cause it to crash. (kill -11 $APP) 3) Confirm there is a crash report in /var/crash 4) Run 'sudo /usr/share/apport/whoopsie-upload-all' 5) Observe the Traceback in this bug report is produced by whoopsie-upload-all. With the version of apport from -proposed the Traceback will not occur and a .uploaded file will be created for the corresponding .crash file. [Regression Potential] Not all systems may have /proc/sys/fs/protected_regular set to 1, so we should also test the case where /proc/sys/fs/protected_regular is set to 0. This can be done by manually changing the value and running through the test case above and confirming that a .uploaded file is created for the .crash file. + Original Description + The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/d9f09f3b3e7aa8ab77434ef30f33416a856971ae 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/. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1848064 Title: /usr/share/apport/whoopsie-upload- all:PermissionError:/usr/share/apport/whoopsie-upload- all@168:collect_info:process_report Status in apport package in Ubuntu: Fix Released Status in apport source package in Eoan: In Progress Bug description: [Impact] whoopsie-upload-all is not collecting data for existing crash reports which are not owned by root if /proc/sys/fs/protected_regular is set to 1. Subsequently, the crash reports are incomplete and not getting uploaded to the Error Tracker therefore Ubuntu developers may be missing out on important crash reports. [Test Case] 1) Confirm /proc/sys/fs/protected_regular is set to 1. 2) Run an application as your user and cause it to crash. (kill -11 $APP) 3) Confirm there is a crash report in /var/crash 4) Run 'sudo /usr/share/apport/whoopsie-upload-all' 5) Observe the Traceback in this bug report is produced by whoopsie-upload-all. With the version of apport from -proposed the Traceback will not occur and a .uploaded file will be created for the corresponding .crash file. [Regression Potential] Not all systems may have /proc/sys/fs/protected_regular set to 1, so we should also test the case where /proc/sys/fs/protected_regular is set to 0. This can be done by manually changing the value and running through the test case above
[Touch-packages] [Bug 1848064] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report
** Changed in: apport (Ubuntu Eoan) Status: Confirmed => In Progress ** Changed in: apport (Ubuntu Eoan) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1848064 Title: /usr/share/apport/whoopsie-upload- all:PermissionError:/usr/share/apport/whoopsie-upload- all@168:collect_info:process_report Status in apport package in Ubuntu: Fix Released Status in apport source package in Eoan: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu8, the problem page at https://errors.ubuntu.com/problem/d9f09f3b3e7aa8ab77434ef30f33416a856971ae 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/apport/+bug/1848064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
For clickhouse, the fix was added in https://launchpad.net/ubuntu/+source/clickhouse/18.16.1+ds-5ubuntu1 but that is currently failing to build on arm64 and s390x for other reasons. I'll mark its task as "fix committed". ** Changed in: clickhouse (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: Fix Released Status in asterisk package in Ubuntu: Fix Released Status in clickhouse package in Ubuntu: Fix Committed Status in cppdb package in Ubuntu: Fix Released Status in dballe package in Ubuntu: Fix Released Status in gambas3 package in Ubuntu: Fix Released Status in gearmand package in Ubuntu: Fix Released Status in gerbera package in Ubuntu: Fix Released Status in gnokii package in Ubuntu: Fix Released Status in gnunet package in Ubuntu: Fix Released Status in hoel package in Ubuntu: Fix Released Status in isc-kea package in Ubuntu: Fix Released Status in jabberd2 package in Ubuntu: Fix Released Status in kannel package in Ubuntu: Fix Released Status in libgda5 package in Ubuntu: Fix Released Status in libodb-mysql package in Ubuntu: Fix Released Status in lyricue package in Ubuntu: Fix Released Status in motion package in Ubuntu: Fix Released Status in mysql-8.0 package in Ubuntu: Fix Released Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: Fix Released Status in opendnssec package in Ubuntu: Fix Released Status in opensmtpd-extras package in Ubuntu: Fix Released Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: Fix Released Status in pvpgn package in Ubuntu: Fix Released Status in qt4-x11 package in Ubuntu: Fix Released Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: Fix Released Status in tntdb package in Ubuntu: Fix Released Status in voms-mysql-plugin package in Ubuntu: Fix Released Status in vtk7 package in Ubuntu: Fix Released Status in w1retap package in Ubuntu: Fix Released Status in zoneminder package in Ubuntu: In Progress Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1532440] Re: touchpad setting missing when using a wireless keyboard with touchpad
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: d-conf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1532440 Title: touchpad setting missing when using a wireless keyboard with touchpad Status in d-conf package in Ubuntu: Confirmed Bug description: 1. Plug in a wireless keyboard with a built-in trackpad (I have the logitech K400 Plus). 2. open dconf-editor 3. go to org > gnome > settings-daemon > peripherals 4. see that there is no "touchpad" entry My laptop has a touchpad entry that allows me to adjust touchpad-specific parameters. I would expect these to show up with the wireless keyboard/touchpad. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: dconf-cli 0.24.0-2 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 9 14:41:02 2016 InstallationDate: Installed on 2015-09-30 (100 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) JournalErrors: No journal files were found. -- No entries -- SourcePackage: d-conf UpgradeStatus: Upgraded to wily on 2015-11-01 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1532440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563110]
Our vision for every child, life in all its fullness. Our prayer for every heart, the will to make it so.We work toward a nation and a world where every child experiences life in all its fullness. Where they are protected, cared for to and given the opportunities to become everything they’re Child Ngos meant to be. https://www.hopetoshine.in -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Fix Released Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563110]
Sponsoring a child through World Vision India is one of the best, motivating and compensating approaches to support youngsters. You'll be doing significantly more than assisting with meeting youngsters' fundamental needs – you'll be assisting with equiping them forever. By achieving enduring change in your supported kid's locale, you'll likewise be improving the lives of numerous other defenseless youngsters to Child Ngos child sponsorship is probably the most ideal approaches to give kids better lives and prospects of. At the point when you support a youngster, you will get photo of your supported kid, data about your kid, kid's family and network, yearly report showing the advancement of your kid, World Vision India's magazine Jeevan Sparsh and a chance to blessing, compose or visit your supported kid. https://www.worldvision.in -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Fix Released Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864057] Re: Xorg Server terminated with error (1) on Intel/18.04 Laptop
Thanks timo , I understand this would be never patched in 18.04 ? Can you publish a "workaround" so our clients on 18.04 could avoid 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/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in systemd package in Ubuntu: Fix Released Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 Notes : Possible Root cause : [ 9.014] (EE) modeset(0): drmSetMaster failed: Permission denied [ 9.014] (EE) Fatal server error: [ 9.014] (EE) AddScreen/ScreenInit failed for driver 0 [ 9.014] (EE) It seems related to systemd : https://github.com/systemd/systemd/issues/13943 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1864057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864057] Re: Xorg Server terminated with error (1) on Intel/18.04 Laptop
right, this should be a systemd bug and fixed in focal ** Package changed: xorg-server (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1864057 Title: Xorg Server terminated with error (1) on Intel/18.04 Laptop Status in systemd package in Ubuntu: Fix Released Bug description: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 Notes : Possible Root cause : [ 9.014] (EE) modeset(0): drmSetMaster failed: Permission denied [ 9.014] (EE) Fatal server error: [ 9.014] (EE) AddScreen/ScreenInit failed for driver 0 [ 9.014] (EE) It seems related to systemd : https://github.com/systemd/systemd/issues/13943 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1864057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864057] [NEW] Xorg Server terminated with error (1) on Intel/18.04 Laptop
You have been subscribed to a public bug: On a 18.04 ( kernel 5.3 ) Intel laptop : - At cold start Xorg keeps crashing several times - After Several restart , Xorg finally suceed to start - it seems user encounter that since kernel 5.3 Notes : Possible Root cause : [ 9.014] (EE) modeset(0): drmSetMaster failed: Permission denied [ 9.014] (EE) Fatal server error: [ 9.014] (EE) AddScreen/ScreenInit failed for driver 0 [ 9.014] (EE) It seems related to systemd : https://github.com/systemd/systemd/issues/13943 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1325] InstallationDate: Installed on 2019-03-04 (353 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc. Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N150ZU Package: xorg-server (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_AG.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Tags: bionic ubuntu Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/19/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.01 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: systemd (Ubuntu) Importance: Undecided Status: Fix Released ** Tags: apport-collected bionic ubuntu -- Xorg Server terminated with error (1) on Intel/18.04 Laptop https://bugs.launchpad.net/bugs/1864057 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758529] Please test proposed package
Hello Adam, or anyone else affected, Accepted landscape-client into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/landscape- client/18.01-0ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1758529 Title: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno Status in Landscape Client: Fix Committed Status in landscape-client package in Ubuntu: Fix Released Status in python-apt package in Ubuntu: Invalid Status in landscape-client source package in Bionic: Fix Committed Status in python-apt source package in Bionic: Invalid Status in landscape-client source package in Disco: Won't Fix Status in python-apt source package in Disco: Invalid Status in landscape-client source package in Eoan: Fix Committed Status in python-apt source package in Eoan: Invalid Bug description: [Impact] * landscape-package-changer will output stack traces when executed with python3. This adds noise in the logs and confuse apport into thinking there was a crash, even though the error does not affect functionality. * The activity log for package operations will also show errors. * The patch overrides python-apt reporting of progress, as landscape-package-changer is never executed from a terminal. [Test Case] * register landscape-client and wait for packages to be reported. * trigger a package installation from the landscape server. * check /var/log/landscape/manager.log for Package changer warnings [Regression Potential] * The change is trivially simple. * The changed code path is only used by python-apt progress reporting. Since landscape-package-changer does not rely on it and is able to continue, other errors would likely have the same fate: that is crashing the progress reporting thread and continuing. [Original Description] Crash in the background ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: landscape-client 18.01-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Mar 24 07:05:34 2018 ExecutablePath: /usr/bin/landscape-package-changer InstallationDate: Installed on 2015-07-04 (994 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.6 ProcCmdline: /usr/bin/python3 /usr/bin/landscape-package-changer --quiet ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonArgs: ['/usr/bin/landscape-package-changer', '--quiet'] PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 SourcePackage: landscape-client Title: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno Traceback: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apt/progress/text.py", line 164, in pulse not os.isatty(self._file.fileno())): io.UnsupportedOperation: fileno UpgradeStatus: Upgraded to bionic on 2018-03-15 (8 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1758529/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758529] Re: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno
Hello Adam, or anyone else affected, Accepted landscape-client into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/landscape- client/18.01-0ubuntu9.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: landscape-client (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan ** Changed in: landscape-client (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1758529 Title: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno Status in Landscape Client: Fix Committed Status in landscape-client package in Ubuntu: Fix Released Status in python-apt package in Ubuntu: Invalid Status in landscape-client source package in Bionic: Fix Committed Status in python-apt source package in Bionic: Invalid Status in landscape-client source package in Disco: Won't Fix Status in python-apt source package in Disco: Invalid Status in landscape-client source package in Eoan: Fix Committed Status in python-apt source package in Eoan: Invalid Bug description: [Impact] * landscape-package-changer will output stack traces when executed with python3. This adds noise in the logs and confuse apport into thinking there was a crash, even though the error does not affect functionality. * The activity log for package operations will also show errors. * The patch overrides python-apt reporting of progress, as landscape-package-changer is never executed from a terminal. [Test Case] * register landscape-client and wait for packages to be reported. * trigger a package installation from the landscape server. * check /var/log/landscape/manager.log for Package changer warnings [Regression Potential] * The change is trivially simple. * The changed code path is only used by python-apt progress reporting. Since landscape-package-changer does not rely on it and is able to continue, other errors would likely have the same fate: that is crashing the progress reporting thread and continuing. [Original Description] Crash in the background ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: landscape-client 18.01-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Mar 24 07:05:34 2018 ExecutablePath: /usr/bin/landscape-package-changer InstallationDate: Installed on 2015-07-04 (994 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.6 ProcCmdline: /usr/bin/python3 /usr/bin/landscape-package-changer --quiet ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonArgs: ['/usr/bin/landscape-package-changer', '--quiet'] PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 SourcePackage: landscape-client Title: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno Traceback: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apt/progress/text.py", line 164, in pulse not os.isatty(self._file.fileno())): io.UnsupportedOperation: fileno UpgradeStatus: Upgraded to bionic on 2018-03-15 (8 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1758529/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~
[Touch-packages] [Bug 1864423] Re: Failed test 'default log is not used' with new procps 3.3.16-1
The behavior change is because the new procps from Debian is setting an additional sysctl setting: ./debian/protect- links.conf:fs.protected_regular = 2 systemd in 20.04 was previously setting this to 1, which led to some issues, discussed at https://lists.ubuntu.com/archives/ubuntu- devel/2020-February/040904.html No one appears to be asking for this to be set to 2, and we don't know how many other things will be broken by this change. We might want to revert this in procps. ** Changed in: procps (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1864423 Title: Failed test 'default log is not used' with new procps 3.3.16-1 Status in postgresql-common package in Ubuntu: In Progress Status in procps package in Ubuntu: New Bug description: Since the new procps upload procps | 2:3.3.16-1ubuntu1 | focal-proposed | source, amd64, arm64, armhf, i386, ppc64el, s390x the tests of postgresql-common fail. The issues are: autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - results - - - - - - - - - - run-testsuiteFAIL non-zero exit status 2 autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - stderr - - - - - - - - - - # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 143. # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 154. # Looks like you failed 2 tests of 144. It was retried a few times by different people now and reproduced so we can assume it is a real issues for now. I was running two VMs to compare: $ sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries --apt-upgrade --test-name=run-testsuite --apt-pocket=proposed=src:procps --shell postgresql-common_211.dsc -- qemu --qemu-options='-cpu host' --ram-size=2048 --cpus 2 ~/work/autopkgtest-focal-amd64.img (and the other one without --apt-pocket=proposed=src:procps) The issue reproduced locally in only the one with the new procps. In Debian the latest similar run is https://ci.debian.net/data/autopkgtest/testing/amd64/p/postgresql-common/4279031/log.gz https://ci.debian.net/data/packages/testing/amd64/p/postgresql-common/4279031.log But that is pre-3.3.16 and I wasn't able to find their result with the same combination. Lets mark this bug update-excuse and check if we can find anything in these VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1864423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864424] Re: new vim version in 20.04 sets mouse=a by default
** Changed in: vim (Ubuntu) Importance: Undecided => High ** Changed in: vim (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1864424 Title: new vim version in 20.04 sets mouse=a by default Status in vim package in Ubuntu: Fix Committed Bug description: Upgrading vim in Focal from 2:8.1.0875-5ubuntu4 to 2:8.1.2269-1ubuntu1 changed the default behavior. Old: :set mouse mouse= New: :set mouse mouse=a That new behavior prevents most peoples common In fact that is one thing that always annoys me when working with a Debian VM/Container to have switch to mouse=v to get things working again. Issues: - marking something with the mouse does NOT copy it anymore - marking something with the mouse does not even allow right-click to copy - probably more Yes I know one could press shift to get the old behavior, but that isn't how the rest of the terminal works. I'd much prefer to "press shift for the uncommon/new behavior". We always had in the changelog: - debian/patches/ubuntu-mouse-off.patch: + Mouse mode is actively harmful in some chroots. Old bug 1661691 brought that delta in early 2017 But this was dropped on the last merge: * Dropped changes, included upstream: - debian/patches/ubuntu-mouse-off.patch: + Mouse mode is actively harmful in some chroots. Yet if this would be upstream then the behavior would not have changed right? Was this change intentional and is there a good reason that makes up for the drawback? Or is it a bug that was missed on the merge of the new version and should be resolved before 20.04 goes into FF? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1864424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758529] Re: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1758529 Title: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno Status in Landscape Client: Fix Committed Status in landscape-client package in Ubuntu: Fix Released Status in python-apt package in Ubuntu: Invalid Status in landscape-client source package in Bionic: In Progress Status in python-apt source package in Bionic: Invalid Status in landscape-client source package in Disco: Won't Fix Status in python-apt source package in Disco: Invalid Status in landscape-client source package in Eoan: In Progress Status in python-apt source package in Eoan: Invalid Bug description: [Impact] * landscape-package-changer will output stack traces when executed with python3. This adds noise in the logs and confuse apport into thinking there was a crash, even though the error does not affect functionality. * The activity log for package operations will also show errors. * The patch overrides python-apt reporting of progress, as landscape-package-changer is never executed from a terminal. [Test Case] * register landscape-client and wait for packages to be reported. * trigger a package installation from the landscape server. * check /var/log/landscape/manager.log for Package changer warnings [Regression Potential] * The change is trivially simple. * The changed code path is only used by python-apt progress reporting. Since landscape-package-changer does not rely on it and is able to continue, other errors would likely have the same fate: that is crashing the progress reporting thread and continuing. [Original Description] Crash in the background ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: landscape-client 18.01-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Mar 24 07:05:34 2018 ExecutablePath: /usr/bin/landscape-package-changer InstallationDate: Installed on 2015-07-04 (994 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.6 ProcCmdline: /usr/bin/python3 /usr/bin/landscape-package-changer --quiet ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonArgs: ['/usr/bin/landscape-package-changer', '--quiet'] PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 SourcePackage: landscape-client Title: landscape-package-changer crashed with io.UnsupportedOperation in pulse(): fileno Traceback: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apt/progress/text.py", line 164, in pulse not os.isatty(self._file.fileno())): io.UnsupportedOperation: fileno UpgradeStatus: Upgraded to bionic on 2018-03-15 (8 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1758529/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
** Changed in: network-manager (Ubuntu Bionic) Status: Confirmed => In Progress ** Tags added: sts-sponsor-dgadomski -- 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/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: In Progress Bug description: [Impact] In case creating bond interface, IPv4 address is not automatically assigned when IPv6 has manual setting. [Test Case] 1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description. 2. ipv6 manual, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5; sudo nmcli c s bond0 ## 3. ipv6 auto, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method auto; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5 sudo nmcli c s bond0 ## when run #3, it is working, but with #2, it is not working. [Potential Regression] Actually nothing special. fix just remove if statement. but it needs Network Manager restarted. [Other informations] After upstream fix, it is working fine with #2 and #3 above. * Upstream bug and fix: https://bugzilla.redhat.com/show_bug.cgi?id=1575944 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35 * Only affecting Bionic: $ git describe --contains f03ae35 1.10.8~2 $ rmadison network-manager ==> network-manager | 1.10.6-2ubuntu1.2 | bionic-updates network-manager | 1.20.4-2ubuntu2.2 | eoan-updates network-manager | 1.22.4-1ubuntu2 | focal [Original description] ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of
[Touch-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
@xtrusia, Is this ready for sponsorship ? I'll have a look when ready. - Eric -- 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/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: In Progress Bug description: [Impact] In case creating bond interface, IPv4 address is not automatically assigned when IPv6 has manual setting. [Test Case] 1. create 18.04.4 instance, network-manager version is 1.10.6-2ubuntu.1.2 as original description. 2. ipv6 manual, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method manual ipv6.addresses fe81::ff:fe97:a27f/64; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5; sudo nmcli c s bond0 ## 3. ipv6 auto, ipv4 auto ## sudo nmcli con add type bond con-name bond0 ifname bond0 mode active-backup; sudo nmcli con mod bond0 bond.options "downdelay=0, fail_over_mac=none, miimon=100, mode=active-backup,num_grat_arp=0, primary_reselect=always, updelay=0"; sudo nmcli con mod bond0 ipv6.method auto; sudo nmcli con mod bond0 ipv4.method auto; sudo nmcli con add type bond-slave ifname ens34 master bond0; sudo nmcli con add type bond-slave ifname ens35 master bond0; sudo nmcli con mod bond0 +bond.options mii=100 sleep 5 sudo nmcli con up bond-slave-ens34 sudo nmcli con up bond-slave-ens35 sudo nmcli con up bond0; sleep 5 sudo nmcli c s bond0 ## when run #3, it is working, but with #2, it is not working. [Potential Regression] Actually nothing special. fix just remove if statement. but it needs Network Manager restarted. [Other informations] After upstream fix, it is working fine with #2 and #3 above. * Upstream bug and fix: https://bugzilla.redhat.com/show_bug.cgi?id=1575944 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35 * Only affecting Bionic: $ git describe --contains f03ae35 1.10.8~2 $ rmadison network-manager ==> network-manager | 1.10.6-2ubuntu1.2 | bionic-updates network-manager | 1.20.4-2ubuntu2.2 | eoan-updates network-manager | 1.22.4-1ubuntu2 | focal [Original description] ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 N
[Touch-packages] [Bug 1861408] Re: firefox apparmor messages
/ r,
/**/ r,
is not enough. because thumbnails are not shown. much better would be to use a
separate program as a helper application, while it can read all files but it is
very simple and can only open a file by gui mouse click, and cannot connect
internet.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1861408
Title:
firefox apparmor messages
Status in apparmor package in Ubuntu:
New
Status in firefox package in Ubuntu:
New
Bug description:
firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
19.3.
i see there is newer ubuntu version in
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
, 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
apparmor.
i have not found a page for firefox bugs in linux mint sites, so i
belive i should report here. but i have also asked about that in linux
mint's irc and then github.
i have enabled apparmor for firefox and see these types of messages in
syslog:
Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")
Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5525.077960] audit: type=1400 audit(1580226276.440:27):
apparmor="DENIED" operation="capable"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
comm="firefox" capability=21 capname="sys_admin"
Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/RealtimeKit1"
interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
name="org.freedesktop.RealtimeKit1" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/Private/RemoteVolumeMonitor"
interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
mask="send" name=":1.35" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="ListMounts2" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="LookupMount" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
pid=15948 comm="/usr/lib/firefox/firefox "
label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/hostname1"
interface="org.freedesktop.DBus.Properties" member="GetAll"
mask="send" name=":1.120" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
peer_label="unconfined"
Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
member="Change" mask="send" name="ca.desrt.dconf" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
peer_label="unconfined"
Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel:
[10131.880788] audit: type=1400 audit(1580237490.777:123):
apparmor="DENIED" operation="open"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/dinar/.cache/mesa_
[Touch-packages] [Bug 1864466] [NEW] abstraction file for tcpwrappers
Public bug reported: Please include an abstraction file for TCP wappers - e.g. abstractions/tcpwap This would include, at minimum, ``` /etc/hosts.allow r, /etc/hosts.deny r, ``` Software built to read hosts.allow (e.g. built with libwrap0) will usually have these permissions incorporated into their AppArmor profiles. However, the hosts.allow/deny files can reference other files in arbitrary filesystem locations - so any file references in hosts.allow must also then be added to all profiles that reference hosts.allow. Using an abstraction would allow this to be added once. from man 5 hosts.allow ``` A string that begins with a '/' character is treated as a file name. A host name or address is matched if it matches any host name or address pattern listed in the named file. The file format is zero or more lines with zero or more host name or address patterns separated by whitespace. A file name pattern can be used anywhere a host name or address pattern can be used. ``` ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1864466 Title: abstraction file for tcpwrappers Status in apparmor package in Ubuntu: New Bug description: Please include an abstraction file for TCP wappers - e.g. abstractions/tcpwap This would include, at minimum, ``` /etc/hosts.allow r, /etc/hosts.deny r, ``` Software built to read hosts.allow (e.g. built with libwrap0) will usually have these permissions incorporated into their AppArmor profiles. However, the hosts.allow/deny files can reference other files in arbitrary filesystem locations - so any file references in hosts.allow must also then be added to all profiles that reference hosts.allow. Using an abstraction would allow this to be added once. from man 5 hosts.allow ``` A string that begins with a '/' character is treated as a file name. A host name or address is matched if it matches any host name or address pattern listed in the named file. The file format is zero or more lines with zero or more host name or address patterns separated by whitespace. A file name pattern can be used anywhere a host name or address pattern can be used. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1864466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1742941] Re: zlib: improve crc32 performance on P8
** Changed in: ubuntu-power-systems Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1742941 Title: zlib: improve crc32 performance on P8 Status in The Ubuntu-power-systems project: Triaged Status in zlib package in Ubuntu: Triaged Bug description: Calculate the checksum of data that is 16 byte aligned and a multiple of 16 bytes. The first step is to reduce it to 1024 bits. We do this in 8 parallel chunks in order to mask the latency of the vpmsum instructions. If we have more than 32 kB of data to checksum we repeat this step multiple times, passing in the previous 1024 bits. The next step is to reduce the 1024 bits to 64 bits. This step adds 32 bits of 0s to the end - this matches what a CRC does. We just calculate constants that land the data in this 32 bits. We then use fixed point Barrett reduction to compute a mod n over GF(2) for n = CRC using POWER8 instructions. We use x = 32. http://en.wikipedia.org/wiki/Barrett_reduction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1742941/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container
Just in case, I also removed any arptables or iptables on the host. The problem is still present. Here is an even simpler LXC configuration file to reproduce (privileged LXC container on Debian Buster, 5.4.13 kernel): # Distribution configuration lxc.include = /usr/share/lxc/config/common.conf lxc.arch = linux64 # Container specific configuration lxc.hook.pre-start = /usr/local/share/lxc/hooks/pre-start.sh vps526706 lxc.hook.post-stop = /usr/local/share/lxc/hooks/post-stop.sh vps526706 lxc.hook.destroy = /usr/local/share/lxc/hooks/destroy.sh vps526706 lxc.mount.fstab = /lxc/vps526706/fstab lxc.rootfs.path = dir:/lxc/vps526706/rootfs lxc.uts.name = vps526706 # Network configuration lxc.net.0.type = veth lxc.net.0.veth.pair = vps526706 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:67:06 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.171/32 -- 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/1863873 Title: Systemd fails to configure bridged network in LXC container Status in systemd package in Ubuntu: Incomplete Bug description: In all our unprivileged LXC containers running Bionic Beaver, installing systemd 237-3ubuntu10.39 results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. Hosts: Debian Buster custom 5.3.9, 5.4.8 or 5.4.13 kernel Example container network configuration: lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Steps to reproduce, inside the container: root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.39 [104 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.39 [107 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.39 [2912 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.39 [206 kB] Fetched 3330 kB in 3s (1274 kB/s) (Reading database ... 18195 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libnss-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.39_amd64.deb ... Unpacking libpam-systemd:amd64 (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../systemd_237-3ubuntu10.39_amd64.deb ... Unpacking systemd (237-3ubuntu10.39) over (237-3ubuntu10.38) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.39_amd64.deb ... Unpacking libsyste
[Touch-packages] [Bug 1025418] Re: Using ProxyCommand w/a non-existant host results in infinite spawns.
A fix has been provided upstream. I believe the Ubuntu community should pick up from here and packages the fix. [ ... snip ...] Darren Tucker: We had some discussion about it amongst ourselves, but we were working on the 8.2 release at the time and we judged it too late to risk including this as it would potentially invalidate testing done to that point. I actually commited[1] this change earlier today, and you can try it yourself by trying either checking out the source or trying a development snapshot[3]. Please let us know if you notice any problems. [1] https://github.com/openssh/openssh-portable/commit/de1f3564cd85915b3002859873a37cb8d31ac9ce [3] https://www.mindrot.org/openssh_snap/openssh-SNAP-20200218.tar.gz or https://www.mindrot.org/openssh_snap/openssh-SNAP-20200219.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1025418 Title: Using ProxyCommand w/a non-existant host results in infinite spawns. Status in openssh package in Ubuntu: Invalid Bug description: Version: OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012 Package: openssh-client Today we discovered a possible bug in the OpenSSH-Client package (openssh) that happens when you enable ProxyCommand with a non- existant hostname. This bug is easily replicated with the default example in /etc/ssh/ssh_config. If one uncomments that line and then for example tries to push via Git SSH you end up with SSH spawning over and over and over again as seein the attached screenshot. I have flagged this as a security bug (but ultimately it's up to ya'll if it is) because any user can do this and take down any server quite easily by adding add a bad ProxyCommand to their ~/.ssh/config. I was able to take out one of my personal servers (which happens to be a pretty big server) within a few minutes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1025418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864423] Re: Failed test 'default log is not used' with new procps 3.3.16-1
Submitted to Debian via: https://salsa.debian.org/postgresql/postgresql-common/merge_requests/8 And if there are no other blockers Myon will do an upload soon, so we can sync and retest procps against that then. ** Changed in: postgresql-common (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1864423 Title: Failed test 'default log is not used' with new procps 3.3.16-1 Status in postgresql-common package in Ubuntu: In Progress Status in procps package in Ubuntu: New Bug description: Since the new procps upload procps | 2:3.3.16-1ubuntu1 | focal-proposed | source, amd64, arm64, armhf, i386, ppc64el, s390x the tests of postgresql-common fail. The issues are: autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - results - - - - - - - - - - run-testsuiteFAIL non-zero exit status 2 autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - stderr - - - - - - - - - - # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 143. # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 154. # Looks like you failed 2 tests of 144. It was retried a few times by different people now and reproduced so we can assume it is a real issues for now. I was running two VMs to compare: $ sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries --apt-upgrade --test-name=run-testsuite --apt-pocket=proposed=src:procps --shell postgresql-common_211.dsc -- qemu --qemu-options='-cpu host' --ram-size=2048 --cpus 2 ~/work/autopkgtest-focal-amd64.img (and the other one without --apt-pocket=proposed=src:procps) The issue reproduced locally in only the one with the new procps. In Debian the latest similar run is https://ci.debian.net/data/autopkgtest/testing/amd64/p/postgresql-common/4279031/log.gz https://ci.debian.net/data/packages/testing/amd64/p/postgresql-common/4279031.log But that is pre-3.3.16 and I wasn't able to find their result with the same combination. Lets mark this bug update-excuse and check if we can find anything in these VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1864423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864423] Re: Failed test 'default log is not used' with new procps 3.3.16-1
I see no difference between the simple test above and the status when the real test is running: Bad: -rw-r- 1 postgres adm 559 Feb 24 10:55 /var/log/postgresql/postgresql-12-main.log 12 main 5432 online postgres /var/lib/postgresql/12/main /var/log/postgresql/postgresql-12-main.log Good: -rw-r- 1 postgres adm 1594 Feb 24 10:56 /var/log/postgresql/postgresql-12-main.log 12 main 5432 online postgres /var/lib/postgresql/12/main /var/log/postgresql/postgresql-12-main.log That is exactly the same (some file size difference) and works to clean in one, but fails in the other environment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1864423 Title: Failed test 'default log is not used' with new procps 3.3.16-1 Status in postgresql-common package in Ubuntu: New Status in procps package in Ubuntu: New Bug description: Since the new procps upload procps | 2:3.3.16-1ubuntu1 | focal-proposed | source, amd64, arm64, armhf, i386, ppc64el, s390x the tests of postgresql-common fail. The issues are: autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - results - - - - - - - - - - run-testsuiteFAIL non-zero exit status 2 autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - stderr - - - - - - - - - - # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 143. # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 154. # Looks like you failed 2 tests of 144. It was retried a few times by different people now and reproduced so we can assume it is a real issues for now. I was running two VMs to compare: $ sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries --apt-upgrade --test-name=run-testsuite --apt-pocket=proposed=src:procps --shell postgresql-common_211.dsc -- qemu --qemu-options='-cpu host' --ram-size=2048 --cpus 2 ~/work/autopkgtest-focal-amd64.img (and the other one without --apt-pocket=proposed=src:procps) The issue reproduced locally in only the one with the new procps. In Debian the latest similar run is https://ci.debian.net/data/autopkgtest/testing/amd64/p/postgresql-common/4279031/log.gz https://ci.debian.net/data/packages/testing/amd64/p/postgresql-common/4279031.log But that is pre-3.3.16 and I wasn't able to find their result with the same combination. Lets mark this bug update-excuse and check if we can find anything in these VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1864423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864253] Re: Pulseaudio sink/source selection, weird behaviour.
Link to the report to the PulseAudio developers. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/814 ** Bug watch added: PulseAudio #814 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/814 -- 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/1864253 Title: Pulseaudio sink/source selection, weird behaviour. Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have a Laptop connected to an USB-C dock. By default the docks analog audio output is chosen as the default pulse audio sink. I want that the analog output of the Laptop is the default, hence I configured this in /etc/pulse/default.py This does not work and journalctl informs me that the device chosen by me (alsa_output.pci-_00_1f.3.analog-stereo) does not exist, see attached output from journalctl. I have followed Workaround 1 here https://wiki.debian.org/BluetoothUser/a2dp to prevent pulseaudio getting started in gdm to prevent device capture. This does not work, the device does still not exist. Restarting pulseaudio sometimes, but not always sets the configured default sink. Furthermore plugging in the headphones in the Laptops analog input switches audio to the dock. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: findus 3055 F pulseaudio /dev/snd/controlC1: findus 3055 F pulseaudio /dev/snd/controlC0: findus 3055 F pulseaudio /dev/snd/pcmC0D0p: findus 3055 F...m pulseaudio CurrentDesktop: i3 Date: Fri Feb 21 22:19:04 2020 InstallationDate: Installed on 2019-06-13 (253 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET80W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S0UB00 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET80W(1.58):bd11/26/2019:svnLENOVO:pn20N3S0UB00:pvrThinkPadT490:rvnLENOVO:rn20N3S0UB00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S0UB00 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-02-21T20:38:20.081439 mtime.conffile..etc.pulse.default.pa: 2020-02-21T19:27:57.386938 mtime.conffile..etc.pulse.system.pa: 2020-02-21T15:23:09.470494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1864253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864253] Re: Pulseaudio sink/source selection, weird behaviour.
You might only need to comment out: load-module module-switch-on-port-available -- 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/1864253 Title: Pulseaudio sink/source selection, weird behaviour. Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have a Laptop connected to an USB-C dock. By default the docks analog audio output is chosen as the default pulse audio sink. I want that the analog output of the Laptop is the default, hence I configured this in /etc/pulse/default.py This does not work and journalctl informs me that the device chosen by me (alsa_output.pci-_00_1f.3.analog-stereo) does not exist, see attached output from journalctl. I have followed Workaround 1 here https://wiki.debian.org/BluetoothUser/a2dp to prevent pulseaudio getting started in gdm to prevent device capture. This does not work, the device does still not exist. Restarting pulseaudio sometimes, but not always sets the configured default sink. Furthermore plugging in the headphones in the Laptops analog input switches audio to the dock. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: findus 3055 F pulseaudio /dev/snd/controlC1: findus 3055 F pulseaudio /dev/snd/controlC0: findus 3055 F pulseaudio /dev/snd/pcmC0D0p: findus 3055 F...m pulseaudio CurrentDesktop: i3 Date: Fri Feb 21 22:19:04 2020 InstallationDate: Installed on 2019-06-13 (253 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET80W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S0UB00 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET80W(1.58):bd11/26/2019:svnLENOVO:pn20N3S0UB00:pvrThinkPadT490:rvnLENOVO:rn20N3S0UB00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S0UB00 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-02-21T20:38:20.081439 mtime.conffile..etc.pulse.default.pa: 2020-02-21T19:27:57.386938 mtime.conffile..etc.pulse.system.pa: 2020-02-21T15:23:09.470494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1864253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864253] Re: Pulseaudio sink/source selection, weird behaviour.
I also have this commented out. I will report to the PulseAudio developers. -- 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/1864253 Title: Pulseaudio sink/source selection, weird behaviour. Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have a Laptop connected to an USB-C dock. By default the docks analog audio output is chosen as the default pulse audio sink. I want that the analog output of the Laptop is the default, hence I configured this in /etc/pulse/default.py This does not work and journalctl informs me that the device chosen by me (alsa_output.pci-_00_1f.3.analog-stereo) does not exist, see attached output from journalctl. I have followed Workaround 1 here https://wiki.debian.org/BluetoothUser/a2dp to prevent pulseaudio getting started in gdm to prevent device capture. This does not work, the device does still not exist. Restarting pulseaudio sometimes, but not always sets the configured default sink. Furthermore plugging in the headphones in the Laptops analog input switches audio to the dock. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: findus 3055 F pulseaudio /dev/snd/controlC1: findus 3055 F pulseaudio /dev/snd/controlC0: findus 3055 F pulseaudio /dev/snd/pcmC0D0p: findus 3055 F...m pulseaudio CurrentDesktop: i3 Date: Fri Feb 21 22:19:04 2020 InstallationDate: Installed on 2019-06-13 (253 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET80W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S0UB00 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET80W(1.58):bd11/26/2019:svnLENOVO:pn20N3S0UB00:pvrThinkPadT490:rvnLENOVO:rn20N3S0UB00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S0UB00 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-02-21T20:38:20.081439 mtime.conffile..etc.pulse.default.pa: 2020-02-21T19:27:57.386938 mtime.conffile..etc.pulse.system.pa: 2020-02-21T15:23:09.470494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1864253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864253] Re: Pulseaudio sink/source selection, weird behaviour.
It sounds like PulseAudio is not very smart and doesn't understand docks are hotpluggable audio devices which themselves may be dormant and unused. Try commenting out both: load-module module-switch-on-port-available and load-module module-switch-on-connect If those two changes together do not solve the problem then please report the bug to the PulseAudio developers at https://gitlab.freedesktop.org/groups/pulseaudio/-/issues ** Changed in: pulseaudio (Ubuntu) Status: Won't Fix => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1864253 Title: Pulseaudio sink/source selection, weird behaviour. Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have a Laptop connected to an USB-C dock. By default the docks analog audio output is chosen as the default pulse audio sink. I want that the analog output of the Laptop is the default, hence I configured this in /etc/pulse/default.py This does not work and journalctl informs me that the device chosen by me (alsa_output.pci-_00_1f.3.analog-stereo) does not exist, see attached output from journalctl. I have followed Workaround 1 here https://wiki.debian.org/BluetoothUser/a2dp to prevent pulseaudio getting started in gdm to prevent device capture. This does not work, the device does still not exist. Restarting pulseaudio sometimes, but not always sets the configured default sink. Furthermore plugging in the headphones in the Laptops analog input switches audio to the dock. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: findus 3055 F pulseaudio /dev/snd/controlC1: findus 3055 F pulseaudio /dev/snd/controlC0: findus 3055 F pulseaudio /dev/snd/pcmC0D0p: findus 3055 F...m pulseaudio CurrentDesktop: i3 Date: Fri Feb 21 22:19:04 2020 InstallationDate: Installed on 2019-06-13 (253 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET80W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S0UB00 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET80W(1.58):bd11/26/2019:svnLENOVO:pn20N3S0UB00:pvrThinkPadT490:rvnLENOVO:rn20N3S0UB00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S0UB00 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-02-21T20:38:20.081439 mtime.conffile..etc.pulse.default.pa: 2020-02-21T19:27:57.386938 mtime.conffile..etc.pulse.system.pa: 2020-02-21T15:23:09.470494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1864253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864423] Re: Failed test 'default log is not used' with new procps 3.3.16-1
I found that it depends on file permissions/ownership.
The construct:
open L, ">$default_log"; close L; # empty default log file
only works if you are the file owner.
The test is running as root and the open/close will fail to open the
postgres:adm opened file.
A simple test might look like:
use strict;
use warnings;
my $default_log = "/tmp/test";
system("rm $default_log");
system("echo 'SOME TEST CONTENT' > $default_log");
system("chmod 666 $default_log");
system("chown postgres:adm $default_log");
system("id");
system("/usr/bin/ls","-laF","$default_log");
system("echo","PRE");
system("/usr/bin/cat","$default_log");
open L, ">$default_log"; close L; # empty default log file
system("echo","POST");
system("/usr/bin/cat","$default_log");
I'm still missing the role of the new procps version in this, as the
above is the same in both procps versions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1864423
Title:
Failed test 'default log is not used' with new procps 3.3.16-1
Status in postgresql-common package in Ubuntu:
New
Status in procps package in Ubuntu:
New
Bug description:
Since the new procps upload
procps | 2:3.3.16-1ubuntu1 | focal-proposed | source, amd64, arm64,
armhf, i386, ppc64el, s390x
the tests of postgresql-common fail.
The issues are:
autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - results - -
- - - - - - - -
run-testsuiteFAIL non-zero exit status 2
autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - stderr - - -
- - - - - - -
# Failed test 'default log is not used'
# at ./t/020_create_sql_remove.t line 143.
# Failed test 'default log is not used'
# at ./t/020_create_sql_remove.t line 154.
# Looks like you failed 2 tests of 144.
It was retried a few times by different people now and reproduced so
we can assume it is a real issues for now.
I was running two VMs to compare:
$ sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries
--apt-upgrade --test-name=run-testsuite --apt-pocket=proposed=src:procps
--shell postgresql-common_211.dsc -- qemu --qemu-options='-cpu host'
--ram-size=2048 --cpus 2 ~/work/autopkgtest-focal-amd64.img
(and the other one without --apt-pocket=proposed=src:procps)
The issue reproduced locally in only the one with the new procps.
In Debian the latest similar run is
https://ci.debian.net/data/autopkgtest/testing/amd64/p/postgresql-common/4279031/log.gz
https://ci.debian.net/data/packages/testing/amd64/p/postgresql-common/4279031.log
But that is pre-3.3.16 and I wasn't able to find their result with the same
combination.
Lets mark this bug update-excuse and check if we can find anything in
these VMs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1864423/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864253] Re: Pulseaudio sink/source selection, weird behaviour.
I have commented `load-module module-switch-on-connect` out in both `/etc/pulse/default.pa` and `~/.config/pulse/default.pa`. This does not work. For instance unplugging the headset from the laptop switches the default sink to the dock. The laptop has speakers and a microphone built in, the dock has not. Why switch the default devices to somewhere where no sound can be played or recorded. And why switch even if the switching module is not loaded? -- 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/1864253 Title: Pulseaudio sink/source selection, weird behaviour. Status in pulseaudio package in Ubuntu: Won't Fix Bug description: I have a Laptop connected to an USB-C dock. By default the docks analog audio output is chosen as the default pulse audio sink. I want that the analog output of the Laptop is the default, hence I configured this in /etc/pulse/default.py This does not work and journalctl informs me that the device chosen by me (alsa_output.pci-_00_1f.3.analog-stereo) does not exist, see attached output from journalctl. I have followed Workaround 1 here https://wiki.debian.org/BluetoothUser/a2dp to prevent pulseaudio getting started in gdm to prevent device capture. This does not work, the device does still not exist. Restarting pulseaudio sometimes, but not always sets the configured default sink. Furthermore plugging in the headphones in the Laptops analog input switches audio to the dock. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: findus 3055 F pulseaudio /dev/snd/controlC1: findus 3055 F pulseaudio /dev/snd/controlC0: findus 3055 F pulseaudio /dev/snd/pcmC0D0p: findus 3055 F...m pulseaudio CurrentDesktop: i3 Date: Fri Feb 21 22:19:04 2020 InstallationDate: Installed on 2019-06-13 (253 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET80W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S0UB00 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET80W(1.58):bd11/26/2019:svnLENOVO:pn20N3S0UB00:pvrThinkPadT490:rvnLENOVO:rn20N3S0UB00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S0UB00 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-02-21T20:38:20.081439 mtime.conffile..etc.pulse.default.pa: 2020-02-21T19:27:57.386938 mtime.conffile..etc.pulse.system.pa: 2020-02-21T15:23:09.470494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1864253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831736] Re: [MIR] lz4 by default
** Merge proposal linked: https://code.launchpad.net/~lihow731/ubuntu/+source/live-build/+git/live-build/+merge/379717 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1831736 Title: [MIR] lz4 by default Status in Release Upgrader: New Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in live-build package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in lz4 package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: Use `lz4 -9 -l` compression for initramfs by default as discussed on ubuntu-devel. This would also pull the lz4 package into main https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html [Regression Potential] We are trying to optimize for total boot speed, but performing a micro-optimization upon time to create/unpack kernel/initrd is an insufficient benchmark for total boot speed. This is because it ignores time to load the kernel/initrd, and whether the firmware/bootloader were able to stream decompress it whilst loading it. I.e. it is argued that in the real world, subsecond decompression gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot longer than that to read extra 10s of MBs of boot material. [TODO] Measure pure i/o load speed with stopwatch, to figure out MB/s speed of loading initrds/kernel off FAT32, EXT4, TFTP, HTTP. Re-evaluate if we should provide different compression mechanisms: - ie. gzip instead of lz4 for most cases (revert) - ie. xz for painful i/o cases (e.g. netboot) I booted grub2 and measured loading largish amount of files, ie. $ date; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; date To get a rough speed between 30 and 44 MB/s of loading these files off ext4 on nvme. With lz4 initrd taking 67M, and gzip initrd taking 59M, the grub i/o penalty is 0.18s whilst I gain over a second in faster decompression time. Overall a win. xz initrd is 36M meaning saving e.g. 0.8s of i/o time whilst gaining 2.4s of decompression time, meaning overall worse than gzip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1831736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
Can you please check the config file under /boot? -- 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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864423] Re: Failed test 'default log is not used' with new procps 3.3.16-1
A trivial check like: $ echo foo > testfile; perl -e 'my $test = "/home/ubuntu/testfile"; open L, ">$test"; close L;' cat testfile Is not broken, it must be more special to the test env of postgresql- common ?! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1864423 Title: Failed test 'default log is not used' with new procps 3.3.16-1 Status in postgresql-common package in Ubuntu: New Status in procps package in Ubuntu: New Bug description: Since the new procps upload procps | 2:3.3.16-1ubuntu1 | focal-proposed | source, amd64, arm64, armhf, i386, ppc64el, s390x the tests of postgresql-common fail. The issues are: autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - results - - - - - - - - - - run-testsuiteFAIL non-zero exit status 2 autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - stderr - - - - - - - - - - # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 143. # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 154. # Looks like you failed 2 tests of 144. It was retried a few times by different people now and reproduced so we can assume it is a real issues for now. I was running two VMs to compare: $ sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries --apt-upgrade --test-name=run-testsuite --apt-pocket=proposed=src:procps --shell postgresql-common_211.dsc -- qemu --qemu-options='-cpu host' --ram-size=2048 --cpus 2 ~/work/autopkgtest-focal-amd64.img (and the other one without --apt-pocket=proposed=src:procps) The issue reproduced locally in only the one with the new procps. In Debian the latest similar run is https://ci.debian.net/data/autopkgtest/testing/amd64/p/postgresql-common/4279031/log.gz https://ci.debian.net/data/packages/testing/amd64/p/postgresql-common/4279031.log But that is pre-3.3.16 and I wasn't able to find their result with the same combination. Lets mark this bug update-excuse and check if we can find anything in these VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1864423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864423] Re: Failed test 'default log is not used' with new procps 3.3.16-1
Replacing the perl construct open L, ">$default_log"; close L; # empty default log file with the also more readable: truncate "$default_log", 0; Fixes the issue in postgresql-common. That might be a fix for this particular test, but (unfortunately) the construct above is a common use-case in perl how did procps break that?? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1864423 Title: Failed test 'default log is not used' with new procps 3.3.16-1 Status in postgresql-common package in Ubuntu: New Status in procps package in Ubuntu: New Bug description: Since the new procps upload procps | 2:3.3.16-1ubuntu1 | focal-proposed | source, amd64, arm64, armhf, i386, ppc64el, s390x the tests of postgresql-common fail. The issues are: autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - results - - - - - - - - - - run-testsuiteFAIL non-zero exit status 2 autopkgtest [15:43:10]: test run-testsuite: - - - - - - - - - - stderr - - - - - - - - - - # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 143. # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 154. # Looks like you failed 2 tests of 144. It was retried a few times by different people now and reproduced so we can assume it is a real issues for now. I was running two VMs to compare: $ sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries --apt-upgrade --test-name=run-testsuite --apt-pocket=proposed=src:procps --shell postgresql-common_211.dsc -- qemu --qemu-options='-cpu host' --ram-size=2048 --cpus 2 ~/work/autopkgtest-focal-amd64.img (and the other one without --apt-pocket=proposed=src:procps) The issue reproduced locally in only the one with the new procps. In Debian the latest similar run is https://ci.debian.net/data/autopkgtest/testing/amd64/p/postgresql-common/4279031/log.gz https://ci.debian.net/data/packages/testing/amd64/p/postgresql-common/4279031.log But that is pre-3.3.16 and I wasn't able to find their result with the same combination. Lets mark this bug update-excuse and check if we can find anything in these VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1864423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864423] Re: Failed test 'default log is not used' with new procps 3.3.16-1
The failing tests are part of 020_create_sql_remove.t: The checks are like: ok -z $default_log, "default log is not used"; And $default_log points to /var/log/postgresql/postgresql-12-main.log in both cases. Entering interactive mode on fail: $ sudo ./testsuite -f 20 -V -s Eventually the whole cluster is cleaned, so the config and dirs are missing. Changing the tests to find more details ... The test sets a link: /etc/postgresql/12/main/log -> /var/lib/postgresql/12/main/mylog And then the instance is correctly using that log: $ pg_lsclusters -h 12 main 5432 online postgres /var/lib/postgresql/12/main /var/lib/postgresql/12/main/mylog But the old log "still" exists in the bad case and that breaks it. log: Config >> symlink >> default path The check wants to see the "default path" to be not existing - or actually not used. It tries to clean the log via: is ((exec_as 'root', "pg_ctlcluster $v main stop"), 0, 'stopping cluster'); open L, ">$default_log"; close L; # empty default log file The problem seems to be non synchronous stop or a log file clean issue - the log still contains stuff after being cleaned. ok 11 - correct output of pg_lsclusters -h /usr/bin/ls: cannot access '/etc/postgresql/12/main/log': No such file or directory -rw-r- 1 postgres adm 559 Feb 24 09:23 /var/log/postgresql/postgresql-12-main.log 12 main 5432 online postgres /var/lib/postgresql/12/main /var/log/postgresql/postgresql-12-main.log PRE STOP 2020-02-24 09:23:07.177 CET [16492] LOG: starting PostgreSQL 12.1 (Ubuntu 12.1-2build1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.2.1-25ubuntu1) 9.2.1 20200123, 64-bit 2020-02-24 09:23:07.177 CET [16492] LOG: listening on IPv4 address "127.0.0.1", port 5432 2020-02-24 09:23:07.177 CET [16492] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2020-02-24 09:23:07.188 CET [16493] LOG: database system was shut down at 2020-02-24 09:23:06 CET 2020-02-24 09:23:07.192 CET [16492] LOG: database system is ready to accept connections -- END -- ok 12 - stopping cluster PRE CLEAN 2020-02-24 09:23:07.177 CET [16492] LOG: starting PostgreSQL 12.1 (Ubuntu 12.1-2build1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.2.1-25ubuntu1) 9.2.1 20200123, 64-bit 2020-02-24 09:23:07.177 CET [16492] LOG: listening on IPv4 address "127.0.0.1", port 5432 2020-02-24 09:23:07.177 CET [16492] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2020-02-24 09:23:07.188 CET [16493] LOG: database system was shut down at 2020-02-24 09:23:06 CET 2020-02-24 09:23:07.192 CET [16492] LOG: database system is ready to accept connections 2020-02-24 09:23:09.669 CET [16492] LOG: received fast shutdown request 2020-02-24 09:23:09.669 CET [16492] LOG: aborting any active transactions 2020-02-24 09:23:09.671 CET [16492] LOG: background worker "logical replication launcher" (PID 16499) exited with exit code 1 2020-02-24 09:23:09.673 CET [16494] LOG: shutting down 2020-02-24 09:23:09.680 CET [16492] LOG: database system is shut down -- END -- POST CLEAN 2020-02-24 09:23:07.177 CET [16492] LOG: starting PostgreSQL 12.1 (Ubuntu 12.1-2build1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.2.1-25ubuntu1) 9.2.1 20200123, 64-bit 2020-02-24 09:23:07.177 CET [16492] LOG: listening on IPv4 address "127.0.0.1", port 5432 2020-02-24 09:23:07.177 CET [16492] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2020-02-24 09:23:07.188 CET [16493] LOG: database system was shut down at 2020-02-24 09:23:06 CET 2020-02-24 09:23:07.192 CET [16492] LOG: database system is ready to accept connections 2020-02-24 09:23:09.669 CET [16492] LOG: received fast shutdown request 2020-02-24 09:23:09.669 CET [16492] LOG: aborting any active transactions 2020-02-24 09:23:09.671 CET [16492] LOG: background worker "logical replication launcher" (PID 16499) exited with exit code 1 2020-02-24 09:23:09.673 CET [16494] LOG: shutting down 2020-02-24 09:23:09.680 CET [16492] LOG: database system is shut down -- END -- ok 13 - restarting cluster with nondefault log symlink lrwxrwxrwx 1 root root 33 Feb 24 09:23 /etc/postgresql/12/main/log -> /var/lib/postgresql/12/main/mylog -rw-r- 1 postgres adm 961 Feb 24 09:23 /var/log/postgresql/postgresql-12-main.log 12 main 5432 online postgres /var/lib/postgresql/12/main /var/lib/postgresql/12/main/mylog ok 14 - log target is used as log file not ok 15 - default log is not used # Failed test 'default log is not used' # at ./t/020_create_sql_remove.t line 104. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1864423 Title: Failed test 'default log is not used' with new procps 3.3.16-1 Status in postgresql-common package in Ubuntu: New Status in procps package in Ubuntu: New Bug description: Since the new procps upload procps | 2:3.3.16-1ubuntu1 | focal-proposed |
[Touch-packages] [Bug 1861472] Re: upgrade from fresh bionic to focal needlessly prompts user
** Changed in: openssh (Debian) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1861472 Title: upgrade from fresh bionic to focal needlessly prompts user Status in openssh package in Ubuntu: Triaged Status in openssh package in Debian: Fix Released Bug description: Upgrading from a fresh 18.04 LTS install to focal unexpectedly prompts for how to handle a change to /etc/ssh/sshd_config To reproduce the issue: lxc launch ubuntu:18.04 u18 lxc exec u18 -- bash # within container do-release-upgrade -d # select restart services when prompted Eventually you'll be prompted to accept changes to /etc/ssh/sshd_config or not because of "local changes". Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.1p1-5 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Fri Jan 31 03:37:55 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: openssh UpgradeStatus: Upgraded to focal on 2020-01-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1861472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864424] Re: new vim version in 20.04 sets mouse=a by default
Subscribing Steve who did the merge according to the Changelog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1864424 Title: new vim version in 20.04 sets mouse=a by default Status in vim package in Ubuntu: New Bug description: Upgrading vim in Focal from 2:8.1.0875-5ubuntu4 to 2:8.1.2269-1ubuntu1 changed the default behavior. Old: :set mouse mouse= New: :set mouse mouse=a That new behavior prevents most peoples common In fact that is one thing that always annoys me when working with a Debian VM/Container to have switch to mouse=v to get things working again. Issues: - marking something with the mouse does NOT copy it anymore - marking something with the mouse does not even allow right-click to copy - probably more Yes I know one could press shift to get the old behavior, but that isn't how the rest of the terminal works. I'd much prefer to "press shift for the uncommon/new behavior". We always had in the changelog: - debian/patches/ubuntu-mouse-off.patch: + Mouse mode is actively harmful in some chroots. Old bug 1661691 brought that delta in early 2017 But this was dropped on the last merge: * Dropped changes, included upstream: - debian/patches/ubuntu-mouse-off.patch: + Mouse mode is actively harmful in some chroots. Yet if this would be upstream then the behavior would not have changed right? Was this change intentional and is there a good reason that makes up for the drawback? Or is it a bug that was missed on the merge of the new version and should be resolved before 20.04 goes into FF? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1864424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864424] [NEW] new vim version in 20.04 sets mouse=a by default
Public bug reported: Upgrading vim in Focal from 2:8.1.0875-5ubuntu4 to 2:8.1.2269-1ubuntu1 changed the default behavior. Old: :set mouse mouse= New: :set mouse mouse=a That new behavior prevents most peoples common In fact that is one thing that always annoys me when working with a Debian VM/Container to have switch to mouse=v to get things working again. Issues: - marking something with the mouse does NOT copy it anymore - marking something with the mouse does not even allow right-click to copy - probably more Yes I know one could press shift to get the old behavior, but that isn't how the rest of the terminal works. I'd much prefer to "press shift for the uncommon/new behavior". We always had in the changelog: - debian/patches/ubuntu-mouse-off.patch: + Mouse mode is actively harmful in some chroots. Old bug 1661691 brought that delta in early 2017 But this was dropped on the last merge: * Dropped changes, included upstream: - debian/patches/ubuntu-mouse-off.patch: + Mouse mode is actively harmful in some chroots. Yet if this would be upstream then the behavior would not have changed right? Was this change intentional and is there a good reason that makes up for the drawback? Or is it a bug that was missed on the merge of the new version and should be resolved before 20.04 goes into FF? ** Affects: vim (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1864424 Title: new vim version in 20.04 sets mouse=a by default Status in vim package in Ubuntu: New Bug description: Upgrading vim in Focal from 2:8.1.0875-5ubuntu4 to 2:8.1.2269-1ubuntu1 changed the default behavior. Old: :set mouse mouse= New: :set mouse mouse=a That new behavior prevents most peoples common In fact that is one thing that always annoys me when working with a Debian VM/Container to have switch to mouse=v to get things working again. Issues: - marking something with the mouse does NOT copy it anymore - marking something with the mouse does not even allow right-click to copy - probably more Yes I know one could press shift to get the old behavior, but that isn't how the rest of the terminal works. I'd much prefer to "press shift for the uncommon/new behavior". We always had in the changelog: - debian/patches/ubuntu-mouse-off.patch: + Mouse mode is actively harmful in some chroots. Old bug 1661691 brought that delta in early 2017 But this was dropped on the last merge: * Dropped changes, included upstream: - debian/patches/ubuntu-mouse-off.patch: + Mouse mode is actively harmful in some chroots. Yet if this would be upstream then the behavior would not have changed right? Was this change intentional and is there a good reason that makes up for the drawback? Or is it a bug that was missed on the merge of the new version and should be resolved before 20.04 goes into FF? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1864424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
