[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905688 Title: systemd-timesyncd.service: Timed out waiting for reply from NTP server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905688 Title: systemd-timesyncd.service: Timed out waiting for reply from NTP server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905688 Title: systemd-timesyncd.service: Timed out waiting for reply from NTP server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905688 Title: systemd-timesyncd.service: Timed out waiting for reply from NTP server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
** Tags added: originate-from-1911479 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789201] Re: prime-select doesn't work in phase 2
** Description changed: SRU Request: [Impact] We need to be able to disable the discrete GPU in phase 2 of the oem installer, and this requires running gpu-manager.service before oem-config.service. [Test Case] Add the new ubuntu-drivers-common in -proposed repository, and see if gpu-manager.service is called in phase 2. [Regression Potential] Low, as no action will be taken unless custom settings for hybrid graphics are available. + + What is "phase 2": + https://docs.google.com/presentation/d/18q2VtQt3OJzh12--2Llzwz36DlF3Lca6iLPCnhIbQds/edit?usp=sharing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789201 Title: prime-select doesn't work in phase 2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1789201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797322] [NEW] gsd-rfkill-manager fails to receive rfkill event
Public bug reported: The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. If the value is invalid UTF-8, gsd-rfkill-manager will fail to receive rfkill event. Steps: Run suspend/resume Test (> 127 times) Failure Rate: 100% In some platforms, bt will be re-probed after s3. If bt is re-probed, rfkill-idx will increase. And, 128 is the first invalid UTF-8 $ rfkill list ID TYPE DEVICE SOFT HARD 1 wlan phy0 unblocked unblocked 128 bluetooth hci0 unblocked unblocked Error Message: gnome-settings-daemon/plugins/rfkill/rfkill-glib.c gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: g_io_channel_fill_buffer: cur_len=0, read_size=8 gsd-rfkill[2062]: g_io_channel_read_chars: 5 *bytes_read=8 gsd-rfkill[2062]: event_cb: 1 read=8 gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=0 gsd-rfkill[2062]: event_cb: 1 source->encoded_read_buf->len=0 gsd-rfkill[2062]: RFKILL event: idx 127 type 2 (BLUETOOTH) op 1 (DEL) soft 0 hard 0 gsd-rfkill[2062]: event_cb: 2 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 2 read=0 gsd-rfkill[2062]: event_cb: 2 source->read_buf->len=8 gsd-rfkill[2062]: event_cb: g_list_length=1 gsd-rfkill[2062]: Removed Bluetooth rfkill with ID 127 gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 1 read=0T gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=16 gsd-rfkill[2062]: event_cb: g_list_length=0 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic ** Patch added: "0001-rfkill-set-encoding-as-NULL.patch" https://bugs.launchpad.net/bugs/1797322/+attachment/5199851/+files/0001-rfkill-set-encoding-as-NULL.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797322 Title: gsd-rfkill-manager fails to receive rfkill event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1797322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797322] Re: gsd-rfkill-manager fails to receive rfkill event
Have sent a merge request to GitLab and wait for approval. https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/57 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797322 Title: gsd-rfkill-manager fails to receive rfkill event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1797322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797322] Re: gsd-rfkill-manager fails to receive rfkill event
Thanks for your reminder. Bug description has been updated. ** Description changed: + [Impact] + + The default encoding for GIOChannel is UTF-8, but rfkill event is binary + data. gsd-rfkill-manager will fail to receive rfkill event if rfkill-idx + is larger than 127. + + The solution is to set the encoding of GIOChannel as NULL (binary data). + + [Test Case] + + 1) Enable the -proposed repository, and install new "gnome-settings- + daemon-schemas" and "gnome-settings-daemon" + + 2) Reboot system + + 3) Run suspend/resume test more than 127 times and then check if BT + settings still works well. + + [Regression Potential] + + Low. The default encoding for GIOChannel is wrong. Just set correct + encoding to receive rfkill event. + + --- + The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. If the value is invalid UTF-8, gsd-rfkill-manager will fail to receive rfkill event. Steps: Run suspend/resume Test (> 127 times) Failure Rate: 100% In some platforms, bt will be re-probed after s3. If bt is re-probed, rfkill-idx will increase. And, 128 is the first invalid UTF-8 $ rfkill list ID TYPE DEVICE SOFT HARD 1 wlan phy0 unblocked unblocked 128 bluetooth hci0 unblocked unblocked Error Message: gnome-settings-daemon/plugins/rfkill/rfkill-glib.c gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: g_io_channel_fill_buffer: cur_len=0, read_size=8 gsd-rfkill[2062]: g_io_channel_read_chars: 5 *bytes_read=8 gsd-rfkill[2062]: event_cb: 1 read=8 gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=0 gsd-rfkill[2062]: event_cb: 1 source->encoded_read_buf->len=0 gsd-rfkill[2062]: RFKILL event: idx 127 type 2 (BLUETOOTH) op 1 (DEL) soft 0 hard 0 gsd-rfkill[2062]: event_cb: 2 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 2 read=0 gsd-rfkill[2062]: event_cb: 2 source->read_buf->len=8 gsd-rfkill[2062]: event_cb: g_list_length=1 gsd-rfkill[2062]: Removed Bluetooth rfkill with ID 127 gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 1 read=0T gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=16 gsd-rfkill[2062]: event_cb: g_list_length=0 ** Description changed: [Impact] The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. gsd-rfkill-manager will fail to receive rfkill event if rfkill-idx is larger than 127. + + Settings will always shows Bluetooth is off after resume. The solution is to set the encoding of GIOChannel as NULL (binary data). [Test Case] 1) Enable the -proposed repository, and install new "gnome-settings- daemon-schemas" and "gnome-settings-daemon" 2) Reboot system 3) Run suspend/resume test more than 127 times and then check if BT settings still works well. [Regression Potential] Low. The default encoding for GIOChannel is wrong. Just set correct encoding to receive rfkill event. --- The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. If the value is invalid UTF-8, gsd-rfkill-manager will fail to receive rfkill event. Steps: Run suspend/resume Test (> 127 times) Failure Rate: 100% In some platforms, bt will be re-probed after s3. If bt is re-probed, rfkill-idx will increase. And, 128 is the first invalid UTF-8 $ rfkill list ID TYPE DEVICE SOFT HARD 1 wlan phy0 unblocked unblocked 128 bluetooth hci0 unblocked unblocked Error Message: gnome-settings-daemon/plugins/rfkill/rfkill-glib.c gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: g_io_channel_fill_buffer: cur_len=0, read_size=8 gsd-rfkill[2062]: g_io_channel_read_chars: 5 *bytes_read=8 gsd-rfkill[2062]: event_cb: 1 read=8 gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=0 gsd-rfkill[2062]: event_cb: 1 source->encoded_read_buf->len=0 gsd-rfkill[2062]: RFKILL event: idx 127 type 2 (BLUETOOTH) op 1 (DEL) soft 0 hard 0 gsd-rfkill[2062]: event_cb: 2 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 2 read=0 gsd-rfkill[2062]: event_cb: 2 source->read_buf->len=8 gsd-rfkill[2062]: event_cb: g_list_length=1 gsd-rfkill[2062]: Removed Bluetooth rfkill with ID 127 gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 1 read=0T gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=16 gsd-rfkill[2062]: event_cb: g_list_length=0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797322 Title: gsd-rfkill-manager fails to receive rfkill event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1797322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797322] Re: gsd-rfkill-manager fails to receive rfkill event
@Sebastien The patch has been merged. Could you help to land it to bionic? Thanks~ commit a5514ae097e5881df3ef26c63f4f4652b3f77811 Author: Ethan Hsieh Date: Tue Oct 9 10:28:31 2018 +0800 rfkill: set encoding as NULL The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. If the value is invalid UTF-8, gsd-rfkill-manager will fail to receive rfkill event. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797322 Title: gsd-rfkill-manager fails to receive rfkill event To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1797322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797322] Re: gsd-rfkill-manager fails to receive rfkill event
@Brian The issue is gone after upgrading gnome-settings-daemon to 3.28.1-0ubuntu1.1. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797322 Title: gsd-rfkill-manager fails to receive rfkill event To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1797322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789201] Re: prime-select doesn't work in phase 2
The issue is gone after installing packages at https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.5.2.1. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789201 Title: prime-select doesn't work in phase 2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1789201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824073] [NEW] USB stick isn't mounted automatically
Public bug reported: [Impact] USB stick isn't mounted automatically. Auto-mount function fails. [Test Case] 1) Plug USB stick and check if USB stick is mounted automatically. 2) Umount USB stick 3) Unplug USB stick 4) Go to 1) --- If the error message below appears, auto-mount function will fail. systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory Error Message: 1. when auto-mount fails: kernel: [ 175.661572] usb 2-2.3.3: USB disconnect, device number 6 systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 kernel: [ 222.843326] usb 2-2.3.3: new SuperSpeed USB device number 7 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c470 2. when auto-mount works: kernel: [ 124.313084] usb 2-2.3.3: USB disconnect, device number 5 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_disconnected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b9dea0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 kernel: [ 136.531496] usb 2-2.3.3: new SuperSpeed USB device number 6 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_connected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: in handle_volume_mount udisksd[2274]: Mounted /dev/sda1 at /media/u/U on behalf of uid 1001 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: oem-priority/xenial Importance: Undecided Status: New ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1824073/+attachment/5254607/+files/syslog.txt ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/xenial Importance: Undecided Status: New ** No longer affects: oem-priority/xenial ** No longer affects: oem-priority ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/xenial Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824073 Title: USB stick isn't mounted automatically To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824073] Re: USB stick isn't mounted automatically
This issue fixed by the commit below. Please help to backport the patch to xenial. commit 3574f9876634c29091655733a8f07ab5c242 Author: Tomas Smetana Date: Wed Oct 12 09:47:03 2016 +0200 Don't add new drive object on "change" uevent -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824073 Title: USB stick isn't mounted automatically To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786244] Re: package linux-image-4.15.0-24-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 1
@Christian The issue doesn't happen to Binoic, it only happens to customized Binoic server image. Thanks for your help. LP: #1844738 has been fixed by new customized image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786244 Title: package linux-image-4.15.0-24-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-legacy-ec2/+bug/1786244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786244] Re: package linux-image-4.15.0-24-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 1
@Christian LP: #1844738 doesn't happen to Bionic, it only happens to customized Bionic server image. Thanks for your help. It has been fixed by new customized image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786244 Title: package linux-image-4.15.0-24-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-legacy-ec2/+bug/1786244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858615] Re: dmidecode triggers system reboot on Inforce 6640
@Colin @dann @Timo I have verified the following packages on my inforce 6640. eoan-proposed: dmidecode_3.2-2ubuntu0.1_arm64.deb bionic-proposed: dmidecode_3.1-1ubuntu0.1_arm64.deb xenial-proposed: dmidecode_3.0-2ubuntu0.2_arm64.deb They look good. When I run dmidecode, I get the following message instead of system reboot. # dmidecode 3.X # No SMBIOS nor DMI entry point found, sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858615 Title: dmidecode triggers system reboot on Inforce 6640 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1858615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858615] Re: dmidecode triggers system reboot on Inforce 6640
Verified dmidecode_(3.1-1ubuntu0.1_amd64.deb) on my x86 laptop (Ubuntu 18.04.3 LTS, Desktop). It works well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858615 Title: dmidecode triggers system reboot on Inforce 6640 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1858615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858615] Re: dmidecode triggers system reboot on Inforce 6640
@Ryan Not all aarch64 platforms can support demidecode well. How about revert the patch? or create a black list? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858615 Title: dmidecode triggers system reboot on Inforce 6640 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1858615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858615] Re: dmidecode triggers system reboot on Inforce 6640
@Dan Got it. Thanks~ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858615 Title: dmidecode triggers system reboot on Inforce 6640 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1858615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734278] Re: Grub2 cannot boot up when 8254 time function disable
For OEM project, we need grub and debian-installer packages to be SRUed (xenial-proposed) before 2018/1/5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734278 Title: Grub2 cannot boot up when 8254 time function disable To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1734278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734278] Re: Grub2 cannot boot up when 8254 time function disable
amd64 build of grub2-signed 1.66.15 in ubuntu xenial PROPOSED https://launchpad.net/ubuntu/+source/grub2-signed/1.66.15/+build/13848452 Dependency wait on lgw01-amd64-021 Missing build dependencies: grub-efi-amd64-bin (>= 2.02~beta2-36ubuntu3.15) Started 6 hours ago Finished 6 hours ago (took 1 minute, 18.5 seconds) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734278 Title: Grub2 cannot boot up when 8254 time function disable To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1734278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734278] Re: Grub2 cannot boot up when 8254 time function disable
@Brian System can boot to Ubuntu desktop after installing following packages. grub2-common_2.02_beta2-36ubuntu3.15_amd64.deb grub-efi-amd64_2.02_beta2-36ubuntu3.15_amd64.deb grub-efi-amd64-signed_1.66.15+2.02_beta2-36ubuntu3.15_amd64.deb grub-common_2.02_beta2-36ubuntu3.15_amd64.deb grub-efi-amd64-bin_2.02_beta2-36ubuntu3.15_amd64.deb From: https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-36ubuntu3.15/+build/13848315 https://launchpad.net/ubuntu/+source/grub2-signed/1.66.15/+build/13848452 ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734278 Title: Grub2 cannot boot up when 8254 time function disable To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1734278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727390 Title: New bugfix release 17.2.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786244] Re: package linux-image-4.15.0-24-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 1
@Christian This issue also happens to bionic. (LP: #1844738) Could you help to backport the patch to binoic? ** Patch added: "grub-legacy-ec2_1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/grub-legacy-ec2/+bug/1786244/+attachment/5295370/+files/grub-legacy-ec2_1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786244 Title: package linux-image-4.15.0-24-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-legacy-ec2/+bug/1786244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
The issue is gone after upgrading gnome-control-center to 1:3.32.2-0ubuntu1. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
The issue is fixed by the attached patch in comment#1 and #2. Please help to review and integrate it to hirsute and focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] [NEW] Cursor bleeds on the platform with Mali armsoc driver
Public bug reported: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx has upstreamed the patch. https://lists.x.org/archives/xorg-devel/2021-March/058672.html But, it's still under review. ** Affects: oem-priority Importance: Critical Status: New ** Affects: oem-priority/focal Importance: Critical Status: New ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: patch ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/focal Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
debdiff for focal ** Patch added: "xorg-server_1.20.9-2ubuntu1.2~20.04.2.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1920096/+attachment/5478042/+files/xorg-server_1.20.9-2ubuntu1.2~20.04.2.debdiff ** Description changed: [Impact] - The cursor bleeds because of the bug in xorg which does not refresh the sprite background. + The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx has upstreamed the patch. https://lists.x.org/archives/xorg-devel/2021-March/058672.html But, it's still under review. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
debdiff for hirsute ** Patch added: "xorg-server_1.20.10-3ubuntu4.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1920096/+attachment/5478041/+files/xorg-server_1.20.10-3ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority/focal Importance: Undecided => High ** Changed in: oem-priority Importance: High => Critical ** Changed in: oem-priority/focal Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
** Description changed: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- - Xilinx has upstreamed the patch. + Xilinx is trying to upstream the patch. It's still under review. https://lists.x.org/archives/xorg-devel/2021-March/058672.html - But, it's still under review. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
debdiff for hirsute ** Patch added: "xorg-server_1.20.10-3ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1920096/+attachment/5478240/+files/xorg-server_1.20.10-3ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
debdiff for focal ** Patch added: "xorg-server_1.20.9-2ubuntu1.2~20.04.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1920096/+attachment/5478242/+files/xorg-server_1.20.9-2ubuntu1.2~20.04.2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
@Timo I got the attached patch from [1] and found it has duplicate content. --- [1] https://launchpad.net/ubuntu/+source/xorg-server/2:1.20.10-3ubuntu6 ** Patch added: "300-mi-sprite-SaveUnderCursor2.patch" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1920096/+attachment/5485754/+files/300-mi-sprite-SaveUnderCursor2.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
I built the package in my local machine without problems. The issue in [1] is caused by the duplicate content in the attached patch (comment#9). In file included from ../../../../mi/misprite.c:48: ../../../../mi/mipointer.h:132:23: warning: redundant redeclaration of ‘miDCSaveUnderCursor2’ [-Wredundant-decls] 132 | extern _X_EXPORT void miDCSaveUnderCursor2(ScreenPtr pScreen); | ^~~~ ../../../../mi/mipointer.h:130:23: note: previous declaration of ‘miDCSaveUnderCursor2’ was here 130 | extern _X_EXPORT void miDCSaveUnderCursor2(ScreenPtr pScreen); | ^~~~ ../../../../mi/misprite.c:977:1: error: redefinition of ‘miDCSaveUnderCursor2’ 977 | miDCSaveUnderCursor2(ScreenPtr pScreen) | ^~~~ ../../../../mi/misprite.c:960:1: note: previous definition of ‘miDCSaveUnderCursor2’ was here 960 | miDCSaveUnderCursor2(ScreenPtr pScreen) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824073] Re: USB stick isn't mounted automatically
@Mathew I didn't find the patch in latest udisk2 (xenial) from the link below. https://launchpad.net/ubuntu/+source/udisks2 May I know when it will be landed to udisks2 (xenial)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824073 Title: USB stick isn't mounted automatically To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827030] [NEW] Keyboard brightness control not working
Public bug reported: [Impact] Keyboard brightness control not working [Test Case] 1) Go to [All Settings][Power][Keyboard brightness] 2) Adjust keyboard brightness by sidebar --- $ cat /sys/class/leds/dell::/kbd_backlight/max_brightness 2 The valid value for my machine is 0, 1, and 2. The Power.Keyboard.Brightness property should be in percent. ** Affects: oem-priority Importance: High Status: New ** Affects: oem-priority/xenial Importance: High Status: New ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Patch added: "0001-New-upstream-bug-fix-release.patch" https://bugs.launchpad.net/bugs/1827030/+attachment/5260251/+files/0001-New-upstream-bug-fix-release.patch ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/xenial Importance: Undecided Status: New ** Changed in: oem-priority/xenial Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827030 Title: Keyboard brightness control not working To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827030] Re: Keyboard brightness control not working
The issue can be fixed by the commit below. Please help to backport it to xenial. commit 2b28b00a7e9ef21d3b94277e517692896e46e58c Author: Hans de Goede Date: Fri Oct 14 18:25:35 2016 +0200 power: The Power.Keyboard.Brightness property is in percent -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827030 Title: Keyboard brightness control not working To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827030] Re: Keyboard brightness control not working
@Sebastien Yes. I have one project using GNOME. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827030 Title: Keyboard brightness control not working To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
** Attachment added: "1_set-delay-to-90-mins.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5260822/+files/1_set-delay-to-90-mins.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
The attached patch has been accepted by upstream. Please help to backport it to bionic and xenial. ** Patch added: "0001-power-correct-the-value-of-90-minutes-to-5400.patch" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5260824/+files/0001-power-correct-the-value-of-90-minutes-to-5400.patch ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/bionic Importance: Undecided Status: New ** Also affects: oem-priority/xenial Importance: Undecided Status: New ** Changed in: oem-priority/bionic Importance: Undecided => High ** Changed in: oem-priority/xenial Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
** Attachment added: "2_value-is-80-after-reopen-power-settings.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5260823/+files/2_value-is-80-after-reopen-power-settings.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827346] [NEW] Power: Fail to set delay time when the value is 90 minutes
Public bug reported: [Impact] Power: Fail to set delay time when the value is 90 minutes [Test Case] 1) Go to [All Settings][Power][Automatic suspend] 2) Set delay time to 90 minutes (On Battery Power or Plugged in) 3) Close [All Settings] 4) Reopen [All Settings][Power][Automatic suspend] 5) The value of delay time is 80 minutes ** Affects: oem-priority Importance: High Status: New ** Affects: oem-priority/bionic Importance: High Status: New ** Affects: oem-priority/xenial Importance: High Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/xenial Importance: Undecided Status: New ** Also affects: oem-priority/bionic Importance: Undecided Status: New ** Changed in: oem-priority/bionic Importance: Undecided => High ** Changed in: oem-priority/xenial Importance: Undecided => High ** No longer affects: oem-priority ** No longer affects: oem-priority/bionic ** No longer affects: oem-priority/xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
@Sebastien The description has been updated. ** Description changed: [Impact] - Power: Fail to set delay time when the value is 90 minutes + Fail to set delay time when the value is 90 minutes. + + In cc-power-panel.ui, the value of 90 minutes is 4800 (80*60), not 5400 + (90*60). When setting the delay time to 90 minutes, the UI will show "80 + minutes" after reopening "All Settings". (Please refer to the photo in + #1 and #2) [Test Case] 1) Go to [All Settings][Power][Automatic suspend] 2) Set delay time to 90 minutes (On Battery Power or Plugged in) 3) Close [All Settings] 4) Reopen [All Settings][Power][Automatic suspend] - 5) The value of delay time is 80 minutes + 5) Check if the value is 90 minutes. + + [Regression Potential] + + Low. The value of 90 minutes is wrong. Just correct the value to 5400. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
** Patch added: "xenial.diff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5261103/+files/xenial.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
** Patch added: "bionic.diff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5261104/+files/bionic.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
** Patch added: "disco.diff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5261105/+files/disco.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
@Sebastien Please check the diff for xenial as attached. ** Patch added: "xenial.diff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1827346/+attachment/5261724/+files/xenial.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824073] Re: USB stick isn't mounted automatically
** Changed in: oem-priority/xenial Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824073 Title: USB stick isn't mounted automatically To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824073] Re: USB stick isn't mounted automatically
** Patch added: "Do-not-add-new-drive-object-on-change-uevent.patch" https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1824073/+attachment/5256478/+files/Do-not-add-new-drive-object-on-change-uevent.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824073 Title: USB stick isn't mounted automatically To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824073] Re: USB stick isn't mounted automatically
@Sebastien Please check the attached file. ** Patch added: "0001-New-upstream-bug-fix-release.patch" https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1824073/+attachment/5256492/+files/0001-New-upstream-bug-fix-release.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824073 Title: USB stick isn't mounted automatically To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
The issue is gone after upgrading gnome-control-center. --- Bionic: ubuntu-18.04.2-desktop-amd64.iso Xenial: ubuntu-gnome-16.04.5-desktop-amd64.iso ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770565] Re: [i915_bpo] Fix flickering issue after panel change
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770565 Title: [i915_bpo] Fix flickering issue after panel change To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1770565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770565] Re: [i915_bpo] Fix flickering issue after panel change
Need special instrument to verify this issue. ODM verified the following patch in their lab and got positive test result. UBUNTU: Ubuntu-4.4.0-128.154 commit 2d19b35bc9773eb4de54b6104bfec79814f930db Author: Ville Syrjälä Date: Fri May 11 08:21:00 2018 +0200 drm/i915: Ignore OpRegion panel type except on select machines -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770565 Title: [i915_bpo] Fix flickering issue after panel change To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1770565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1639896 Title: Backport support for AMD Polaris To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1639896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694665] Re: [DP MST] No audio output through HDMI/DP/mDP ports in Dell WD15 and TB15 docking stations
@klebers There is still no HDMI/DP/mDP audio output after enabling xenial- proposed. Test environment: 1) The installed packages (online update): log_0615-1/history.log 2) $ lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial 3) Kernel 4.11.0-041100rc8-generic: can see HDMI/DP/mDP audio output 4.4.0-79-generic: no HDMI/DP/mDP audio output 4.4.0-80-generic: no HDMI/DP/mDP audio output For details, please check log_0615-1/*.png ** Attachment added: "screenshot, apt log, dkms status, pactl list" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694665/+attachment/4896234/+files/log_0615-1.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694665 Title: [DP MST] No audio output through HDMI/DP/mDP ports in Dell WD15 and TB15 docking stations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694665] Re: [DP MST] No audio output through HDMI/DP/mDP ports in Dell WD15 and TB15 docking stations
@Hui Wang, I ran Software Updater, but there was no 0616 in PPA. I downloaded the package from the link below, and installed it manually. oem-audio-hda-daily-dkms (0.201706180301~ubuntu16.04.1) https://launchpad.net/~ubuntu-audio-dev/+archive/ubuntu/alsa-daily/+packages I can see HDMI/Display Port in [All Settings][Sound] after installing the package. $ uname -r 4.4.0-80-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694665 Title: [DP MST] No audio output through HDMI/DP/mDP ports in Dell WD15 and TB15 docking stations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727401 Title: Corruption on windowed 3D apps running on dGPU (Intel/AMD) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1727401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727401 Title: Corruption on windowed 3D apps running on dGPU (Intel/AMD) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1727401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727401 Title: Corruption on windowed 3D apps running on dGPU (Intel/AMD) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1727401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727401 Title: Corruption on windowed 3D apps running on dGPU (Intel/AMD) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1727401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734278] Re: Grub2 cannot boot up when 8254 time function disable
System can boot to Ubuntu desktop (artful) after installing following packages. Installed packages: grub2-common_2.02_beta3-4ubuntu7.1_amd64.deb grub-common_2.02_beta3-4ubuntu7.1_amd64.deb grub-efi-amd64_2.02_beta3-4ubuntu7.1_amd64.deb grub-efi-amd64-bin_2.02_beta3-4ubuntu7.1_amd64.deb grub-efi-amd64-signed_1.85.1+2.02_beta3-4ubuntu7.1_amd64.deb Image: ubuntu-17.10-desktop-amd64.iso -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734278 Title: Grub2 cannot boot up when 8254 time function disable To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1734278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734278] Re: Grub2 cannot boot up when 8254 time function disable
** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734278 Title: Grub2 cannot boot up when 8254 time function disable To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1734278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589889 Title: Bluetooth search gets nothing on Dell XPS 15 9550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1589889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589889 Title: Bluetooth search gets nothing on Dell XPS 15 9550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1589889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 172937] Re: SQUASHFS error while booting from live cd
I have also encountered this issue with a SanDisk USB 3.0 drive. And, this workaround works for me. http://forums.sandisk.com/t5/ratings/ratingdetailpage/message-uid/342584/rating-system/message_ratings -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/172937 Title: SQUASHFS error while booting from live cd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/172937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511301] Re: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.
@Alberto fglrx 2:14.101-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511301 Title: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1511301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714178] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941762/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714178] Re: Triple monitor display failed with Dell Dock (HiDPI) (modesetting)
apport information ** Tags added: apport-collected compiz-0.9 ubuntu xenial ** Description changed: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi + --- + .tmp.unity_support_test.0: + + ApportVersion: 2.20.1-0ubuntu2.10 + 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 + CurrentDesktop: Unity + DistUpgraded: Fresh install + DistributionChannelDescriptor: + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-xenial-amd64-20160624-2 + DistroCodename: xenial + DistroRelease: Ubuntu 16.04 + DistroVariant: ubuntu + ExtraDebuggingInterest: Yes + GraphicsCard: + Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) +Subsystem: Dell Device [1028:07bf] +Subsystem: Dell Device [1028:07bf] + InstallationDate: Installed on 2017-08-29 (2 days ago) + InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 + MachineType: Dell Inc. Precision 5520 + Package: xorg-server (not installed) + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 + Tags: xenial ubuntu compiz-0.9 + Uname: Linux 4.11.0-14-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/08/2017 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.3.3 + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: + dmi.product.name: Precision 5520 + dmi.sys.vendor: Dell Inc. + version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 + version.ia32-libs: ia32-libs N/A + version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 + version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 + version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A + version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 + version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 + version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 + version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941759/+files/BootLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714178] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941760/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714178] GconfCompiz.txt
apport information ** Attachment added: "GconfCompiz.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941763/+files/GconfCompiz.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714178] LightdmDisplayLog.txt
apport information ** Attachment added: "LightdmDisplayLog.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941765/+files/LightdmDisplayLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714178] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941775/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714178] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941774/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714178] LightdmLog.txt
apport information ** Attachment added: "LightdmLog.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941766/+files/LightdmLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714178] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941767/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714178] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941771/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714178] DkmsStatus.txt
apport information ** Attachment added: "DkmsStatus.txt" https://bugs.launchpad.net/bugs/1714178/+attachment/4941761/+files/DkmsStatus.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714178] Re: Triple monitor display failed with Dell Dock (HiDPI) (modesetting)
** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+attachment/4941782/+files/Screenshot%20from%202017-08-31%2015-26-31.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1714178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
