[Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd

** Changed in: oem-priority Assignee: (unassigned) => Cyrus Lien (cyruslien) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesy

[Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd

** Tags added: oem-priority originate-from-1933586 wenshan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd To manage

[Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure

@Daniel @Timo, I fund the root cause of my X crash issue, which is not same as this bug. Please ignore my comments and thanks for your response. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918855

[Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure

I encountered exactly same issue as this bug on bionic so I would like to leverage iris fix (iris-avoid-abort-if-enomem.diff) but bionic mesa prefer i965 by default over iris. Do I need to file a new one on mesa/i965 driver? Aug 3 03:12:39 u-Vostro /usr/lib/gdm3/gdm-x-session[1864]: (EE)

[Bug 1918855] Re: Xorg crashed with SIGABRT when under memory pressure

@Timo, In bionic mesa (20.0.8-0ubuntu1~18.04.1) it prefer i965 by default over iris. rules: confflags_GALLIUM += -Dprefer-iris=false Is it available to enable iris by default in bionic? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1920204] Re: [MIR] oem-somerville-warcraft-intel-meta

Verified passed. Test steps: 1. install a focal, upgrade the whole os, on the target machine. 2. turned on proposed. 3. sudo ubuntu-drivers install 4. sudo reboot 5. sudo apt update 6. sudo apt upgrade It does install the bootstrap meta oem-somerville-warcraft-intel-meta (20.04~ubuntu1)

[Bug 1920204] Re: [MIR] oem-somerville-warcraft-intel-meta

Attach oem-somerville-warcraft-intel-meta_20.04~ubuntu1.debdiff by oem- scripts 1.6. ** Patch removed: "oem-somerville-warcraft-intel-meta_20.04~ubuntu1.debdiff" https://bugs.launchpad.net/bugs/1920204/+attachment/5514611/+files/oem-somerville-warcraft-intel-meta_20.04~ubuntu1.debdiff **

[Bug 1920204] Re: [MIR] oem-somerville-warcraft-intel-meta

Attach oem-somerville-warcraft-intel-meta_20.04~ubuntu1.debdiff by oem- scripts 1.6. ** Patch added: "oem-somerville-warcraft-intel-meta_20.04~ubuntu1.debdiff" https://bugs.launchpad.net/bugs/1920204/+attachment/5514611/+files/oem-somerville-warcraft-intel-meta_20.04~ubuntu1.debdiff ** Tags

[Bug 1920204] Re: [MIR] oem-somerville-warcraft-intel-meta

** Summary changed: - [DRAFT][MIR] oem-somerville-warcraft-intel-meta + [MIR] oem-somerville-warcraft-intel-meta ** Description changed: - [DRAFT][Availability] + [Background] + + Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and +

[Bug 1883839] Re: [MIR] oem-somerville-beric-icl-meta

Test procedure: 1. install a focal, upgrade the whole os, on the target machine. 2. turned on proposed. 3. sudo ubuntu-deriver install It does install the bootstrap meta (oem-somerville-beric-icl-meta 20.04~ubuntu1) automatically. Given it install new source list, then get the index from new

[Bug 1883839] Re: [MIR] oem-somerville-beric-icl-meta

** Also affects: 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/1883839 Title: [MIR] oem-somerville-beric-icl-meta To manage notifications about

[Bug 1883839] [NEW] [MIR] oem-somerville-beric-icl-meta

ce package in the archive. ** Affects: oem-priority Importance: High Assignee: Cyrus Lien (cyruslien) Status: Confirmed ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High ** Changed in:

[Bug 1872034] Re: [Focal] No HDMI output through thunderbolt docking station

** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1872034] Re: [Focal] No HDMI output through thunderbolt docking station

Can not reproduce the issue with drm-tip kernel (#3). ** Attachment added: "dmesg-5.5.0-rc1-drm-tip.log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1872034/+attachment/5355435/+files/dmesg-5.5.0-rc1-drm-tip.log ** Changed in: oem-priority Status: New => Triaged --

[Bug 1872034] Re: [Focal] No HDMI output through thunderbolt docking station

The issue only reproduced on first thunderbolt port which next to escape key. The external monitor doesn't lit up even though xrandr shows it is connected. Switching output modes by hotkey or GUI doesn't help. xrandr output: ... DP-2-3 connected 1920x1080+0+0 ... ** Attachment added:

[Bug 1872034] Re: [Focal] No HDMI output through thunderbolt docking station

The issue only reproduced on first thunderbolt port which next to escape key. ** Attachment added: "dmesg-5.4.0-21-switch-fail.log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1872034/+attachment/5355433/+files/dmesg-5.4.0-21-switch-fail.log -- You received this bug

[Bug 1872034] Re: [Focal] No HDMI output through thunderbolt docking station

@Gavin, Would you please try the drm-tip kernel with drm debug option "drm.debug=0xe log_buf_len=4M" ? Also, please provide the output of `fwupdmgr get-devices`. ** Attachment added: "drm-tip-5.5.0-rc1.tgz"

[Bug 1852691] Re: Disable touchscreen gesture

affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Assignee: (unassigned) => Cyrus Lien (cyruslien) -- You received

[Bug 1852691] Re: Disable touchscreen gesture

** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Cyrus Lien (cyruslien) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed ** T

[Bug 1839818] Re: System won't enter suspend after idle over 20 minutes (TSC unstable)

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1030.34 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840239/comments/17 ** Changed in: oem-priority Status: Confirmed => Fix Released ** Changed in: linux-oem (Ubuntu) Status: New => Fix Released -- You received

[Bug 1852691] Re: Disable touchscreen gesture

Need revert commit 53abe85 for Disco, Eoan 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/1852691 Title: Disable touchscreen gesture To manage notifications about this bug go to:

[Bug 1852691] Re: Disable touchscreen gesture

debdiff for bionic ** Patch added: "xf86-input-wacom_0.36.1-0ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1852691/+attachment/5305542/+files/xf86-input-wacom_0.36.1-0ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu

[Bug 1852691] [NEW] Disable touchscreen gesture

Public bug reported: [Impact] Wacom touchscreen doesn't works well when in-driver gesture was enabled (lp: 1774242), the issue can be fixed by disabling in-driver gestures for touchscreens. Config file that instructs driver to disable in-driver gestures for touchscreens: # Prevent the Wacom

[Bug 1845285] Re: SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu 18.04

** Changed in: oem-priority Status: Confirmed => Invalid ** Changed in: oem-priority/bionic Status: Confirmed => Invalid ** Changed in: xf86-input-wacom (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1845285] Re: SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu 18.04

** Changed in: oem-priority/bionic Status: New => Confirmed ** Changed in: oem-priority/bionic Importance: Undecided => High ** Changed in: oem-priority/bionic Assignee: (unassigned) => Cyrus Lien (cyruslien) -- You received this bug notification because you are

[Bug 1845285] Re: SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu 18.04

** Also affects: oem-priority/bionic 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/1845285 Title: SRU request: Include xf86-input-wacom -

[Bug 1845285] Re: SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu 18.04

tatus: New ** Changed in: oem-priority Assignee: (unassigned) => Cyrus Lien (cyruslien) ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of

[Bug 1845285] [NEW] SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu 18.04

Public bug reported: SRU Request: [Impact] xf86-input-wacom version 1:0.36.1-0ubuntu1 shipped /usr/share/X11/xorg.conf.d/70-wacom.conf has this: Section "InputClass" Identifier "Wacom touchscreen class" MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4" MatchDevicePath

[Bug 1839818] Re: System won't enter suspend after idle over 20 minutes (TSC unstable)

** Changed in: oem-priority Assignee: (unassigned) => Cyrus Lien (cyruslien) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed ** Description changed: Summary: System won't enter suspend after idle over 2

[Bug 1839818] Re: System won't enter suspend after idle over 20 minutes (TSC unstable)

** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839818 Title: System won't enter suspend after idle over 20 minutes (TSC unstable) To manage notifications about this bug

[Bug 1839818] [NEW] System won't enter suspend after idle over 20 minutes (TSC unstable)

Public bug reported: Summary: System won't enter suspend after idle over 20 minutes Steps to reproduce: 1. install manifest and boot into OS 2. idle system for 20 mins Expected result: System could enter suspend after idle over 20 minutes Actual result: System won't enter suspend after idle

[Bug 1834603] Re: SRU request: Include the 430 driver in Ubuntu 18.04

** Changed in: oem-priority Assignee: (unassigned) => Cyrus Lien (cyruslien) ** Changed in: oem-priority/bionic Status: New => Fix Released ** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Ub

[Bug 1834603] Re: SRU request: Include the 430 driver in Ubuntu 18.04

Tried version 430.26-0ubuntu0.18.04.2, it works great. ** 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/1834603

[Bug 1836619] [NEW] Preseed "partman-ext3/lazy_itable_init boolean false" can not disable lazy_itable_init

Public bug reported: Preseed "partman-ext3/lazy_itable_init boolean false" can not disable lazy_itable_init it is due to mkfs.ext4/mkfs.ext3 default enabled lazy_itable_init option. ** Affects: partman-ext3 (Ubuntu) Importance: Undecided Status: New ** Patch added:

[Bug 1834603] Re: SRU request: Include the 430 driver in Ubuntu 18.04

Also, 71-nvidia.rules need additional rule or it will stuck at gdm3 login window. Compare to nvidia-kernel-common-430 (430.26-0ubuntu0~gpu18.10.1) from ppa:graphics-drivers/ppa. diff a/lib/udev/rules.d/71-nvidia.rules b/lib/udev/rules.d/71-nvidia.rules 27,29d26 < # This will create the

[Bug 1834603] Re: SRU request: Include the 430 driver in Ubuntu 18.04

Got dependency problem with 18.04 HWE stack. $ sudo dpkg -i xserver-xorg-video-nvidia-430_430.26-0ubuntu0.18.04.1_amd64.deb (Reading database ... 135894 files and directories currently installed.) Preparing to unpack xserver-xorg-video-nvidia-430_430.26-0ubuntu0.18.04.1_amd64.deb ... Unpacking

[Bug 1834603] [NEW] SRU request: Include the 430 driver in Ubuntu 18.04

Public bug reported: SRU Request: [Impact] The nvidia packages in Ubuntu 18.04 do not support recent NVIDIA GPUs. ([10de:2191][10de:1f91][10de:1c91] [Test Case] 1) Enable the bionic-proposed repository, and install the nvidia-430 package 2) Restart and see if the system boots correctly. If

[Bug 1821194] WifiSyslog.txt

apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248432/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821194

[Bug 1821194] IwConfig.txt

apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248418/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821194

[Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout

ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 3364 F pulseaudio /dev/snd/controlC0: u 3364 F pulseaudio DistributionChannelDescriptor: # This is the distribution channel

[Bug 1821194] PulseList.txt

apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248429/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821194

[Bug 1821194] ProcModules.txt

apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248427/+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/1821194

[Bug 1821194] Lsusb.txt

apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248420/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title:

[Bug 1821194] RfKill.txt

apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248430/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title:

[Bug 1821194] ProcCpuinfo.txt

apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248421/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821194

[Bug 1821194] CurrentDmesg.txt

apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248417/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1821194] AlsaInfo.txt

apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248415/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821194

[Bug 1821194] UdevDb.txt

apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248431/+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/1821194 Title:

[Bug 1821194] ProcCpuinfoMinimal.txt

apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248422/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1821194] CRDA.txt

apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248416/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title:

[Bug 1821194] ProcInterrupts.txt

apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248424/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1821194] Lspci.txt

apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1821194/+attachment/5248419/+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/1821194 Title:

[Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout

The directory /var/crash is empty. ** Attachment added: "frozenjournal.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1821194/+attachment/5248393/+files/frozenjournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout

** Attachment added: "frozendmesg.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1821194/+attachment/5248375/+files/frozendmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1794656] [NEW] Airplane mode permanently off if quickly switch on/off by airplane mode key

Public bug reported: Airplane mode permanently off if quickly switch on/off by airplane mode key. Steps to reproduce: 1. Switch on and off Airplane mode by pressing Fn+Home(wireless key) very quickly (about 10 times per second). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package:

[Bug 1794656] Re: Airplane mode permanently off if quickly switch on/off by airplane mode key

Can not reproduce it on gnome-settings-daemon(3.30.0-0ubuntu1). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794656 Title: Airplane mode permanently off if quickly switch on/off by airplane

[Bug 1773268] Re: locked out of system when upgrading to bionic from xenial

Apport output attached. ** Attachment added: "apport.lightdm.je6ylqei.apport" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1773268/+attachment/5146513/+files/apport.lightdm.je6ylqei.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1773291] [NEW] gnome-session fail-whale is dead and gdm3 won't start on upgrade to bionic beaver

Public bug reported: May 24 20:02:54 beehive gnome-screensav[2382]: Couldn't get presence status: The name org.gnome.SessionManager was not provided by any .service files May 24 20:02:54 beehive dbus-daemon[1751]: [session uid=112 pid=1751] Successfully activated service 'org.gnome.ScreenSaver'

[Bug 1773268] [NEW] locked out of system when upgrading to bionic from xenial

Public bug reported: I was attempting to upgrade to bionic from xenial using do-release- upgrade but forgot to turn off screen locking. After an hour of inactivity, I ended up at the login screen but the keyboard won't allow me to enter keys in the login window and clicking the field results in a

[Bug 1759303] Re: Update Aquantia driver to fix various issues

@Time, Backporting those patches are request from our customer and we really have no idea how to verify those fixes. Is there any way to keep those fixes ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1768906] Re: Xorg crash

*** This bug is a duplicate of bug 1543192 *** https://bugs.launchpad.net/bugs/1543192 It's not clear that there's an actual crash here, but rather maybe that gdm3 can't acquire modesetting permission and can't find a display to work with. Not sure that's going to trigger an actual crash.

[Bug 1768906] Re: Xorg crash

Well, I tried the workaround, switched to gdm3 and was able to trigger the problem, but nothing (new) appears in /var/crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768906 Title: Xorg crash

[Bug 1768906] Re: Xorg crash

Perhaps the folks from bug 994921 should reconsider the WON'T Fix... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768906 Title: Xorg crash To manage notifications about this bug go to:

[Bug 1768906] Re: Xorg crash

** Package changed: xorg (Ubuntu) => gdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768906 Title: Xorg crash To manage notifications about this bug go to:

[Bug 1768906] Re: Xorg crash

Switching to lightdm instead of gdm3 gets around the problem. Should I change the component to gdm3? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768906 Title: Xorg crash To manage notifications

[Bug 1748656] Re: Black Screen of Death after logging into Ubuntu Bionic: "Failed to acquire modesetting permission"

I'm wondering if this could be related to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768906 Might it make sense to unexpire this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748656

[Bug 1768906] Re: Xorg crash

I am able to reproduce this following a reinstall of 18.04 from the ISO image, but only on the same box. No problems on two other computers. Will try reverting to 17.10 to see if that fixes the problem. As for the component, can I test with alternative session managers, or is gdm3 the only game

[Bug 1769310] [NEW] "bootloader install failed" dialog box broken

Public bug reported: On attempting to update to 18.04, and running into problems with my Ubuntu video card, I decided to try to reinstall the OS, booting from a USB formatted with the 18.04 ISO image. So far so good, until I got to the the "bootloader install failed" dialog box. Unfortunately, no

[Bug 1768906] Re: Xorg crash

This happens with all combination of (bionic-ish) kernels and drivers I've tried so far, including: Drivers: NVIDIA proprietary installer 396.24, nvidia-driver-396 (396.24-0ubuntu0~gpu18.04.1), nvidia-390 (390.48-0ubuntu3+gpu18.04.2) kernels: 4.15.0-20-lowlatency, a locally built 4.16.3 cards:

[Bug 1768906] Re: Xorg crash

I'm not exactly clear what you mean by purging and settings removal. I've run uninstall with the proprietary driver (and rebooted) I've used nvidia-driver-396 and apt-cache remove --purge'd that. I've tried to video cards now. In short, I've tried everything I can think of, but still end up with

[Bug 1768906] Re: Xorg crash

Same symptoms with a brand new GTX 1070 ti :( ** Changed in: xorg (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768906 Title: Xorg crash To manage

[Bug 1768906] Re: Xorg crash

Should I set this back to new? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768906 Title: Xorg crash To manage notifications about this bug go to:

[Bug 1768906] Re: Xorg crash

Same thing happens with nvidia-346. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768906 Title: Xorg crash To manage notifications about this bug go to:

[Bug 1768906] [NEW] Xorg crash

Public bug reported: When attempting to log in to a newly updated bionic beaver via the display manager (I think this is the right term), I immediately see a crash, a return to the user selection/login screen and a no-longer functioning keyboard and mouse. This happens both with the proprietary

[Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

Confirmed, the issue was gone with firmware from https://askubuntu.com/a/1029749/95109. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) To

[Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

Will escalate this issue to Qualcomm. ** Changed in: dell-sputnik 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/1766825 Title: Bluetooth issues with Dell XPS 13

[Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

A quick workaround is rmmod btusb before suspend and insert btusb after resume. To do this, you can put a executable script of any name in /lib/systemd/system-sleep/. Example: #!/bin/sh if [ "$1" = "pre" ]; then systemctl stop bluetooth && rmmod btusb elif [ "$1" = "post" ]; then modprobe

[Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

I can reproduce it only on AC mode. Still can reproduce it after disable tlp. kernel: 4.4.0-100 BIOS: 1.2.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell

[Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

** Attachment added: "collect-log.sh" https://bugs.launchpad.net/dell-sputnik/+bug/1766825/+attachment/5127476/+files/collect-log.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title:

[Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

@Felix, Also, need more system information. Please execute attached script by `sudo collect-log.sh' to collect more system information and attach debuglog.tgz here. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

The kernel is 4.4.0-121-generic(#4), I though it was solved on kernel version >= 4.4.0-93.116. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell XPS 13 (9370)

[Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

@Felix, Would you please try this issue on kernel 4.4.0-93.117 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) To manage notifications

[Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)

** Changed in: dell-sputnik Status: New => Confirmed ** Changed in: dell-sputnik Importance: Undecided => Critical ** Changed in: dell-sputnik Assignee: (unassigned) => Cyrus Lien (cyruslien) -- You received this bug notification because you are a member of Ubuntu Bu

[Bug 1664602] Re: Using an NVMe drive causes huge power drain

Verified on 4.4.0-117-generic, APST was enabled. #sudo nvme get-feature -f 0x0c -H /dev/nvme0n1 get-feature:0x0c (Autonomous Power State Transition), Current value: 0x01 Autonomous Power State Transition Enable (APSTE): Enabled Auto PST Entries.

[Bug 1510570] Re: Bluetooth LE pairing fail

With bluez 5.37-0ubuntu5.2 Designer keyboard still can not connect on 4.13.0-32-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: Bluetooth LE pairing fail To manage

[Bug 1510570] Re: Bluetooth LE pairing fail

Designer keyboard still can not connect on 4.13.0-32-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: Bluetooth LE pairing fail To manage notifications about this bug go to:

[Bug 1510570] Re: Bluetooth LE pairing fail

Verified bluez 5.37-0ubuntu5.2 from -proposed, designer mouse works but designer keyboard failed. To fully support BT LE, looks like we need to upgrade bluez >5.44. (verified bluez 5.46-0ubuntu4~somerville1 which comes form artful can make designer keyboard works) -- You received this bug

[Bug 1480673] Re: [ELAN 3320KD-3100] Asus T300 CHI bluetooth Touchpad is recognized incorrectly

Touchpad multitouch works on 4.15-rc8 kernel but need blacklist hid- generic. $xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad

[Bug 1480673] Re: [ELAN 3320KD-3100] Asus T300 CHI bluetooth Touchpad is recognized incorrectly

Below commits should be related. commit 73c75d395857960ea135913da7bb9537248a11e6 Author: Hans de Goede Date: Fri Aug 4 15:31:04 2017 +0200 HID: asus: Add T100CHI bluetooth keyboard dock touchpad support Put the touchpad in native (absolute coordinate mode)

[Bug 1107935] Re: Support for WPA Enterprise wireless networks

** Changed in: oem-priority/xenial Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1107935 Title: Support for WPA Enterprise wireless networks To manage

[Bug 1107935] Re: Support for WPA Enterprise wireless networks

Verified image (serial 20171101), the issue was fixed. The package name and version in the image are: network-manager-gnome 1.2.6-0ubuntu0.16.04.4 ubiquity 2.21.63.5 ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification

[Bug 1716369] Re: ubiquity crashes once user double click wpa enterprise access point in network manager widget

Tried Artful daily build, the WPA Enterprise behavior works very well. Need backport wpa enterprise support to xenial. ** Changed in: oem-priority Status: Confirmed => Invalid ** Changed in: ubiquity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification

[Bug 1716369] Re: ubiquity crashes once user double click wpa enterprise access point in network manager widget

https://code.launchpad.net/~cyruslien/ubiquity/fix-1716369/+merge/330559 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716369 Title: ubiquity crashes once user double click wpa enterprise access

[Bug 1716369] Re: ubiquity crashes once user double click wpa enterprise access point in network manager widget

** Attachment added: "_usr_lib_ubiquity_bin_ubiquity.0.crash" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1716369/+attachment/4947858/+files/_usr_lib_ubiquity_bin_ubiquity.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1716369] Re: ubiquity crashes once user double click wpa enterprise access point in network manager widget

Adding exception handling can prevent crashing, but the question is how to connect to wpa enterprise network during installation ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716369 Title:

[Bug 1716369] [NEW] ubiquity crashes once user double click wpa enterprise access point in network manager widget

Public bug reported: During wireless configuration, ubiquity crashes once double click SSID which is a wpa-enterprise access pointer.  Traceback (most recent call last):    File "/usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py", line 170, in row_activated  

[Bug 1702685] Re: No wifi connectivity with kernel 4.4.0-83 if ath9k-msi dkms is installed

Need to confirm the issue on correct platform before online update verify. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702685 Title: No wifi connectivity with kernel 4.4.0-83 if ath9k-msi dkms

[Bug 1702685] Re: No wifi connectivity with kernel 4.4.0-83 if ath9k-msi dkms is installed

[168c:0042] DW1810 [168c:0036] DW1707 #8 is incorrect platform as bug reported, the manifest for #8 platform doesn't include ath9k-msi dkms. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702685

[Bug 1702685] Re: No wifi connectivity with kernel 4.4.0-83

** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Assignee: (unassigned) => Shih-Yuan Lee (fourdollars) -- You

[Bug 1686061] Re: Precision Rack failed to resume from S4

Test case: fwts --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120 --s4-multiple=30 Result: Pass S4 hibernate/resume test 30 cycles. ** Attachment added: "results.log" https://bugs.launchpad.net/hwe-next/+bug/1686061/+attachment/4887168/+files/results.log ** Tags removed:

  1   2   3   4   5   6   >