[Touch-packages] [Bug 2044664] Re: HDMI plugin after boot, but display can't work
Hi Sam, Canonical will take a look at this issue and get back to you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/2044664 Title: HDMI plugin after boot, but display can't work Status in webbrowser-app package in Ubuntu: New Bug description: [Summary] HDMI plugin but display can't work after boot under HDMI only display [Reproduce] 1. Set display configuration as single HDMI only 2. Boot into the system without plugging HDMI cable 3. Ensure system is booted (check it by debug console), then plug HDMI cable 4. Check the image on HDMI monitor [Expected result] Ubuntu desktop should be shown on HDMI monitor [Actual result] Ubuntu desktop was not shown on HDMI monitor [Fail Rate] 100% [Additional information] Platform: Mediatek Genio1200 EVK Ubuntu Version: 22.04.2 LTS Image: baoshan-classic-desktop-2204-x01-20231005-133.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/2044664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2044664] Re: HDMI plugin after boot, but display can't work
Hi Sam, Could you update the kernel to the latest version[1] and then try it again? Thanks~ --- [1] linux-mtk (5.15.0-1033.38), https://launchpad.net/ubuntu/+source/linux-mtk -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/2044664 Title: HDMI plugin after boot, but display can't work Status in webbrowser-app package in Ubuntu: New Bug description: [Summary] HDMI plugin but display can't work after boot under HDMI only display [Reproduce] 1. Set display configuration as single HDMI only 2. Boot into the system without plugging HDMI cable 3. Ensure system is booted (check it by debug console), then plug HDMI cable 4. Check the image on HDMI monitor [Expected result] Ubuntu desktop should be shown on HDMI monitor [Actual result] Ubuntu desktop was not shown on HDMI monitor [Fail Rate] 100% [Additional information] Platform: Mediatek Genio1200 EVK Ubuntu Version: 22.04.2 LTS Image: baoshan-classic-desktop-2204-x01-20231005-133.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/2044664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038512] Re: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image
** Attachment added: "mediatek.conf" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2038512/+attachment/5708343/+files/mediatek.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2038512 Title: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image Status in initramfs-tools package in Ubuntu: New Bug description: [Impact] Peripheral probe failure for MediaTek boards 'mt8195-demo' and 'genio-1200-evk'. [Ubuntu Version] Jammy [initramfs-tools] 0.140ubuntu13.4 [Kernel version] 5.15 -> 6.2 (Generate initrd.img-6.2.0 on 5.15 kernel.) [Fix] I've used 'dracut' to examing the driver dependencies for boards 'mt8195-demo' and 'genio-1200-evk'. It is able to buot into console and use USB port3. Hope these drivers could help to run installer with USB disk in next daily build. Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if just simply add driver lists in '/etc/modules', '/etc/modprobe.d/mediatek.conf' or '/etc/modules- load.d/mediatek.conf'. I fixed this issue with 'dracut' and it seems this tool will include more common framework drivers into initrd.img. [MediaTek relate drivers] file: mediatek-drivers-for-mt8195-demo-bringup.txt (Not listed in probing sequence) i2c-mt65xx spi-mt65xx reset-ti-syscon mt6397 rtc-mt6397 mtk-pmic-wrap mt6315-regulator spmi-mtk-pmif mtk_scp_ipi mediatek-drm mtk-vcodec-dec mtk-vcodec-enc mtk_jpeg mtk-vcodec-common mtk-jpeg-enc-hw mtk-vpu mtk-jpeg-dec-hw mtk-cmdq-helper mtk-cmdq-helper mtk-cmdq-mailbox mtk-mdp3 phy-mtk-mipi-dsi-drv btmtk leds-mt6360 tcpci_mt6360 mt6360_charger mt6360-regulator mt6360-core mt6359-regulator mt6360-adc snd-soc-mt8195-afe snd-soc-mtk-common snd-soc-dmic dwmac-mediatek stmmac-platform stmmac mtk-rng mtk_scp mtk_rpmsg pwm-mediatek pwm-mtk-disp nvmem_mtk-efuse mtk-sd cqhci phy-mtk-tphy mtu3 xhci-mtk-hcd phy-mtk-pcie pcie-mediatek-gen3 [lsmod log] file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt [Other info] effected kernel (6.2-latest) ubuntu kernel for lunar, and Mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2038512/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905688] Re: systemd-timesyncd.service: Timed out waiting for reply from NTP server
@Marjan I set time by BIOS settings. -- 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/1905688 Title: systemd-timesyncd.service: Timed out waiting for reply from NTP server Status in systemd package in Ubuntu: New Bug description: systemd-timesyncd.service fails to correct time if the system time is later than February 7, 2036. Image: ubuntu-20.10-desktop-amd64.iso systemd: 246.6-1ubuntu1 $ timedatectl status Local time: Fri 2038-11-26 07:58:16 UTC Universal time: Fri 2038-11-26 07:58:16 UTC RTC time: Fri 2038-11-26 07:58:17 Time zone: Etc/UTC (UTC, +) System clock synchronized: no NTP service: active RTC in local TZ: no ubuntu@ubuntu:~$ sudo systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2038-11-26 07:36:55 UTC; 7min ago Docs: man:systemd-timesyncd.service(8) Main PID: 1257 (systemd-timesyn) Status: "Idle." Tasks: 2 (limit: 9283) Memory: 1.8M CGroup: /system.slice/systemd-timesyncd.service └─1257 /lib/systemd/systemd-timesyncd Nov 26 07:39:09 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com). Nov 26 07:39:19 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com). Nov 26 07:40:34 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com). Nov 26 07:40:44 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com). There is no issue with ntpdate: ubuntu@ubuntu:~$ sudo ntpdate -v ntp.ubuntu.com 26 Nov 08:16:21 ntpdate[8926]: ntpdate 4.2.8p12@1.3728-o (1) 26 Nov 08:16:30 ntpdate[8926]: step time server 91.189.91.157 offset -567993599.624839 sec ubuntu@ubuntu:~$ date Thu Nov 26 08:16:33 AM UTC 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905688] Re: systemd-timesyncd.service: Timed out waiting for reply from NTP server
** Attachment added: "ntp_systemd-timesyncd.pcapng" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905688/+attachment/5438201/+files/ntp_systemd-timesyncd.pcapng -- 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/1905688 Title: systemd-timesyncd.service: Timed out waiting for reply from NTP server Status in systemd package in Ubuntu: New Bug description: systemd-timesyncd.service fails to correct time if the system time is later than February 7, 2036. Image: ubuntu-20.10-desktop-amd64.iso systemd: 246.6-1ubuntu1 $ timedatectl status Local time: Fri 2038-11-26 07:58:16 UTC Universal time: Fri 2038-11-26 07:58:16 UTC RTC time: Fri 2038-11-26 07:58:17 Time zone: Etc/UTC (UTC, +) System clock synchronized: no NTP service: active RTC in local TZ: no ubuntu@ubuntu:~$ sudo systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2038-11-26 07:36:55 UTC; 7min ago Docs: man:systemd-timesyncd.service(8) Main PID: 1257 (systemd-timesyn) Status: "Idle." Tasks: 2 (limit: 9283) Memory: 1.8M CGroup: /system.slice/systemd-timesyncd.service └─1257 /lib/systemd/systemd-timesyncd Nov 26 07:39:09 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com). Nov 26 07:39:19 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com). Nov 26 07:40:34 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com). Nov 26 07:40:44 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com). There is no issue with ntpdate: ubuntu@ubuntu:~$ sudo ntpdate -v ntp.ubuntu.com 26 Nov 08:16:21 ntpdate[8926]: ntpdate 4.2.8p12@1.3728-o (1) 26 Nov 08:16:30 ntpdate[8926]: step time server 91.189.91.157 offset -567993599.624839 sec ubuntu@ubuntu:~$ date Thu Nov 26 08:16:33 AM UTC 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905688] Re: systemd-timesyncd.service: Timed out waiting for reply from NTP server
Based on the wireshark log in comment#1, system received the package from NTP server. But, the log showed "Timed out waiting for reply from NTP server" -- 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/1905688 Title: systemd-timesyncd.service: Timed out waiting for reply from NTP server Status in systemd package in Ubuntu: New Bug description: systemd-timesyncd.service fails to correct time if the system time is later than February 7, 2036. Image: ubuntu-20.10-desktop-amd64.iso systemd: 246.6-1ubuntu1 $ timedatectl status Local time: Fri 2038-11-26 07:58:16 UTC Universal time: Fri 2038-11-26 07:58:16 UTC RTC time: Fri 2038-11-26 07:58:17 Time zone: Etc/UTC (UTC, +) System clock synchronized: no NTP service: active RTC in local TZ: no ubuntu@ubuntu:~$ sudo systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2038-11-26 07:36:55 UTC; 7min ago Docs: man:systemd-timesyncd.service(8) Main PID: 1257 (systemd-timesyn) Status: "Idle." Tasks: 2 (limit: 9283) Memory: 1.8M CGroup: /system.slice/systemd-timesyncd.service └─1257 /lib/systemd/systemd-timesyncd Nov 26 07:39:09 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com). Nov 26 07:39:19 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com). Nov 26 07:40:34 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com). Nov 26 07:40:44 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com). There is no issue with ntpdate: ubuntu@ubuntu:~$ sudo ntpdate -v ntp.ubuntu.com 26 Nov 08:16:21 ntpdate[8926]: ntpdate 4.2.8p12@1.3728-o (1) 26 Nov 08:16:30 ntpdate[8926]: step time server 91.189.91.157 offset -567993599.624839 sec ubuntu@ubuntu:~$ date Thu Nov 26 08:16:33 AM UTC 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905688] [NEW] systemd-timesyncd.service: Timed out waiting for reply from NTP server
Public bug reported: systemd-timesyncd.service fails to correct time if the system time is later than February 7, 2036. Image: ubuntu-20.10-desktop-amd64.iso systemd: 246.6-1ubuntu1 $ timedatectl status Local time: Fri 2038-11-26 07:58:16 UTC Universal time: Fri 2038-11-26 07:58:16 UTC RTC time: Fri 2038-11-26 07:58:17 Time zone: Etc/UTC (UTC, +) System clock synchronized: no NTP service: active RTC in local TZ: no ubuntu@ubuntu:~$ sudo systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2038-11-26 07:36:55 UTC; 7min ago Docs: man:systemd-timesyncd.service(8) Main PID: 1257 (systemd-timesyn) Status: "Idle." Tasks: 2 (limit: 9283) Memory: 1.8M CGroup: /system.slice/systemd-timesyncd.service └─1257 /lib/systemd/systemd-timesyncd Nov 26 07:39:09 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com). Nov 26 07:39:19 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com). Nov 26 07:40:34 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com). Nov 26 07:40:44 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com). There is no issue with ntpdate: ubuntu@ubuntu:~$ sudo ntpdate -v ntp.ubuntu.com 26 Nov 08:16:21 ntpdate[8926]: ntpdate 4.2.8p12@1.3728-o (1) 26 Nov 08:16:30 ntpdate[8926]: step time server 91.189.91.157 offset -567993599.624839 sec ubuntu@ubuntu:~$ date Thu Nov 26 08:16:33 AM UTC 2020 ** 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/1905688 Title: systemd-timesyncd.service: Timed out waiting for reply from NTP server Status in systemd package in Ubuntu: New Bug description: systemd-timesyncd.service fails to correct time if the system time is later than February 7, 2036. Image: ubuntu-20.10-desktop-amd64.iso systemd: 246.6-1ubuntu1 $ timedatectl status Local time: Fri 2038-11-26 07:58:16 UTC Universal time: Fri 2038-11-26 07:58:16 UTC RTC time: Fri 2038-11-26 07:58:17 Time zone: Etc/UTC (UTC, +) System clock synchronized: no NTP service: active RTC in local TZ: no ubuntu@ubuntu:~$ sudo systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2038-11-26 07:36:55 UTC; 7min ago Docs: man:systemd-timesyncd.service(8) Main PID: 1257 (systemd-timesyn) Status: "Idle." Tasks: 2 (limit: 9283) Memory: 1.8M CGroup: /system.slice/systemd-timesyncd.service └─1257 /lib/systemd/systemd-timesyncd Nov 26 07:39:09 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.94.4:123 (ntp.ubuntu.com). Nov 26 07:39:19 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.198:123 (ntp.ubuntu.com). Nov 26 07:40:34 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com). Nov 26 07:40:44 ubuntu systemd-timesyncd[1257]: Timed out waiting for reply from 91.189.89.199:123 (ntp.ubuntu.com). There is no issue with ntpdate: ubuntu@ubuntu:~$ sudo ntpdate -v ntp.ubuntu.com 26 Nov 08:16:21 ntpdate[8926]: ntpdate 4.2.8p12@1.3728-o (1) 26 Nov 08:16:30 ntpdate[8926]: step time server 91.189.91.157 offset -567993599.624839 sec ubuntu@ubuntu:~$ date Thu Nov 26 08:16:33 AM UTC 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)
** Tags added: verification-done-xenial -- 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/1727401 Title: Corruption on windowed 3D apps running on dGPU (Intel/AMD) Status in Mesa: In Progress Status in OEM Priority Project: Triaged Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] Corruption is seen on windowed 3D apps running on dGPU [Test case] Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears', see how the window has corrupted gfx. The fix is to patch Intel i965_dri driver. [Regression potential] There could be a slight loss of performance, but corruption free behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1727401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)
@Timo Here is the test result of mesa (xenial-proposed) A. Test Result: 1. DRI_PRIME=1 glxgear: Pass 2. DRI_PRIME=1 glxgear -fulscreen: Pass 3. glxgear: Pass 4. glxgear -fulscreen: Pass 5. Unigine_Heaven-4.0.run (5mins): Pass 6. Unigine_Heaven-4.0.run (Fullscreen, 5mins): Pass 7. DRI_PRIME=1 Unigine_Heaven-4.0.run (5mins): Pass 8. DRI_PRIME=1 Unigine_Heaven-4.0.run (Fullscreen, 5mins): Pass B. Test Environment: 1. Ubuntu: Xenial 16.04 2. Graphic Card: b. Intel [8086:5917] (rev 07) + AMD [1002:6900] (rev ff) 3.Installed package: a. Online Update b. Enable xenial-proposed and then upgrade mesa libglapi-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libgl1-mesa-dri_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libxatracker2_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libwayland-egl1-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libgl1-mesa-glx_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libgbm1_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libegl1-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb ** Tags removed: verification-needed-xenial -- 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/1727401 Title: Corruption on windowed 3D apps running on dGPU (Intel/AMD) Status in Mesa: In Progress Status in OEM Priority Project: Triaged Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] Corruption is seen on windowed 3D apps running on dGPU [Test case] Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears', see how the window has corrupted gfx. The fix is to patch Intel i965_dri driver. [Regression potential] There could be a slight loss of performance, but corruption free behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1727401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)
@Timo Here is the test result for mesa (17.2.4-0ubuntu1~16.04.3~1) A. Test Result: 1. DRI_PRIME=1 glxgear: Pass 2. DRI_PRIME=1 glxgear -fulscreen: Pass 3. glxgear: Pass 4. glxgear -fulscreen: Pass 5. Change Resolution: Pass 6. Scale for menu and title bars: Pass 7. Unigine_Heaven-4.0.run (5mins): Pass 8. Unigine_Heaven-4.0.run (Fullscreen, 5mins): Pass B. Test Environment: 1. Ubuntu: Xenial 16.04 2. Graphic Card: b. Intel [8086:5917] (rev 07) + AMD [1002:6900] (rev ff) 3.Installed package: a. Online Update b. mesa (17.2.4-0ubuntu1~16.04.3~1) libglapi-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libgl1-mesa-dri_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libxatracker2_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libwayland-egl1-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libgl1-mesa-glx_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libgbm1_17.2.4-0ubuntu1~16.04.3~1_amd64.deb libegl1-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb 4. src: https://launchpad.net/~tjaalton/+archive/ubuntu/ppa/+files/mesa_17.2.4-0ubuntu1~16.04.3~1.dsc -- 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/1727401 Title: Corruption on windowed 3D apps running on dGPU (Intel/AMD) Status in Mesa: In Progress Status in OEM Priority Project: Fix Released Status in mesa package in Ubuntu: In Progress Status in mesa source package in Xenial: Triaged Status in mesa source package in Artful: Fix Committed Bug description: [Impact] Corruption is seen on windowed 3D apps running on dGPU [Test case] Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears', see how the window has corrupted gfx. The fix is to patch Intel i965_dri driver. [Regression potential] There could be a slight loss of performance, but corruption free behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1727401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)
Cannot reproudce the issue on xenial. A. Test Result: 1. DRI_PRIME=1 glxgear -info: Pass 2. Change Resolution: Pass 3. Scale for menu and title bars: Pass 4. Unigine_Heaven-4.0.run (5mins): Pass B. Test Environment: 1. Ubuntu: Xenial 16.04 2. Graphic Card: a. AMD [1002:9874] (rev e2) b. Intel [8086:5917] (rev 07) + AMD [1002:6900] (rev ff) 3.Installed package: (Online Update: xenial-proposed: mesa) libdrm-common all 2.4.83-1~16.04.1 libdrm2 amd64 2.4.83-1~16.04.1 libcapnp-0.5.3 amd64 0.5.3-2ubuntu1 libdrm-amdgpu1 amd64 2.4.83-1~16.04.1 libwayland-egl1-mesa amd64 17.2.4-0ubuntu1~16.04.2 libwayland-client0 amd64 1.12.0-1~ubuntu16.04.2 libwayland-server0 amd64 1.12.0-1~ubuntu16.04.2 libegl1-mesa amd64 17.2.4-0ubuntu1~16.04.2 libgbm1 amd64 17.2.4-0ubuntu1~16.04.2 libmircore1 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libmircommon7 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libmirprotobuf3 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libmirclient9 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libllvm5.0 amd64 1:5.0-3~16.04.1 libgl1-mesa-dri amd64 17.2.4-0ubuntu1~16.04.2 ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1727401 Title: Corruption on windowed 3D apps running on dGPU (Intel/AMD) Status in Mesa: In Progress Status in OEM Priority Project: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] Corruption is seen on windowed 3D apps running on dGPU [Test case] Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears', see how the window has corrupted gfx. The fix is to patch Intel i965_dri driver. [Regression potential] There could be a slight loss of performance, but corruption free behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1727401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727390] Re: New bugfix release 17.2.4
mesa 17.2.4 works well on my two devices. Here is the test result: 1) AMD [1002:9874] (rev e2) glxgear -info: Pass Unigine_Heaven-4.0 (5mins): Pass 2) Intel [8086:5917] (rev 07) + AMD [1002:6900] (rev ff) glxgear -info: Pass DRI_PRIME=1 glxgear -info: Pass Unigine_Heaven-4.0 (5mins): Pass DRI_PRIME=1 Unigine_Heaven-4.0.run (5mins): Pass --- Installed package: (Online Update: xenial-proposed: mesa) libdrm-common all 2.4.83-1~16.04.1 libdrm2 amd64 2.4.83-1~16.04.1 libcapnp-0.5.3 amd64 0.5.3-2ubuntu1 libdrm-amdgpu1 amd64 2.4.83-1~16.04.1 libwayland-egl1-mesa amd64 17.2.4-0ubuntu1~16.04.2 libwayland-client0 amd64 1.12.0-1~ubuntu16.04.2 libwayland-server0 amd64 1.12.0-1~ubuntu16.04.2 libegl1-mesa amd64 17.2.4-0ubuntu1~16.04.2 libgbm1 amd64 17.2.4-0ubuntu1~16.04.2 libmircore1 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libmircommon7 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libmirprotobuf3 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libmirclient9 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libllvm5.0 amd64 1:5.0-3~16.04.1 libgl1-mesa-dri amd64 17.2.4-0ubuntu1~16.04.2 -- 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/1727390 Title: New bugfix release 17.2.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] A new upstream bugfix release is available. Release note diff compared to 17.2.2: "Mesa 17.2.3 is now available. In this release we have: The Vulkan drivers ANV and RADV have multiple small fixes. The EGL code has improved handling of the new wl_dmabuf codepath. SWR no longer crashes when checking environment variables. Other gallium drivers have also seen updates - freedreno, nouveau and radeonsi. The gallivm module, used by llvmpipe et al. has gained little endian PPC64 fixes. The VA and VDPAU state-trackers have seems improvements handling interlaced videos. We're using python3 compatible constructs which gives us SCons 3.0 support." "Mesa 17.2.4 is now available. In this release we have: In Mesa Core we have included a change to prevent KOTOR from breaking when in combination with the ATI fragment shader extension. Additionally, NIR has also received a correction. Mesa's state tracker has gotten a patch to avoid leaks in certain situations like when resizing a window. Intel drivers have received several fixes. The compiler has gotten a couple, while anv also received one. i965 got a patch to avoid VA- API, Beignet and other contexts in the system to break when in combination with previous versions of Mesa 17.2.x. AMD's compiler has received a couple of fixes while radv has also received another couple, including one to avoid a hang due to an overflow on huge textures. Broadcom's vc4 has corrected a problem when compiling with Android's clang. clover has also seen fixed a problem compiling after a specific clang revision. Vulkan's WSI has gotten plugged a memory leak for X11." [Test case] Test typical use cases on the most common hw/driver combinations: intel/i965 nvidia/nouveau radeon/radeonsi [Regression potential] These releases are tested against compliance, bugfix releases in particular have minimal risk of regressing anything major at least. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
typo... u-u in #73 should be 0.97ubuntu1~16.04.1 -- 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/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: New Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: New Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Balint Here is test result for InstallOnShutdown:false Timestamp: 1. 13:25:10~13:40:32: 15mins 2. reboot system 3. 14:59:17~16:44:18: 1hr45mins Total: 2hr Comparing to the test result in #69, 0.97ubuntu1~16.04.1 saves 4~5 hours. Log: Please check full log as attached. Installed packages: apt (1.2.25-rbalint2) unattended-upgrades_0.97ubuntu1~16.04.1_all.deb ** Attachment added: "unattended-upgrades-shutdown.log, unattended-upgrades.log, apt log, and dpkg log" https://bugs.launchpad.net/oem-priority/+bug/1690980/+attachment/4954978/+files/log_0922_InstallOnShutdown_False.tar.gz -- 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/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: New Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: New Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Balint Here is test result for InstallOnShutdown:true "Errors were encountered while processing: apport" u-u still has packages to upgrade after this issue happens. So, when I reboot system every time, u-u still tries to upgrade package. We expect that there are 30 mins to do the update. But, dependency problem will prevent u-u from upgrading packages. 1. unattended-upgrades-shutdown.log: (Please check full log as attached) 2017-09-22 14:54:25,865 WARNING - Running unattended-upgrades in shutdown mode 14:54:25~14:55:54 => 1:29, u-u only takes 1:29 to upgrade packges. 2017-09-22 14:57:02,183 WARNING - Running unattended-upgrades in shutdown mode 14:57:02~14:58:30 => 1:28 2017-09-22 15:00:00,233 WARNING - Running unattended-upgrades in shutdown mode 15:00:00~15:01:28 => 1:28 2. unattended-upgrades-dpkg.log: Log started: 2017-09-22 14:34:24 ... Preparing to unpack .../apport_2.20.1-0ubuntu2.10_all.deb ... Failed to get load state of apport-forward.socket: Connection reset by peer 2017-09-22 14:37:26,769 WARNING SIGTERM received, will stop Log ended: 2017-09-22 14:37:26 Installed packages: apt (1.2.25-rbalint2) unattended-upgrades_0.96ubuntu1-16.04.1_all.deb ** Attachment added: "unattended-upgrades-shutdown.log, unattended-upgrades.log, apt log, and dpkg log" https://bugs.launchpad.net/oem-priority/+bug/1690980/+attachment/4954864/+files/log_0922_InstallOnShutdown.tar.gz -- 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/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: New Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: New Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Balint Here is another test result for InstallOnShutdown:false Log: 2017-09-14 17:20:14 ~ 2017-09-15 00:00:03 It took 6~7 hours to finish online update. (Packages: around 700mb) unattended-upgrades.log // Online update was triggered. 2017-09-14 17:15:03,561 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] // Reboot system manually 2017-09-14 18:07:49,988 WARNING SIGTERM received, will stop // Online udpate didn't be finished. apt-daily-upgrade triggerred it again. 2017-09-14 18:16:29,208 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] (Please check full log as attached) $ grep -r -e "Install" 50unattended-upgrades // Install all unattended-upgrades when the machine is shutting down //Unattended-Upgrade::InstallOnShutdown "true"; Installed packages: apt_1.2.25-rbalint2_amd64.deb apt-doc_1.2.25-rbalint2_all.deb apt-transport-https_1.2.25-rbalint2_amd64.deb apt-utils_1.2.25-rbalint2_amd64.deb libapt-inst2.0_1.2.25-rbalint2_amd64.deb libapt-pkg5.0_1.2.25-rbalint2_amd64.deb libapt-pkg-doc_1.2.25-rbalint2_all.deb unattended-upgrades_0.96ubuntu1-16.04.1_all.deb ** Attachment added: "unattended-upgrades-shutdown.log, unattended-upgrades.log, apt log, and dpkg log" https://bugs.launchpad.net/oem-priority/+bug/1690980/+attachment/4950491/+files/log_0914_InstallOnShutdown_False.tar.gz -- 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/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: New Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: New Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Balint Here is my test result: (InstallOnShutdown:true) Packages will be installed when rebooting system. I rebooted system five times, but system still didn't finish the update. It took too long to finish online update. Timestamp: (reboot system) 1. 2017-09-14 13:57:00,998 2. 2017-09-14 14:32:26,172 3. 2017-09-14 15:20:41,267 4. 2017-09-14 16:00:18,694 5. 2017-09-14 16:36:47,174 (Please check full log as attached) $ apt-config dump Unattended-Upgrade::InstallOnShutdown "true"; Installed packages: apt_1.2.25-rbalint2_amd64.deb apt-doc_1.2.25-rbalint2_all.deb apt-transport-https_1.2.25-rbalint2_amd64.deb apt-utils_1.2.25-rbalint2_amd64.deb libapt-inst2.0_1.2.25-rbalint2_amd64.deb libapt-pkg5.0_1.2.25-rbalint2_amd64.deb libapt-pkg-doc_1.2.25-rbalint2_all.deb unattended-upgrades_0.96ubuntu1-16.04.1_all.deb ** Attachment added: "unattended-upgrades-shutdown.log, unattended-upgrades.log, apt log, and dpkg log" https://bugs.launchpad.net/oem-priority/+bug/1690980/+attachment/4950042/+files/log_0914_InstallOnShutdown_True.tar.gz -- 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/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: New Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: New Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Balint I tried three times, and 0.95-16.04.0rbalint1 didn't work well. Please refer to attached file for detailed log. 1) Reboot system when unattended upgrades starts to download packages. //unattended-upgrades.log 2017-08-08 15:34:07,782 INFO Starting unattended upgrades script 2017-08-08 15:34:07,782 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] //unattended-upgrades-shutdown.log 2017-08-08 15:36:06,358 INFO - All upgrades installed The log shows "All upgrades installed", but there is no package installed. 2) Reboot system after unattended upgrades downloads packages for 5mins //unattended-upgrades.log 2017-08-08 15:55:27,907 INFO Starting unattended upgrades script 2017-08-08 15:55:27,907 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] System reboots immediately. There is no unattended-upgrades-shutdown log. 3) Reboot system when unattended upgrades starts to download packages. //unattended-upgrades.log 2017-08-08 16:09:03,548 INFO Starting unattended upgrades script 2017-08-08 16:09:03,549 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] //unattended-upgrades-shutdown.log 2017-08-08 16:10:50,573 INFO - All upgrades installed The log shows "All upgrades installed", but there is no package installed. --- The installed packages: apt_1.2.25-rbalint2_amd64.deb apt-doc_1.2.25-rbalint2_all.deb apt-transport-https_1.2.25-rbalint2_amd64.deb apt-utils_1.2.25-rbalint2_amd64.deb libapt-inst2.0_1.2.25-rbalint2_amd64.deb libapt-pkg5.0_1.2.25-rbalint2_amd64.deb libapt-pkg-doc_1.2.25-rbalint2_all.deb unattended-upgrades_0.95-16.04.0rbalint1_all.deb ** Attachment added: "unattended-upgrades-shutdown.log, unattended-upgrades.log, apt log, and dpkg log" https://bugs.launchpad.net/oem-priority/+bug/1690980/+attachment/4928762/+files/log_0808.tar.gz -- 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/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Balint unattended-upgrades didn't finish online-update. https://launchpad.net/~rbalint/+archive/ubuntu/scratch/+packages unattended-upgrades: (0.93.2~16.04.0+rbalint2） apt:（1.2.25~rbalint2） Here are logs: /var/log/unattended-upgrades/unattended-upgrades.log 2017-07-26 15:58:59,769 INFO Initial blacklisted packages: 2017-07-26 15:58:59,770 INFO Initial whitelisted packages: 2017-07-26 15:58:59,770 INFO Starting unattended upgrades script 2017-07-26 15:58:59,770 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] 2017-07-26 16:03:53,918 WARNING SIGTERM received, will stop 2017-07-26 16:03:54,073 WARNING SIGTERM received, will stop 2017-07-26 16:03:55,082 WARNING SIGTERM received, will stop /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2017-07-26 16:03:54,924 WARNING - Unattended-upgrade in progress during shutdown, sleeping for 5s 2017-07-26 16:04:00,607 INFO - All upgrades installed Installed packages: apt_1.2.25-rbalint2_amd64.deb apt-doc_1.2.25-rbalint2_all.deb apt-transport-https_1.2.25-rbalint2_amd64.deb apt-utils_1.2.25-rbalint2_amd64.deb libapt-inst2.0_1.2.25-rbalint2_amd64.deb libapt-pkg5.0_1.2.25-rbalint2_amd64.deb libapt-pkg-doc_1.2.25-rbalint2_all.deb unattended-upgrades_0.93.2-16.04.0+rbalint2_all.deb -- 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/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Balint Something wrong happens when installing deb package apport. (Please check full log as attached) unattended-upgrades-dpkg.log Unpacking python3-apport (2.20.1-0ubuntu2.10) over (2.20.1-0ubuntu2) ... Preparing to unpack .../apport_2.20.1-0ubuntu2.10_all.deb ... unattended-upgrades-shutdown.log 2017-07-25 11:27:46,257 WARNING - Unattended-upgrade in progress during shutdown, sleeping for 5s Progress: 38.7177 % (apport) ... 2017-07-25 11:33:12,886 WARNING - Unattended-upgrade in progress during shutdown, sleeping for 5s Progress: 38.7177 % (apport) 2017-07-25 11:33:17,906 WARNING - Unattended-upgrade in progress during shutdown, sleeping for 5s Progress: 38.7177 % (apport) 2017-07-25 11:33:22,925 WARNING - Giving up on lockfile after 10 delay //No progress when installing apport. It's always 38.7177 % ** Attachment added: "logs (unattended-upgrades, apt, dpkg, and kern)" https://bugs.launchpad.net/oem-priority/+bug/1690980/+attachment/4920802/+files/log_0725.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Brian My test result with Balint's patch is in #22. According to the previous test in #18, the behavior of my test script is different from apt-daily timer. If you want to reproduce this issue, creating override.conf would be a better way. --- sudo cat << EOF > /etc/systemd/system/apt-daily.timer.d/override.conf [Timer] OnCalendar= OnCalendar= *-*-* XX:YY RandomizedDelaySec=1m AccuracySec=1m EOF fi PS: Please remember to modify XX:YY to the time you want. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Balint The attached patch can fix the communication between u-u and u-u-shutdown. However, without workaround 1 or 2 in #19, u-u will be killed when users reboot/shutdown the device. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates
In xenial and yakkety, unattended-upgrade can finish security updates after applying workaround 1&2. workaround 3: If users reboot/shutdown by UI, there will be a pop-up window which asks users for root password. If users reboot/shutdown by command (sudo reboot), unattended-upgrade will be killed and cannot finish security updates. Workaround 1: /lib/systemd/system/apt-daily.service [Service] Type=oneshot ExecStart=/usr/lib/apt/apt.systemd.daily +KillMode=none +TimeoutStopSec=0 Wordaround 2: /lib/systemd/system/apt-daily.service [Unit] Description=Daily apt activities Documentation=man:apt(8) +DefaultDependencies=no +Before=shutdown.target Workaround 3: /lib/systemd/system/apt-daily.service [Service] Type=oneshot -ExecStart=/usr/lib/apt/apt.systemd.daily +ExecStart=/bin/systemd-inhibit --what=shutdown --mode=block /usr/lib/apt/apt.systemd.daily --- the code flow of unattended-upgrades: (1) -> apt_pkg.get_lock() -> do_install() -> (2) If users reboot/shutdown system in (1), unattended-upgrades-shutdown will break from monitoring loop and then there will no message to tell user that security update is ongoing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates
New test result: 1. unattended-upgrades is triggered by apt-daily.timer. yakkety (triggered by apt-daily.timer): Failed xenial (triggered by apt-daily.timer): Failed 2. unattended-upgrades is triggered by cmdline (sudo unattended-upgrade) yakkety (triggered by cmdline): Pass xenial (triggered by cmdline): Failed This issue can be reproduced on yakkety. unattended-upgrades received signal, and then it was stopped. Here is the log: 1. unattended-upgrades.log 2017-06-26 17:30:59,944 INFO Initial blacklisted packages: 2017-06-26 17:30:59,948 INFO Initial whitelisted packages: 2017-06-26 17:30:59,948 INFO Starting unattended upgrades script 2017-06-26 17:30:59,948 INFO Allowed origins are: ['o=Ubuntu,a=yakkety-security'] 2017-06-26 17:33:21,236 INFO Packages that will be upgraded: apparmor apparmor-easyprof ... 2017-06-26 17:33:21,236 INFO get_lock returned 174 2017-06-26 17:33:41,569 INFO signal received, will stop 2017-06-26 17:33:41,610 INFO signal received, will stop 2. syslog: Jun 26 17:33:41 u-Inspiron-5379 systemd[1]: Starting Unattended Upgrades Shutdown... 3. unattended-upgrades-shutdown.log 2017-06-26 17:33:41,871 WARNING - Running unattended-upgrades in shutdown mode 2017-06-26 17:33:42,079 WARNING - ps -aef | grep unatteded-upgrade 2017-06-26 17:33:42,316 WARNING - root 25511 4 17:33 ? 00:00:00 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown 2017-06-26 17:33:42,329 WARNING - root 2670 2551 0 17:33 ? 00:00:00 grep unattended-upgrade 2017-06-26 17:33:42,345 WARNING - get_lock returned 4 2017-06-26 17:33:42,362 WARNING - lock not taken ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1690980/+attachment/4903481/+files/syslog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates
I added more debug messages (ps -aef | grep unatteded-upgrade) to unattended-upgrades-shutdown. In xenial, it looks like unattended-upgrade is killed before unattended-upgrades-shutdown is running. That is why unattended-upgrades-shutdown can get lock. Log: 1. xenial (unattended-upgrades-0.90ubuntu0.6): unattended-upgrades-shutdown.log 2017-06-23 15:27:09,824 WARNING - Running unattended-upgrades in shutdown mode WARNING - ps -aef | grep unatteded-upgrade WARNING - root 16581 1 0 15:27 ?00:00:00 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown WARNING - root 16662 16581 0 15:27 ?00:00:00 grep unattended-upgrade WARNING - get_lock returned 4 WARNING - lock not taken 2. yakkety (unattended-upgrades-0.92ubuntu1.5): unattended-upgrades-shutdown.log 2017-06-23 13:52:55,720 WARNING - Running unattended-upgrades in shutdown mode WARNING - ps -aef | grep unatteded-upgrade WARNING - root 5193 1298 0 13:49 ?00:00:00 sudo unattended-upgrade WARNING - root 5196 5193 61 13:49 ?00:02:14 /usr/bin/python3 /usr/bin/unattended-upgrade WARNING - root 5379 1 0 13:52 ?00:00:00 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown WARNING - root 5444 5379 0 13:52 ?00:00:00 grep unattended-upgrade WARNING - get_lock returned -1 WARNING - Unattended-upgrade in progress during shutdown, sleeping for 5s ... WARNING - get_lock returned -1 WARNING - Unattended-upgrade in progress during shutdown, sleeping for 5s WARNING - get_lock returned 4 WARNING - lock not taken INFO - All upgrades installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates
I added more debug messages and reproduced the issue again. Here are logs: lock_file: /var/run/unattended-upgrades.lock 1. xenial (unattended-upgrades-0.90ubuntu0.6): a. /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2017-06-22 03:43:09,028 WARNING - get_lock returned... 2017-06-22 03:43:09,040 WARNING - lock not taken b. $ ls /var/run/una* nothing 2. yakkety (unattended-upgrades-0.92ubuntu1.5): a. /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2017-06-22 03:35:21,038 WARNING - get_lock returned... 2017-06-22 03:35:21,052 WARNING - log_progress... 2017-06-22 03:35:21,066 WARNING - Unattended-upgrade in progress during shutdown, sleeping for 5s Progress: 17.1429 % (libreoffice-math) ... 2017-06-22 03:41:30,797 WARNING - Unattended-upgrade in progress during shutdown, sleeping for 5s Progress: 98.5525 % (initramfs-tools) 2017-06-22 03:41:35,816 WARNING - get_lock returned... 2017-06-22 03:41:35,833 WARNING - lock not taken 2017-06-22 03:41:35,866 INFO - All upgrades installed b. $ ls /var/run/una* /var/run/unattended-upgrades.lock /var/run/unattended-upgrades.progress $ sudo lslocks COMMAND PID TYPE SIZE MODE M STARTEND PATH ... unattended-upgr 3006 POSIX 0B WRITE 0 0 0 /run/unattended-upgrades.lock -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates
** Changed in: oem-priority Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates
@Brian Murray It seems to me that Yakkety (16.10) deals better with a reboot while unattended-upgrades is running. After I shutdowned system by GUI, I saw the following message. "Unattended-upgrade in progress during shutdown, sleeping for 5s Progress: 67.5656 % .." (Please check logs as attached) And, I still can login to Ubuntu desktop after shutdown. ** Attachment added: "logs of unattended-upgrades, syslog, dpkg, and apt" https://bugs.launchpad.net/oem-priority/+bug/1690980/+attachment/4883195/+files/log_0525_16.10.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Status in OEM Priority Project: In Progress Status in OEM Priority Project xenial series: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates
@Brian Murray Still can reproduce this issue if I reboot system by GUI. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Status in OEM Priority Project: In Progress Status in OEM Priority Project xenial series: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates
@Brian Murray I still can reproduce this issue with 0.90ubuntu0.6 $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90ubuntu0.6 Candidate: 0.90ubuntu0.6 Please check full log as attached. Here are reproduction steps: 1. sudo /usr/bin/unattended-upgrade 2. Run the following script. #!/bin/sh loop=1 count=0 while [ $loop -gt 0 ] do count=`expr $count + 1` echo "loop...$count" if [ `grep -r -e "status half-installed linux-headers-4.4.0-78" /var/log/dpkg.log | wc -l` -ge 1 ]; then aplay /usr/share/sounds/alsa/Front_Right.wav sudo reboot fi sleep 1 done ** Attachment added: "dpkg.log, term.log, history,log, syslog, unattended-upgrades.log" https://bugs.launchpad.net/oem-priority/+bug/1690980/+attachment/4881783/+files/log_0523.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Status in OEM Priority Project: In Progress Status in OEM Priority Project xenial series: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates
** Changed in: oem-priority Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Status in OEM Priority Project: In Progress Status in OEM Priority Project xenial series: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates
@Brian Murray Here is the log which I uploaded in #1 //dpkg.log 2017-05-12 08:22:24 status unpacked linux-headers-4.4.0-75:all 4.4.0-75.96 2017-05-12 08:22:24 install linux-headers-4.4.0-75-generic:amd64 4.4.0-75.96 2017-05-12 08:22:24 status half-installed linux-headers-4.4.0-75-generic:amd64 4.4.0-75.96 //term.log Selecting previously unselected package linux-headers-4.4.0-75. Preparing to unpack .../linux-headers-4.4.0-75_4.4.0-75.96_all.deb ... Unpacking linux-headers-4.4.0-75 (4.4.0-75.96) ... Selecting previously unselected package linux-headers-4.4.0-75-generic. Preparing to unpack .../linux-headers-4.4.0-75-generic_4.4.0-75.96_amd64.deb ... Unpacking linux-headers-4.4.0-75-generic (4.4.0-75.96) ... In my case, the installation of linux-header/linux-image was interrupted, and then system failed to boot to Ubuntu desktop. unattended-upgrades had no chance to finish the installation. It looks like not all packages can be recovered after reboot. It seems to me that the ideal way is that reboot/shutdown is blocked until unattended-upgrades finishes secure update. ** Changed in: oem-priority Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates
@Brian Murray When I saw this issue first time, unattended-upgrades was triggered automatically. I tried to reproduce this issue, so I executed the python script manually. I filed the bug because users don't know security updates is ongoing when unattended-upgrades is triggered automatically. If users reboot or shutdown system at that moment, system may fail to boot at next time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Status in OEM Priority Project: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates
** Project changed: unattended-upgrades => unattended-upgrades (Ubuntu) ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Assignee: (unassigned) => ethan.hsieh (ethan.hsieh) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Status in OEM Priority Project: New Status in unattended-upgrades package in Ubuntu: New Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] [NEW] No pop-up window to warn users that system should not reboot or shutdown while installing security updates
Public bug reported: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS ** Affects: unattended-upgrades Importance: Undecided Status: New ** Also affects: unattended-upgrades Importance: Undecided Status: New ** 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/1690980 Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Status in unattended-upgrades: New Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639896] Re: Backport support for AMD Polaris
I have verified xserver-xorg-video-amdgpu (1.1.2) and mesa (12.0.6) Test result: 1. glxgears: Pass 2. glmark2: Pass 3. S3 Test: Pass (sudo fwts s3 --s3-multiple=30 --s3-min-delay=30 --s3-max-delay=30) Test Environment 1. Kernel: 4.4.0-49-generic 2. VGA compatible controller [AMD/ATI] Device [1002:67df], Kernel driver in use: amdgpu 3. Installed packages: amdgpu-pro-dkms (16.60-377537) xserver-xorg-video-amdgpu (1.1.2-0ubuntu0.16.04.1) libegl1-mesa-drivers:amd64 (12.0.6-0ubuntu0.16.04.1) libgbm1:amd64 (12.0.6-0ubuntu0.16.04.1) libgl1-mesa-dri:amd64 (12.0.6-0ubuntu0.16.04.1) libglapi-mesa:amd64 (12.0.6-0ubuntu0.16.04.1) libgles1-mesa:amd64 (12.0.6-0ubuntu0.16.04.1) libgles2-mesa:amd64 (12.0.6-0ubuntu0.16.04.1) libosmesa6:amd64 (12.0.6-0ubuntu0.16.04.1) libxatracker2:amd64 (12.0.6-0ubuntu0.16.04.1) libegl1-mesa:amd64 (12.0.6-0ubuntu0.16.04.1) libgl1-mesa-glx:amd64 (12.0.6-0ubuntu0.16.04.1) libwayland-egl1-mesa:amd64 (12.0.6-0ubuntu0.16.04.1) -- 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/1639896 Title: Backport support for AMD Polaris Status in mesa package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in mesa source package in Xenial: Fix Released Status in xserver-xorg-video-amdgpu source package in Xenial: Fix Committed Bug description: [Impact] Xenial has x-x-v-amdgpu 1.1.0 but 1.1.2 adds more PCI-ID's and fixes bugs. Mesa needs a bunch of commits backported from 12.0.x. [update] 12.0.6 backported instead [Test case] Test desktop with a Polaris GPU, it should run with full 2D/3D-acceleration [Regression potential] This is a stable upstream release, and 16.10 ships the same versions so regression potential should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1639896/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589889] Re: Bluetooth search gets nothing on Dell XPS 15 9550
** Changed in: bluez (Ubuntu) Status: In Progress => Confirmed -- 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/1589889 Title: Bluetooth search gets nothing on Dell XPS 15 9550 Status in bluez package in Ubuntu: Confirmed Bug description: Title: Bluetooth search gets nothing on Dell XPS 15 9550 Summary: Bluetooth search gets nothing on Dell XPS 15 9550 Steps: 1. Open Bluetooth Setting 2. Click "+" to search nearby bluetooth devices Expected results: BT search could get nearby BT devices Actual results: Nothing shows from BT search Additional information: BT device: Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 1 bDeviceProtocol 1 bMaxPacketSize064 idVendor 0x0a5c Broadcom Corp. idProduct 0x6410 CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8x) GPU: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) Manufacturer: Dell ProductName: XPS 15 9550 BiosVersion: 01.02.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1589889/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589889] Re: Bluetooth search gets nothing on Dell XPS 15 9550
** Changed in: bluez (Ubuntu) Status: Confirmed => In Progress -- 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/1589889 Title: Bluetooth search gets nothing on Dell XPS 15 9550 Status in bluez package in Ubuntu: In Progress Bug description: Title: Bluetooth search gets nothing on Dell XPS 15 9550 Summary: Bluetooth search gets nothing on Dell XPS 15 9550 Steps: 1. Open Bluetooth Setting 2. Click "+" to search nearby bluetooth devices Expected results: BT search could get nearby BT devices Actual results: Nothing shows from BT search Additional information: BT device: Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 1 bDeviceProtocol 1 bMaxPacketSize064 idVendor 0x0a5c Broadcom Corp. idProduct 0x6410 CPU: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8x) GPU: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) Manufacturer: Dell ProductName: XPS 15 9550 BiosVersion: 01.02.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1589889/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
