[Touch-packages] [Bug 1824118] Re: wpa_supplicant executes hundreds of failed atempts in a second
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wpa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1824118 Title: wpa_supplicant executes hundreds of failed atempts in a second Status in wpa package in Ubuntu: Confirmed Bug description: I use my computer to create a wifi hotspot to my local wired network. Whenever I do so I get short hangs that last for about a second every few minutes. Looking into the syslog in /var/log/syslog I get the output at the end of this message. I have tried my best to look for an answer to this bug, but the reported bugs on wpa_supplicant are all for other ret codes. Best, Victor Apr 10 10:54:40 Amaterasu wpa_supplicant[1048]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1 Apr 10 10:55:13 Amaterasu wpa_supplicant[1048]: message repeated 33 times: [ wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1] Apr 10 10:55:14 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] Activating via systemd: service name='org.gnome.evince.Daemon' unit='evince.service' requested by ':1.413' (uid=1000 pid=6414 comm="emacs lib/legacy/uv_check.f90 " label="unconfined") Apr 10 10:55:14 Amaterasu systemd[1695]: Starting Evince document viewer... Apr 10 10:55:14 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] Successfully activated service 'org.gnome.evince.Daemon' Apr 10 10:55:14 Amaterasu systemd[1695]: Started Evince document viewer. Apr 10 10:55:14 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] Activating service name='org.x.reader.Daemon' requested by ':1.413' (uid=1000 pid=6414 comm="emacs lib/legacy/uv_check.f90 " label="unconfined") Apr 10 10:55:14 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] Successfully activated service 'org.x.reader.Daemon' Apr 10 10:55:14 Amaterasu wpa_supplicant[1048]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1 Apr 10 10:55:37 Amaterasu wpa_supplicant[1048]: message repeated 23 times: [ wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1] Apr 10 10:55:38 Amaterasu dbus-daemon[1748]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/Notifications" interface="org.freedesktop.Notifications" member="Notify" mask="send" name="org.freedesktop.Notifications" pid=2263 label="snap.spotify.spotify" Apr 10 10:55:38 Amaterasu wpa_supplicant[1048]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1 Apr 10 10:57:39 Amaterasu wpa_supplicant[1048]: message repeated 120 times: [ wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1] Apr 10 10:57:40 Amaterasu dbus-daemon[1748]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/Notifications" interface="org.freedesktop.Notifications" member="Notify" mask="send" name="org.freedesktop.Notifications" pid=2263 label="snap.spotify.spotify" Apr 10 10:57:40 Amaterasu wpa_supplicant[1048]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1 Apr 10 10:58:15 Amaterasu wpa_supplicant[1048]: message repeated 35 times: [ wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1] Apr 10 10:58:15 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] Activating via systemd: service name='org.gnome.evince.Daemon' unit='evince.service' requested by ':1.421' (uid=1000 pid=6772 comm="emacs /var/log/syslog " label="unconfined") Apr 10 10:58:15 Amaterasu systemd[1695]: Starting Evince document viewer... Apr 10 10:58:15 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] Successfully activated service 'org.gnome.evince.Daemon' Apr 10 10:58:15 Amaterasu systemd[1695]: Started Evince document viewer. Apr 10 10:58:15 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] Activating service name='org.x.reader.Daemon' requested by ':1.421' (uid=1000 pid=6772 comm="emacs /var/log/syslog " label="unconfined") Apr 10 10:58:15 Amaterasu dbus-daemon[1748]: [session uid=1000 pid=1748] Successfully activated service 'org.x.reader.Daemon' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1824118/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552577] Re: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123]
** Changed in: gtk Status: Unknown => New -- 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/1552577 Title: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123] Status in Apport: New Status in GTK+: New Status in apport package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/92c580cf48dae63a366ee45b28a16be710f70347 --- Crash displayed after logging in. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport-gtk 2.20-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 1 22:13:24 2016 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2016-02-21 (10 days ago) InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208 InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk SegvAnalysis: Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi PC (0x7f3a0219cb89) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1552577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812014] Re: keyboard not responding after suspend after some time
[Expired for upower (Ubuntu) because there has been no activity for 60 days.] ** Changed in: upower (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Expired Status in nvidia-graphics-drivers-390 package in Ubuntu: Expired Status in upower package in Ubuntu: Expired Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812014] Re: keyboard not responding after suspend after some time
[Expired for nvidia-graphics-drivers-390 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Expired Status in nvidia-graphics-drivers-390 package in Ubuntu: Expired Status in upower package in Ubuntu: Expired Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812014] Re: keyboard not responding after suspend after some time
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Expired Status in nvidia-graphics-drivers-390 package in Ubuntu: Expired Status in upower package in Ubuntu: Expired Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831264] Re: Sun keyboard Front key not accepted by gnome-control-center
** Changed in: xkeyboard-config Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1831264 Title: Sun keyboard Front key not accepted by gnome-control-center Status in xkeyboard-config: New Status in xkeyboard-config package in Ubuntu: Triaged Bug description: A Sun keyboards is recognized by the hardware detector with no problem. xmodmap -pk gives the following for the relevant keys: 136 0xff69 (Cancel) 0x (NoSymbol) 0xff69 (Cancel) 137 0xff66 (Redo) 0x (NoSymbol) 0xff66 (Redo) 138 0x1005ff70 (SunProps) 0x (NoSymbol) 0x1005ff70 (SunProps) 139 0xff65 (Undo) 0x (NoSymbol) 0xff65 (Undo) 140 0x1005ff71 (SunFront) 0x (NoSymbol) 0x1005ff71 (SunFront) 141 0x1008ff57 (XF86Copy) 0x (NoSymbol) 0x1008ff57 (XF86Copy) 142 0x1008ff6b (XF86Open) 0x (NoSymbol) 0x1008ff6b (XF86Open) 143 0x1008ff6d (XF86Paste) 0x (NoSymbol) 0x1008ff6d (XF86Paste) 144 0xff68 (Find) 0x (NoSymbol) 0xff68 (Find) 145 0x1008ff58 (XF86Cut)0x (NoSymbol) 0x1008ff58 (XF86Cut) 146 0xff6a (Help) 0x (NoSymbol) 0xff6a (Help) Observe that the names of the two keysyms 0x1005ff70 and 0x1005ff71 are SUN specials, not in the XF86 set. Pressing either of these using xev behaves as expected: KeyPress event, serial 37, synthetic NO, window 0x361, root 0x4fe, subw 0x0, time 3071686, (118,83), root:(1365,168), state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x361, root 0x4fe, subw 0x0, time 3071688, (118,83), root:(1365,168), state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False I tried binding "Lower window below other windows" to the SunFront using the Settings app, but it did not work.(Note that back in the days of 14.04 where you uses CCSM to make this setting, it worked fine.) After this I did $ dconf dump /org/gnome/desktop/wm/keybindings/ [/] lower=['0x1005ff71'] switch-to-workspace-1=['1'] move-to-workspace-1=@as [] switch-to-workspace-2=['2'] switch-to-workspace-3=['3'] switch-to-workspace-4=['4'] move-to-monitor-down=@as [] move-to-monitor-up=@as [] So it had recognized the correct keysym, but does not know that the name of that keysym is SunFront. So far so bad. It works fine with keysyms with known names (e.g. the CANCEL key), and it should not be hard to construct a workaround my modifying the keyboard tables to map that key to some better-named keysym, so it might be argued that this bug is of Low Priority. BUT there is a serious side effect. With that dconf setting in place: the Left Arrow key on the keyboard no longer works (for example, I made that change whilst composing this report, and I cannot now move the cursor backwards with the Left Arrow key, though fortunately the Left Arrow on the numeric keypad still behaves). All applications seem to be affected (e.g. Firefox, Terminal, Gedit). Left and Left still work, except that if you engage Num Lock, Left now stops working. Using xev to see what happens when Left Arrow is pressed yields: FocusOut event, serial 37, synthetic NO, window 0x361, mode NotifyGrab, detail NotifyAncestor FocusOut event, serial 37, synthetic NO, window 0x361, mode NotifyUngrab, detail NotifyPointer FocusIn event, serial 37, synthetic NO, window 0x361, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 37, synthetic NO, window 0x0, keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 which is crazy! You should not be surprised that I spent a whole day gradually removing all the changes I had made until finally I narrowed it down to dconf, and then to that particular setting. Changing the binding back to CANCEL removes the problem (except that you have to restart each application affected, so I have just restarted Terminal, but I cannot restart Firefox while I am still typing this report). My main worry is that there may be some other keybinding errors that cause the same side effect, and therefor the Priority of fixing this bug needs to be much higher. Moreover, this problem seems to have been around for a long time. see:
[Touch-packages] [Bug 1820666] Re: wifi disconnects when a device connects with bluetooth to the computer
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1820666 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1820666 Title: wifi disconnects when a device connects with bluetooth to the computer Status in Ubuntu MATE: Invalid Status in linux package in Ubuntu: Incomplete Bug description: When a device connects to the computer using Bluetooth the Wi-Fi disconnects for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1820666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812310] Re: No more sound on lenovo R61i booting MATE 16.04
** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1812310 Title: No more sound on lenovo R61i booting MATE 16.04 Status in Ubuntu MATE: Invalid Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: When booting MATE 16.04 on my lenovo R61i, I no longer have sound. I was able to listen to a YouTube video from the laptop when booting Linux Mint, but can no longer hear ANYTHING when booting MATE 16.04 Thanks for your consideration, Abu Billy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1812310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769391] Re: 18.04 Install, not detecting bluetooth
** No longer affects: bluez (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769391 Title: 18.04 Install, not detecting bluetooth Status in Ubuntu MATE: Invalid Status in linux package in Ubuntu: Incomplete Bug description: tyoma@HP-Pavilion-g7-Notebook-PC:~$ lspci -knn | grep Net -A3; lsusb 01:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01) Subsystem: Hewlett-Packard Company AR9485 Wireless Network Adapter [103c:1785] Kernel driver in use: ath9k Kernel modules: ath9k 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 05) Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 004: ID 0cf3:311d Atheros Communications, Inc. Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 058f:a001 Alcor Micro Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 0e8f:00a7 GreenAsia Inc. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub tyoma@HP-Pavilion-g7-Notebook-PC:~$ 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no tyoma@HP-Pavilion-g7-Notebook-PC:~$ sudo /etc/init.d/bluetooth start [ ok ] Starting bluetooth (via systemctl): bluetooth.service. tyoma@HP-Pavilion-g7-Notebook-PC:~$ hciconfig -a hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:6 acl:0 sco:0 events:1 errors:0 TX bytes:3 acl:0 sco:0 commands:6 errors:5 Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Packet type: DM1 DH1 HV1 Link policy: Link mode: SLAVE ACCEPT tyoma@HP-Pavilion-g7-Notebook-PC:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1769391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552577] Re: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123]
Now tracking in https://gitlab.gnome.org/GNOME/gtk/issues/994 I submitted a fix in 2017 but unfortunately it was not accepted. ** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #994 https://gitlab.gnome.org/GNOME/gtk/issues/994 ** Changed in: gtk Importance: High => Unknown ** Changed in: gtk Status: Expired => Unknown ** Changed in: gtk Remote watch: GNOME Bug Tracker #791647 => gitlab.gnome.org/GNOME/gtk/issues #994 -- 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/1552577 Title: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123] Status in Apport: New Status in GTK+: Unknown Status in apport package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/92c580cf48dae63a366ee45b28a16be710f70347 --- Crash displayed after logging in. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport-gtk 2.20-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 1 22:13:24 2016 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2016-02-21 (10 days ago) InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208 InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk SegvAnalysis: Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi PC (0x7f3a0219cb89) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1552577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831523] [NEW] recoverable_problem (PermissionError) /usr/share/apport/recoverable_problem@78 → main → add_proc_info
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu23, the problem page at https://errors.ubuntu.com/problem/72c621876cfe04b51b37f8f3ef08c3da0460b462 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic disco kylin-18.04 kylin-18.10 zesty -- 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/1831523 Title: recoverable_problem (PermissionError) /usr/share/apport/recoverable_problem@78 → main → add_proc_info Status in apport package in Ubuntu: New 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.10-0ubuntu23, the problem page at https://errors.ubuntu.com/problem/72c621876cfe04b51b37f8f3ef08c3da0460b462 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/1831523/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831523] Re: recoverable_problem (PermissionError) /usr/share/apport/recoverable_problem@78 → main → add_proc_info
** Summary changed: - /usr/share/apport/recoverable_problem:PermissionError:/usr/share/apport/recoverable_problem@78:main:add_proc_info + recoverable_problem (PermissionError) /usr/share/apport/recoverable_problem@78 → main → add_proc_info -- 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/1831523 Title: recoverable_problem (PermissionError) /usr/share/apport/recoverable_problem@78 → main → add_proc_info Status in apport package in Ubuntu: New 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.10-0ubuntu23, the problem page at https://errors.ubuntu.com/problem/72c621876cfe04b51b37f8f3ef08c3da0460b462 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/1831523/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821904] Re: Sound is muted by default after upgrading 18.04->18.10->19.04
** Changed in: pulseaudio (Ubuntu) Status: Expired => 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/1821904 Title: Sound is muted by default after upgrading 18.04->18.10->19.04 Status in pulseaudio package in Ubuntu: New Bug description: On Disco, Gnome Shell always starts muted. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe4766 F pulseaudio /dev/snd/pcmC0D0p: joe4766 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-09-15 (193 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:12.2-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Tags: disco wayland-session Uname: Linux 5.0.0-7-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-03-20 (7 days ago) UserGroups: adm cdrom dip input kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1821904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822446] Re: [B450M DS3H, Realtek ALC887-VD] Sound is occasionally distorted
** Changed in: pulseaudio (Ubuntu) Status: Expired => New ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1822446 Title: [B450M DS3H, Realtek ALC887-VD] Sound is occasionally distorted Status in pulseaudio package in Ubuntu: Invalid Bug description: Sound from youtube in playing firefox is distorted. After waiting a half hour the problem went away. i then tried to file a bug report. while playing the first set of test tones the test tone played fine after it finished the youtube audio was distorted again. then the second set of test tones from the troubleshooter played and were distorted as well. Also in the summary it ended up saying "FRONT" but it is the rear green jack on my motherboard that i am plugged into. Description: Ubuntu Disco Dingo (development branch) Release: 19.04 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mike 1833 F pulseaudio /dev/snd/pcmC1D0p: mike 1833 F...m pulseaudio /dev/snd/controlC0: mike 1833 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 21:02:38 2019 InstallationDate: Installed on 2019-03-30 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190329) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [B450M DS3H, Realtek ALC887-VD, Green Headphone Out, Front] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1822446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)
I just hit this bug with 19.04... The following "/usr/lib/gnome-online-accounts/goa-daemon --replace" did sort of reactivated my accounts accessibility. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: GNOME Online Accounts breaks if you log out (until you reboot) Status in gnome-online-accounts: Confirmed Status in Ubuntu GNOME: Fix Released Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-session package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Yakkety: Won't Fix Status in gnome-session source package in Yakkety: Won't Fix Status in gnome-online-accounts source package in Zesty: Won't Fix Status in gnome-session source package in Zesty: Won't Fix Bug description: Impact == After logging out, GNOME Online Accounts doesn't work the next time you log in. This bug was a Release Blocker for Fedora 26. (Fedora 26 will be released in July). gnome-session is the only package updated in this update (not gnome- online-accounts). Test Case = From Ubuntu GNOME, click Settings>Online Accounts and add your Google account. Install Evolution if it's not installed. Verified that your Google account has synced. Log out. Log in. It may help to reproduce the bug log in to a different session (GNOME on Wayland instead of GNOME, or the other way around). Open Evolution. Verify that no errors are reported and that your Google account is still syncing. After installing the gnome-session update, I recommend rebooting once to clear any old lingering GNOME Online Accounts processes from previous sessions. Regression Potential This fix is the same as was accepted into Fedora 26. It is a workaround by killing all the user's D-Bus sessions when the user logs out. This fix has been backported from gnome-session 3.25.3. It has not been applied to the 3.24 git branch upstream. Since 16.10 has almost reached its end of life (July), I am not proposing this fix there. I believe 16.10 is the first release affected since Ubuntu moved many more services to systemd user sessions in that release. The patch tries to only kill the D-Bus sessions if the session being logged out is the final remaining session for the user. The workaround makes sense to me. It seems similar to the KillUserProcesses option that was pushed into systemd to fix this kind of problem but it's more limited than the systemd method so hopefully it won't be as controversial. Original Bug Report === Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831490] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1831490 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: xenial -- 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/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: This error is being reproduced on i386 arch when using the pc-kernel snap from beta or candidate. > sudo snap install test-snapd-tools > dmesg [15131.806107] audit: type=1400 audit(1559585825.240:93): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.test-snapd-tools" pid=18240 comm="apparmor_parser" [15131.871610] vmap allocation for size 73728 failed: use vmalloc= to increase size. [15131.871614] vmalloc: allocation failure: 68481 bytes [15131.871616] apparmor_parser: page allocation failure: order:0, mode:0x24000c2 [15131.871619] CPU: 0 PID: 18242 Comm: apparmor_parser Not tainted 4.4.0-150-generic #176-Ubuntu [15131.871620] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [15131.871622] c1b15967 5ed07e43 0286 cfee9e00 c13c12ef c1a1ce6c 0001 cfee9e30 [15131.871625] c11821b6 c1a1b220 f40ba700 024000c2 cfee9e44 c1a1ce6c cfee9e18 [15131.871629] 5ed07e43 00010b81 cfee9e60 c11ba86f 024000c2 c1a1ce6c [15131.871632] Call Trace: [15131.871637] [] dump_stack+0x58/0x79 [15131.871640] [] warn_alloc_failed+0xd6/0x110 [15131.871643] [] __vmalloc_node_range+0x1ef/0x210 [15131.871645] [] __vmalloc_node+0x66/0x70 [15131.871648] [] ? __aa_kvmalloc+0x28/0x60 [15131.871650] [] vmalloc+0x38/0x40 [15131.871652] [] ? __aa_kvmalloc+0x28/0x60 [15131.871654] [] __aa_kvmalloc+0x28/0x60 [15131.871656] [] aa_simple_write_to_buffer+0x34/0x90 [15131.871658] [] policy_update+0x73/0x230 [15131.871660] [] ? security_file_permission+0x3e/0xd0 [15131.871662] [] profile_replace+0x98/0xe0 [15131.871664] [] ? policy_update+0x230/0x230 [15131.871666] [] __vfs_write+0x22/0x50 [15131.871668] [] vfs_write+0x8c/0x1b0 [15131.871669] [] SyS_write+0x51/0xb0 [15131.871672] [] do_fast_syscall_32+0x9f/0x190 [15131.871675] [] sysenter_past_esp+0x3d/0x61 [15131.871676] Mem-Info: [15131.871679] active_anon:16802 inactive_anon:2068 isolated_anon:0 active_file:84472 inactive_file:25195 isolated_file:0 unevictable:0 dirty:34 writeback:0 unstable:0 slab_reclaimable:7222 slab_unreclaimable:14030 mapped:8431 shmem:5785 pagetables:204 bounce:0 free:289381 free_pcp:659 free_cma:0 [15131.871685] DMA free:8848kB min:788kB low:984kB high:1180kB active_anon:636kB inactive_anon:0kB active_file:2720kB inactive_file:800kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB managed:15916kB mlocked:0kB dirty:0kB writeback:0kB mapped:472kB shmem:308kB slab_reclaimable:484kB slab_unreclaimable:424kB kernel_stack:8kB pagetables:4kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871686] lowmem_reserve[]: 0 834 1942 1942 [15131.871692] Normal free:364440kB min:42432kB low:53040kB high:63648kB active_anon:30164kB inactive_anon:2776kB active_file:158404kB inactive_file:32020kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:897016kB managed:862444kB mlocked:0kB dirty:116kB writeback:0kB mapped:11176kB shmem:6332kB slab_reclaimable:28404kB slab_unreclaimable:55696kB kernel_stack:1040kB pagetables:348kB unstable:0kB bounce:0kB free_pcp:1336kB local_pcp:676kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871693] lowmem_reserve[]: 0 0 8863 8863 [15131.871698] HighMem free:784236kB min:512kB low:14600kB high:28688kB active_anon:36408kB inactive_anon:5496kB active_file:176764kB inactive_file:67960kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1134472kB managed:1134472kB mlocked:0kB dirty:20kB writeback:0kB mapped:22076kB shmem:16500kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:464kB unstable:0kB bounce:0kB free_pcp:1300kB local_pcp:680kB free_cma:0kB writeback_tmp:0kB pages_scanned:0
[Touch-packages] [Bug 1831490] Re: kernel is out of memory and killed during a kernel sys_write operation
Can you run apport-collect 1831490 on this machine to collect additional logs and data? Thanks ** Also affects: linux (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/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: This error is being reproduced on i386 arch when using the pc-kernel snap from beta or candidate. > sudo snap install test-snapd-tools > dmesg [15131.806107] audit: type=1400 audit(1559585825.240:93): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.test-snapd-tools" pid=18240 comm="apparmor_parser" [15131.871610] vmap allocation for size 73728 failed: use vmalloc= to increase size. [15131.871614] vmalloc: allocation failure: 68481 bytes [15131.871616] apparmor_parser: page allocation failure: order:0, mode:0x24000c2 [15131.871619] CPU: 0 PID: 18242 Comm: apparmor_parser Not tainted 4.4.0-150-generic #176-Ubuntu [15131.871620] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [15131.871622] c1b15967 5ed07e43 0286 cfee9e00 c13c12ef c1a1ce6c 0001 cfee9e30 [15131.871625] c11821b6 c1a1b220 f40ba700 024000c2 cfee9e44 c1a1ce6c cfee9e18 [15131.871629] 5ed07e43 00010b81 cfee9e60 c11ba86f 024000c2 c1a1ce6c [15131.871632] Call Trace: [15131.871637] [] dump_stack+0x58/0x79 [15131.871640] [] warn_alloc_failed+0xd6/0x110 [15131.871643] [] __vmalloc_node_range+0x1ef/0x210 [15131.871645] [] __vmalloc_node+0x66/0x70 [15131.871648] [] ? __aa_kvmalloc+0x28/0x60 [15131.871650] [] vmalloc+0x38/0x40 [15131.871652] [] ? __aa_kvmalloc+0x28/0x60 [15131.871654] [] __aa_kvmalloc+0x28/0x60 [15131.871656] [] aa_simple_write_to_buffer+0x34/0x90 [15131.871658] [] policy_update+0x73/0x230 [15131.871660] [] ? security_file_permission+0x3e/0xd0 [15131.871662] [] profile_replace+0x98/0xe0 [15131.871664] [] ? policy_update+0x230/0x230 [15131.871666] [] __vfs_write+0x22/0x50 [15131.871668] [] vfs_write+0x8c/0x1b0 [15131.871669] [] SyS_write+0x51/0xb0 [15131.871672] [] do_fast_syscall_32+0x9f/0x190 [15131.871675] [] sysenter_past_esp+0x3d/0x61 [15131.871676] Mem-Info: [15131.871679] active_anon:16802 inactive_anon:2068 isolated_anon:0 active_file:84472 inactive_file:25195 isolated_file:0 unevictable:0 dirty:34 writeback:0 unstable:0 slab_reclaimable:7222 slab_unreclaimable:14030 mapped:8431 shmem:5785 pagetables:204 bounce:0 free:289381 free_pcp:659 free_cma:0 [15131.871685] DMA free:8848kB min:788kB low:984kB high:1180kB active_anon:636kB inactive_anon:0kB active_file:2720kB inactive_file:800kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB managed:15916kB mlocked:0kB dirty:0kB writeback:0kB mapped:472kB shmem:308kB slab_reclaimable:484kB slab_unreclaimable:424kB kernel_stack:8kB pagetables:4kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871686] lowmem_reserve[]: 0 834 1942 1942 [15131.871692] Normal free:364440kB min:42432kB low:53040kB high:63648kB active_anon:30164kB inactive_anon:2776kB active_file:158404kB inactive_file:32020kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:897016kB managed:862444kB mlocked:0kB dirty:116kB writeback:0kB mapped:11176kB shmem:6332kB slab_reclaimable:28404kB slab_unreclaimable:55696kB kernel_stack:1040kB pagetables:348kB unstable:0kB bounce:0kB free_pcp:1336kB local_pcp:676kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871693] lowmem_reserve[]: 0 0 8863 8863 [15131.871698] HighMem free:784236kB min:512kB low:14600kB high:28688kB active_anon:36408kB inactive_anon:5496kB active_file:176764kB inactive_file:67960kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1134472kB managed:1134472kB mlocked:0kB dirty:20kB writeback:0kB mapped:22076kB shmem:16500kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:464kB unstable:0kB bounce:0kB free_pcp:1300kB local_pcp:680kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871699] lowmem_reserve[]: 0 0 0 0 [15131.871701] DMA: 12*4kB (UME) 10*8kB (UME) 7*16kB (ME) 5*32kB (UM) 2*64kB (U) 3*128kB (UM) 3*256kB (UM) 4*512kB (UME) 3*1024kB (ME) 1*2048kB (M) 0*4096kB = 8848kB [15131.871711] Normal: 87*4kB (UME) 106*8kB (UME) 168*16kB (UME) 195*32kB (UME) 135*64kB (UME) 161*128kB (ME) 120*256kB (ME) 61*512kB (UME) 25*1024kB (ME) 6*2048kB (M) 55*4096kB (M) = 364492kB [15131.871720] HighMem: 131*4kB
[Touch-packages] [Bug 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard
The CPU architecture is not the problem. Got the same behavior on amd64 <-> amd64 connection with default settings of TightVNC server. ** Tags added: amd64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1831505 Title: Qt5 incorrectly interpret keypresses from remote VNC keyboard Status in qtbase-opensource-src package in Ubuntu: New Status in qttools-opensource-src package in Ubuntu: New Status in tightvnc package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 18.04 LTS installed with VNC server 2. Connect to Ubuntu 18.04 LTS from other machine with VNC client 3. Launch any Qt5 based application such as `assistant`, `kate` or `retext` 4. Press keyboard combination on VNC client Expected results: all keypresses are recognized successfully Actual results: * produces `1` * produces `5` * <`> produces `p` * and are not working * all letters are messed Note: only Qt applications are affected, the GTK-based work as expected (including Chromium from which I write this bug-report) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qt5-assistant 5.9.5-0ubuntu1 Uname: Linux 4.4.78-perf+ aarch64 NonfreeKernelModules: wlan exfat ApportVersion: 2.20.9-0ubuntu7 Architecture: armhf CurrentDesktop: MATE Date: Tue Jun 4 00:46:55 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qttools-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard
** Also affects: tightvnc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1831505 Title: Qt5 incorrectly interpret keypresses from remote VNC keyboard Status in qtbase-opensource-src package in Ubuntu: New Status in qttools-opensource-src package in Ubuntu: New Status in tightvnc package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 18.04 LTS installed with VNC server 2. Connect to Ubuntu 18.04 LTS from other machine with VNC client 3. Launch any Qt5 based application such as `assistant`, `kate` or `retext` 4. Press keyboard combination on VNC client Expected results: all keypresses are recognized successfully Actual results: * produces `1` * produces `5` * <`> produces `p` * and are not working * all letters are messed Note: only Qt applications are affected, the GTK-based work as expected (including Chromium from which I write this bug-report) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qt5-assistant 5.9.5-0ubuntu1 Uname: Linux 4.4.78-perf+ aarch64 NonfreeKernelModules: wlan exfat ApportVersion: 2.20.9-0ubuntu7 Architecture: armhf CurrentDesktop: MATE Date: Tue Jun 4 00:46:55 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qttools-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831505] [NEW] Qt5 incorrectly interpret keypresses from remote VNC keyboard
Public bug reported: Steps to reproduce: 1. Have Ubuntu 18.04 LTS installed with VNC server 2. Connect to Ubuntu 18.04 LTS from other machine with VNC client 3. Launch any Qt5 based application such as `assistant`, `kate` or `retext` 4. Press keyboard combination on VNC client Expected results: all keypresses are recognized successfully Actual results: * produces `1` * produces `5` * <`> produces `p` * and are not working * all letters are messed Note: only Qt applications are affected, the GTK-based work as expected (including Chromium from which I write this bug-report) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qt5-assistant 5.9.5-0ubuntu1 Uname: Linux 4.4.78-perf+ aarch64 NonfreeKernelModules: wlan exfat ApportVersion: 2.20.9-0ubuntu7 Architecture: armhf CurrentDesktop: MATE Date: Tue Jun 4 00:46:55 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qttools-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Affects: qttools-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf bionic ** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1831505 Title: Qt5 incorrectly interpret keypresses from remote VNC keyboard Status in qtbase-opensource-src package in Ubuntu: New Status in qttools-opensource-src package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 18.04 LTS installed with VNC server 2. Connect to Ubuntu 18.04 LTS from other machine with VNC client 3. Launch any Qt5 based application such as `assistant`, `kate` or `retext` 4. Press keyboard combination on VNC client Expected results: all keypresses are recognized successfully Actual results: * produces `1` * produces `5` * <`> produces `p` * and are not working * all letters are messed Note: only Qt applications are affected, the GTK-based work as expected (including Chromium from which I write this bug-report) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qt5-assistant 5.9.5-0ubuntu1 Uname: Linux 4.4.78-perf+ aarch64 NonfreeKernelModules: wlan exfat ApportVersion: 2.20.9-0ubuntu7 Architecture: armhf CurrentDesktop: MATE Date: Tue Jun 4 00:46:55 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qttools-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798369] Re: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock"
Actually I did not see an error message regarding the log file, nor can I find one on disk, but the packages I had installed before the reinstall are no longer installed. ** Tags removed: rls-dd-incoming ** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1798369 Title: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock" Status in APT: New Status in ubiquity: New Status in apt package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Confirmed Bug description: When trying to reinstall an existing Ubuntu cosmic installation using latest 18.10 desktop images, the install shows an error dialog around the end of the installation with an "Error restoring installed applications". Looking at the syslog such a traceback can be seen: apt_pkg.Error: E:Could not get lock /target/var/cache/apt/archives/lock - open (11: Resource temporarily unavailable), E:Unable to lock directory /target/var/cache/apt/archives/ After reproducing this on a live session, after chrooting into /target indeed any apt-get install operations result in the same lock-file error. The whole syslog of the reinstall attached to the bug. Test case: * Download latest cosmic image * Install cosmic on the whole disk (can be on a VM) * (optional) Boot into the system and leave a file in the home directory (to leave a trace, just in case) * Reboot and install cosmic using the first option in ubiquity: Reinstall Ubuntu * Finish configuration The install itself doesn't fail, but around the end of the installation process the error dialog appears. System is still bootable but left with old packages. To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1798369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798369] Re: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock"
This option is still present in Disco and it fails in the same way. ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Confirmed ** Attachment added: "Screenshot_clean-disco-amd64_2019-06-03_14:43:29.png" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1798369/+attachment/5268602/+files/Screenshot_clean-disco-amd64_2019-06-03_14%3A43%3A29.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1798369 Title: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock" Status in APT: New Status in ubiquity: New Status in apt package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Confirmed Bug description: When trying to reinstall an existing Ubuntu cosmic installation using latest 18.10 desktop images, the install shows an error dialog around the end of the installation with an "Error restoring installed applications". Looking at the syslog such a traceback can be seen: apt_pkg.Error: E:Could not get lock /target/var/cache/apt/archives/lock - open (11: Resource temporarily unavailable), E:Unable to lock directory /target/var/cache/apt/archives/ After reproducing this on a live session, after chrooting into /target indeed any apt-get install operations result in the same lock-file error. The whole syslog of the reinstall attached to the bug. Test case: * Download latest cosmic image * Install cosmic on the whole disk (can be on a VM) * (optional) Boot into the system and leave a file in the home directory (to leave a trace, just in case) * Reboot and install cosmic using the first option in ubiquity: Reinstall Ubuntu * Finish configuration The install itself doesn't fail, but around the end of the installation process the error dialog appears. System is still bootable but left with old packages. To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1798369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831335] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for filing this bug in Ubuntu. The error message is: SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 88: Bad configuration option: Y /etc/ssh/sshd_config: terminating, 1 bad configuration options That means that there is a configuration error in your /etc/ssh/sshd_config file, specifically on line 80. That file isn't attached to this bug report, so I cannot tell you what is wrong. What you should do is open that file, fix what's wrong in line 80, and then you can issue these commands: sudo apt update sudo apt -f install That should retry the operation and this time, if there are no other errors, it should succeed. I'll mark this bug as invalid, since it's a local configuration issue. If you disagree, then feel free to reopen the bug, but please state the reasons why you think it's a valid bug, and steps to reproduce it. Thanks! ** Changed in: openssh (Ubuntu) Status: New => Invalid -- 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/1831335 Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Invalid Bug description: Can not this be fixed? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 Uname: Linux 4.4.0-148-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 Date: Sat Jun 1 12:03:59 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-18 (743 days ago) InstallationMedia: Custom 14.04 - Release i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 88: Bad configuration option: Y /etc/ssh/sshd_config: terminating, 1 bad configuration options SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-10-11 (233 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1831335/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824111] Re: Backport packages for 18.04.3 HWE stack
Boaz, I've filed bug 1831498 for tracking the radeon bug, though I'm a bit surprised no-one has filed this issue before now. Anyway, please test the update once it's available. -- 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/1824111 Title: Backport packages for 18.04.3 HWE stack Status in OEM Priority Project: Confirmed Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-8 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-8 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: New Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: New Bug description: [Impact] These are needed for 18.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-8: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.0.x series, so there shouldn't be any regressions left at that point xserver: a new minor release xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831498] [NEW] radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice)
Public bug reported: [impact] imported from https://bugs.freedesktop.org/show_bug.cgi?id=110355 : "I am currently experiencing some issues with GTK elements (GtkMenuItem, GtkMenu) becoming invisible with GIMP and LibreOffice. I am currently using radeonsi+glamor and I'm on Arch Linux (x86_64). My hardware is a Ryzen 5 2400G APU with vega graphics." [test case] test that GIMP/Libreoffice work fine on AMD Vega/Raven [regression potential] the fix/workaround is already in mesa 19.0.4, shouldn't regress anything ** Affects: mesa (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: mesa (Ubuntu Bionic) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: New ** Affects: mesa (Ubuntu Disco) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: New ** Also affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Disco) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1831498 Title: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice) Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: New Status in mesa source package in Disco: New Bug description: [impact] imported from https://bugs.freedesktop.org/show_bug.cgi?id=110355 : "I am currently experiencing some issues with GTK elements (GtkMenuItem, GtkMenu) becoming invisible with GIMP and LibreOffice. I am currently using radeonsi+glamor and I'm on Arch Linux (x86_64). My hardware is a Ryzen 5 2400G APU with vega graphics." [test case] test that GIMP/Libreoffice work fine on AMD Vega/Raven [regression potential] the fix/workaround is already in mesa 19.0.4, shouldn't regress anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1831498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831498] Re: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice)
eoan has 19.0.5 ** Changed in: mesa (Ubuntu) Status: New => Fix Released ** Changed in: mesa (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu Disco) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/1831498 Title: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice) Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: New Status in mesa source package in Disco: New Bug description: [impact] imported from https://bugs.freedesktop.org/show_bug.cgi?id=110355 : "I am currently experiencing some issues with GTK elements (GtkMenuItem, GtkMenu) becoming invisible with GIMP and LibreOffice. I am currently using radeonsi+glamor and I'm on Arch Linux (x86_64). My hardware is a Ryzen 5 2400G APU with vega graphics." [test case] test that GIMP/Libreoffice work fine on AMD Vega/Raven [regression potential] the fix/workaround is already in mesa 19.0.4, shouldn't regress anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1831498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831495] [NEW] LVM pauses for a long time during boot for a "Generic- SD/MMC/MS PRO" with no media inserted
Public bug reported: Boot time is greatly impacted by a media detection timer for a SD/MMC card reader with no media inserted. DEVICE: [1.857492] scsi host6: usb-storage 1-9:1.0 [1.857539] usbcore: registered new interface driver usb-storage [1.858178] usbcore: registered new interface driver uas [1.981335] usb 1-10: new full-speed USB device number 4 using xhci_hcd [2.131529] usb 1-10: New USB device found, idVendor=8087, idProduct=0aa7, bcdDevice= 0.01 [2.131530] usb 1-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [2.872111] scsi 6:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [2.872343] sd 6:0:0:0: Attached scsi generic sg2 type 0 [2.877942] sd 6:0:0:0: [sdb] Attached SCSI removable disk ERRORS: /var/log/syslog:Jun 3 15:19:42 CKR-1 lvm[469]: /dev/sdb: open failed: No medium found /var/log/syslog:Jun 3 15:19:42 CKR-1 lvm[648]: /dev/sdb: open failed: No medium found /var/log/syslog:Jun 3 15:19:42 CKR-1 lvm[648]: /dev/sdb: open failed: No medium found /var/log/syslog:Jun 3 15:19:42 CKR-1 e2scrub_reap[749]: /dev/sdb: open failed: No medium found ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lvm2 2.03.02-2ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 Date: Mon Jun 3 15:22:34 2019 InstallationDate: Installed on 2018-11-23 (191 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: Upgraded to eoan on 2019-05-30 (4 days ago) ** Affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Also affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New ** Description changed: - Boot time is greatly impacted by a non-existent media detection timer - for a SD/MMC card reader. - + Boot time is greatly impacted by a media detection timer for a SD/MMC + card reader with no media inserted. DEVICE: [1.857492] scsi host6: usb-storage 1-9:1.0 [1.857539] usbcore: registered new interface driver usb-storage [1.858178] usbcore: registered new interface driver uas [1.981335] usb 1-10: new full-speed USB device number 4 using xhci_hcd [2.131529] usb 1-10: New USB device found, idVendor=8087, idProduct=0aa7, bcdDevice= 0.01 [2.131530] usb 1-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [2.872111] scsi 6:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [2.872343] sd 6:0:0:0: Attached scsi generic sg2 type 0 [2.877942] sd 6:0:0:0: [sdb] Attached SCSI removable disk ERRORS: /var/log/syslog:Jun 3 15:19:42 CKR-1 lvm[469]: /dev/sdb: open failed: No medium found /var/log/syslog:Jun 3 15:19:42 CKR-1 lvm[648]: /dev/sdb: open failed: No medium found /var/log/syslog:Jun 3 15:19:42 CKR-1 lvm[648]: /dev/sdb: open failed: No medium found /var/log/syslog:Jun 3 15:19:42 CKR-1 e2scrub_reap[749]: /dev/sdb: open failed: No medium found ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lvm2 2.03.02-2ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 Date: Mon Jun 3 15:22:34 2019 InstallationDate: Installed on 2018-11-23 (191 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: Upgraded to eoan on 2019-05-30 (4 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1831495 Title: LVM pauses for a long time during boot for a "Generic- SD/MMC/MS PRO" with no media inserted Status in e2fsprogs package in Ubuntu: New Status in lvm2 package in Ubuntu: New Bug description: Boot time is greatly impacted by a media detection timer for a SD/MMC card reader with no media inserted. DEVICE: [1.857492] scsi host6: usb-storage 1-9:1.0 [1.857539] usbcore: registered new interface driver usb-storage [1.858178] usbcore: registered new interface driver uas [1.981335] usb 1-10: new full-speed USB device number 4 using xhci_hcd [2.131529] usb 1-10: New USB device found, idVendor=8087, idProduct=0aa7, bcdDevice= 0.01 [2.131530] usb 1-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [
[Touch-packages] [Bug 1831264] Re: Sun keyboard Front key not accepted by gnome-control-center
Thanks ** Changed in: xkeyboard-config (Ubuntu) Importance: Undecided => Low ** Changed in: xkeyboard-config (Ubuntu) Status: New => Triaged ** Also affects: xkeyboard-config via https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/172 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1831264 Title: Sun keyboard Front key not accepted by gnome-control-center Status in xkeyboard-config: Unknown Status in xkeyboard-config package in Ubuntu: Triaged Bug description: A Sun keyboards is recognized by the hardware detector with no problem. xmodmap -pk gives the following for the relevant keys: 136 0xff69 (Cancel) 0x (NoSymbol) 0xff69 (Cancel) 137 0xff66 (Redo) 0x (NoSymbol) 0xff66 (Redo) 138 0x1005ff70 (SunProps) 0x (NoSymbol) 0x1005ff70 (SunProps) 139 0xff65 (Undo) 0x (NoSymbol) 0xff65 (Undo) 140 0x1005ff71 (SunFront) 0x (NoSymbol) 0x1005ff71 (SunFront) 141 0x1008ff57 (XF86Copy) 0x (NoSymbol) 0x1008ff57 (XF86Copy) 142 0x1008ff6b (XF86Open) 0x (NoSymbol) 0x1008ff6b (XF86Open) 143 0x1008ff6d (XF86Paste) 0x (NoSymbol) 0x1008ff6d (XF86Paste) 144 0xff68 (Find) 0x (NoSymbol) 0xff68 (Find) 145 0x1008ff58 (XF86Cut)0x (NoSymbol) 0x1008ff58 (XF86Cut) 146 0xff6a (Help) 0x (NoSymbol) 0xff6a (Help) Observe that the names of the two keysyms 0x1005ff70 and 0x1005ff71 are SUN specials, not in the XF86 set. Pressing either of these using xev behaves as expected: KeyPress event, serial 37, synthetic NO, window 0x361, root 0x4fe, subw 0x0, time 3071686, (118,83), root:(1365,168), state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x361, root 0x4fe, subw 0x0, time 3071688, (118,83), root:(1365,168), state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False I tried binding "Lower window below other windows" to the SunFront using the Settings app, but it did not work.(Note that back in the days of 14.04 where you uses CCSM to make this setting, it worked fine.) After this I did $ dconf dump /org/gnome/desktop/wm/keybindings/ [/] lower=['0x1005ff71'] switch-to-workspace-1=['1'] move-to-workspace-1=@as [] switch-to-workspace-2=['2'] switch-to-workspace-3=['3'] switch-to-workspace-4=['4'] move-to-monitor-down=@as [] move-to-monitor-up=@as [] So it had recognized the correct keysym, but does not know that the name of that keysym is SunFront. So far so bad. It works fine with keysyms with known names (e.g. the CANCEL key), and it should not be hard to construct a workaround my modifying the keyboard tables to map that key to some better-named keysym, so it might be argued that this bug is of Low Priority. BUT there is a serious side effect. With that dconf setting in place: the Left Arrow key on the keyboard no longer works (for example, I made that change whilst composing this report, and I cannot now move the cursor backwards with the Left Arrow key, though fortunately the Left Arrow on the numeric keypad still behaves). All applications seem to be affected (e.g. Firefox, Terminal, Gedit). Left and Left still work, except that if you engage Num Lock, Left now stops working. Using xev to see what happens when Left Arrow is pressed yields: FocusOut event, serial 37, synthetic NO, window 0x361, mode NotifyGrab, detail NotifyAncestor FocusOut event, serial 37, synthetic NO, window 0x361, mode NotifyUngrab, detail NotifyPointer FocusIn event, serial 37, synthetic NO, window 0x361, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 37, synthetic NO, window 0x0, keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 which is crazy! You should not be surprised that I spent a whole day gradually removing all the changes I had made until finally I narrowed it down to dconf, and then to that particular setting. Changing the binding back to CANCEL removes the problem (except that you have to restart each application affected, so I have just restarted Terminal, but I cannot restart Firefox while I am still typing this report). My main worry is that there may be some other keybinding errors
[Touch-packages] [Bug 1830121] Re: rsync --rsync-path="sudo rsync" over ssh via pki fails due to protocol mismatch
It's possible sudo is printing something to stderr, can you check that? My bet would be on a hostname name resolution (i.e., a warning). ** Changed in: rsync (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1830121 Title: rsync --rsync-path="sudo rsync" over ssh via pki fails due to protocol mismatch Status in Ubuntu MATE: Invalid Status in rsync package in Ubuntu: Incomplete Bug description: rsync with remote sudo fails over ssh on Ubuntu Mate 18.04.2 rsync version 3.1.2 protocol version 31 - same on local and remote OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 - same on local and remote I have checked for spurious output from .bashrc using $ ssh user@host /bin/true > out.dat which results in $ ls -l *.dat -rw-rw-r-- 1 user user 0 May 22 23:33 out.dat -- The [redacted] command is rsync -AEavvvogt --rsync-path="sudo rsync" --debug=CONNECT -e "ssh -i /home/xxx/.ssh/id_rsa -tt -v -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null" --exclude-from=/home/xxx/backup.exclude --delete --link-dest=../$lastdt /etc $dest/$dt; -- The [redacted] output is opening connection using: ssh -i /home/user/.ssh/id_rsa -tt -v -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -l user xxx "sudo rsync" --server -vvvlogDtpAre.iLsfxC --delete --link-dest ../20190506_021137 . /home/backups/xxx/20190522_232738 (20 args) OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to xxx [192.168.1.120] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /home/user/.ssh/id_rsa type 0 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400 debug1: Authenticating to xxx:22 as 'user' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: xxx Warning: Permanently added 'xxx,192.168.1.120' (ECDSA) to the list of known hosts. debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey after 134217728 blocks debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs= debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Offering public key: RSA SHA256:xxx /home/user/.ssh/id_rsa debug1: Server accepts key: xxx debug1: Authentication succeeded (publickey). Authenticated to xxx ([192.168.1.120]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: pledge: network debug1: client_input_global_request: rtype hostkeys...@openssh.com want_reply 0 debug1: tty_make_modes: no fd or tio debug1: Sending environment. debug1: Sending env LANG = en_GB.UTF-8 debug1: Sending command: sudo rsync --server -vvvlogDtpAre.iLsfxC --delete --link-dest ../20190506_021137 . /home/backups/xxx/20190522_232738 protocol version mismatch -- is your shell clean? (see the rsync man page for an explanation) rsync error: protocol incompatibility (code 2) at compat.c(178) [sender=3.1.2] [sender] _exit_cleanup(code=2, file=compat.c, line=178): about to call exit(2) /etc/sudoers contains userALL= NOPASSWD:/usr/bin/rsync ...which I have tried placing above (as is the default) and below lines beginning %admin and %sudo and the space in "ALL= NOPASSWD..." doesn't seem to make any difference I followed the instructions at https://www.digitalocean.com/community/tutorials/how-to-copy-files-with-rsync-over-ssh https://askubuntu.com/questions/719439/using-rsync-with-sudo-on-the-destination-machine - which worked on 16.04, so I wonder if there may be a bug, although grateful for any other suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1830121/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1825997] Re: boot-smoke fails due to running jobs
note on the corosync autopkgtest failure in disco; i opened bug 1831492 and the failure can be ignored for this upload. -- 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/1825997 Title: boot-smoke fails due to running jobs Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Committed Bug description: [impact] boot-smoke test reboots 5 times and verifies systemd is fully started up after each boot, including checking if there are any running jobs (with list-jobs). However, this test makes the assumption that no further jobs will be started after systemd reaches 'running' (or 'degraded') state, which is a false assumption. [test case] see various boot-smoke failures in autopkgtest.ubuntu.com [regression potential] possible false-positive or false-negative autopkgtest results. [other info] Note: This patch is not required for debian, because debian's boot- smoke does not include the wait for systemctl is-system-running. The problem appears to be that systemd reaches 'running' (or 'degraded') state, and then other systemd services are started. This confuses the boot-smoke test, because it sees that 'is-system-running' is done, but then it sees running jobs, which fails the test. What is starting jobs after systemd reaches running state appears to be X inside the test system. There are various services started by gnome-session and dbus-daemon. Additionally, from the artifacts of one example: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- bionic/bionic/i386/s/systemd/20190416_171327_478f6@/artifacts.tar.gz the artifacts/journal.txt shows that after the boot-smoke test causes the reboot and then re-ssh into the system after the reboot, it only gives the test system 9 seconds before deciding it has failed, and only 4 seconds after ssh'ing into the rebooted test system. Another wait is needed when checking for remaining running jobs. Or, the running jobs check could be removed entirely, and we can just trust that systemd correctly knows when it has reached running|degraded state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831491] [NEW] Do not unset XDG_SEAT & XDG_SESSION_ID in 95dbus_update-activation-env (Unity7)
Public bug reported: Unity still requires it. For example indicator-session depends on those session environments. Without those set it doesn't behave properly. ** Affects: dbus (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: eoan ** Description changed: - Unity still requires it. Fir example indicator-session depends on those + Unity still requires it. For example indicator-session depends on those session environments. Without those set it doesn't behave properly. ** Changed in: dbus (Ubuntu) Status: New => Confirmed ** Summary changed: - Do not unset XDG_SEAT & XDG_SESSION_ID in 95dbus_update-activation-env + Do not unset XDG_SEAT & XDG_SESSION_ID in 95dbus_update-activation-env (Unity7) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1831491 Title: Do not unset XDG_SEAT & XDG_SESSION_ID in 95dbus_update-activation-env (Unity7) Status in dbus package in Ubuntu: Confirmed Bug description: Unity still requires it. For example indicator-session depends on those session environments. Without those set it doesn't behave properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1831491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831490] [NEW] kernel is out of memory and killed during a kernel sys_write operation
Public bug reported: This error is being reproduced on i386 arch when using the pc-kernel snap from beta or candidate. > sudo snap install test-snapd-tools > dmesg [15131.806107] audit: type=1400 audit(1559585825.240:93): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.test-snapd-tools" pid=18240 comm="apparmor_parser" [15131.871610] vmap allocation for size 73728 failed: use vmalloc= to increase size. [15131.871614] vmalloc: allocation failure: 68481 bytes [15131.871616] apparmor_parser: page allocation failure: order:0, mode:0x24000c2 [15131.871619] CPU: 0 PID: 18242 Comm: apparmor_parser Not tainted 4.4.0-150-generic #176-Ubuntu [15131.871620] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [15131.871622] c1b15967 5ed07e43 0286 cfee9e00 c13c12ef c1a1ce6c 0001 cfee9e30 [15131.871625] c11821b6 c1a1b220 f40ba700 024000c2 cfee9e44 c1a1ce6c cfee9e18 [15131.871629] 5ed07e43 00010b81 cfee9e60 c11ba86f 024000c2 c1a1ce6c [15131.871632] Call Trace: [15131.871637] [] dump_stack+0x58/0x79 [15131.871640] [] warn_alloc_failed+0xd6/0x110 [15131.871643] [] __vmalloc_node_range+0x1ef/0x210 [15131.871645] [] __vmalloc_node+0x66/0x70 [15131.871648] [] ? __aa_kvmalloc+0x28/0x60 [15131.871650] [] vmalloc+0x38/0x40 [15131.871652] [] ? __aa_kvmalloc+0x28/0x60 [15131.871654] [] __aa_kvmalloc+0x28/0x60 [15131.871656] [] aa_simple_write_to_buffer+0x34/0x90 [15131.871658] [] policy_update+0x73/0x230 [15131.871660] [] ? security_file_permission+0x3e/0xd0 [15131.871662] [] profile_replace+0x98/0xe0 [15131.871664] [] ? policy_update+0x230/0x230 [15131.871666] [] __vfs_write+0x22/0x50 [15131.871668] [] vfs_write+0x8c/0x1b0 [15131.871669] [] SyS_write+0x51/0xb0 [15131.871672] [] do_fast_syscall_32+0x9f/0x190 [15131.871675] [] sysenter_past_esp+0x3d/0x61 [15131.871676] Mem-Info: [15131.871679] active_anon:16802 inactive_anon:2068 isolated_anon:0 active_file:84472 inactive_file:25195 isolated_file:0 unevictable:0 dirty:34 writeback:0 unstable:0 slab_reclaimable:7222 slab_unreclaimable:14030 mapped:8431 shmem:5785 pagetables:204 bounce:0 free:289381 free_pcp:659 free_cma:0 [15131.871685] DMA free:8848kB min:788kB low:984kB high:1180kB active_anon:636kB inactive_anon:0kB active_file:2720kB inactive_file:800kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB managed:15916kB mlocked:0kB dirty:0kB writeback:0kB mapped:472kB shmem:308kB slab_reclaimable:484kB slab_unreclaimable:424kB kernel_stack:8kB pagetables:4kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871686] lowmem_reserve[]: 0 834 1942 1942 [15131.871692] Normal free:364440kB min:42432kB low:53040kB high:63648kB active_anon:30164kB inactive_anon:2776kB active_file:158404kB inactive_file:32020kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:897016kB managed:862444kB mlocked:0kB dirty:116kB writeback:0kB mapped:11176kB shmem:6332kB slab_reclaimable:28404kB slab_unreclaimable:55696kB kernel_stack:1040kB pagetables:348kB unstable:0kB bounce:0kB free_pcp:1336kB local_pcp:676kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871693] lowmem_reserve[]: 0 0 8863 8863 [15131.871698] HighMem free:784236kB min:512kB low:14600kB high:28688kB active_anon:36408kB inactive_anon:5496kB active_file:176764kB inactive_file:67960kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1134472kB managed:1134472kB mlocked:0kB dirty:20kB writeback:0kB mapped:22076kB shmem:16500kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:464kB unstable:0kB bounce:0kB free_pcp:1300kB local_pcp:680kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871699] lowmem_reserve[]: 0 0 0 0 [15131.871701] DMA: 12*4kB (UME) 10*8kB (UME) 7*16kB (ME) 5*32kB (UM) 2*64kB (U) 3*128kB (UM) 3*256kB (UM) 4*512kB (UME) 3*1024kB (ME) 1*2048kB (M) 0*4096kB = 8848kB [15131.871711] Normal: 87*4kB (UME) 106*8kB (UME) 168*16kB (UME) 195*32kB (UME) 135*64kB (UME) 161*128kB (ME) 120*256kB (ME) 61*512kB (UME) 25*1024kB (ME) 6*2048kB (M) 55*4096kB (M) = 364492kB [15131.871720] HighMem: 131*4kB (UM) 835*8kB (UM) 302*16kB (UM) 119*32kB (UM) 95*64kB (UM) 50*128kB (UM) 67*256kB (UM) 55*512kB (UM) 52*1024kB (M) 23*2048kB (UM) 149*4096kB (M) = 784292kB [15131.871729] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB [15131.871730] 115450 total pagecache pages [15131.871731] 0 pages in swap cache [15131.871733] Swap cache stats: add 0, delete 0, find 0/0 [15131.871734] Free swap = 0kB [15131.871734] Total swap = 0kB [15131.871735] 511870 pages RAM [15131.871736] 283618 pages HighMem/MovableOnly [15131.871737] 8662 pages reserved [15131.871738] 0 pages cma reserved
[Touch-packages] [Bug 1831459] Re: 'storage' test needs to wait for systemd-cryptsetup to be active before stopping it
** Tags added: ddstreet-next -- 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/1831459 Title: 'storage' test needs to wait for systemd-cryptsetup to be active before stopping it Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: Fix Released Bug description: [impact] test case fails because it does not wait for the service to become active before stopping it, resulting in failure to rmmod the scsi_debug module because it's still in use. [test case] check 'storage' test results for systemd in autopkgtest logs, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/s/systemd/20190601_160043_a5281@/log.gz [regression potential] low; test case fix only. [other info] detected and reported by @cascardo in bug 1814373 comment 4 and 5, but separate (non-test) systemd bugfix uploaded for that bug so opening this bug to track fixing the test case. larger fixes/improvements to 'storage' testcase in bug 1829347, but those rejected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831459/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
FYI, please note that seccomp 2.4.1 was pushed to bionic in
https://usn.ubuntu.com/4001-1/ on 2019/05/30. It shouldn't affect this
bug report AFAICT because while the 2.4.1 Ubuntu packaging drops these
patches, the upstream commits for lp-1815415-arch-update-syscalls-for-
Linux-4.9.patch and lp-1815415-update-the-syscall-tables-to-4.10.patch
are both included in 2.4.1. Based on the 2.4.1 changelog, nothing else
was changed in this area, so 2.4.1 should be affected in the same way as
2.3.1-2.1ubuntu4.1.
--
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/1821625
Title:
systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
seccomp)
Status in libseccomp package in Ubuntu:
Incomplete
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in libseccomp source package in Bionic:
Incomplete
Status in linux source package in Bionic:
In Progress
Status in systemd source package in Bionic:
Invalid
Bug description:
Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
failing on Bionic on ppc64el with the error messages:
Operating on architecture: ppc
Failed to add n/a() rule for architecture ppc, skipping: Bad address
Operating on architecture: ppc64
Failed to add n/a() rule for architecture ppc64, skipping: Bad address
Operating on architecture: ppc64-le
Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical
argument out of domain
Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413,
function test_memory_deny_write_execute_mmap(). Aborting.
memoryseccomp-mmap terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG)
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function
test_memory_deny_write_execute_mmap(). Aborting.
Aborted (core dumped)
FAIL: test-seccomp (code: 134)
Full logs at:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz
The testcase passed with systemd version 237-3ubuntu10.13 running on the same
4.15.0-45 kernel on ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1821625/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831351] Re: Please provide option to continue bug report from different computer
ubuntu-bug can take a file name as an argument so if you have created a bug report on another system you can use 'ubuntu-bug samba.apport' as the argument and you'll be able to report that bug on Launchpad. The only strange thing here is that the file name must end in .apport which isn't made terribly clear in the documentation for the --save switch. ** Changed in: apport (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1831351 Title: Please provide option to continue bug report from different computer Status in apport package in Ubuntu: Incomplete Bug description: There are some situations where it is desirable to gather debugging information on a system affected by a bug, but to login (to Launchpad/Ubuntu SSO) and complete editing this bug report from a different system. This is already implemented for situations where the affected system runs headless, i.e. servers without a graphical display. However, this should also be a user choice exposed as a command line option to ubuntu-bug (which, at least according to --help it currently is not). A common use case where this would be nice to have is testing software in a VM, but not wanting to expose Ubuntu SSO credentials to this VM (e.g. for security concerns). Another use case is a need to report a serious bug in the default web browser where this web browser is unable to access any websites. There is a workaround: DISPLAY= ubuntu-bug somepackage Unfortunately this means the debugging data collection phase will provide a text-only UI instead of the nicer / more user-friendly GTK one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.6 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 01:24:07 2019 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-01-17T11:47:59.939850 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1831351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831264] Re: Sun keyboard Front key not accepted by gnome-control-center
See also https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard- config/issues/172 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1831264 Title: Sun keyboard Front key not accepted by gnome-control-center Status in xkeyboard-config package in Ubuntu: New Bug description: A Sun keyboards is recognized by the hardware detector with no problem. xmodmap -pk gives the following for the relevant keys: 136 0xff69 (Cancel) 0x (NoSymbol) 0xff69 (Cancel) 137 0xff66 (Redo) 0x (NoSymbol) 0xff66 (Redo) 138 0x1005ff70 (SunProps) 0x (NoSymbol) 0x1005ff70 (SunProps) 139 0xff65 (Undo) 0x (NoSymbol) 0xff65 (Undo) 140 0x1005ff71 (SunFront) 0x (NoSymbol) 0x1005ff71 (SunFront) 141 0x1008ff57 (XF86Copy) 0x (NoSymbol) 0x1008ff57 (XF86Copy) 142 0x1008ff6b (XF86Open) 0x (NoSymbol) 0x1008ff6b (XF86Open) 143 0x1008ff6d (XF86Paste) 0x (NoSymbol) 0x1008ff6d (XF86Paste) 144 0xff68 (Find) 0x (NoSymbol) 0xff68 (Find) 145 0x1008ff58 (XF86Cut)0x (NoSymbol) 0x1008ff58 (XF86Cut) 146 0xff6a (Help) 0x (NoSymbol) 0xff6a (Help) Observe that the names of the two keysyms 0x1005ff70 and 0x1005ff71 are SUN specials, not in the XF86 set. Pressing either of these using xev behaves as expected: KeyPress event, serial 37, synthetic NO, window 0x361, root 0x4fe, subw 0x0, time 3071686, (118,83), root:(1365,168), state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x361, root 0x4fe, subw 0x0, time 3071688, (118,83), root:(1365,168), state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False I tried binding "Lower window below other windows" to the SunFront using the Settings app, but it did not work.(Note that back in the days of 14.04 where you uses CCSM to make this setting, it worked fine.) After this I did $ dconf dump /org/gnome/desktop/wm/keybindings/ [/] lower=['0x1005ff71'] switch-to-workspace-1=['1'] move-to-workspace-1=@as [] switch-to-workspace-2=['2'] switch-to-workspace-3=['3'] switch-to-workspace-4=['4'] move-to-monitor-down=@as [] move-to-monitor-up=@as [] So it had recognized the correct keysym, but does not know that the name of that keysym is SunFront. So far so bad. It works fine with keysyms with known names (e.g. the CANCEL key), and it should not be hard to construct a workaround my modifying the keyboard tables to map that key to some better-named keysym, so it might be argued that this bug is of Low Priority. BUT there is a serious side effect. With that dconf setting in place: the Left Arrow key on the keyboard no longer works (for example, I made that change whilst composing this report, and I cannot now move the cursor backwards with the Left Arrow key, though fortunately the Left Arrow on the numeric keypad still behaves). All applications seem to be affected (e.g. Firefox, Terminal, Gedit). Left and Left still work, except that if you engage Num Lock, Left now stops working. Using xev to see what happens when Left Arrow is pressed yields: FocusOut event, serial 37, synthetic NO, window 0x361, mode NotifyGrab, detail NotifyAncestor FocusOut event, serial 37, synthetic NO, window 0x361, mode NotifyUngrab, detail NotifyPointer FocusIn event, serial 37, synthetic NO, window 0x361, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 37, synthetic NO, window 0x0, keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 which is crazy! You should not be surprised that I spent a whole day gradually removing all the changes I had made until finally I narrowed it down to dconf, and then to that particular setting. Changing the binding back to CANCEL removes the problem (except that you have to restart each application affected, so I have just restarted Terminal, but I cannot restart Firefox while I am still typing this report). My main worry is that there may be some other keybinding errors that cause the same side effect, and therefor the Priority of fixing this bug needs to be much higher. Moreover, this problem seems to have been around for a long time. see:
[Touch-packages] [Bug 1831264] Re: Sun keyboard Front key not accepted by gnome-control-center
On 03/06/2019 16:05, Gunnar Hjalmarsson wrote: > Thanks for your report! > > The issues you describe are upstream in nature, and it would be great if > you could file an upstream issue as well: See https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard- config/issues/172 > > https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues > > If you do, please post the URL to it here for tracking purposes. > -- Charles H. Lindsey -At my New Home, still doing my own thing-- Tel: +44 161 488 1845Web: http://www.cs.man.ac.uk/~chl Email: c...@clerew.man.ac.uk Snail-mail: Apt 40, SK8 5BF, U.K. PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5 ** Bug watch added: gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues #172 https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/172 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1831264 Title: Sun keyboard Front key not accepted by gnome-control-center Status in xkeyboard-config package in Ubuntu: New Bug description: A Sun keyboards is recognized by the hardware detector with no problem. xmodmap -pk gives the following for the relevant keys: 136 0xff69 (Cancel) 0x (NoSymbol) 0xff69 (Cancel) 137 0xff66 (Redo) 0x (NoSymbol) 0xff66 (Redo) 138 0x1005ff70 (SunProps) 0x (NoSymbol) 0x1005ff70 (SunProps) 139 0xff65 (Undo) 0x (NoSymbol) 0xff65 (Undo) 140 0x1005ff71 (SunFront) 0x (NoSymbol) 0x1005ff71 (SunFront) 141 0x1008ff57 (XF86Copy) 0x (NoSymbol) 0x1008ff57 (XF86Copy) 142 0x1008ff6b (XF86Open) 0x (NoSymbol) 0x1008ff6b (XF86Open) 143 0x1008ff6d (XF86Paste) 0x (NoSymbol) 0x1008ff6d (XF86Paste) 144 0xff68 (Find) 0x (NoSymbol) 0xff68 (Find) 145 0x1008ff58 (XF86Cut)0x (NoSymbol) 0x1008ff58 (XF86Cut) 146 0xff6a (Help) 0x (NoSymbol) 0xff6a (Help) Observe that the names of the two keysyms 0x1005ff70 and 0x1005ff71 are SUN specials, not in the XF86 set. Pressing either of these using xev behaves as expected: KeyPress event, serial 37, synthetic NO, window 0x361, root 0x4fe, subw 0x0, time 3071686, (118,83), root:(1365,168), state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x361, root 0x4fe, subw 0x0, time 3071688, (118,83), root:(1365,168), state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False I tried binding "Lower window below other windows" to the SunFront using the Settings app, but it did not work.(Note that back in the days of 14.04 where you uses CCSM to make this setting, it worked fine.) After this I did $ dconf dump /org/gnome/desktop/wm/keybindings/ [/] lower=['0x1005ff71'] switch-to-workspace-1=['1'] move-to-workspace-1=@as [] switch-to-workspace-2=['2'] switch-to-workspace-3=['3'] switch-to-workspace-4=['4'] move-to-monitor-down=@as [] move-to-monitor-up=@as [] So it had recognized the correct keysym, but does not know that the name of that keysym is SunFront. So far so bad. It works fine with keysyms with known names (e.g. the CANCEL key), and it should not be hard to construct a workaround my modifying the keyboard tables to map that key to some better-named keysym, so it might be argued that this bug is of Low Priority. BUT there is a serious side effect. With that dconf setting in place: the Left Arrow key on the keyboard no longer works (for example, I made that change whilst composing this report, and I cannot now move the cursor backwards with the Left Arrow key, though fortunately the Left Arrow on the numeric keypad still behaves). All applications seem to be affected (e.g. Firefox, Terminal, Gedit). Left and Left still work, except that if you engage Num Lock, Left now stops working. Using xev to see what happens when Left Arrow is pressed yields: FocusOut event, serial 37, synthetic NO, window 0x361, mode NotifyGrab, detail NotifyAncestor FocusOut event, serial 37, synthetic NO, window 0x361, mode NotifyUngrab, detail NotifyPointer FocusIn event, serial 37, synthetic NO, window 0x361, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 37, synthetic NO, window 0x0, keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan
I wrote earlier that the dhclient works fine on this interface, so the problem is apparently that dhcp does not work as requested for the vlan network ** Changed in: systemd (Ubuntu) Status: Incomplete => New ** Description changed: root@gwd:~# uname -a Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@gwd:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic root@gwd:~# cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Link] MACAddress=C8:D3:A3:50:02:33 [Network] VLAN=enp3s0.2 + root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev + [NetDev] + Name=enp3s0.2 + Kind=vlan + + [VLAN] + Id=2 + root@gwd:~# cat /etc/systemd/network/enp3s0.2.network [Match] Name=enp3s0.2 [Network] DHCP=ipv4 [DHCP] UseRoutes=true - No ip on enp3s0.2 after boot! dhclient enp3s0.2 works fine, i create systemd service for it as temporary workaround -- 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/1831470 Title: systemd dhcp don't work on vlan Status in systemd package in Ubuntu: New Bug description: root@gwd:~# uname -a Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@gwd:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic root@gwd:~# cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Link] MACAddress=C8:D3:A3:50:02:33 [Network] VLAN=enp3s0.2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev [NetDev] Name=enp3s0.2 Kind=vlan [VLAN] Id=2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.network [Match] Name=enp3s0.2 [Network] DHCP=ipv4 [DHCP] UseRoutes=true - No ip on enp3s0.2 after boot! dhclient enp3s0.2 works fine, i create systemd service for it as temporary workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan
root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev [NetDev] Name=enp3s0.2 Kind=vlan [VLAN] Id=2 -- 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/1831470 Title: systemd dhcp don't work on vlan Status in systemd package in Ubuntu: Incomplete Bug description: root@gwd:~# uname -a Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@gwd:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic root@gwd:~# cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Link] MACAddress=C8:D3:A3:50:02:33 [Network] VLAN=enp3s0.2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.network [Match] Name=enp3s0.2 [Network] DHCP=ipv4 [DHCP] UseRoutes=true - No ip on enp3s0.2 after boot! dhclient enp3s0.2 works fine, i create systemd service for it as temporary workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778073] Re: dnsmasq and resolvconf hangs on start
Hi Thomas, have you had a chance to re-test this on 18.04? From Christian's comment #3, sounds like this issue may already be resolved, but if not we can investigate further. ** Changed in: dnsmasq (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1778073 Title: dnsmasq and resolvconf hangs on start Status in dnsmasq package in Ubuntu: Incomplete Status in dnsmasq package in Debian: New Bug description: I installed today dnsmasq and I use resolvconf in background. Problem is, that systemd takes 1 minute or so after service start and than reports: root@proxy:~# service dnsmasq status dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled) Drop-In: /run/systemd/generator/dnsmasq.service.d 50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf Active: failed (Result: timeout) since Do 2018-06-21 15:58:13 CEST; 2min 10s ago Process: 3295 ExecStop=/etc/init.d/dnsmasq systemd-stop-resolvconf (code=killed, signal=TERM) Process: 3865 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf (code=killed, signal=TERM) Process: 3837 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=0/SUCCESS) Process: 3825 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS) Main PID: 3862 (code=exited, status=0/SUCCESS) Jun 21 15:56:43 proxy dnsmasq[3862]: Benutze Namensserver 192.168.23.1#53 Jun 21 15:56:43 proxy dnsmasq[3865]: * Awakening mail retriever agent: Jun 21 15:56:43 proxy dnsmasq[3865]:...done. Jun 21 15:56:43 proxy postfix[3951]: Postfix is running with backwards-compatible default settings Jun 21 15:56:43 proxy postfix[3951]: See http://www.postfix.org/COMPATIBILITY_README.html for details Jun 21 15:56:43 proxy postfix[3951]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload" Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Start-post operation timed out. Stopping. Jun 21 15:58:13 proxy systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Unit entered failed state. Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Failed with result 'timeout'. when I look into the start script /etc/init.d/dnsmasq there is a func systemd-start-resolvconf which points to start-resolvconf. There is this part: for interface in $DNSMASQ_EXCEPT do [ $interface = lo ] && return done Before I had not defined DNSMASQ_EXCEPT in /etc/defaults/dnsmasq. Problem is, that this part MUST be faulty! When I commend it out, I can start dnsmasq! It looks like it loops forever there?! Also if I define DNSMASQ_EXCEPT to my listen interface, it works - but is is really needed? I found a other user which had the same problem: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871958 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1ubuntu0.16.04.4 [modified: etc/default/dnsmasq] ProcVersionSignature: Ubuntu 4.15.0-23.25~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Jun 21 16:12:14 2018 InstallationDate: Installed on 2017-02-27 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) PackageArchitecture: all ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8 SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.dnsmasq: 2018-06-21T16:07:24.818774 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1778073/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825997] Re: boot-smoke fails due to running jobs
autopkgtest failures: disco: linux-oracle, linux-snapdragon: tests never passed; ignore dbus: this appears to be the same issue as is seen for systemd in bug 1829829; i'm re-running the test (again), but if it still doesn't pass I think we need to ignore it as a failure due to that bug. systemd (amd64): only failure is due to bug 1831459 systemd (ppc64el): also fails due to bug 1831459, and also has some upstream failed tests: FAILED TESTS: test/TEST-18-FAILUREACTION test/TEST-19-DELEGATE test/TEST-25-IMPORT test/TEST-27-STDOUTFILE I opened bug 1831468 to track these failures; they do not appear related/caused-by this upload. corosync (all archs): this has failed since before this upload, and looks like problem with the corosync source not being available in disco, possibly due to using disco-proposed. in any case, not caused or related to this upload and can be ignored. -- 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/1825997 Title: boot-smoke fails due to running jobs Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Committed Bug description: [impact] boot-smoke test reboots 5 times and verifies systemd is fully started up after each boot, including checking if there are any running jobs (with list-jobs). However, this test makes the assumption that no further jobs will be started after systemd reaches 'running' (or 'degraded') state, which is a false assumption. [test case] see various boot-smoke failures in autopkgtest.ubuntu.com [regression potential] possible false-positive or false-negative autopkgtest results. [other info] Note: This patch is not required for debian, because debian's boot- smoke does not include the wait for systemctl is-system-running. The problem appears to be that systemd reaches 'running' (or 'degraded') state, and then other systemd services are started. This confuses the boot-smoke test, because it sees that 'is-system-running' is done, but then it sees running jobs, which fails the test. What is starting jobs after systemd reaches running state appears to be X inside the test system. There are various services started by gnome-session and dbus-daemon. Additionally, from the artifacts of one example: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- bionic/bionic/i386/s/systemd/20190416_171327_478f6@/artifacts.tar.gz the artifacts/journal.txt shows that after the boot-smoke test causes the reboot and then re-ssh into the system after the reboot, it only gives the test system 9 seconds before deciding it has failed, and only 4 seconds after ssh'ing into the rebooted test system. Another wait is needed when checking for remaining running jobs. Or, the running jobs check could be removed entirely, and we can just trust that systemd correctly knows when it has reached running|degraded state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan
How does your vlan .netdev unit looks like? You need something that creates the vlan device on top of the selected underlying device, ie.: $ cat enp3s0.2.netdev [NetDev] Name=enp3s0.2 Kind=vlan [VLAN] Id=2 Without that, there won't be vlan device created (nor visiable in $ ip a), and thus no network on it either. ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1831470 Title: systemd dhcp don't work on vlan Status in systemd package in Ubuntu: Incomplete Bug description: root@gwd:~# uname -a Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@gwd:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic root@gwd:~# cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Link] MACAddress=C8:D3:A3:50:02:33 [Network] VLAN=enp3s0.2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.network [Match] Name=enp3s0.2 [Network] DHCP=ipv4 [DHCP] UseRoutes=true - No ip on enp3s0.2 after boot! dhclient enp3s0.2 works fine, i create systemd service for it as temporary workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1747765] Please test proposed package
Hello Bo, or anyone else affected, Accepted cups into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cups/2.1.3-4ubuntu0.9 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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 cups in Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Committed Status in cups source package in Disco: Fix Committed Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Hello Bo, or anyone else affected, Accepted cups into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cups/2.2.7-1ubuntu2.6 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. ** Changed in: cups (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic ** Changed in: cups (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Committed Status in cups source package in Disco: Fix Committed Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Hello Bo, or anyone else affected, Accepted cups into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cups/2.2.8-5ubuntu1.4 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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. 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: cups (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed-cosmic -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: Fix Committed Status in cups source package in Disco: Fix Committed Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Thanks for the SRU! The upload looks good, but could I request that the new packages are tested against the PreserveJobHistory Yes/No values additionally to the 'seconds' case? As an additional safety check. I will accept this upload but please include those 2 additional tests in the Test Case. ** Changed in: cups (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: In Progress Status in cups source package in Disco: Fix Committed Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1747765] Please test proposed package
Hello Bo, or anyone else affected, Accepted cups into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cups/2.2.10-4ubuntu2 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-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. 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 cups in Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: In Progress Status in cups source package in Disco: Fix Committed Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan
on same machine usb modem works fine with DHCP option root@gwd:~# cat /etc/systemd/network/yota.network [Match] Name=enx0c5b8f279a64 [Network] DHCP=yes -- 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/1831470 Title: systemd dhcp don't work on vlan Status in systemd package in Ubuntu: New Bug description: root@gwd:~# uname -a Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@gwd:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic root@gwd:~# cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Link] MACAddress=C8:D3:A3:50:02:33 [Network] VLAN=enp3s0.2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.network [Match] Name=enp3s0.2 [Network] DHCP=ipv4 [DHCP] UseRoutes=true - No ip on enp3s0.2 after boot! dhclient enp3s0.2 works fine, i create systemd service for it as temporary workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan
netplan and cloud-init not used and was purged -- 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/1831470 Title: systemd dhcp don't work on vlan Status in systemd package in Ubuntu: New Bug description: root@gwd:~# uname -a Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@gwd:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic root@gwd:~# cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Link] MACAddress=C8:D3:A3:50:02:33 [Network] VLAN=enp3s0.2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.network [Match] Name=enp3s0.2 [Network] DHCP=ipv4 [DHCP] UseRoutes=true - No ip on enp3s0.2 after boot! dhclient enp3s0.2 works fine, i create systemd service for it as temporary workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831468] [NEW] 'upstream' tests fail, usually TEST-18, TEST-19, TEST-25, and/or TEST-27
Public bug reported: [impact] some tests in the 'upstream' test suite fail on disco for ppc64el, e.g.: FAILED TESTS: test/TEST-18-FAILUREACTION test/TEST-19-DELEGATE test/TEST-25-IMPORT test/TEST-27-STDOUTFILE [test case] check autopkgtest logs, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/s/systemd/20190601_160043_a5281@/log.gz [regression potential] TBD [other info] this appears to fail only on ppc64el on disco and eoan, not cosmic or earlier or any other archs, but that is only from checking a few logs from other releases/archs, and without any investigation into the problem yet, so could be incorrect. ** Affects: systemd (Ubuntu) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Disco) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Eoan) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Eoan) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Disco) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Eoan) Status: New => In Progress ** Changed in: systemd (Ubuntu Disco) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1831468 Title: 'upstream' tests fail, usually TEST-18, TEST-19, TEST-25, and/or TEST-27 Status in systemd package in Ubuntu: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [impact] some tests in the 'upstream' test suite fail on disco for ppc64el, e.g.: FAILED TESTS: test/TEST-18-FAILUREACTION test/TEST-19-DELEGATE test/TEST-25-IMPORT test/TEST-27-STDOUTFILE [test case] check autopkgtest logs, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/s/systemd/20190601_160043_a5281@/log.gz [regression potential] TBD [other info] this appears to fail only on ppc64el on disco and eoan, not cosmic or earlier or any other archs, but that is only from checking a few logs from other releases/archs, and without any investigation into the problem yet, so could be incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831470] [NEW] systemd dhcp don't work on vlan
Public bug reported: root@gwd:~# uname -a Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@gwd:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic root@gwd:~# cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Link] MACAddress=C8:D3:A3:50:02:33 [Network] VLAN=enp3s0.2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.network [Match] Name=enp3s0.2 [Network] DHCP=ipv4 [DHCP] UseRoutes=true - No ip on enp3s0.2 after boot! dhclient enp3s0.2 works fine, i create systemd service for it as temporary workaround ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1831470 Title: systemd dhcp don't work on vlan Status in systemd package in Ubuntu: New Bug description: root@gwd:~# uname -a Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@gwd:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic root@gwd:~# cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Link] MACAddress=C8:D3:A3:50:02:33 [Network] VLAN=enp3s0.2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.network [Match] Name=enp3s0.2 [Network] DHCP=ipv4 [DHCP] UseRoutes=true - No ip on enp3s0.2 after boot! dhclient enp3s0.2 works fine, i create systemd service for it as temporary workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825997] Re: boot-smoke fails due to running jobs
autopkgtest failures: cosmic: linux-oracle: tests never passed; ignore. umockdev: I opened bug 1831467, and i'm re-running the test; it's an intermittent failure so hopefully it will pass the next time, but even if not i believe we can ignore its failure as it seems to be a test case problem of expecting very-accurate ms-level usleep() timing, as explained in the bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1825997 Title: boot-smoke fails due to running jobs Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Committed Bug description: [impact] boot-smoke test reboots 5 times and verifies systemd is fully started up after each boot, including checking if there are any running jobs (with list-jobs). However, this test makes the assumption that no further jobs will be started after systemd reaches 'running' (or 'degraded') state, which is a false assumption. [test case] see various boot-smoke failures in autopkgtest.ubuntu.com [regression potential] possible false-positive or false-negative autopkgtest results. [other info] Note: This patch is not required for debian, because debian's boot- smoke does not include the wait for systemctl is-system-running. The problem appears to be that systemd reaches 'running' (or 'degraded') state, and then other systemd services are started. This confuses the boot-smoke test, because it sees that 'is-system-running' is done, but then it sees running jobs, which fails the test. What is starting jobs after systemd reaches running state appears to be X inside the test system. There are various services started by gnome-session and dbus-daemon. Additionally, from the artifacts of one example: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- bionic/bionic/i386/s/systemd/20190416_171327_478f6@/artifacts.tar.gz the artifacts/journal.txt shows that after the boot-smoke test causes the reboot and then re-ssh into the system after the reboot, it only gives the test system 9 seconds before deciding it has failed, and only 4 seconds after ssh'ing into the rebooted test system. Another wait is needed when checking for remaining running jobs. Or, the running jobs check could be removed entirely, and we can just trust that systemd correctly knows when it has reached running|degraded state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831467] [NEW] 'testbed_script_replay_simple' test fails intermittently
Public bug reported: [impact] this test fails intermittently, due to read failures when the test expects to read data, but the umockdev 'replay' script device doesn't provide the data to read. this appears to just be a timing issue, as the test expects the umockdev device to provide specific data replayed at specific times, and those times are very short (ms). Looking at the autopkgtest results: http://autopkgtest.ubuntu.com/packages/umockdev it looks like the failures are mostly on armhf, presumably because that is run in a container and provides the least guarantee of accurate short usleep() timing, but it also does fail on other archs sometimes as well. [test case] check the previous autopkgtest logs, e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/armhf/u/umockdev/20190601_015323_8f795@/log.gz [regression potential] probably low, as it seems like this is really just a test case issue of expecting very specific ms-range timing. ** Affects: umockdev (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to umockdev in Ubuntu. https://bugs.launchpad.net/bugs/1831467 Title: 'testbed_script_replay_simple' test fails intermittently Status in umockdev package in Ubuntu: New Bug description: [impact] this test fails intermittently, due to read failures when the test expects to read data, but the umockdev 'replay' script device doesn't provide the data to read. this appears to just be a timing issue, as the test expects the umockdev device to provide specific data replayed at specific times, and those times are very short (ms). Looking at the autopkgtest results: http://autopkgtest.ubuntu.com/packages/umockdev it looks like the failures are mostly on armhf, presumably because that is run in a container and provides the least guarantee of accurate short usleep() timing, but it also does fail on other archs sometimes as well. [test case] check the previous autopkgtest logs, e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/armhf/u/umockdev/20190601_015323_8f795@/log.gz [regression potential] probably low, as it seems like this is really just a test case issue of expecting very specific ms-range timing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1831467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831264] Re: Sun keyboard Front key not accepted by gnome-control-center
Thanks for your report! The issues you describe are upstream in nature, and it would be great if you could file an upstream issue as well: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues If you do, please post the URL to it here for tracking purposes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1831264 Title: Sun keyboard Front key not accepted by gnome-control-center Status in xkeyboard-config package in Ubuntu: New Bug description: A Sun keyboards is recognized by the hardware detector with no problem. xmodmap -pk gives the following for the relevant keys: 136 0xff69 (Cancel) 0x (NoSymbol) 0xff69 (Cancel) 137 0xff66 (Redo) 0x (NoSymbol) 0xff66 (Redo) 138 0x1005ff70 (SunProps) 0x (NoSymbol) 0x1005ff70 (SunProps) 139 0xff65 (Undo) 0x (NoSymbol) 0xff65 (Undo) 140 0x1005ff71 (SunFront) 0x (NoSymbol) 0x1005ff71 (SunFront) 141 0x1008ff57 (XF86Copy) 0x (NoSymbol) 0x1008ff57 (XF86Copy) 142 0x1008ff6b (XF86Open) 0x (NoSymbol) 0x1008ff6b (XF86Open) 143 0x1008ff6d (XF86Paste) 0x (NoSymbol) 0x1008ff6d (XF86Paste) 144 0xff68 (Find) 0x (NoSymbol) 0xff68 (Find) 145 0x1008ff58 (XF86Cut)0x (NoSymbol) 0x1008ff58 (XF86Cut) 146 0xff6a (Help) 0x (NoSymbol) 0xff6a (Help) Observe that the names of the two keysyms 0x1005ff70 and 0x1005ff71 are SUN specials, not in the XF86 set. Pressing either of these using xev behaves as expected: KeyPress event, serial 37, synthetic NO, window 0x361, root 0x4fe, subw 0x0, time 3071686, (118,83), root:(1365,168), state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x361, root 0x4fe, subw 0x0, time 3071688, (118,83), root:(1365,168), state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False I tried binding "Lower window below other windows" to the SunFront using the Settings app, but it did not work.(Note that back in the days of 14.04 where you uses CCSM to make this setting, it worked fine.) After this I did $ dconf dump /org/gnome/desktop/wm/keybindings/ [/] lower=['0x1005ff71'] switch-to-workspace-1=['1'] move-to-workspace-1=@as [] switch-to-workspace-2=['2'] switch-to-workspace-3=['3'] switch-to-workspace-4=['4'] move-to-monitor-down=@as [] move-to-monitor-up=@as [] So it had recognized the correct keysym, but does not know that the name of that keysym is SunFront. So far so bad. It works fine with keysyms with known names (e.g. the CANCEL key), and it should not be hard to construct a workaround my modifying the keyboard tables to map that key to some better-named keysym, so it might be argued that this bug is of Low Priority. BUT there is a serious side effect. With that dconf setting in place: the Left Arrow key on the keyboard no longer works (for example, I made that change whilst composing this report, and I cannot now move the cursor backwards with the Left Arrow key, though fortunately the Left Arrow on the numeric keypad still behaves). All applications seem to be affected (e.g. Firefox, Terminal, Gedit). Left and Left still work, except that if you engage Num Lock, Left now stops working. Using xev to see what happens when Left Arrow is pressed yields: FocusOut event, serial 37, synthetic NO, window 0x361, mode NotifyGrab, detail NotifyAncestor FocusOut event, serial 37, synthetic NO, window 0x361, mode NotifyUngrab, detail NotifyPointer FocusIn event, serial 37, synthetic NO, window 0x361, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 37, synthetic NO, window 0x0, keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 which is crazy! You should not be surprised that I spent a whole day gradually removing all the changes I had made until finally I narrowed it down to dconf, and then to that particular setting. Changing the binding back to CANCEL removes the problem (except that you have to restart each application affected, so I have just restarted Terminal, but I cannot restart Firefox while I am still typing this report). My main worry is that there may be some other keybinding errors that cause the same side effect, and therefor the Priority of fixing this bug
[Touch-packages] [Bug 1825997] Re: boot-smoke fails due to running jobs
autopkgtest failures: bionic: linux-snapdragon, linux-gke-4.15, linux-aws-edge: these have never passed; ignore. gvfs (ppc64el and i386): bug 1713098 (failure matches report from that bug) systemd (ppc64el): only test failure is due to bug 1821625 (which requires kernel patch) systemd (i386): test failed twice due to bug 1829829, re-running test, but impossible to tell when it will pass or fail due to this bug, so may need to just ignore this failure -- 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/1825997 Title: boot-smoke fails due to running jobs Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Committed Bug description: [impact] boot-smoke test reboots 5 times and verifies systemd is fully started up after each boot, including checking if there are any running jobs (with list-jobs). However, this test makes the assumption that no further jobs will be started after systemd reaches 'running' (or 'degraded') state, which is a false assumption. [test case] see various boot-smoke failures in autopkgtest.ubuntu.com [regression potential] possible false-positive or false-negative autopkgtest results. [other info] Note: This patch is not required for debian, because debian's boot- smoke does not include the wait for systemctl is-system-running. The problem appears to be that systemd reaches 'running' (or 'degraded') state, and then other systemd services are started. This confuses the boot-smoke test, because it sees that 'is-system-running' is done, but then it sees running jobs, which fails the test. What is starting jobs after systemd reaches running state appears to be X inside the test system. There are various services started by gnome-session and dbus-daemon. Additionally, from the artifacts of one example: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- bionic/bionic/i386/s/systemd/20190416_171327_478f6@/artifacts.tar.gz the artifacts/journal.txt shows that after the boot-smoke test causes the reboot and then re-ssh into the system after the reboot, it only gives the test system 9 seconds before deciding it has failed, and only 4 seconds after ssh'ing into the rebooted test system. Another wait is needed when checking for remaining running jobs. Or, the running jobs check could be removed entirely, and we can just trust that systemd correctly knows when it has reached running|degraded state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831261] Re: OpenVPN Other DNS Servers ignored if no Search Domains specified
First, please try the systemd SRU proposed in bug 1754671. If it does not solve your problem, do the following: Please create the following files (and directories if needed for them): 1. /etc/systemd/journald.d/noratelimit.conf containing RateLimitIntervalSec=0 RateLimitBurst=0 2. /etc/NetworkManager/conf.d/debug.conf [logging] level=TRACE domains=ALL Then restart journald: sudo systemctl restart systemd-journald and NetworkManager: sudo systemctl restart network-manager Then you get the full debug log of NetworkManager via journalctl -u NetworkManager After all that, reboot and/or connect to your VPN and do journalctl -u NetworkManager > log.txt and attach the log.txt file to this bug report. Do not compress the file and do not package it together with other files. ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1831261 Title: OpenVPN Other DNS Servers ignored if no Search Domains specified Status in network-manager package in Ubuntu: Incomplete Bug description: On Kubuntu 18.04.2 LTS, with network-manager 1.10.14-0ubuntu2, DNS servers in "Other DNS Servers" are ignored unless a Search Domain is also specified. This difference can be seen in the output of `systemd- resolve --status`. For my use case, I need to specify an additional DNS server but I have no need to specify a search domain. Specifying a bogus domain fixes the problem, and the DNS server appears in `systemd-resolve --status`. I suspect this may be related to the fix for #1754671, which was released in 1.10.14-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1831261/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1810241] Re: NULL dereference when decompressing specially crafted archives
** Changed in: tar (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1810241 Title: NULL dereference when decompressing specially crafted archives Status in tar package in Ubuntu: Triaged Bug description: Hi, Fuzzing tar with checksums disabled reveals a NULL pointer dereference when parsing certain archives that have malformed extended headers. This affects tar from (at least) Trusty, Bionic and Cosmic. I haven't tested Xenial's version. A test case with fixed checksums is attached. To avoid breaking anything that looks inside tar archives, I have converted it to text with xxd. To reproduce: $ xxd -r gnutar-crash.tar.txt gnutar-crash.tar $ tar Oxf gnutar-crash.tar tar: Ignoring unknown extended header keyword 'GNU.sparse.minTr' tar: Malformed extended header: missing length Segmentation fault (core dumped) I have also attached a patch against the latest upstream git and against 1.30 (in Cosmic). This fixes the issue by detecting the null result before it is dereferenced. Regards, Daniel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1810241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
bug #1831261 is also described as a potential side effect from this change -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: In Progress Status in systemd source package in Bionic: Fix Committed Status in network-manager source package in Cosmic: New Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831264] Re: Sun keyboard Front key not accepted by gnome-control-center
** Package changed: gnome-control-center (Ubuntu) => xkeyboard-config (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1831264 Title: Sun keyboard Front key not accepted by gnome-control-center Status in xkeyboard-config package in Ubuntu: New Bug description: A Sun keyboards is recognized by the hardware detector with no problem. xmodmap -pk gives the following for the relevant keys: 136 0xff69 (Cancel) 0x (NoSymbol) 0xff69 (Cancel) 137 0xff66 (Redo) 0x (NoSymbol) 0xff66 (Redo) 138 0x1005ff70 (SunProps) 0x (NoSymbol) 0x1005ff70 (SunProps) 139 0xff65 (Undo) 0x (NoSymbol) 0xff65 (Undo) 140 0x1005ff71 (SunFront) 0x (NoSymbol) 0x1005ff71 (SunFront) 141 0x1008ff57 (XF86Copy) 0x (NoSymbol) 0x1008ff57 (XF86Copy) 142 0x1008ff6b (XF86Open) 0x (NoSymbol) 0x1008ff6b (XF86Open) 143 0x1008ff6d (XF86Paste) 0x (NoSymbol) 0x1008ff6d (XF86Paste) 144 0xff68 (Find) 0x (NoSymbol) 0xff68 (Find) 145 0x1008ff58 (XF86Cut)0x (NoSymbol) 0x1008ff58 (XF86Cut) 146 0xff6a (Help) 0x (NoSymbol) 0xff6a (Help) Observe that the names of the two keysyms 0x1005ff70 and 0x1005ff71 are SUN specials, not in the XF86 set. Pressing either of these using xev behaves as expected: KeyPress event, serial 37, synthetic NO, window 0x361, root 0x4fe, subw 0x0, time 3071686, (118,83), root:(1365,168), state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x361, root 0x4fe, subw 0x0, time 3071688, (118,83), root:(1365,168), state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False I tried binding "Lower window below other windows" to the SunFront using the Settings app, but it did not work.(Note that back in the days of 14.04 where you uses CCSM to make this setting, it worked fine.) After this I did $ dconf dump /org/gnome/desktop/wm/keybindings/ [/] lower=['0x1005ff71'] switch-to-workspace-1=['1'] move-to-workspace-1=@as [] switch-to-workspace-2=['2'] switch-to-workspace-3=['3'] switch-to-workspace-4=['4'] move-to-monitor-down=@as [] move-to-monitor-up=@as [] So it had recognized the correct keysym, but does not know that the name of that keysym is SunFront. So far so bad. It works fine with keysyms with known names (e.g. the CANCEL key), and it should not be hard to construct a workaround my modifying the keyboard tables to map that key to some better-named keysym, so it might be argued that this bug is of Low Priority. BUT there is a serious side effect. With that dconf setting in place: the Left Arrow key on the keyboard no longer works (for example, I made that change whilst composing this report, and I cannot now move the cursor backwards with the Left Arrow key, though fortunately the Left Arrow on the numeric keypad still behaves). All applications seem to be affected (e.g. Firefox, Terminal, Gedit). Left and Left still work, except that if you engage Num Lock, Left now stops working. Using xev to see what happens when Left Arrow is pressed yields: FocusOut event, serial 37, synthetic NO, window 0x361, mode NotifyGrab, detail NotifyAncestor FocusOut event, serial 37, synthetic NO, window 0x361, mode NotifyUngrab, detail NotifyPointer FocusIn event, serial 37, synthetic NO, window 0x361, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 37, synthetic NO, window 0x0, keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 which is crazy! You should not be surprised that I spent a whole day gradually removing all the changes I had made until finally I narrowed it down to dconf, and then to that particular setting. Changing the binding back to CANCEL removes the problem (except that you have to restart each application affected, so I have just restarted Terminal, but I cannot restart Firefox while I am still typing this report). My main worry is that there may be some other keybinding errors that cause the same side effect, and therefor the Priority of fixing this bug needs to be much higher. Moreover, this problem seems to have been around for a long time. see:
[Touch-packages] [Bug 1831264] [NEW] Sun keyboard Front key not accepted by gnome-control-center
You have been subscribed to a public bug: A Sun keyboards is recognized by the hardware detector with no problem. xmodmap -pk gives the following for the relevant keys: 136 0xff69 (Cancel) 0x (NoSymbol) 0xff69 (Cancel) 137 0xff66 (Redo) 0x (NoSymbol) 0xff66 (Redo) 138 0x1005ff70 (SunProps) 0x (NoSymbol) 0x1005ff70 (SunProps) 139 0xff65 (Undo) 0x (NoSymbol) 0xff65 (Undo) 140 0x1005ff71 (SunFront) 0x (NoSymbol) 0x1005ff71 (SunFront) 141 0x1008ff57 (XF86Copy) 0x (NoSymbol) 0x1008ff57 (XF86Copy) 142 0x1008ff6b (XF86Open) 0x (NoSymbol) 0x1008ff6b (XF86Open) 143 0x1008ff6d (XF86Paste) 0x (NoSymbol) 0x1008ff6d (XF86Paste) 144 0xff68 (Find) 0x (NoSymbol) 0xff68 (Find) 145 0x1008ff58 (XF86Cut)0x (NoSymbol) 0x1008ff58 (XF86Cut) 146 0xff6a (Help) 0x (NoSymbol) 0xff6a (Help) Observe that the names of the two keysyms 0x1005ff70 and 0x1005ff71 are SUN specials, not in the XF86 set. Pressing either of these using xev behaves as expected: KeyPress event, serial 37, synthetic NO, window 0x361, root 0x4fe, subw 0x0, time 3071686, (118,83), root:(1365,168), state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x361, root 0x4fe, subw 0x0, time 3071688, (118,83), root:(1365,168), state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False I tried binding "Lower window below other windows" to the SunFront using the Settings app, but it did not work.(Note that back in the days of 14.04 where you uses CCSM to make this setting, it worked fine.) After this I did $ dconf dump /org/gnome/desktop/wm/keybindings/ [/] lower=['0x1005ff71'] switch-to-workspace-1=['1'] move-to-workspace-1=@as [] switch-to-workspace-2=['2'] switch-to-workspace-3=['3'] switch-to-workspace-4=['4'] move-to-monitor-down=@as [] move-to-monitor-up=@as [] So it had recognized the correct keysym, but does not know that the name of that keysym is SunFront. So far so bad. It works fine with keysyms with known names (e.g. the CANCEL key), and it should not be hard to construct a workaround my modifying the keyboard tables to map that key to some better-named keysym, so it might be argued that this bug is of Low Priority. BUT there is a serious side effect. With that dconf setting in place: the Left Arrow key on the keyboard no longer works (for example, I made that change whilst composing this report, and I cannot now move the cursor backwards with the Left Arrow key, though fortunately the Left Arrow on the numeric keypad still behaves). All applications seem to be affected (e.g. Firefox, Terminal, Gedit). Left and Left still work, except that if you engage Num Lock, Left now stops working. Using xev to see what happens when Left Arrow is pressed yields: FocusOut event, serial 37, synthetic NO, window 0x361, mode NotifyGrab, detail NotifyAncestor FocusOut event, serial 37, synthetic NO, window 0x361, mode NotifyUngrab, detail NotifyPointer FocusIn event, serial 37, synthetic NO, window 0x361, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 37, synthetic NO, window 0x0, keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 which is crazy! You should not be surprised that I spent a whole day gradually removing all the changes I had made until finally I narrowed it down to dconf, and then to that particular setting. Changing the binding back to CANCEL removes the problem (except that you have to restart each application affected, so I have just restarted Terminal, but I cannot restart Firefox while I am still typing this report). My main worry is that there may be some other keybinding errors that cause the same side effect, and therefor the Priority of fixing this bug needs to be much higher. Moreover, this problem seems to have been around for a long time. see: https://unix.stackexchange.com/questions/231307/key-for-the-letter-o-stopped-working-works-only-with-shift-linux which produces exactly the same xev output with a completely different binding problem. To reproduce the Bug, ideally just find a Sun Keyboard and plug it into a spare USB port, and then follow what I have described. If you cannot lay your hands on a Sun Keyboard, then it is likely that $ dconf load /org/gnome/desktop/wm/keybindings/ lower=['0x1005ff71'] will produce the same effect. In case the bug reporting system has not supplied my full details, here is $ uname -a
[Touch-packages] [Bug 1830484] Re: boot-and-services test_no_failed fails if gdm failed to start in testbed
testcase pass on cosmic upload ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done verification-done-cosmic -- 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/1830484 Title: boot-and-services test_no_failed fails if gdm failed to start in testbed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Cosmic: Fix Committed Bug description: [impact] gdm on cosmic running in the autopkgtest is flaky and sometimes fails to start; when it does it causes other systemd service failures like 'user@118.service' or other services, which fail the test case. the test_gdm3 testcase was already skipped because of this in bug 1790478, the test_no_failed testcase needs to be skipped as well if gdm fails to start. [test case] the failure is intermittent, but looking through old cosmic systemd autopkgtest logs look for: May 23 11:13:38 autopkgtest systemd[1]: user@118.service: Killing process 1251 (systemctl) with signal SIGKILL. May 23 11:13:38 autopkgtest systemd[1]: Stopped User Manager for UID 118. May 23 11:13:39 autopkgtest systemd[1]: Starting User Manager for UID 118... May 23 11:13:37 autopkgtest systemd[1280]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0) May 23 11:13:38 autopkgtest systemd[1280]: Failed to fully start up daemon: Permission denied May 23 11:13:38 autopkgtest systemd[1]: user@118.service: Failed with result 'protocol'. May 23 11:13:38 autopkgtest systemd[1]: Failed to start User Manager for UID 118. FAIL test_rsyslog (__main__.ServicesTest) ... ok test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... ok == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.jGFP4N/build.FWq/src/debian/tests/boot-and-services", line 62, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['user@118.service loaded failed failed User Manager for UID 118'] != [] First list contains 1 additional elements. First extra element 0: 'user@118.service loaded failed failed User Manager for UID 118' - ['user@118.service loaded failed failed User Manager for UID 118'] + [] [regression potential] low; testcase skipping due to flaky gdm inside autopkgtest, only on cosmic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766740] Re: apport autopkgtest regression due to kernel packaging changes
** Changed in: apport (Ubuntu Xenial) Status: New => Triaged -- 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/1766740 Title: apport autopkgtest regression due to kernel packaging changes Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Triaged Status in apport source package in Bionic: Fix Released Bug description: [SRU Justification] In bionic, linux-image-$kvers-$flavor is now built from the linux-signed source package on amd64, not from the linux source package. This now causes a test to fail in the apport test suite: [...] == FAIL: test_run_crash_kernel (__main__.T) run_crash() for a kernel error -- Traceback (most recent call last): File "./test_ui.py", line 1305, in test_run_crash_kernel self.assertEqual(self.ui.opened_url, 'http://linux.bugs.example.com/%i' % se lf.ui.crashdb.latest_id()) AssertionError: 'http://linux-signed.bugs.example.com/5' != 'http://linux.bugs.e xample.com/5' - http://linux-signed.bugs.example.com/5 ? --- + http://linux.bugs.example.com/5 -- Ran 70 tests in 79.815s FAILED (failures=1) [...] (https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- bionic/bionic/amd64/a/apport/20180424_19_45dc8@/log.gz) This test needs to be fixed to know about the packaging change. Note that this packaging change is expected to soon be SRUed back to all Ubuntu releases, so apport's testsuite change should also be SRUed. [Test case] This passes if the autopkgtests pass. [Regression potential] The test could be changed to pass while leaving underlying issues in the code. This has probably not happened here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1766740/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825997] Re: boot-smoke fails due to running jobs
boot-smoke passed for all releases/archs from this upload ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco ** Tags added: verification-done verification-done-bionic verification-done-cosmic verification-done-disco -- 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/1825997 Title: boot-smoke fails due to running jobs Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Committed Bug description: [impact] boot-smoke test reboots 5 times and verifies systemd is fully started up after each boot, including checking if there are any running jobs (with list-jobs). However, this test makes the assumption that no further jobs will be started after systemd reaches 'running' (or 'degraded') state, which is a false assumption. [test case] see various boot-smoke failures in autopkgtest.ubuntu.com [regression potential] possible false-positive or false-negative autopkgtest results. [other info] Note: This patch is not required for debian, because debian's boot- smoke does not include the wait for systemctl is-system-running. The problem appears to be that systemd reaches 'running' (or 'degraded') state, and then other systemd services are started. This confuses the boot-smoke test, because it sees that 'is-system-running' is done, but then it sees running jobs, which fails the test. What is starting jobs after systemd reaches running state appears to be X inside the test system. There are various services started by gnome-session and dbus-daemon. Additionally, from the artifacts of one example: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- bionic/bionic/i386/s/systemd/20190416_171327_478f6@/artifacts.tar.gz the artifacts/journal.txt shows that after the boot-smoke test causes the reboot and then re-ssh into the system after the reboot, it only gives the test system 9 seconds before deciding it has failed, and only 4 seconds after ssh'ing into the rebooted test system. Another wait is needed when checking for remaining running jobs. Or, the running jobs check could be removed entirely, and we can just trust that systemd correctly knows when it has reached running|degraded state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
systemd 'storage' test case pass on all releases for ppc64el except disco due to bug 1831459, which i'll queue up to fix in the next upload. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco ** Tags added: verification-done verification-done-bionic verification-done-cosmic verification-done-disco -- 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/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: Fix Committed Status in linux source package in Disco: New Status in systemd source package in Disco: Fix Committed Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Fix Committed Status in systemd package in Debian: New Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829347] Re: systemd autopkgtest 'storage' fails adding/rmmoding scsi_debug
** Description changed:
[impact]
systemd autopkgtest fails
[test case]
run systemd autopkgtest, check for output like:
LUKS device with "tmp" option ... rmmod: ERROR: Module scsi_debug is in use
FAIL
==
FAIL: test_luks_tmp (__main__.CryptsetupTest)
LUKS device with "tmp" option
--
Traceback (most recent call last):
File "/tmp/autopkgtest.It858Q/build.e7O/src/debian/tests/storage", line 59,
in setUp
self.fail('%s exists already' % self.plaintext_dev)
AssertionError: /dev/mapper/testcrypt1 exists already
or for older releases something like:
autopkgtest [19:27:26]: test storage: [---
modprobe: FATAL: Module scsi_debug not found in directory
/lib/modules/4.18.0-1011-kvm
ERROR
==
ERROR: setUpClass (__main__.CryptsetupTest)
--
Traceback (most recent call last):
- File "/tmp/autopkgtest.azsL0q/build.Hbd/src/debian/tests/storage", line 21,
in setUpClass
- subprocess.check_call(['modprobe', 'scsi_debug'])
- File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
- raise CalledProcessError(retcode, cmd)
+ File "/tmp/autopkgtest.azsL0q/build.Hbd/src/debian/tests/storage", line 21,
in setUpClass
+ subprocess.check_call(['modprobe', 'scsi_debug'])
+ File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
+ raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['modprobe', 'scsi_debug']' returned
non-zero exit status 1.
-
- this has attempted to be fixed in disco/eoan so the output is a bit different
across different releases, but all of them have the common point of failing to
modprobe or rmmod the scsi_debug module, which by itself doesn't indicate a
failure.
+ this has attempted to be fixed in disco/eoan so the output is a bit
+ different across different releases, but all of them have the common
+ point of failing to modprobe or rmmod the scsi_debug module, which by
+ itself doesn't indicate a failure.
[regression potential]
low; this is fixing a testcase only.
+
+ [other info]
+
+ fixing test case that generally causes the failed rmmod in bug 1831459
--
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/1829347
Title:
systemd autopkgtest 'storage' fails adding/rmmoding scsi_debug
Status in systemd package in Ubuntu:
New
Status in systemd source package in Bionic:
Incomplete
Status in systemd source package in Cosmic:
Incomplete
Status in systemd source package in Disco:
Incomplete
Status in systemd source package in Eoan:
Won't Fix
Status in systemd package in Debian:
Unknown
Bug description:
[impact]
systemd autopkgtest fails
[test case]
run systemd autopkgtest, check for output like:
LUKS device with "tmp" option ... rmmod: ERROR: Module scsi_debug is in use
FAIL
==
FAIL: test_luks_tmp (__main__.CryptsetupTest)
LUKS device with "tmp" option
--
Traceback (most recent call last):
File "/tmp/autopkgtest.It858Q/build.e7O/src/debian/tests/storage", line 59,
in setUp
self.fail('%s exists already' % self.plaintext_dev)
AssertionError: /dev/mapper/testcrypt1 exists already
or for older releases something like:
autopkgtest [19:27:26]: test storage: [---
modprobe: FATAL: Module scsi_debug not found in directory
/lib/modules/4.18.0-1011-kvm
ERROR
==
ERROR: setUpClass (__main__.CryptsetupTest)
--
Traceback (most recent call last):
File "/tmp/autopkgtest.azsL0q/build.Hbd/src/debian/tests/storage", line 21,
in setUpClass
subprocess.check_call(['modprobe', 'scsi_debug'])
File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['modprobe', 'scsi_debug']' returned
non-zero exit status 1.
this has attempted to be fixed in disco/eoan so the output is a bit
different across different releases, but all of them have the common
point of failing to modprobe or rmmod the scsi_debug module, which by
itself doesn't indicate a failure.
[regression potential]
low; this is fixing a testcase only.
[other info]
fixing test case that generally causes the failed rmmod in bug 1831459
To manage notifications about this bug go to:
[Touch-packages] [Bug 1713017] Re: Enable MIDI support
The option is off by default in the upstream build see https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/README#n252 Since the option is flagged experimental by upstream it doesn't seem like something we want to enable in Ubuntu yet -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1713017 Title: Enable MIDI support Status in bluez package in Ubuntu: Triaged Bug description: Now that bluez has landed with 5.46-0ubuntu2, it would be nice to enable Bluetooth MIDI support. This did not seem to be enabled by default in the build from https://launchpad.net/ubuntu/+source/bluez/5.46-0ubuntu2 (it found BLE MIDI devices, gatttool could talk to them, but no MIDI device was made; also ldd showed no linkage to libasound.so.2). After recompiling it with libasound2-dev installed and --enable-midi in debian/rules, it worked. Suggestion: add libasound2-dev to bluez dependencies, add --enable- midi to rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1713017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831459] [NEW] 'storage' test needs to wait for systemd-cryptsetup to be active before stopping it
Public bug reported: [impact] test case fails because it does not wait for the service to become active before stopping it, resulting in failure to rmmod the scsi_debug module because it's still in use. [test case] check 'storage' test results for systemd in autopkgtest logs, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/s/systemd/20190601_160043_a5281@/log.gz [regression potential] low; test case fix only. [other info] detected and reported by @cascardo in bug 1814373 comment 4 and 5, but separate (non-test) systemd bugfix uploaded for that bug so opening this bug to track fixing the test case. larger fixes/improvements to 'storage' testcase in bug 1829347, but those rejected. ** Affects: systemd (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: systemd (Ubuntu Bionic) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Cosmic) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Disco) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Eoan) Importance: Undecided Status: Fix Released ** Also affects: systemd (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Eoan) Status: New => Fix Released ** Changed in: systemd (Ubuntu Disco) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Cosmic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Disco) Status: New => In Progress ** Changed in: systemd (Ubuntu Cosmic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Disco) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1831459 Title: 'storage' test needs to wait for systemd-cryptsetup to be active before stopping it Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: Fix Released Bug description: [impact] test case fails because it does not wait for the service to become active before stopping it, resulting in failure to rmmod the scsi_debug module because it's still in use. [test case] check 'storage' test results for systemd in autopkgtest logs, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/s/systemd/20190601_160043_a5281@/log.gz [regression potential] low; test case fix only. [other info] detected and reported by @cascardo in bug 1814373 comment 4 and 5, but separate (non-test) systemd bugfix uploaded for that bug so opening this bug to track fixing the test case. larger fixes/improvements to 'storage' testcase in bug 1829347, but those rejected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831459/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829840] Re: Sync libedit 3.1-20190324-1~exp1 (main) from Debian experimental (main)
This bug was fixed in the package libedit - 3.1-20190324-1~exp1 Sponsored for Sylvestre Ledru (sylvestre) --- libedit (3.1-20190324-1~exp1) experimental; urgency=medium * New upstream release -- Sylvestre Ledru Tue, 02 Apr 2019 12:06:41 +0200 ** Changed in: libedit (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libedit in Ubuntu. https://bugs.launchpad.net/bugs/1829840 Title: Sync libedit 3.1-20190324-1~exp1 (main) from Debian experimental (main) Status in libedit package in Ubuntu: Fix Released Bug description: Please sync libedit 3.1-20190324-1~exp1 (main) from Debian experimental (main) Changelog entries since current eoan version 3.1-20181209-1: libedit (3.1-20190324-1~exp1) experimental; urgency=medium * New upstream release -- Sylvestre Ledru Tue, 02 Apr 2019 12:06:41 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libedit/+bug/1829840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766740] Re: apport autopkgtest regression due to kernel packaging changes
** Also affects: apport (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1766740 Title: apport autopkgtest regression due to kernel packaging changes Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: New Status in apport source package in Bionic: Fix Released Bug description: [SRU Justification] In bionic, linux-image-$kvers-$flavor is now built from the linux-signed source package on amd64, not from the linux source package. This now causes a test to fail in the apport test suite: [...] == FAIL: test_run_crash_kernel (__main__.T) run_crash() for a kernel error -- Traceback (most recent call last): File "./test_ui.py", line 1305, in test_run_crash_kernel self.assertEqual(self.ui.opened_url, 'http://linux.bugs.example.com/%i' % se lf.ui.crashdb.latest_id()) AssertionError: 'http://linux-signed.bugs.example.com/5' != 'http://linux.bugs.e xample.com/5' - http://linux-signed.bugs.example.com/5 ? --- + http://linux.bugs.example.com/5 -- Ran 70 tests in 79.815s FAILED (failures=1) [...] (https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- bionic/bionic/amd64/a/apport/20180424_19_45dc8@/log.gz) This test needs to be fixed to know about the packaging change. Note that this packaging change is expected to soon be SRUed back to all Ubuntu releases, so apport's testsuite change should also be SRUed. [Test case] This passes if the autopkgtests pass. [Regression potential] The test could be changed to pass while leaving underlying issues in the code. This has probably not happened here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1766740/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
autopkgtest failures for this upload analyzed in bug 1825997 -- 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/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: Fix Committed Status in linux source package in Disco: New Status in systemd source package in Disco: Fix Committed Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Fix Committed Status in systemd package in Debian: New Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825378] Re: systemd-networkd doesn't set wireguard peer endpoint
autopkgtest failures for this upload analyzed in bug 1825997 -- 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/1825378 Title: systemd-networkd doesn't set wireguard peer endpoint Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Cosmic: Invalid Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Committed Bug description: [impact] systemd does not set endpoints for wireguard interfaces correctly. This makes wireguard unusable. [test case] install a disco or eoan system and set up a wireguard interface: $ sudo add-apt-repository ppa:wireguard/wireguard $ sudo apt install wireguard ...(this does a lot of stuff)... create a file as below; There is no need to setup remote server to reproduce this issue, but PublicKey/PrivateKey should be valid one (used instructions from https://www.linode.com/docs/networking/vpn /set-up-wireguard-vpn-on-ubuntu/#configure-wireguard-server): $ cat /etc/systemd/network/wg0.netdev [NetDev] Name=wg0 Kind=wireguard [WireGuard] PrivateKey=uMuCbguKYdKanRYMbDSriIdgxGxJR57Us1zEy8wRc1M= ListenPort=51820 [WireGuardPeer] PublicKey=ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= AllowedIPs=10.0.0.0/8 Endpoint=192.168.1.1:51820 $ sudo systemctl restart systemd-networkd $ sudo wg show wg0 interface: wg0 public key: BnvFgvPiVb5xURfzZ5liV1P77qeGeJDIX3C1iNquA2k= private key: (hidden) listening port: 51820 peer: ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= allowed ips: 10.0.0.0/8 the last command should print remote endpoint address, e.g.: peer: ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= endpoint: 192.168.1.1:51820 allowed ips: 10.0.0.0/8 [regression potential] any changes to systemd contain the potential for serious regressions. However, this is cherry picked directly from upstream, with the releases requiring patching (disco and eoan) being at exactly the same version and very close to upstream already. Additionally, while this does add 2 new functions (from upstream commit https://github.com/systemd/systemd/pull/11580/commits/abd48ec87f2ac5dd571a99dcb4db88c4affdffc8), they are only used - and code is only changed in - wireguard.c, so any regressions should be limited to wireguard interfaces (unless systemd crashes completely). [other info] this bug is not present in cosmic and earlier, and is already fixed in upstream systemd, so this is needed only for disco and eoan. original description: --- systemd/disco 240 shipped with Ubuntu 19.04 beta does not set endpoints for [WireguradPeer] properly. This regression was introduced in v241 and merged into v240. systemd 241 doesn't set wireguard peer endpoint https://github.com/systemd/systemd/issues/11579 Revert of the regression was landed on v240 stable branch https://github.com/systemd/systemd-stable/pull/39 1)2) confirmed with, systemd/disco 240-6ubuntu5 amd64 3) put a netdev file /etc/systemd/network/wg0.netdev --- [NetDev] Name=wg0 Kind=wireguard [WireGuard] PrivateKey=** ListenPort=51820 [WireGuardPeer] PublicKey=* AllowedIPs=10.0.0.0/8 Endpoint=192.168.1.1:51820 and run --- # systemctl restart systemd-networkd # wg show wg0 interface: wg0 public key: * private key: (hidden) listening port: 51820 peer: * allowed ips: 10.0.0.0/8 4) the last command should print remote endpoint address. --- # wg show wg0 interface: wg0 public key: * private key: (hidden) listening port: 51820 peer: * endpoint: 192.168.1.1:51820 allowed ips: 10.0.0.0/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825378/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830484] Re: boot-and-services test_no_failed fails if gdm failed to start in testbed
autopkgtest failures for this upload analyzed in bug 1825997 -- 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/1830484 Title: boot-and-services test_no_failed fails if gdm failed to start in testbed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Cosmic: Fix Committed Bug description: [impact] gdm on cosmic running in the autopkgtest is flaky and sometimes fails to start; when it does it causes other systemd service failures like 'user@118.service' or other services, which fail the test case. the test_gdm3 testcase was already skipped because of this in bug 1790478, the test_no_failed testcase needs to be skipped as well if gdm fails to start. [test case] the failure is intermittent, but looking through old cosmic systemd autopkgtest logs look for: May 23 11:13:38 autopkgtest systemd[1]: user@118.service: Killing process 1251 (systemctl) with signal SIGKILL. May 23 11:13:38 autopkgtest systemd[1]: Stopped User Manager for UID 118. May 23 11:13:39 autopkgtest systemd[1]: Starting User Manager for UID 118... May 23 11:13:37 autopkgtest systemd[1280]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0) May 23 11:13:38 autopkgtest systemd[1280]: Failed to fully start up daemon: Permission denied May 23 11:13:38 autopkgtest systemd[1]: user@118.service: Failed with result 'protocol'. May 23 11:13:38 autopkgtest systemd[1]: Failed to start User Manager for UID 118. FAIL test_rsyslog (__main__.ServicesTest) ... ok test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... ok == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.jGFP4N/build.FWq/src/debian/tests/boot-and-services", line 62, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['user@118.service loaded failed failed User Manager for UID 118'] != [] First list contains 1 additional elements. First extra element 0: 'user@118.service loaded failed failed User Manager for UID 118' - ['user@118.service loaded failed failed User Manager for UID 118'] + [] [regression potential] low; testcase skipping due to flaky gdm inside autopkgtest, only on cosmic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831413] Re: alsa has to be reloaded afterlogin or else I don't get any sound
Thank you for your bug report. Do you still get the bug if you uninstall "timidity"? That looks similar to bug #1793640 ** Changed in: alsa-driver (Ubuntu) Importance: Undecided => Low ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/1831413 Title: alsa has to be reloaded afterlogin or else I don't get any sound Status in alsa-driver package in Ubuntu: Incomplete Bug description: If I open Firefox or Chrome or any other app to play anything with sound, I get no sound, unless I run ~$ sudo alsa force-reload first. Before upgrading from Bionic to Disco I didn't have to do this. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-15.16-lowlatency 5.0.6 Uname: Linux 5.0.0-15-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 2006 F timidity /dev/snd/pcmC0D0p: timidity 2006 F...m timidity /dev/snd/seq:timidity 2006 F timidity /dev/snd/timer: timidity 2006 f timidity Date: Sun Jun 2 20:12:03 2019 InstallationDate: Installed on 2016-12-19 (895 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B219P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI320NANO series dmi.board.vendor: ZOTAC dmi.board.version: Rev.00 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: N/A dmi.product.name: ZBOX-CI320NANO series dmi.product.sku: N/A dmi.product.version: Rev.00 dmi.sys.vendor: Motherboard by ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1831413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805543] Re: Packaged version of iptables doesn't provide --random-fully flag.
For doing an SRU the bug would need a description of the impact and a test case / description of the regression potential (see https://wiki.ubuntu.com/StableReleaseUpdates). Could someone provide those informations (and ideally a debdiff for the update) ** Changed in: iptables (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1805543 Title: Packaged version of iptables doesn't provide --random-fully flag. Status in iptables package in Ubuntu: Confirmed Bug description: Hello. This isn't strictly a bug, but more of an upgrade-request on the iptables package. Normally i wouldn't be inclined to submit such a bug report, but a user on the ubuntu-devel-discuss mailing list encouraged me to submit this anyway [1]. For our production systems, we're running into a kernel race condition bug, for which a workaround has been made available. The fix boils down to iptables having a new flag which it passes down to the kernel, to enable the workaround. However, the version of iptables in Ubuntu (v1.6.1) doesn't support that kernel feature yet. Specifically, it's introduced in this commit on the iptables codebase: https://git.netfilter.org/iptables/commit/?id=8b0da2130b8af3890ef20afb2305f11224bb39ec. The feature we need from that commit is part of the v1.6.2 and newer iptables releases, but it looks like the Bionic, Cosmic, and Disco releases of Ubuntu all include v1.6.1 without that patch, so for now we're going to have to build iptables from source on our production machines. That shouldn't pose any huge issues, but of course, we'd prefer to be able to use the package from package management, or perhaps a backported package from a newer Ubuntu release. So to summarise, this might be an invalid bug report, but consider it a vote to upgrade the packaged version of iptables. If this bug report is entirely inappropriate, then I apologise. 1. Link to thread on ubuntu-devel-discuss where I describe the problem and Nish suggests I file this bug report: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2018-November/018181.html Ubuntu version we're using: Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy iptables iptables: Installed: 1.6.1-2ubuntu2 Candidate: 1.6.1-2ubuntu2 Version table: *** 1.6.1-2ubuntu2 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Thanks for your time, Paul To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1805543/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830169] Re: lvm udev rule fails to call systemd-run
** Tags added: id-5cf4e60af7841930654ed12b
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1830169
Title:
lvm udev rule fails to call systemd-run
Status in Ubuntu on IBM z Systems:
In Progress
Status in lvm2 package in Ubuntu:
Fix Released
Status in lvm2 source package in Xenial:
New
Status in lvm2 source package in Bionic:
New
Status in lvm2 source package in Cosmic:
New
Status in lvm2 source package in Disco:
New
Status in lvm2 source package in Eoan:
Fix Released
Bug description:
In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run
command during removal ---
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor", GOTO="lvm_end"
But /bin/systemd-run is not found, in fact systemd-run is in /usr/bin
/systemd-run.
xx:~$ cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
xx:~$ ls /bin/systemd-run
ls: cannot access '/bin/systemd-run': No such file or directory
xx:~$ ls /usr/bin/systemd-run
/usr/bin/systemd-run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1830169/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
I'm leaving this as marked against libseccomp, as I don't understand why
it is redefining kernel header values as invalid numbers in its public
header file (so that other programs using its header files pull in those
invalid syscall numbers). I don't think it should but I'll leave the
decision to discuss this upstream to someone more familiar with
libseccomp.
** Changed in: libseccomp (Ubuntu)
Status: Fix Released => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1821625
Title:
systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
seccomp)
Status in libseccomp package in Ubuntu:
Incomplete
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in libseccomp source package in Bionic:
Incomplete
Status in linux source package in Bionic:
In Progress
Status in systemd source package in Bionic:
Invalid
Bug description:
Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
failing on Bionic on ppc64el with the error messages:
Operating on architecture: ppc
Failed to add n/a() rule for architecture ppc, skipping: Bad address
Operating on architecture: ppc64
Failed to add n/a() rule for architecture ppc64, skipping: Bad address
Operating on architecture: ppc64-le
Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical
argument out of domain
Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413,
function test_memory_deny_write_execute_mmap(). Aborting.
memoryseccomp-mmap terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG)
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function
test_memory_deny_write_execute_mmap(). Aborting.
Aborted (core dumped)
FAIL: test-seccomp (code: 134)
Full logs at:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz
The testcase passed with systemd version 237-3ubuntu10.13 running on the same
4.15.0-45 kernel on ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1821625/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
autopkgtest regressions:
some kernel flavours are failing to build from source due to running out
of memory whilst compiling mellanox drivers. Requesting to add all
kernel flavours to big_packages configuration in
https://bugs.launchpad.net/auto-package-testing/+bug/1831446
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1797386
Title:
[SRU] OpenSSL 1.1.1 to 18.04 LTS
Status in libwww-perl package in Ubuntu:
Fix Released
Status in openssl package in Ubuntu:
Fix Released
Status in python-tornado package in Ubuntu:
In Progress
Status in libio-socket-ssl-perl source package in Bionic:
Fix Committed
Status in libnet-ssleay-perl source package in Bionic:
Fix Committed
Status in libwww-perl source package in Bionic:
Fix Committed
Status in openssl source package in Bionic:
Fix Committed
Status in python-cryptography source package in Bionic:
Fix Committed
Status in python2.7 source package in Bionic:
Fix Committed
Status in python3.6 source package in Bionic:
Fix Committed
Status in python3.7 source package in Bionic:
Fix Committed
Status in r-cran-openssl source package in Bionic:
Fix Committed
Status in ruby-openssl source package in Bionic:
Fix Committed
Status in ruby2.5 source package in Bionic:
Fix Committed
Bug description:
[Impact]
* OpenSSL 1.1.1 is an LTS release upstream, which will continue to
receive security support for much longer than 1.1.0 series will.
* OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
be rapidly adopted due to increased set of supported hashes & algoes,
as well as improved handshake [re-]negotiation.
* OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.
* OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some
software is sensitive to the negotiation handshake and may either need
patches/improvements or clamp-down to maximum v1.2.
[Test Case]
* Rebuild all reverse dependencies
* Execute autopkg tests for all of them
* Clamp down to TLS v1.2 software that does not support TLS v1.3
(e.g. mongodb)
* Backport TLS v1.3 support patches, where applicable
[Test cases for the python updates]
python3.7 is a preview in bionic as a non-supported/non-default
version of python3. Passing it's own autopkgtests is sufficient
validation for python3.7. It includes a point release update, with
OpenSSL 1.1.1 compat and features.
python3.6 not only has OpenSSL 1.1.1 compat and features patches, but
also includes a point release update to 3.6.8. It has been part of the
full-archive rebuild and regression analysis. Autopkgtests were
triggered for python3.6 and python3-defaults with regressions already
fixed in the individual packages as appropriate.
python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1
compat only. It has been part of the full-archive rebuild and
regression analysis. Autopkgtests were triggered for python2.7 and
python-defaults with regressions already fixed in the individual
packages as appropriate.
The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1
and python point releases as seen in:
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html
And analyzed in
https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652
[ Test case libwww-perl (and deps) regression ]
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034
1. apt install liblwp-protocol-https-perl
2. enable -proposed
3. apt install libio-socket-ssl-perl libnet-ssleay-perl
4. perl -MLWP::UserAgent -e
'LWP::UserAgent->new->post("https://facebook.com;, { data => "foo" }) or die'
[Regression Potential]
* Connectivity interop is the biggest issues which will be
unavoidable with introducing TLS v1.3. However, tests on cosmic
demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and
negotiate TLS v1.3 without issues.
* Mitigation of discovered connectivity issues will be possible by
clamping down to TLS v1.2 in either server-side or client-side
software or by backporting relevant support fixes
* Notable changes are listed here
https://wiki.openssl.org/index.php/TLS1.3
* Most common connectivity issues so far:
- client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname.
Solution is client change to set hostname, or to clamp down the client to
TLSv1.2.
- session negotiation is different in TLSv1.3, existing client code
may fail to create/negotiate/resume session. Clients need to learn how
to use session callback.
- non-application data records. TLSv1.3 sends more of these, when compared
with previous versions, and some applications may not handle this
[Touch-packages] [Bug 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
> After these patches are applied to bionic, both libseccomp and systemd
> will need to be rebuilt - libseccomp rebuilt against the kernel
> headers, and systemd against the libseccomp headers.
technically both will need to be rebuilt against the new kernel headers,
but systemd doesn't need to wait for libseccomp to be rebuilt, as it
should get the correct value as soon as the kernel headers are updated,
since the libseccomp header file only defines __NR_pkey_mprotect (as an
invalid value) if the kernel header doesn't define it.
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: libseccomp (Ubuntu Bionic)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1821625
Title:
systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
seccomp)
Status in libseccomp package in Ubuntu:
Incomplete
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in libseccomp source package in Bionic:
Incomplete
Status in linux source package in Bionic:
In Progress
Status in systemd source package in Bionic:
Invalid
Bug description:
Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
failing on Bionic on ppc64el with the error messages:
Operating on architecture: ppc
Failed to add n/a() rule for architecture ppc, skipping: Bad address
Operating on architecture: ppc64
Failed to add n/a() rule for architecture ppc64, skipping: Bad address
Operating on architecture: ppc64-le
Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical
argument out of domain
Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413,
function test_memory_deny_write_execute_mmap(). Aborting.
memoryseccomp-mmap terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG)
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function
test_memory_deny_write_execute_mmap(). Aborting.
Aborted (core dumped)
FAIL: test-seccomp (code: 134)
Full logs at:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz
The testcase passed with systemd version 237-3ubuntu10.13 running on the same
4.15.0-45 kernel on ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1821625/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
coverletter explanation as sent to kernel-team list: In bionic, all archs provided by Ubuntu either define __NR_pkey_mprotect (arm/x86) or define __IGNORE_pkey_mprotect (powerpc/s390). This value was used, until libseccomp was updated via bug 1815415, to instead (if __NR_pkey_mprotect was not defined by the kernel headers) define it as a negative error value: +#define __PNR_pkey_mprotect-10201 +#ifndef __NR_pkey_mprotect +#define __NR_pkey_mprotect __PNR_pkey_mprotect +#endif /* __NR_pkey_mprotect */ systemd, the next time it was built against libseccomp, pulled that __NR_pkey_mprotect value and started using it for ppc64el, though it was a negative error value, so it would not actually work as a syscall number. This caused the systemd test-seccomp autopkgtest to start failing, as the systemd function it tested only issued the pkey_mprotect syscall if __NR_pkey_mprotect was defined.
[Touch-packages] [Bug 1830859] Re: new libseccomp 2.4 (in proposed) makes rebuilds need but not generate a dependency to 2.4
Uploaded to Disco-unapproved.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1830859
Title:
new libseccomp 2.4 (in proposed) makes rebuilds need but not generate
a dependency to 2.4
Status in libseccomp package in Ubuntu:
Won't Fix
Status in qemu package in Ubuntu:
Triaged
Bug description:
[Impact]
* Just as of yesterday we have a new libseccomp in all releases.
This brings some new code and features which might impact packages.
For qemu being one of the few that is not so much a problem in many
cases. Prior to Disco we didn't have code in qemu using the new
libseccomp bits. In Eoan we can assume that libseccomp 2.4 (being
release level) will be installed.
But in Disco people might have installed and not updated libseccomp
but install/upgrade to a qemu that was built against that new
libseccomp. Due to that qemu will get a runtime dependency that is
not picked up automatically - this would break all qemu execution
being blocked by a failure to install seccomp filters.
* To fix that we will add an explicit versioned dependency to qemu to
make sure the rebuild will ensure that the right library version is
available.
* This is needed for qemu-system* which all depend on qemu-system-
common so to avoid too much noise changing all qemu-system* packages
the dependency it added there.
[Test Case]
* ensure that the qemu install will ensure that libseccomp2 (>= 2.4.1)
is also installed (not staying on 2.3)
* Then install qemu and run
$ qemu-system-x86_64 -enable-kvm -nographic -nodefaults -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny
which should not trigger this (when fixed)
error: internal error: process exited while connecting to monitor:
2019-05-28T17:10:17.121934Z qemu-system-x86_64: -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny: failed
to install seccomp syscall filter in the kernel
[Regression Potential]
* Well, the regressions might be triggered by pushing the new
libseccomp, not by this dependency fixup. The security Team has
checked and this seems to be the only affected code in the archive.
So libseccomp was pushed to fix CVEs. I have thought if it is a
regression that users of qemu will now be forced to use the newer
libseccomp, but since it would be unusable without that is no
important argument. And it is strongly recommended to upgrade for
security reasons as well.
[Other Info]
* n/a
---
It started with some of my usual KVM checks and found them failing on Disco
with:
error: internal error: process exited while connecting to monitor:
2019-05-28T17:10:17.121934Z qemu-system-x86_64: -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny: failed
to install seccomp syscall filter in the kernel
I realized it works on X/B/C/E but not in a D container
It worked ~4 weeks ago.
This test can be simplified to one command:
$ qemu-system-x86_64 -enable-kvm -nographic -nodefaults -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny
With strace I found different behavior:
Good:
[pid 3487] 0.00 seccomp(SECCOMP_SET_MODE_FILTER,
SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.11>
[pid 3487] 0.003136 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1
EINVAL (Invalid argument) <0.44>
[pid 3487] 0.000250 seccomp(SECCOMP_SET_MODE_FILTER,
SECCOMP_FILTER_FLAG_TSYNC, {len=68, filter=0x55f2b7a5e2d0}) = 0 <0.000251>
Bad:
[pid 484] 0.00 seccomp(SECCOMP_SET_MODE_FILTER,
SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.17>
[pid 484] 0.002680 seccomp(SECCOMP_GET_ACTION_AVAIL, 0,
[SECCOMP_RET_KILL_PROCESS]) = 0 <0.14>
[pid 484] 0.88 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1
EINVAL (Invalid argument) <0.13>
The difference seems to come from being built against seccomp as in
Disco (2.3.3-3ubuntu2 = good) or Disco-proposed ( = bad).
The dependency on the built package stayed
libseccomp2 (>= 2.3.0)
It did not pick up 2.4 via e.g. shlibs.
If I install libseccomp2 2.4 from -proposed the issue is gone.
Strace now looks like:
[pid 1788] 0.00 seccomp(SECCOMP_SET_MODE_FILTER,
SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.15>
[pid 1788] 0.004167 seccomp(SECCOMP_GET_ACTION_AVAIL, 0,
[SECCOMP_RET_KILL_PROCESS]) = 0 <0.13>
[pid 1788] 0.98 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1
EINVAL (Invalid argument) <0.13>
[pid 1788] 0.54 seccomp(SECCOMP_SET_MODE_FILTER,
SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.22>
[pid 1788]
[Touch-packages] [Bug 1830859] Re: new libseccomp 2.4 (in proposed) makes rebuilds need but not generate a dependency to 2.4
Checked on the PPA:
root@d-wily:~# apt install libseccomp2=2.3.3-3ubuntu2
Reading package lists... Done
Building dependency tree
Reading state information... Done
[...]
The following packages will be REMOVED:
qemu-kvm qemu-system-x86
The following packages will be DOWNGRADED:
libseccomp2
0 upgraded, 0 newly installed, 1 downgraded, 2 to remove and 0 not upgraded.
... and similar.
So the dependency works and makes sure a recent libseccomp2 will have to go
along and by that prevent the error.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1830859
Title:
new libseccomp 2.4 (in proposed) makes rebuilds need but not generate
a dependency to 2.4
Status in libseccomp package in Ubuntu:
Won't Fix
Status in qemu package in Ubuntu:
Triaged
Bug description:
[Impact]
* Just as of yesterday we have a new libseccomp in all releases.
This brings some new code and features which might impact packages.
For qemu being one of the few that is not so much a problem in many
cases. Prior to Disco we didn't have code in qemu using the new
libseccomp bits. In Eoan we can assume that libseccomp 2.4 (being
release level) will be installed.
But in Disco people might have installed and not updated libseccomp
but install/upgrade to a qemu that was built against that new
libseccomp. Due to that qemu will get a runtime dependency that is
not picked up automatically - this would break all qemu execution
being blocked by a failure to install seccomp filters.
* To fix that we will add an explicit versioned dependency to qemu to
make sure the rebuild will ensure that the right library version is
available.
* This is needed for qemu-system* which all depend on qemu-system-
common so to avoid too much noise changing all qemu-system* packages
the dependency it added there.
[Test Case]
* ensure that the qemu install will ensure that libseccomp2 (>= 2.4.1)
is also installed (not staying on 2.3)
* Then install qemu and run
$ qemu-system-x86_64 -enable-kvm -nographic -nodefaults -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny
which should not trigger this (when fixed)
error: internal error: process exited while connecting to monitor:
2019-05-28T17:10:17.121934Z qemu-system-x86_64: -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny: failed
to install seccomp syscall filter in the kernel
[Regression Potential]
* Well, the regressions might be triggered by pushing the new
libseccomp, not by this dependency fixup. The security Team has
checked and this seems to be the only affected code in the archive.
So libseccomp was pushed to fix CVEs. I have thought if it is a
regression that users of qemu will now be forced to use the newer
libseccomp, but since it would be unusable without that is no
important argument. And it is strongly recommended to upgrade for
security reasons as well.
[Other Info]
* n/a
---
It started with some of my usual KVM checks and found them failing on Disco
with:
error: internal error: process exited while connecting to monitor:
2019-05-28T17:10:17.121934Z qemu-system-x86_64: -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny: failed
to install seccomp syscall filter in the kernel
I realized it works on X/B/C/E but not in a D container
It worked ~4 weeks ago.
This test can be simplified to one command:
$ qemu-system-x86_64 -enable-kvm -nographic -nodefaults -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny
With strace I found different behavior:
Good:
[pid 3487] 0.00 seccomp(SECCOMP_SET_MODE_FILTER,
SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.11>
[pid 3487] 0.003136 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1
EINVAL (Invalid argument) <0.44>
[pid 3487] 0.000250 seccomp(SECCOMP_SET_MODE_FILTER,
SECCOMP_FILTER_FLAG_TSYNC, {len=68, filter=0x55f2b7a5e2d0}) = 0 <0.000251>
Bad:
[pid 484] 0.00 seccomp(SECCOMP_SET_MODE_FILTER,
SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.17>
[pid 484] 0.002680 seccomp(SECCOMP_GET_ACTION_AVAIL, 0,
[SECCOMP_RET_KILL_PROCESS]) = 0 <0.14>
[pid 484] 0.88 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1
EINVAL (Invalid argument) <0.13>
The difference seems to come from being built against seccomp as in
Disco (2.3.3-3ubuntu2 = good) or Disco-proposed ( = bad).
The dependency on the built package stayed
libseccomp2 (>= 2.3.0)
It did not pick up 2.4 via e.g. shlibs.
If I install libseccomp2 2.4 from -proposed the issue is gone.
Strace now looks like:
[pid 1788]
[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
autopkgtest regressions:
libgeo-coder-googlev3-perl request to badtest + sru to unbreak autopkgtests
https://bugs.launchpad.net/ubuntu/+source/libgeo-coder-googlev3-perl/+bug/1831443
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1797386
Title:
[SRU] OpenSSL 1.1.1 to 18.04 LTS
Status in libwww-perl package in Ubuntu:
Fix Released
Status in openssl package in Ubuntu:
Fix Released
Status in python-tornado package in Ubuntu:
In Progress
Status in libio-socket-ssl-perl source package in Bionic:
Fix Committed
Status in libnet-ssleay-perl source package in Bionic:
Fix Committed
Status in libwww-perl source package in Bionic:
Fix Committed
Status in openssl source package in Bionic:
Fix Committed
Status in python-cryptography source package in Bionic:
Fix Committed
Status in python2.7 source package in Bionic:
Fix Committed
Status in python3.6 source package in Bionic:
Fix Committed
Status in python3.7 source package in Bionic:
Fix Committed
Status in r-cran-openssl source package in Bionic:
Fix Committed
Status in ruby-openssl source package in Bionic:
Fix Committed
Status in ruby2.5 source package in Bionic:
Fix Committed
Bug description:
[Impact]
* OpenSSL 1.1.1 is an LTS release upstream, which will continue to
receive security support for much longer than 1.1.0 series will.
* OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
be rapidly adopted due to increased set of supported hashes & algoes,
as well as improved handshake [re-]negotiation.
* OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.
* OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some
software is sensitive to the negotiation handshake and may either need
patches/improvements or clamp-down to maximum v1.2.
[Test Case]
* Rebuild all reverse dependencies
* Execute autopkg tests for all of them
* Clamp down to TLS v1.2 software that does not support TLS v1.3
(e.g. mongodb)
* Backport TLS v1.3 support patches, where applicable
[Test cases for the python updates]
python3.7 is a preview in bionic as a non-supported/non-default
version of python3. Passing it's own autopkgtests is sufficient
validation for python3.7. It includes a point release update, with
OpenSSL 1.1.1 compat and features.
python3.6 not only has OpenSSL 1.1.1 compat and features patches, but
also includes a point release update to 3.6.8. It has been part of the
full-archive rebuild and regression analysis. Autopkgtests were
triggered for python3.6 and python3-defaults with regressions already
fixed in the individual packages as appropriate.
python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1
compat only. It has been part of the full-archive rebuild and
regression analysis. Autopkgtests were triggered for python2.7 and
python-defaults with regressions already fixed in the individual
packages as appropriate.
The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1
and python point releases as seen in:
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html
And analyzed in
https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652
[ Test case libwww-perl (and deps) regression ]
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034
1. apt install liblwp-protocol-https-perl
2. enable -proposed
3. apt install libio-socket-ssl-perl libnet-ssleay-perl
4. perl -MLWP::UserAgent -e
'LWP::UserAgent->new->post("https://facebook.com;, { data => "foo" }) or die'
[Regression Potential]
* Connectivity interop is the biggest issues which will be
unavoidable with introducing TLS v1.3. However, tests on cosmic
demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and
negotiate TLS v1.3 without issues.
* Mitigation of discovered connectivity issues will be possible by
clamping down to TLS v1.2 in either server-side or client-side
software or by backporting relevant support fixes
* Notable changes are listed here
https://wiki.openssl.org/index.php/TLS1.3
* Most common connectivity issues so far:
- client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname.
Solution is client change to set hostname, or to clamp down the client to
TLSv1.2.
- session negotiation is different in TLSv1.3, existing client code
may fail to create/negotiate/resume session. Clients need to learn how
to use session callback.
- non-application data records. TLSv1.3 sends more of these, when compared
with previous versions, and some applications may not handle this correctly.
Resulting in application data not being available, when previously expected.
[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
RE: perl openssl read/write|_all changes
OpenSSL 1.1.1 has enabled AUTO_RETRY by default and all non-application
data records are retried by default. Thus this is effectively a no-
change for higher level users as retries have moved further down the
stack to libssl itself.
Upstream executes testmatrix across a wide array of openssl
implementations, and perl releases, thus there is a degree of confidence
in shipping upstream preferred change of api.
As a contingency, reverting the api changes and limiting context to cap
at tls1.2 will be our path forward if we need to revert this upload.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1797386
Title:
[SRU] OpenSSL 1.1.1 to 18.04 LTS
Status in libwww-perl package in Ubuntu:
Fix Released
Status in openssl package in Ubuntu:
Fix Released
Status in python-tornado package in Ubuntu:
In Progress
Status in libio-socket-ssl-perl source package in Bionic:
Fix Committed
Status in libnet-ssleay-perl source package in Bionic:
Fix Committed
Status in libwww-perl source package in Bionic:
Fix Committed
Status in openssl source package in Bionic:
Fix Committed
Status in python-cryptography source package in Bionic:
Fix Committed
Status in python2.7 source package in Bionic:
Fix Committed
Status in python3.6 source package in Bionic:
Fix Committed
Status in python3.7 source package in Bionic:
Fix Committed
Status in r-cran-openssl source package in Bionic:
Fix Committed
Status in ruby-openssl source package in Bionic:
Fix Committed
Status in ruby2.5 source package in Bionic:
Fix Committed
Bug description:
[Impact]
* OpenSSL 1.1.1 is an LTS release upstream, which will continue to
receive security support for much longer than 1.1.0 series will.
* OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
be rapidly adopted due to increased set of supported hashes & algoes,
as well as improved handshake [re-]negotiation.
* OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.
* OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some
software is sensitive to the negotiation handshake and may either need
patches/improvements or clamp-down to maximum v1.2.
[Test Case]
* Rebuild all reverse dependencies
* Execute autopkg tests for all of them
* Clamp down to TLS v1.2 software that does not support TLS v1.3
(e.g. mongodb)
* Backport TLS v1.3 support patches, where applicable
[Test cases for the python updates]
python3.7 is a preview in bionic as a non-supported/non-default
version of python3. Passing it's own autopkgtests is sufficient
validation for python3.7. It includes a point release update, with
OpenSSL 1.1.1 compat and features.
python3.6 not only has OpenSSL 1.1.1 compat and features patches, but
also includes a point release update to 3.6.8. It has been part of the
full-archive rebuild and regression analysis. Autopkgtests were
triggered for python3.6 and python3-defaults with regressions already
fixed in the individual packages as appropriate.
python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1
compat only. It has been part of the full-archive rebuild and
regression analysis. Autopkgtests were triggered for python2.7 and
python-defaults with regressions already fixed in the individual
packages as appropriate.
The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1
and python point releases as seen in:
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html
And analyzed in
https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652
[ Test case libwww-perl (and deps) regression ]
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034
1. apt install liblwp-protocol-https-perl
2. enable -proposed
3. apt install libio-socket-ssl-perl libnet-ssleay-perl
4. perl -MLWP::UserAgent -e
'LWP::UserAgent->new->post("https://facebook.com;, { data => "foo" }) or die'
[Regression Potential]
* Connectivity interop is the biggest issues which will be
unavoidable with introducing TLS v1.3. However, tests on cosmic
demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and
negotiate TLS v1.3 without issues.
* Mitigation of discovered connectivity issues will be possible by
clamping down to TLS v1.2 in either server-side or client-side
software or by backporting relevant support fixes
* Notable changes are listed here
https://wiki.openssl.org/index.php/TLS1.3
* Most common connectivity issues so far:
- client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname.
Solution is client change to set hostname, or to clamp down the client to
TLSv1.2.
-
[Touch-packages] [Bug 1821863] Re: Need to add Intel CML related pci-id's
@Timo, tried to upgrade to xorg-server into bionic-proposed and confirmed it fixes a laggy desktop issue found in some OEM CML platforms running on bionic image. ** 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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Committed Status in libdrm source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in mesa source package in Disco: Fix Released Status in xorg-server source package in Disco: Fix Released Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830859] Re: new libseccomp 2.4 (in proposed) makes rebuilds need but not generate a dependency to 2.4
Tested on the PPA, working as expected (after moved to qemu-system-*packacges)
The reason to no more use qemu-system-common is that this only was a recommends
which would not enforce the update.
Even qemu-system-data which is a depends would be wrong as people could install
that without the actual binaries and they would not need the new libseccomp.
Lets take the bitter pill and add them exactly where needed.
I analyzed binaries - qemu-user and others don't need it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1830859
Title:
new libseccomp 2.4 (in proposed) makes rebuilds need but not generate
a dependency to 2.4
Status in libseccomp package in Ubuntu:
Won't Fix
Status in qemu package in Ubuntu:
Triaged
Bug description:
[Impact]
* Just as of yesterday we have a new libseccomp in all releases.
This brings some new code and features which might impact packages.
For qemu being one of the few that is not so much a problem in many
cases. Prior to Disco we didn't have code in qemu using the new
libseccomp bits. In Eoan we can assume that libseccomp 2.4 (being
release level) will be installed.
But in Disco people might have installed and not updated libseccomp
but install/upgrade to a qemu that was built against that new
libseccomp. Due to that qemu will get a runtime dependency that is
not picked up automatically - this would break all qemu execution
being blocked by a failure to install seccomp filters.
* To fix that we will add an explicit versioned dependency to qemu to
make sure the rebuild will ensure that the right library version is
available.
* This is needed for qemu-system* which all depend on qemu-system-
common so to avoid too much noise changing all qemu-system* packages
the dependency it added there.
[Test Case]
* ensure that the qemu install will ensure that libseccomp2 (>= 2.4.1)
is also installed (not staying on 2.3)
* Then install qemu and run
$ qemu-system-x86_64 -enable-kvm -nographic -nodefaults -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny
which should not trigger this (when fixed)
error: internal error: process exited while connecting to monitor:
2019-05-28T17:10:17.121934Z qemu-system-x86_64: -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny: failed
to install seccomp syscall filter in the kernel
[Regression Potential]
* Well, the regressions might be triggered by pushing the new
libseccomp, not by this dependency fixup. The security Team has
checked and this seems to be the only affected code in the archive.
So libseccomp was pushed to fix CVEs. I have thought if it is a
regression that users of qemu will now be forced to use the newer
libseccomp, but since it would be unusable without that is no
important argument. And it is strongly recommended to upgrade for
security reasons as well.
[Other Info]
* n/a
---
It started with some of my usual KVM checks and found them failing on Disco
with:
error: internal error: process exited while connecting to monitor:
2019-05-28T17:10:17.121934Z qemu-system-x86_64: -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny: failed
to install seccomp syscall filter in the kernel
I realized it works on X/B/C/E but not in a D container
It worked ~4 weeks ago.
This test can be simplified to one command:
$ qemu-system-x86_64 -enable-kvm -nographic -nodefaults -sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny
With strace I found different behavior:
Good:
[pid 3487] 0.00 seccomp(SECCOMP_SET_MODE_FILTER,
SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.11>
[pid 3487] 0.003136 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1
EINVAL (Invalid argument) <0.44>
[pid 3487] 0.000250 seccomp(SECCOMP_SET_MODE_FILTER,
SECCOMP_FILTER_FLAG_TSYNC, {len=68, filter=0x55f2b7a5e2d0}) = 0 <0.000251>
Bad:
[pid 484] 0.00 seccomp(SECCOMP_SET_MODE_FILTER,
SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.17>
[pid 484] 0.002680 seccomp(SECCOMP_GET_ACTION_AVAIL, 0,
[SECCOMP_RET_KILL_PROCESS]) = 0 <0.14>
[pid 484] 0.88 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1
EINVAL (Invalid argument) <0.13>
The difference seems to come from being built against seccomp as in
Disco (2.3.3-3ubuntu2 = good) or Disco-proposed ( = bad).
The dependency on the built package stayed
libseccomp2 (>= 2.3.0)
It did not pick up 2.4 via e.g. shlibs.
If I install libseccomp2 2.4 from -proposed the issue is gone.
Strace now looks like:
[pid 1788] 0.00 seccomp(SECCOMP_SET_MODE_FILTER,
[Touch-packages] [Bug 1805543] Re: Packaged version of iptables doesn't provide --random-fully flag.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: iptables (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1805543 Title: Packaged version of iptables doesn't provide --random-fully flag. Status in iptables package in Ubuntu: Confirmed Bug description: Hello. This isn't strictly a bug, but more of an upgrade-request on the iptables package. Normally i wouldn't be inclined to submit such a bug report, but a user on the ubuntu-devel-discuss mailing list encouraged me to submit this anyway [1]. For our production systems, we're running into a kernel race condition bug, for which a workaround has been made available. The fix boils down to iptables having a new flag which it passes down to the kernel, to enable the workaround. However, the version of iptables in Ubuntu (v1.6.1) doesn't support that kernel feature yet. Specifically, it's introduced in this commit on the iptables codebase: https://git.netfilter.org/iptables/commit/?id=8b0da2130b8af3890ef20afb2305f11224bb39ec. The feature we need from that commit is part of the v1.6.2 and newer iptables releases, but it looks like the Bionic, Cosmic, and Disco releases of Ubuntu all include v1.6.1 without that patch, so for now we're going to have to build iptables from source on our production machines. That shouldn't pose any huge issues, but of course, we'd prefer to be able to use the package from package management, or perhaps a backported package from a newer Ubuntu release. So to summarise, this might be an invalid bug report, but consider it a vote to upgrade the packaged version of iptables. If this bug report is entirely inappropriate, then I apologise. 1. Link to thread on ubuntu-devel-discuss where I describe the problem and Nish suggests I file this bug report: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2018-November/018181.html Ubuntu version we're using: Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy iptables iptables: Installed: 1.6.1-2ubuntu2 Candidate: 1.6.1-2ubuntu2 Version table: *** 1.6.1-2ubuntu2 500 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Thanks for your time, Paul To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1805543/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822984] Re: revert tls security level back to 1
This bug was fixed in the package openssl - 1.1.1-1ubuntu2.2 --- openssl (1.1.1-1ubuntu2.2) cosmic; urgency=medium * debian/rules: Ship openssl.cnf in libssl1.1-udeb, as required to use OpenSSL by other udebs, e.g. wget-udeb. LP: #1822898 * Drop debian/patches/UBUNTU-lower-tls-security-level-for-compat.patch to revert TLS_SECURITY_LEVEL back to 1. LP: #1822984 -- Dimitri John Ledkov Wed, 03 Apr 2019 20:37:01 +0100 ** Changed in: openssl (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1822984 Title: revert tls security level back to 1 Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Cosmic: Fix Released Status in openssl source package in Disco: Fix Released Bug description: [Impact] * increase minimum default tls security level from 0 to 1, as is the default upstream [Test Case] * generate 80bits TLS certificate and attempt to use it * with prior openssl it should work, but with this update it should fail [Regression Potential] * This increases the minimum required certificate/keys sizes and algorithms, back to what Bionic GA openssl 1.1.0 shipped as. It also now will match upstream default. It is still lower than Debian's default that raises it to 2 by default. * Cosmic GA shipped with TLS_SECURITY_LEVEL 0, meaning pretty much any weak keys were accepted. With this change keys lower than 112 will be rejected, which are considered to be too weak to be useful by most CAs out there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822898] Re: wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i
This bug was fixed in the package openssl - 1.1.1-1ubuntu2.2 --- openssl (1.1.1-1ubuntu2.2) cosmic; urgency=medium * debian/rules: Ship openssl.cnf in libssl1.1-udeb, as required to use OpenSSL by other udebs, e.g. wget-udeb. LP: #1822898 * Drop debian/patches/UBUNTU-lower-tls-security-level-for-compat.patch to revert TLS_SECURITY_LEVEL back to 1. LP: #1822984 -- Dimitri John Ledkov Wed, 03 Apr 2019 20:37:01 +0100 ** Changed in: openssl (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1822898 Title: wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Cosmic: Fix Released Status in openssl source package in Disco: Fix Released Status in openssl package in Debian: Fix Released Bug description: [Impact] * fetch-url cannot use https protocol (no https preseeds) [Test case] * in d-i, mini.iso, tty try wget https://geoip.ubuntu.com/lookup it should succeed. [Solution] The required openssl.cnf configuration file is missing, needs to simply exists, even if it is empty. [Regression Potential] well, if one cannot download over https / init ssl library in d-i, it's hard to get openssl busted more than that. No code changes on the .deb side of things To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822898] Update Released
The verification of the Stable Release Update for openssl has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1822898 Title: wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Cosmic: Fix Released Status in openssl source package in Disco: Fix Released Status in openssl package in Debian: Fix Released Bug description: [Impact] * fetch-url cannot use https protocol (no https preseeds) [Test case] * in d-i, mini.iso, tty try wget https://geoip.ubuntu.com/lookup it should succeed. [Solution] The required openssl.cnf configuration file is missing, needs to simply exists, even if it is empty. [Regression Potential] well, if one cannot download over https / init ssl library in d-i, it's hard to get openssl busted more than that. No code changes on the .deb side of things To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822984] Update Released
The verification of the Stable Release Update for openssl has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1822984 Title: revert tls security level back to 1 Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Cosmic: Fix Released Status in openssl source package in Disco: Fix Released Bug description: [Impact] * increase minimum default tls security level from 0 to 1, as is the default upstream [Test Case] * generate 80bits TLS certificate and attempt to use it * with prior openssl it should work, but with this update it should fail [Regression Potential] * This increases the minimum required certificate/keys sizes and algorithms, back to what Bionic GA openssl 1.1.0 shipped as. It also now will match upstream default. It is still lower than Debian's default that raises it to 2 by default. * Cosmic GA shipped with TLS_SECURITY_LEVEL 0, meaning pretty much any weak keys were accepted. With this change keys lower than 112 will be rejected, which are considered to be too weak to be useful by most CAs out there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1822984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831423] Re: Bogus warning message in Net::Ping in Bionic
The attachment "Fix to remove bogus socket version warning in Ping.pm"
seems to be a patch. If it isn't, please remove the "patch" flag from
the attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1831423
Title:
Bogus warning message in Net::Ping in Bionic
Status in perl package in Ubuntu:
New
Bug description:
In Ubuntu Bionic's Ping.pm a test of the used socket's version is done
numerically although the Socket.pm's version contains a special
character ("_") which causes this warning message:
Argument "2.020_03" isn't numeric in numeric ge (>=) at
/usr/share/perl/5.26/Net/Ping.pm line 1801, line 755.
Since Socket.pm is part of the same package, the test is not really useful
anymore. I suggest removing it quick'n dirty via the attached patch to get rid
of the warning while conserving the "old way".
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1831423/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821863] Re: Need to add Intel CML related pci-id's
Hello Chih-Hsyuan, or anyone else affected, Accepted xorg-server into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.19.6-1ubuntu4.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance 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: xorg-server (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed verification-needed-bionic ** Changed in: mesa (Ubuntu Bionic) Status: New => Fix Committed -- 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/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Committed Status in libdrm source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in mesa source package in Disco: Fix Released Status in xorg-server source package in Disco: Fix Released Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831423] [NEW] Bogus warning message in Net::Ping in Bionic
Public bug reported:
In Ubuntu Bionic's Ping.pm a test of the used socket's version is done
numerically although the Socket.pm's version contains a special
character ("_") which causes this warning message:
Argument "2.020_03" isn't numeric in numeric ge (>=) at
/usr/share/perl/5.26/Net/Ping.pm line 1801, line 755.
Since Socket.pm is part of the same package, the test is not really useful
anymore. I suggest removing it quick'n dirty via the attached patch to get rid
of the warning while conserving the "old way".
** Affects: perl (Ubuntu)
Importance: Undecided
Status: New
** Tags: bionic
** Patch added: "Fix to remove bogus socket version warning in Ping.pm"
https://bugs.launchpad.net/bugs/1831423/+attachment/5268480/+files/ping-warning-fix.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1831423
Title:
Bogus warning message in Net::Ping in Bionic
Status in perl package in Ubuntu:
New
Bug description:
In Ubuntu Bionic's Ping.pm a test of the used socket's version is done
numerically although the Socket.pm's version contains a special
character ("_") which causes this warning message:
Argument "2.020_03" isn't numeric in numeric ge (>=) at
/usr/share/perl/5.26/Net/Ping.pm line 1801, line 755.
Since Socket.pm is part of the same package, the test is not really useful
anymore. I suggest removing it quick'n dirty via the attached patch to get rid
of the warning while conserving the "old way".
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1831423/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831299] Re: i cant install driver
What hardware do you want to install a driver for? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1831299 Title: i cant install driver Status in Ubuntu: Incomplete Bug description: idk more about this bug , but can you fix it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 1 06:10:43 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0724] InstallationDate: Installed on 2019-05-30 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Acer Aspire V5-431 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=c6efd4c5-770f-43f5-babc-e1f4d6123bf6 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V1.05. dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire V5-431 dmi.board.vendor: Acer dmi.board.version: V1.05. dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05. dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV1.05.:bd04/18/2012:svnAcer:pnAspireV5-431:pvrV1.05.:rvnAcer:rnAspireV5-431:rvrV1.05.:cvnAcer:ct9:cvrV1.05.: dmi.product.family: ChiefRiver System dmi.product.name: Aspire V5-431 dmi.product.sku: System SKUNumber dmi.product.version: V1.05. dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.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/+bug/1831299/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831339] Re: Backup Unbuntu ERROR undefined
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Backup Unbuntu ERROR undefined + duplicity crashed in with_tempdir ** Package changed: ubuntu => duplicity (Ubuntu) ** Changed in: duplicity (Ubuntu) Status: Incomplete => New -- 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/1831339 Title: duplicity crashed in with_tempdir Status in duplicity package in Ubuntu: New Bug description: Backup Unbuntu ERROR undefined ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sat Jun 1 14:59:04 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335] InstallationDate: Installed on 2019-03-27 (66 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406 dmi.board.name: P5N-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.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 xserver.bootTime: Wed Apr 24 21:29:22 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1831339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831347] Re: Xorg freeze - update
Could you please describe the problem in a single sentence so we can give this bug a more appropriate title and assign it to the correct package? ** Tags added: nvidia ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1831347 Title: Xorg freeze - update Status in Ubuntu: Incomplete Bug description: Dear Ubuntu, Thank you for taking the time to read this report. My last report stated that nvidia-430 driver was the problem. I have since reinstalled ubuntu 18.4 and carefully followed the EGPU setup provided online using gswitch. I should note that last install I forgot to add "systemctl enable gswitch". I have noticed far fewer issues. Interestingly, I also enabled autologin for my account. This appears to have helped the problem significantly. I did try switching to regular password required at login and the freezing / hanging did occur during some web browsing but it was only for about 5 - 10 seconds. I then immediately switched back to autologins and I have not noticed any freezing or hanging! I believe the problem with regular password req logins is that it causes my internal display (laptop screen) to be enabled first during the login when I enter my password. After I enter my password the internal display turns off and then I use my external display only as I have that confiured in the ubuntu device settings. But with autologin, the computer boots momentarily to internal screen when you see the ubuntu dots sliding to the right and then into gnome. So it appears using autologin is more stable when using an EGPU with external display only! I am using nvidia-430 drivers. So I think gdm3 needs an update or X11 needs an update so that it can honor the external display better? Anyways! I will keep you posted. Thanks for your dedication guys!! Take care, Peter ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:07:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 430.14 Wed May 8 01:10:53 UTC 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 1 16:26:04 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 418.67, 4.18.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6696] InstallationDate: Installed on 2019-06-01 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 15 9570 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=96ec9aa4-d13a-4223-b15b-4284df054c79 ro quiet splash nouveau.modeset=0 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A
[Touch-packages] [Bug 1831218] Re: xorg
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1831218 Title: xorg Status in Ubuntu: Incomplete Bug description: ubuntu 16.04 GF106GL $ sudo ubuntu-drivers autoinstall nvidia-384 $ sudo ubuntu-bug xorg Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.130 Wed Mar 21 03:37:26 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri May 31 12:33:50 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-50-generic, x86_64: installed nvidia-384, 384.130, 4.15.0-50-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF106GL [Quadro 2000] [10de:0dd8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF106GL [Quadro 2000] [10de:084a] InstallationDate: Installed on 2019-05-24 (6 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=ru TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=010c1118-5303-4b15-9fc0-a5cb2c806fb5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z270-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ270-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri May 31
