from:"Kent"

@Erich,

Correct, those 2 items were "Not" checked.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941620

Title:
  System still install update packages even uncheck "Download
  updates..." during install OS Edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1941620/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1941620] Re: System still install update packages even uncheck "Download updates..." during install OS Edit

@Erich,

Why this is expected?
The user downloads the Ubuntu 20.04.02 image from 
https://releases.ubuntu.com/20.04/.
The image was built at 2021-02-09 19:07.
The user disables the following in ubiquity while installation. Why all the 
update packages will still be updated when installation?
1. "Download updates while installing Ubuntu"
2. "Install third-party software for graphics and WiFi hardware and additional 
media formats"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941620

Title:
  System still install update packages even uncheck "Download
  updates..." during install OS Edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1941620/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1941620] Re: System still install update packages even uncheck "Download updates..." during install OS Edit

** Changed in: ubiquity (Ubuntu)
   Status: Fix Released => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941620

Title:
  System still install update packages even uncheck "Download
  updates..." during install OS Edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1941620/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1941620] Re: System still install update packages even uncheck "Download updates..." during install OS Edit

** Attachment added: "dpkg_list_wo_network.txt"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1941620/+attachment/5520541/+files/dpkg_list_wo_network.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941620

Title:
  System still install update packages even uncheck "Download
  updates..." during install OS Edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1941620/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1941620] Re: System still install update packages even uncheck "Download updates..." during install OS Edit

** Attachment added: "dpkg_list_with_network.txt"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1941620/+attachment/5520540/+files/dpkg_list_with_network.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941620

Title:
  System still install update packages even uncheck "Download
  updates..." during install OS Edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1941620/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1941620] [NEW] System still install update packages even uncheck "Download updates..." during install OS Edit

Public bug reported:

Steps to repro:
1. Connect to the internet and install ubuntu-20.04.2.0-desktop-amd64.iso.
2. In the "Updates and other software" page, select "Normal installation", 
uncheck "Download updates while..." and "Install third-party...".
3. While the system shows "Installation Complete", remove the LAN cable.
4. Reboot system then login, execute "dpkg --list".

Expected results:
The system did not install any update packages.

Actual results:
The system installed update packages.

Please review the attachment.
While connecting to the internet during installation, the system installed 
linux-image-5.11.0-27-generic and other update packages.
If we don't connect to the internet during installation, the linux-image is 
5.8.0-43.

** Affects: ubiquity (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/1941620

Title:
  System still install update packages even uncheck "Download
  updates..." during install OS Edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1941620/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

2021-08-24 Thread Kent Lin

Test pass with Dell DW5821e [413C:81D7] on hirsute

* The version of the packages tested:
   ModemManager: 1.16.6
   libmbim: 1.24.8
   libqmi: 1.28.6

** Attachment added: "DW5821e.log"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1934286/+attachment/5520406/+files/DW5821e.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934286

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934286/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938678] Re: [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on TGL-H

2021-08-17 Thread Kent Lin

@sachinmokashi,

SM3 is forbidden to ship to some countries. Why Intel will not provide
the option to disable it in BIOS?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938678

Title:
  [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on
  TGL-H

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1938678/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1936899] Re: [IoTG] [TGL-H] TPM tests fail

2021-08-10 Thread Kent Lin

** Also affects: linux-intel (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/1936899

Title:
  [IoTG] [TGL-H] TPM tests fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1936899/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1936903] Re: CDTS Network (Ethernet) failures

2021-08-06 Thread Kent Lin

** Also affects: ubuntu
   Importance: Undecided
   Status: New

** Also affects: linux-intel (Ubuntu)
   Importance: Undecided
   Status: New

** Tags removed: tgl-h
** Tags added: iotg-tgl-h

** Tags removed: iotg-tgl-h
** Tags added: tglh-iotg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936903

Title:
  CDTS Network (Ethernet) failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1936903/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

2021-07-23 Thread Kent Lin

Test Pass on
WWAN Test: 
https://certification.canonical.com/hardware/202010-28324/submission/223136/
ACPI Stress Test: 
https://certification.canonical.com/hardware/202010-28324/submission/223167/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934286

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934286/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

2021-07-20 Thread Kent Lin

Test pass on
https://certification.canonical.com/hardware/202010-28320/submission/223095/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934286

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934286/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1864764] Re: [EGL] enable intel_idle for Eagle Stream

2021-04-23 Thread Kent Lin

** Tags added: egl

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864764

Title:
  [EGL] enable intel_idle for Eagle Stream

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1864764/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875706] Re: ERROR: xsane-startimage not found.

2021-02-21 Thread Kent Svensson

Have the same problem: (Ubuntu 20.04)
[xsane] ERROR: xsane-startimage not found. Looks like xsane is not installed 
correct.

The above workaround (from Krzysztof Śmigrodzki) was like this for me:

sudo mkdir -p /usr/share/sane/xsane (no problem)
sudo ln -t /usr/share/sane/xsane /usr/share/doc/xsane-common/*.pnm (no problem)

/usr/share/doc/xsane-common/*.rc /usr/share/doc/xsane-common/*.xpm
bash: /usr/share/doc/xsane-common/xsane-icon.rc: Access denied

sudo /usr/share/doc/xsane-common/*.rc /usr/share/doc/xsane-common/*.xpm
sudo: /usr/share/doc/xsane-common/xsane-icon.rc: command not found

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875706

Title:
  ERROR: xsane-startimage not found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xsane/+bug/1875706/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1913855] [NEW] Failure to pass system check and present login screen

2021-01-29 Thread Kent Lion

Public bug reported:

I'm reporting this against xorg, because of where the problem occurs, as
indicated below, I can't tell if the problem is with xorg, lightdm or
light-locker. The system is a Dell Optiplex 745 single-booting to
Xubuntu 20.04 up-to-date as of today.

I replaced one of 2 monitors, the one rotated to portrait orientation, with a 
higher resolution monitor. Started the system, logged in as another user and 
changed the desktop background however, when I then logged out and restarted 
the system, it behaved normally until it displayed the usual
/dev/sda1: clean, x/x files, /x blocks
on both monitors. The prompt remained for a few seconds, slowly blinked off and 
on 6 times, and then remained with no further activity. The system works fine 
if I boot from a Xubuntu 18.04 DVD (I didn't have a 20.04 DVD, and this is the 
only machine with a burner). On another machine, I determined that the system 
was booting, because the machine was visible on the network, and its shared 
folders were accessible.

I could get to a login prompt and log on using Alt+F1 to F6. Alt-F7
returned me to the file system check prompt. I was able to start xorg
after logging on with startx, and changing all settings for the new
monitor, everything worked normally until logging out, which of course
returned me to the command line where I had given the command startx.

If I log out requesting a restart, the system reboots, but still stops at the 
same place every time. That behavior hadn't changed the next day. I can use the 
machine, but only by selecting a terminal, logging as myself or the other user 
and giving the startx command. I have been unable to find anything on the 
Internet that corrects the problem. Since the problem first started, two 
crashes have occurred and I allowed them to be reported; however, they were 
light-locker crashes. I reinstalled lightdm and light-locker, but that made no 
difference. I installed gdm3, which works fine, but switching back to lightdm 
with:
sudo dpkg-reconfigure gdm3
sudo dpkg --configure lightdm
resulted in:
dpkg: error processing package lightdm (--configure):
 package lightdm is already installed and configured
Errors were encountered while processing:
 lightdm

So I can't really be sure if the problem is with xorg, lightdm or light-
locker, but since there are no error messages and everything else works
fine, it's clearly a bug, if a strange one. I do not relish the idea of
having to reinstall Xubuntu; so for the time being, I'll use gdm3,
though I prefer lightdm's ability to properly display backdrops and use
the two monitors properly extended (with gdm3, the mouse moves down the
left portrait monitor before moving onto the right monitor where gdm3
sees fit to put the logon dialog). The next thing I'll try is
autoremoving lightdm rebooting a few times and then reinstalling it...

Because of the absence of error messages and information even suggesting
why X isn't starting, I have no idea what other information about my
system might be useful to you, but if you need something additional,
I'll try to provide it.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: XFCE
Date: Fri Jan 29 22:12:37 2021
DistUpgraded: 2020-10-20 06:56:14,405 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.16, 5.4.0-62-generic, x86_64: installed
 virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV620 LE [Radeon HD 3450] [1002:95c5] 
(prog-if 00 [VGA controller])
   Subsystem: Dell OptiPlex 980 [1028:0342]
InstallationDate: Installed on 2019-11-29 (427 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. OptiPlex 780
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic 
root=UUID=68c4f426-dc84-48e8-be0f-cd1a5acfb729 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-10-20 (101 days ago)
dmi.bios.date: 08/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0C27VV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd08/06/2013:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 780
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubunt

[Bug 1912083] [NEW] the icons are longer

2021-01-16 Thread Kent Tai

Public bug reported:

the icons are longer than they should be

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
Uname: Linux 5.8.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
BootLog: Error: [Errno 13] 拒絕不符權限的操作: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 17 11:12:46 2021
DistUpgraded: 2021-01-17 10:47:32,279 DEBUG openCache()
DistroCodename: groovy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.16, 5.8.0-36-generic, x86_64: installed
 virtualbox, 6.1.16, 5.8.0-38-generic, x86_64: installed
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company UHD Graphics [103c:86cd]
ImageMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 13d3:56c9 IMC Networks HP TrueVision HD Camera
 Bus 001 Device 002: ID 145f:021f Trust 2.4G Mouse
 Bus 001 Device 004: ID 8087:0026 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP 348 G7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=aea93e03-8fb8-49c7-8081-a18a438e7864 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to groovy on 2021-01-17 (0 days ago)
dmi.bios.date: 06/11/2020
dmi.bios.release: 15.21
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 86CD
dmi.board.vendor: HP
dmi.board.version: 98.08
dmi.chassis.asset.tag: 5CG0351KMK
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 98.8
dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd06/11/2020:br15.21:efr98.8:svnHP:pnHP348G7:pvrType1ProductConfigId:rvnHP:rn86CD:rvr98.08:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN HP Notebook
dmi.product.name: HP 348 G7
dmi.product.sku: 7HC08AV
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy third-party-packages ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912083

Title:
  the icons are longer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1912083/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900809] Re: [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to stable-v1.6

2020-12-07 Thread Kent Lin

The certification team helps to perform the test. The v1.6 firmware is good to 
go.
Test result is attached.

** Attachment added: "sof-firmware testing.xlsx"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1900809/+attachment/5441898/+files/sof-firmware%20testing.xlsx

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900809

Title:
  [SRU]sof-firmware: update the sof-firmware from version v1.4.2 to
  stable-v1.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1900809/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1889342] Re: Thunderbolt Dock Loses Monitors

2020-11-29 Thread Kent Lin

@rhpot1991,
Here you are:

https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2020-11-30/amd64/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889342

Title:
  Thunderbolt Dock Loses Monitors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897530] Re: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"

2020-11-19 Thread Kent Lin

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897530

Title:
  [modeset][nvidia] X Server session crash with "No space left on
  device" and then "EnterVT failed for gpu screen 0"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897530] Re: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"

2020-11-19 Thread Kent Lin

The comment#12 is tested on Focal.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897530

Title:
  [modeset][nvidia] X Server session crash with "No space left on
  device" and then "EnterVT failed for gpu screen 0"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897530] Re: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"

2020-11-19 Thread Kent Lin

Test WD19TB with Dell Precision 7750
Kernel: 5.6.0-1035-OEM#37
xorg-server (2:1.20.8-2ubuntu2.5)
NV driver:450.80.02

The issue is fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897530

Title:
  [modeset][nvidia] X Server session crash with "No space left on
  device" and then "EnterVT failed for gpu screen 0"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897530] Re: The modesetting driver does not gracefully handle missing connectors on EnterVT

2020-11-05 Thread Kent Lin

Original bug: https://bugs.launchpad.net/somerville/+bug/1857443

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897530

Title:
  The modesetting driver does not gracefully handle missing connectors
  on EnterVT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1889342] Re: Thunderbolt Dock Loses Monitors

2020-11-02 Thread Kent Lin

@rhpot1991,

How many monitors are connected to the dock?
What are the maximum resolutions of those monitors connected to the dock?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889342

Title:
  Thunderbolt Dock Loses Monitors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901335] [NEW] Repository version of Sigil won't run on all Ubuntu 20.04 systems.

2020-10-24 Thread Kent Lion

Public bug reported:

I doubt there's much point in asking a question about this, because a
couple of hours searching the Internet turned up nothing on this
problem, on launchpad.net or anywhere else.

When I try to run Sigil 1.1 installed from the Canonical repository on a Dell 
Optiplex GX620 running 64 bit Xubuntu 20.04 installed from an iso (because 
do-release-upgrade failed beyond repair), I get the error message:
/usr/local/lib/sigil/sigil: error while loading shared libraries: 
libpython3.6m.so.1.0: cannot open shared object file: No such file or directory

That tells me that libpython3.6m.so.1.0 doesn't exist (which it
doesn't), but on a Dell Optiplex 780 on which do-release-upgrade was
successful (but only after I completely removed gnuradio and snap),
libpython3.6m.so.1.0 also does not exist, but Sigil 1.1 works.

I found very few references to libpython3.6m.so.1.0 on the Internet,
none relating to Sigil, and none that helped (including one that
suggested installing python3-venv, which installed successfully, but
told me I needed to install python3-venv when I entered pyvenv --help or
python3-venv --help).

So I can't tell if this is a bug, or due to a capability missing from
the older GX620, or to a forgotten error message being triggered that is
no longer valid and therefore tells nothing about the error that
triggered it...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: sigil 1.1.0+dfsg-1
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Sat Oct 24 12:58:41 2020
InstallationDate: Installed on 2020-10-22 (2 days ago)
InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: sigil
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sigil (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901335

Title:
  Repository version of Sigil won't run on all Ubuntu 20.04 systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sigil/+bug/1901335/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900887] [NEW] Screensaver lock screen incomplete and doesn't work properly for mult-head setup.

2020-10-21 Thread Kent Lion

Public bug reported:

After upgrading to 20.04 on a dual monitor setup using multi-head
settings for each monitor, when I boot, the wallpaper defined for each
screen is properly displayed. When I log on, the wallpaper defined for
each screen is properly displayed in each workspace. However, when the
screensaver kicks in, the lock screen only uses the wallpaper from the
(portrait oriented) primary monitor, which doesn't fit too well on the
landscape oriented secondary monitor. Never had that problem in 18.04,
so I'm guessing the problem is that multi-head considerations were
forgotten when the screensaver was separated from the power manager for
20.04. I don't know what package the screensaver is part of.

Also, on the 18.04 startup login screen and screensaver lock screens,
moving the mouse between monitors causes the login dialog to move to the
screen that the mouse cursor is on. This does not occur with the 20.04
screensaver lock screen, though it does occur with the login screens, so
that's either an omission or a bug in the screensaver.

To reproduce the bug(s)/problems, on a dual monitor system set up so
that each monitor displays a different wallpaper when logged on and
logged off, and also from each other and in all workspaces, set the
screensaver to lock after 5 minutes or less and let it lock with the
mouse cursor left on the primary screen and then again with the mouse
cursor left on the secondary screen.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.28
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: XFCE
Date: Wed Oct 21 13:07:21 2020
InstallationDate: Installed on 2019-11-29 (327 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to focal on 2020-10-20 (1 days ago)
VarLogDistupgradeXorgFixuplog:
 INFO:root:/usr/bin/do-release-upgrade running
 INFO:root:No xorg.conf, exiting

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 dist-upgrade focal screensaver

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900887

Title:
  Screensaver lock screen incomplete and doesn't work properly for mult-
  head setup.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1900887/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1889342] Re: Thunderbolt Dock Loses Monitors

2020-10-05 Thread Kent Lin

ICL. Gen 10

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889342

Title:
  Thunderbolt Dock Loses Monitors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897530] Re: The modesetting driver does not gracefully handle missing connectors on EnterVT

2020-09-28 Thread Kent Lin

The “real” fix has been released by Intel and has also been merged.
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1010

Could Canonical consider to revert follow temporary patch.

0001-WIP-modesetting-check-the-kms-state-on-EnterVT.patch

0002-WIP-modesetting-do-not-reset-the-mode-on-disconnecte.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897530

Title:
  The modesetting driver does not gracefully handle missing connectors
  on EnterVT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897530] [NEW] The modesetting driver does not gracefully handle missing connectors on EnterVT

2020-09-28 Thread Kent Lin

Public bug reported:

Expectation: on removal of external display during S3, after resume eDP 
rendering should still continue by Nvidia.
Symptom description: Plug out DP cable when suspension, when resume, X will 
crash.

1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but 
NV was rendering for eDP.
2. After S3 entry dock was removed.
3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails 
resume of TB3 devices and logs confirm that.
4. X fails to enter VT due to Null meta mode.


To address the explanation, X is not failing to enter the VT due to NVIDIA’s 
NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the 
VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no 
displays connected to it. Our driver is pretty robust to head state changes – 
even if we have to fall back to a NULL MetaMode, we will still enter the VT 
successfully.

The logs clearly show that the failure is originating from the Intel
(modesetting) driver, not the NVIDIA driver. The relevant path in X is
driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes(). In
this function, the Intel driver tries to set a mode on each of the
previously connected/enabled displays, and it tries to find the closest
possible mode using xf86OutputFindClosestMode(). This is similar to our
driver’s functionality, but unlike us, they don’t support a NULL
fallback. If there are no modes supported on one of the displays, it
simply fails, which causes X to terminate:

DisplayModePtr mode = xf86OutputFindClosestMode(output,
pScrn->currentMode);

if (!mode)
return FALSE;

Since we removed one of the displays via the dock, it fails. It doesn’t
matter if the internal panel is still available, Intel will fail if it
can’t re-enable ANY of the previously connected displays.

Technically the modesetting driver isn’t specifically an Intel driver,
it’s a generic driver that can be used by any DRM device – it’s just
that Intel has chosen to use the modesetting driver as their standard
Linux X driver going forward.

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: xorg-server (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1010
   https://gitlab.freedesktop.org/xorg/xserver/-/issues/1010

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897530

Title:
  The modesetting driver does not gracefully handle missing connectors
  on EnterVT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896866] [NEW] All directory navigation more than a couple of levels crashes.

2020-09-23 Thread Kent Lion

Public bug reported:

A few weeks ago Thunar started crashing when I tried to navigate any
more than 2 or 3 levels from the folder shown at startup. Now I can't
even start Thunar from the GUI, and when I start it from a terminal all
I get is "Segmentation fault (core dumped)". Nautilus does the same.
Dolphin and Krusader don't. Earlier when I started gedit and tried to
open a file that required navigating any more than 2 or 3 levels from
where the dialog started, there would be delay when I selected the last
folder to open and then gedit would crash. Now when I start gedit from
the gui, nothing happens; and from a terminal I get the same
"Segmentation fault (core dumped)" error. It doesn't matter what program
I use, if I try to open something that requires navigating more than 2
or 3 levels from where the open dialog started, there's a delay when I
select the last folder to open and then that program crashes with the
same error. However, if I navigate to a folder in Krusader and double-
click on a .JPG file, Kolourpaint opens with the file loaded; then, if I
try to save the file in a different folder, I can. However, double-
clicking or using "open with" on a .TXT file does not successfully start
gedit, though it will start mousepad...but if I then try to save the
text file in a path that requires navigating down a couple of levels,
mousepad crashes. Note that all these crashes are registered as such and
generate the GUI error "The application [name] has closed unexpectedly.
Send a problem report to the developers?", which I do; though I'm never
asked anything about what I was doing when the crash occurred.

I did find that programs installed with snap didn't have the same
problems, but the snap installation isolates them in a way that doesn't
allow me to navigate anywhere outside the snap folder. I have done
recovery starts of Ubuntu, checked the file system, checked system
memory, and found nothing wrong. Firefox and Chromium work find, until I
try to save a download in a folder more than 2 or 3 levels deeper from
the one the save/save as dialog starts in, or try to load a file more
than 2 or 3 levels deeper from the one the open dialog starts in.
Navigating up doesn't seem to be a problem, and navigating within shared
folders on the machine from the network works fine.

If I start Win XP Pro in a VirtualBox VM, navigation into shared folders
using the Windows file explorer isn't a problem. If I start Sigil and
select open, the selection window appears, nothing happens, and then
Sigil crashes. Starting from a terminal tells me that Sigil is
generating the same segmentation fault as above. However, if I start
Sigil and open a file from the File menu's list of previously opened
files, no problem and no problem saving changes...as long as I don't try
to save the changes somewhere that requires navigating 2 or 3 levels
down.

I don't know if this is a linux system bug or a XFCE-4 bug, but it makes
the machine pretty frustrating.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: thunar 1.6.15-0ubuntu1.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
Uname: Linux 4.15.0-118-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Sep 23 23:49:59 2020
InstallationDate: Installed on 2019-11-29 (299 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: thunar
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: thunar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896866

Title:
  All directory navigation more than a couple of levels crashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1896866/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1851183] Re: network support for Tiger Lake

2020-05-13 Thread Kent Lin

** Tags added: tigerlake

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851183

Title:
  network support for Tiger Lake

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1851183/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1855608] Re: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake

2020-02-19 Thread Kent Lin

@packet,
Could you attached edid of the system?
So we could get to know which panel has this kind of issue.
thank you.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855608

Title:
  Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on
  Intel Comet Lake

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855608/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1827440] Re: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

2020-01-28 Thread kent christopher

Update: a kernel upgrade solved the mic white noise for me. I had been
running a 5.0 kernel. Updating to a 5.4 kernel fixed it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827440

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827440/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1827440] Re: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

2020-01-28 Thread kent christopher

Tyler, did you ever find a solution to this? I'm having the same problem
with a the same laptop (X1 Carbon 6th gen) running Kubuntu 18.04. The
only "solution" I've found is to turn off "internal mic boost" using
alsa-mixer (hit F5 to show all channels, cursor all the way to the
right) and keep the mic capture level below 20%. So it works, but far
from ideal since the mic is low (but better than making the person on
the other end of a call hearing a shitload of white noise that's
produced otherwise).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827440

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827440/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1859741] Re: Graphics: Local Memory support for Discrete GPU

2020-01-14 Thread Kent Lin

@quanxian,

Is this for NV's or AMD dGPU or it is for Intel's dGPU like Xe GPU?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859741

Title:
  Graphics: Local Memory support for Discrete GPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1859741/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection

2019-12-18 Thread Kent Lion

Perhaps this can help: The symptoms I experience started sometime during
the past year after an update (sudo apt update && sudo apt upgrade &&
sudo apt autoremove) are that some indefinite time (usually less than ½
hour) after I log on, the network disconnects without warning or error.
Clicking on the up/down arrows of the indicator plugin and selecting the
interface reconnects; however, I recently discovered that if, as soon as
I log on, I select "Disconnect" and then select the adapter to
reconnect, my session will be fine until I log out and back in again. So
perhaps the bug is not with network-manager, samba or ifupdown, but with
the logon process(es). My version is 18.04 and I'm using LiteDM GTK+. I
haven't the faintest idea where to look for a cause that might be
related to the logon process(s), but none of the very many "solutions"
offered on various web pages I found on the problem have fixed it for
me.

One other unexpected thing I've noticed is that in editing Ethernet
connections (I don't used wireless enough to have noticed a problem), I
can't edit (or delete) the one the system creates without first adding
another (even if it's the same, e.g., enp2s0, with the same settings)
and switching to it; however, after I did that the first time, and
deleted the system's entry ("Wired connection 1", I think it was
called), at some point the system added another entry, identical in
every way to the one I had added, but called "Ifupdown (enp2s0)" and
connects to that when I log on, not to the one I created (which I have
since deleted, but the original problem still occurs, and disconnecting
and reconnecting still prevents the random disconnect).

All of this applies to 2 other machines, also running up-to-date xubuntu
18.04, although on one of the other machines, the adapter is enp4s25. It
also occurs with xubuntu and xfce sessions. I suspect the difficutly in
finding the cause(s) is in part due to the confusing way samba/network
settings are stored, with the same setting sometimes stored in different
locations, entered via GUI or command line or both, possibly leading to
conflicts.

I have spent many hours on this problem, and have only the above work-
around, not a fix. Even though this problem has been around longer than
18.04, since 18.04, samba has clearly been broken, and until networking
is as reliable and as easy to set up as in Windows, (x/l/k)ubuntu will
not be suitable for typical home users.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666432

Title:
  Internet drops every few minutes on wired and wireless connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1666432/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1658921] Re: NetworkManager does not manage wired connection

2019-11-23 Thread Kent Lion

*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547

I'm posting here instead of the bug at: https://bugs.launchpad.net/bugs/1676547
because it got me on the path that may have solved the problem (time will tell).
My /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf also 
contained:
[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:wwan
When I cleared it out and rebooted, it was still empty and the problem was 
still there. At that point, I noticed that when I clicked on the Network 
Manager applet (↑↓) it displayed the lines:
Ethernet Network (gray title)
Wired connection 1
Disconnect
enp0s25
VPN Connections
Enable Networking (checkbox)
Connection Information
Edit Connections...

But the machine has only one ethernet card, so I chose Edit Connections... and 
changed the connection name to the device name enp0s25. Using ifdown -a worked 
fine, but ifup -a gave me a long pause followed by:
sudo unable to resolve host [hostname]: Resource temporarily unavailable
When I then clicked on the Network Manager applet it showed enp0s25 above AND 
below Disconnect. When I then clicked Disconnect and then clicked enp0s25, it 
reconnected just fine. If I delete or restore the original 
/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf, it stops 
working; the file must be empty. On the machine I'm typing this on (also 
updated Bionic 64), 
/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf is not empty, 
but I don't do file sharing on it. Now that the other machine is working, I 
find I can access its shared folders on my network without a problem.

So this bug probably has more than one cause. It's as if network
connection information is being taken from at least 2 different
locations, and one or more of them has/have been forgotten but should be
gone.

I do note that when I click Edit Connections... the connection
information does not necessarily agree with what's in
/etc/network/interfaces, in particular netmask refuses to keep the value
255.255.255.0 and reverts to 24 (could 24 refer to /24 in
192.168.15.109/24 ?), which is not the netmask /etc/network/interfaces
requires for a static IP setting.

My problem began with a clean install from a freshly downloaded ISO of
Xubuntu 18.04 LTS 64 bit desktop (not server). Networking and Internet
worked, but while setting it up for file sharing over the network (as
the machine it replaced had done), I eventually lost all network access,
and the network manager applet refused to connect, even when it said it
"connection established"...before changing to say "disconnected". I
previously reported a bug that suddenly disappeared by itself for a few
months and that then recently reappeared: after some minutes connected
to the Internet, my network connection would suddenly disconnect, and
I'd have to reconnect it in the Network Manager applet. So I just made
the change to it's name on that machine, and we'll see if that solves
the problem or not (it's a pain to reproduce, because it requires
rebooting and waiting an unknown amount of time.

Getting file sharing in Linux is like finding an Android app: multiple
choices to try, only to discover that none (or almost none) does the
minimum that is reasonable to expect from it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658921

Title:
  NetworkManager does not manage wired connection

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1847445] Re: [CML-S] intel_idle support CML-S 6+2

2019-11-18 Thread Kent Lin

@quanxian,

Is this the patches we need for this bug?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.4-rc7&id=1ffa6c04dae39776a3c222bdf88051e394386c01

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847445

Title:
  [CML-S] intel_idle support CML-S 6+2

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1847445/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848978] Re: CML: perf enabling for core

2019-11-18 Thread Kent Lin

perf/x86/cstate: Add Comet Lake CPU support:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.4-rc7&id=1ffa6c04dae39776a3c222bdf88051e394386c01
perf/x86/msr: Add Comet Lake CPU support:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.4-rc7&id=9674b1cc0f94c34f76e58c102623a866836f269e
perf/x86/intel: Add Comet Lake CPU support:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.4-rc7&id=9066288b2aab1804dc1eebec6ff88474363b89cb

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848978

Title:
  CML: perf enabling for core

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1848978/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848978] Re: CML: perf enabling for core

2019-11-05 Thread Kent Lin

** Also affects: linux-oem-osp1 (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/1848978

Title:
  CML: perf enabling for core

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1848978/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1848829] Re: upgrade from 19.04 to 19.10 failed due pip install of distro-info

2019-10-25 Thread Kent Frazier

I have multiple versions of python installed... not sure of the path 
that was used .
However of the versions that may have been used ...
the only "distro" I see is

python3.8 -m pip list | grep distro
WARNING: pip is configured with locations that require TLS/SSL, however 
the ssl module in Python is not available.
 > pip3 list | grep distro
distro?? 1.4.0
 > python3 -m pip list | grep distro
distro?? 1.4.0
 >python3.7 -m pip list | grep distro
distro?? 1.4.0
 > python -m pip list | grep distro
distro?? 1.4.0

I am now up and running on 19.10
I upgraded update-manager to version 1.19.10.15 (19.04 had an older 
version)
That allowed update to occur.
I did have a problem with logging in after update. For some reason only 
2 ids were available on the login screen (unity). One of which (Sophos 
Anti-Virus) was disabled (it hadn't been listed before upgrade) and was 
id  (one less than my usual id, so maybe a one-off problem?), and 
another account that I was able to log in to (with admin privileges) . 
My usual account was not available for login. Settings showed only the 
same two users noted above. I was able to open a terminal and su to my 
normal ID, however. I ended up doing a deluser on my usual user account, 
and then went into settings and added my usual account back. ...I think 
all is well now...

On 10/25/19 3:11 PM, Brian Murray wrote:
> @Kent - do you have distro-info installed from pip? You can check via
> pip list.
>
> ** Summary changed:
>
> - upgrade from 19.04 to 19.10 fails due pip install of distro-info
> + upgrade from 19.04 to 19.10 failed due pip install of distro-info
>
> ** Changed in: ubuntu-release-upgrader (Ubuntu)
> Status: Confirmed => Incomplete
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848829

Title:
  upgrade from 19.04 to 19.10 failed due pip install of distro-info

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1848829/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849278] [NEW] [CML-S] Add-new-CNL-PCH-ID-seen-on-a-CML-platform

2019-10-22 Thread Kent Lin

Public bug reported:

Add-new-CNL-PCH-ID-seen-on-a-CML-platform for
https://bugs.freedesktop.org/show_bug.cgi?id=112051

Fix patch: https://bugs.freedesktop.org/attachment.cgi?id=145786

** Affects: intel
 Importance: Undecided
 Status: New

** Affects: linux-oem-osp1 (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: linux-oem-osp1 (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/1849278

Title:
  [CML-S] Add-new-CNL-PCH-ID-seen-on-a-CML-platform

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1849278/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1848829] Re: upgrade from 19.04 to 19.10 fails

2019-10-19 Thread Kent Frazier

Upgraded update-manager to 1:19.10.15 

That allowed update to occur.
I did have a problem with logging in after update. For some reason only 
2 ids were available on the login screen (unity). One of which (Sophos 
Anti-Virus) was disabled (it hadn't been listed before upgrade), and 
another account that I was able to log in to (with admin privileges) . 
My usual account was not available for login. Settings showed only the 
same two users noted above. I was able to open a terminal and su to my 
normal ID, however. I ended up doing a deluser on my user account, and 
then go into settings and add my usual account back. ...

On 10/19/19 1:20 AM, Arul wrote:
> Upgrade from 19.04 to 19.10 failed for me
>
> Fetched 586 B in 0s (0 B/s)
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
>
> Restoring original system state
>
> Aborting
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848829

Title:
  upgrade from 19.04 to 19.10 fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1848829/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1848829] Re: upgrade from 19.04 to 19.10 fails

2019-10-19 Thread Kent Frazier

Upgraded update-manager to 1:19.10.15 

That allowed update to occur.
I did have a problem with logging in after update. For some reason only 
2 ids were available on the login screen (unity). One of which (Sophos 
Anti-Virus) was disabled (it hadn't been listed before upgrade), and 
another account that I was able to log in to (with admin privileges) . 
My usual account was not available for login. Settings showed only the 
same two users noted above. I was able to open a terminal and su to my 
normal ID, however. I ended up doing a deluser on my usual user account, 
and then went into settings and add my usual account back. ...
On 10/19/19 1:15 AM, Launchpad Bug Tracker wrote:
> Status changed to 'Confirmed' because the bug affects multiple users.
>
> ** Changed in: ubuntu-release-upgrader (Ubuntu)
> Status: New => Confirmed
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848829

Title:
  upgrade from 19.04 to 19.10 fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1848829/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848829] [NEW] upgrade from 19.04 to 19.10 fails

2019-10-18 Thread Kent Frazier

Public bug reported:

sudo update-manager -d
[sudo] password for frazier: 

(update-manager:30033): Gtk-WARNING **: 20:09:59.851: Theme parsing
error: gtk.css:7:26: The style property GtkRange:slider-width is
deprecated and shouldn't be used anymore. It will be removed in a future
version

(update-manager:30033): Gtk-WARNING **: 20:09:59.851: Theme parsing
error: gtk.css:8:26: The style property GtkRange:stepper-size is
deprecated and shouldn't be used anymore. It will be removed in a future
version

(update-manager:30033): Gtk-WARNING **: 20:09:59.851: Theme parsing error: 
gtk.css:45:6: Expected a valid selector
Checking for a new Ubuntu release
/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcher.py:23: 
PyGIWarning: Gtk was imported without specifying a version first. Use 
gi.require_version('Gtk', '3.0') before import to ensure that the right version 
gets loaded.
  from gi.repository import Gtk, Gdk

(do-release-upgrade:2867): Gtk-WARNING **: 20:10:25.756: Theme parsing
error: gtk.css:7:26: The style property GtkRange:slider-width is
deprecated and shouldn't be used anymore. It will be removed in a future
version

(do-release-upgrade:2867): Gtk-WARNING **: 20:10:25.756: Theme parsing
error: gtk.css:8:26: The style property GtkRange:stepper-size is
deprecated and shouldn't be used anymore. It will be removed in a future
version

(do-release-upgrade:2867): Gtk-WARNING **: 20:10:25.756: Theme parsing error: 
gtk.css:45:6: Expected a valid selector
/usr/lib/python3/dist-packages/DistUpgrade/ReleaseNotesViewerWebkit.py:33: 
PyGIWarning: WebKit2 was imported without specifying a version first. Use 
gi.require_version('WebKit2', '4.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import WebKit2 as WebKit

(WebKitWebProcess:2883): Gtk-WARNING **: 20:10:25.886: Theme parsing error: 
gtk.css:45:6: Expected a valid selector
authenticate 'eoan.tar.gz' against 'eoan.tar.gz.gpg' 
extracting 'eoan.tar.gz'

(eoan:2867): Gtk-WARNING **: 20:10:31.210: Theme parsing error:
gtk.css:7:26: The style property GtkRange:slider-width is deprecated and
shouldn't be used anymore. It will be removed in a future version

(eoan:2867): Gtk-WARNING **: 20:10:31.210: Theme parsing error:
gtk.css:8:26: The style property GtkRange:stepper-size is deprecated and
shouldn't be used anymore. It will be removed in a future version

(eoan:2867): Gtk-WARNING **: 20:10:31.210: Theme parsing error: gtk.css:45:6: 
Expected a valid selector
Traceback (most recent call last):
  File 
"/tmp/ubuntu-release-upgrader-aue69nj7/DistUpgrade/DistUpgradeQuirks.py", line 
802, in _prepare_snap_replacement_data
di.version('%s' % self.controller.fromDist).split()[0]
AttributeError: 'UbuntuDistroInfo' object has no attribute 'version'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/tmp/ubuntu-release-upgrader-aue69nj7/eoan", line 8, in 
sys.exit(main())
  File "/tmp/ubuntu-release-upgrader-aue69nj7/DistUpgrade/DistUpgradeMain.py", 
line 238, in main
if app.run():
  File 
"/tmp/ubuntu-release-upgrader-aue69nj7/DistUpgrade/DistUpgradeController.py", 
line 2084, in run
return self.fullUpgrade()
  File 
"/tmp/ubuntu-release-upgrader-aue69nj7/DistUpgrade/DistUpgradeController.py", 
line 1921, in fullUpgrade
if not self.doPostInitialUpdate():
  File 
"/tmp/ubuntu-release-upgrader-aue69nj7/DistUpgrade/DistUpgradeController.py", 
line 927, in doPostInitialUpdate
self.quirks.run("PostInitialUpdate")
  File 
"/tmp/ubuntu-release-upgrader-aue69nj7/DistUpgrade/DistUpgradeQuirks.py", line 
97, in run
func()
  File 
"/tmp/ubuntu-release-upgrader-aue69nj7/DistUpgrade/DistUpgradeQuirks.py", line 
129, in eoanPostInitialUpdate
self._calculateSnapSizeRequirements()
  File 
"/tmp/ubuntu-release-upgrader-aue69nj7/DistUpgrade/DistUpgradeQuirks.py", line 
459, in _calculateSnapSizeRequirements
self._prepare_snap_replacement_data()
  File 
"/tmp/ubuntu-release-upgrader-aue69nj7/DistUpgrade/DistUpgradeQuirks.py", line 
808, in _prepare_snap_replacement_data
(r.version for r in di.get_all("object")
AttributeError: 'UbuntuDistroInfo' object has no attribute 'get_all'
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/problem_report.py", line 477, in 
add_to_existing
self.write(f)
  File "/usr/lib/python3/dist-packages/problem_report.py", line 430, in write
block = f.read(1048576)
  File "/usr/lib/python3.7/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid 
start byte

Original exception was:
Traceback (most recent call last):
  File 
"/tmp/ubuntu-release-upgrader-aue69nj7/DistUpgrade/DistUpgradeQuirks.py", line 
802, in _prepare_snap_replacement_data
di.version('%s' % self.controller.fromDist).split()[0]
AttributeError: 'UbuntuDistroInfo' object h

[Bug 1847445] Re: [CML-S] intel_idle support CML-S 6+2

2019-10-15 Thread Kent Lin

@quanxian,

Is patch submitted to upstream?
Could you please provide commit ID?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847445

Title:
  [CML-S] intel_idle support CML-S 6+2

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1847445/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1847445] Re: [CML-S] intel_idle support CML-S 6+2

** Also affects: linux-oem-osp1 (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/1847445

Title:
  [CML-S] intel_idle support CML-S 6+2

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1847445/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843794] Re: CML CPUIDs

** Also affects: linux-oem-osp1 (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/1843794

Title:
  CML CPUIDs

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1843794/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843794] Re: CML CPUIDs

For CML-S processor, we will have a new CPU Model#( DEC 165, HEX: 0xA5),
which is different with the CML-U(0x8e), CML-H(0x9e).  The Model# has
been landed to 5.4 rc3 as follow

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/x86/include/asm
/intel-family.h?h=v5.4-rc3

diff --git a/arch/x86/include/asm/intel-family.h 
b/arch/x86/include/asm/intel-family.h
index f04622500da3..c606c0b70738 100644
--- a/arch/x86/include/asm/intel-family.h
+++ b/arch/x86/include/asm/intel-family.h

@@ -83,6 +83,9 @@

#define INTEL_FAM6_TIGERLAKE_L   0x8C

#define INTEL_FAM6_TIGERLAKE   0x8D


+#define INTEL_FAM6_COMETLAKE   0xA5

+#define INTEL_FAM6_COMETLAKE_L   0xA6

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843794

Title:
  CML CPUIDs

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1843794/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1846335] Re: [CML] New device id's for CMP-H

Intel GFX ID for CML-S GFX. It is just landed in v5.4-rc3 kernel.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/i915?h=v5.4-rc3&id=a8064d577dab1a81222a50c2de66a2de495f14f4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846335

Title:
  [CML] New device id's for CMP-H

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1846335/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1844559] Re: [GLK-R]enable CPUID

** Also affects: linux-oem (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-osp1 (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/1844559

Title:
  [GLK-R]enable CPUID

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1844559/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1847219] Re: HDMI audio lost function after the dGPU did runtime suspend. (AMD RX 580)

2019-10-08 Thread Kent Lin

5.0 Kernel + following patched [1] + AMD 19.30 driver [2], the issue is
fixed.

[1] Takashi Iwai's sound component support patch for AMDGPU
- https://patchwork.kernel.org/patch/10540417/

[2] AMD 19.30 driver: https://www.amd.com/en/support/kb/release-notes
/rn-amdgpu-unified-linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847219

Title:
  HDMI audio lost function after the dGPU did runtime suspend. (AMD RX
  580)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1847219/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843774] Re: [CML] New device IDs for CML-U and CMP-H

2019-10-02 Thread Kent Lin

** Also affects: linux-oem (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-osp1 (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/1843774

Title:
  [CML] New device IDs for CML-U and CMP-H

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1843774/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843775] Re: [CML-U] Comet lake platform need ISH driver support

2019-10-02 Thread Kent Lin

** Also affects: linux-oem (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-osp1 (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/1843775

Title:
  [CML-U] Comet lake platform need ISH driver support

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1843775/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1837923] [NEW] mate-notification-daemon quits after ~30-60 seconds

2019-07-25 Thread Stephen Kent

Public bug reported:

I'm running MATE on Ubuntu 18.04.2. Recently, mate-notification-daemon
has started quitting within ~30-60 seconds after being invoked, so I
have no notifications daemon. This causes the entire desktop environment
to hang for about a minute each time the system tries to show a
notification (such as when wifi connects or disconnects, or I receive a
chat message).

My notifications used to work fine. I don't know why this has changed.
My apt update logs show no updates to mate-notification-daemon. However,
this issue is easy to reproduce:

1) Observe via ps that mate-notification-daemon isn't running
2) Invoke it (e.g. by running "time
/usr/lib/mate-notification-daemon/mate-notification-daemon" in a terminal)
3) Observe that the daemon quits after ~30-60 seconds:

$ time /usr/lib/mate-notification-daemon/mate-notification-daemon

real0m29.954s
user0m0.044s
sys 0m0.018s

I've run mate-notification-daemon under gdb, with the same behavior. gdb
reports the daemon is quitting normally.

Notifications being broken and causing the entire DE to hang each time I
get a notification is a severe usability problem.

** Affects: mate-notification-daemon (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/1837923

Title:
mate-notification-daemon quits after ~30-60 seconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-notification-daemon/+bug/1837923/+subscriptions

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1837923] Re: mate-notification-daemon quits after ~30-60 seconds

2019-07-25 Thread Stephen Kent

I should also note that during the ~30-60 seconds that the daemon runs
when I invoke it, notifications work fine during that time (tested using
notify-send). But after that brief time, the daemon just quits.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837923

Title:
  mate-notification-daemon quits after ~30-60 seconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-notification-daemon/+bug/1837923/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1836020] Re: Sometimes touchpad(goodix) can't use tap function

2019-07-10 Thread Kent Lin

@Acelan,

For Nebula, We have following product name:
Inspiron 7590
Inspiron 7591
Vostro 7590

And why you are using product name to add the quirk not using the
touchpad's vid/pid?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836020

Title:
  Sometimes touchpad(goodix) can't use tap function

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1836020/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824247] [NEW] Upgrade from 16.04 to 18.04 fails.

2019-04-10 Thread Kent Lion

Public bug reported:

kent@Dimension8300:~$ sudo do-release-upgrade
[sudo] password for kent: 
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]   
Get:2 Upgrade tool [1,246 kB]  
Fetched 1,247 kB in 0s (0 B/s) 
authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg' 
extracting 'bionic.tar.gz'

Reading cache

Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [109 kB] 
Hit http://us.archive.ubuntu.com/ubuntu xenial InRelease   
Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Hit http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu xenial InRelease
Get:3 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]  
Fetched 325 kB in 0s (0 B/s)   
Reading package lists... Done
Building dependency tree  
Reading state information... Done

Updating repository information

Third party sources disabled

Some third party entries in your sources.list were disabled. You can 
re-enable them after the upgrade with the 'software-properties' tool 
or your package manager. 

To continue please press [ENTER]
Hit http://us.archive.ubuntu.com/ubuntu bionic InRelease   
Hit http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease   
Hit http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease 
Fetched 0 B in 0s (0 B/s)  

Checking package manager
Reading package lists... Done
Building dependency tree  
Reading state information... Done

Calculating the changes

Calculating the changes

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

If none of this applies, then please report this bug using the 
command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal.If 
you want to investigate this yourself the log files in 
'/var/log/dist-upgrade' will contain details about the upgrade. 
Specifically, look at 'main.log' and 'apt.log'. 


Restoring original system state

Aborting
Reading package lists... Done
Building dependency tree  
Reading state information... Done
=== So I tried this:
kent@Dimension8300:/var/log/dist-upgrade$ sudo update-manager -c --debug
/usr/bin/update-manager:28: PyGIWarning: Gtk was imported without specifying a 
version first. Use gi.require_version('Gtk', '3.0') before import to ensure 
that the right version gets loaded.
  from gi.repository import Gtk
WARNING:root:can not import unity GI cannot import name Dbusmenu, introspection 
typelib not found
Checking for a new Ubuntu release
/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcher.py:23: 
PyGIWarning: Gtk was imported without specifying a version first. Use 
gi.require_version('Gtk', '3.0') before import to ensure that the right version 
gets loaded.
  from gi.repository import Gtk, Gdk
/usr/lib/python3/dist-packages/DistUpgrade/ReleaseNotesViewerWebkit.py:33: 
PyGIWarning: WebKit2 was imported without specifying a version first. Use 
gi.require_version('WebKit2', '4.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import WebKit2 as WebKit
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg' 
extracting 'bionic.tar.gz'

(appstreamcli:7279): GLib-CRITICAL **: g_strchug: assertion 'string !=
NULL' failed

(appstreamcli:7279): GLib-CRITICAL **: g_strchomp: assertion 'string !=
NULL' failed

(appstreamcli:7279): GLib-CRITICAL **: g_strchug: assertion 'string !=
NULL' failed

(appstreamcli:7279): GLib-CRITICAL **: g_strchomp: assertion 'string !=
NULL' failed

(appstreamcli:7279): GLib-CRITICAL **: g_strchug: assertion 'string !=
NULL' failed

(appstreamcli:7279): GLib-CRITICAL **: g_strchomp: assertion 'string != NULL' 
failed
AppStream cache update completed, but some metadata was ignored due to errors.
--- Here a GUI window is displayed containing the above error 
message and a "Close" button:-
Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

 If none of this applies, then please report this bug using the command 
'ubuntu-bug ubuntu-release-upgrader-core' in a terminal.If you want to 
investigate t

[Bug 1803663] Re: installed android-androresolvd package post-installation script subprocess returned error exit status 1

2019-02-07 Thread Clark Kent

** Description changed:

  $ uname -a
  Linux Mobile-C 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
+ $ cat /etc/os-release 
+ ID_LIKE="ubuntu debian"
+ VERSION_ID="18.04"
+ 
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
+ VERSION_CODENAME=bionic
+ UBUNTU_CODENAME=bionic
  
  $ sudo apt install android-androresolvd
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  android-androresolvd is already the newest version (1.3-1build1).
  The following packages were automatically installed and are no longer 
required:
    cpp-7-arm-linux-gnueabi cpp-arm-linux-gnueabi gcc-7-arm-linux-gnueabi-base 
gcc-7-cross-base gcc-8-cross-base
    libasan4-armel-cross libatomic1-armel-cross libc6-dev-armel-cross 
libcilkrts5-armel-cross libgcc-7-dev-armel-cross
    libgcc1-armel-cross libgomp1-armel-cross libportaudiocpp0 
libstdc++6-armel-cross libubsan0-armel-cross
    linux-libc-dev-armel-cross
  Use 'sudo apt autoremove' to remove them.
  0 to upgrade, 0 to newly install, 0 to remove and 508 not to upgrade.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up android-androresolvd (1.3-1build1) ...
  Job for android-androresolvd.service failed because the control process 
exited with error code.
  See "systemctl status android-androresolvd.service" and "journalctl -xe" for 
details.
  invoke-rc.d: initscript android-androresolvd, action "start" failed.
  ● android-androresolvd.service - LSB: Updates /etc/resolv.conf from Android 
system props
     Loaded: loaded (/etc/init.d/android-androresolvd; generated)
     Active: failed (Result: exit-code) since Fri 2018-11-16 16:41:07 AEST; 
116ms ago
   Docs: man:systemd-sysv-generator(8)
    Process: 31643 ExecStart=/etc/init.d/android-androresolvd start 
(code=exited, status=255)
  
  Nov 16 16:41:07 Mobile-C systemd[1]: Starting LSB: Updates /etc/resolv.conf 
from Android system props...
  Nov 16 16:41:07 Mobile-C android-androresolvd[31643]: Cannot access system 
properties via ANDROID_PROPERTY_WORKSPACE environment setting.
  Nov 16 16:41:07 Mobile-C systemd[1]: android-androresolvd.service: Control 
process exited, code=exited status=255
  Nov 16 16:41:07 Mobile-C systemd[1]: android-androresolvd.service: Failed 
with result 'exit-code'.
  Nov 16 16:41:07 Mobile-C systemd[1]: Failed to start LSB: Updates 
/etc/resolv.conf from Android system props.
  dpkg: error processing package android-androresolvd (--configure):
   installed android-androresolvd package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   android-androresolvd
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  
  $ systemctl status android-androresolvd.service
  ● android-androresolvd.service - LSB: Updates /etc/resolv.conf from Android 
system props
     Loaded: loaded (/etc/init.d/android-androresolvd; generated)
     Active: failed (Result: exit-code) since Fri 2018-11-16 16:41:07 AEST; 
1min 43s ago
   Docs: man:systemd-sysv-generator(8)
    Process: 31643 ExecStart=/etc/init.d/android-androresolvd start 
(code=exited, status=255)
  
  Nov 16 16:41:07 Mobile-C systemd[1]: Starting LSB: Updates /etc/resolv.conf 
from Android system props...
  Nov 16 16:41:07 Mobile-C android-androresolvd[31643]: Cannot access system 
properties via ANDROID_PROPERTY_WORKSPACE envir
  Nov 16 16:41:07 Mobile-C systemd[1]: android-androresolvd.service: Control 
process exited, code=exited status=255
  Nov 16 16:41:07 Mobile-C systemd[1]: android-androresolvd.service: Failed 
with result 'exit-code'.
  Nov 16 16:41:07 Mobile-C systemd[1]: Failed to start LSB: Updates 
/etc/resolv.conf from Android system props.
  
  $ journalctl -xe
  Nov 16 16:42:41 Mobile-C autosuspend[1727]:   File 
"/usr/lib/python3.6/http/client.py", line 1239, in request
  Nov 16 16:42:41 Mobile-C autosuspend[1727]: self._send_request(method, 
url, body, headers, encode_chunked)
  Nov 16 16:42:41 Mobile-C autosuspend[1727]:   File 
"/usr/lib/python3.6/http/client.py", line 1285, in _send_request
  Nov 16 16:42:41 Mobile-C autosuspend[1727]: self.endheaders(body, 
encode_chunked=encode_chunked)
  Nov 16 16:42:41 Mobile-C autosuspend[1727]:   File 
"/usr/lib/python3.6/http/client.py", line 1234, in endheaders
  Nov 16 16:42:41 Mobile-C autosuspend[1727]: 
self._send_output(message_body, encode_chunked=encode_chunked)
  Nov 16 16:42:41 Mobile-C autosuspend[1727]:   File 
"/usr/lib/python3.6/http/client.py", line 1026, in _send_output
  Nov 16 16:42:41 Mobile-C autosuspend[1727]: self.send(msg)
  Nov 16 16:42:41 Mobile-C autosuspend[1727]:   File 
"/usr/lib/python3.6/http/client.py", line 964, in send
  Nov 16 16:42:41 Mobile-C autosuspend[1727]: self.connect()
  Nov 16 16:42:41 Mobile-C autosuspend[1727]:   File 
"/usr/lib/python3/d

[Bug 1803663] [NEW] installed android-androresolvd package post-installation script subprocess returned error exit status 1

2018-11-15 Thread Clark Kent

Public bug reported:

$ uname -a
Linux Mobile-C 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

$ sudo apt install android-androresolvd
Reading package lists... Done
Building dependency tree
Reading state information... Done
android-androresolvd is already the newest version (1.3-1build1).
The following packages were automatically installed and are no longer required:
  cpp-7-arm-linux-gnueabi cpp-arm-linux-gnueabi gcc-7-arm-linux-gnueabi-base 
gcc-7-cross-base gcc-8-cross-base
  libasan4-armel-cross libatomic1-armel-cross libc6-dev-armel-cross 
libcilkrts5-armel-cross libgcc-7-dev-armel-cross
  libgcc1-armel-cross libgomp1-armel-cross libportaudiocpp0 
libstdc++6-armel-cross libubsan0-armel-cross
  linux-libc-dev-armel-cross
Use 'sudo apt autoremove' to remove them.
0 to upgrade, 0 to newly install, 0 to remove and 508 not to upgrade.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up android-androresolvd (1.3-1build1) ...
Job for android-androresolvd.service failed because the control process exited 
with error code.
See "systemctl status android-androresolvd.service" and "journalctl -xe" for 
details.
invoke-rc.d: initscript android-androresolvd, action "start" failed.
● android-androresolvd.service - LSB: Updates /etc/resolv.conf from Android 
system props
   Loaded: loaded (/etc/init.d/android-androresolvd; generated)
   Active: failed (Result: exit-code) since Fri 2018-11-16 16:41:07 AEST; 116ms 
ago
 Docs: man:systemd-sysv-generator(8)
  Process: 31643 ExecStart=/etc/init.d/android-androresolvd start (code=exited, 
status=255)

Nov 16 16:41:07 Mobile-C systemd[1]: Starting LSB: Updates /etc/resolv.conf 
from Android system props...
Nov 16 16:41:07 Mobile-C android-androresolvd[31643]: Cannot access system 
properties via ANDROID_PROPERTY_WORKSPACE environment setting.
Nov 16 16:41:07 Mobile-C systemd[1]: android-androresolvd.service: Control 
process exited, code=exited status=255
Nov 16 16:41:07 Mobile-C systemd[1]: android-androresolvd.service: Failed with 
result 'exit-code'.
Nov 16 16:41:07 Mobile-C systemd[1]: Failed to start LSB: Updates 
/etc/resolv.conf from Android system props.
dpkg: error processing package android-androresolvd (--configure):
 installed android-androresolvd package post-installation script subprocess 
returned error exit status 1
Errors were encountered while processing:
 android-androresolvd
E: Sub-process /usr/bin/dpkg returned an error code (1)

$ systemctl status android-androresolvd.service
● android-androresolvd.service - LSB: Updates /etc/resolv.conf from Android 
system props
   Loaded: loaded (/etc/init.d/android-androresolvd; generated)
   Active: failed (Result: exit-code) since Fri 2018-11-16 16:41:07 AEST; 1min 
43s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 31643 ExecStart=/etc/init.d/android-androresolvd start (code=exited, 
status=255)

Nov 16 16:41:07 Mobile-C systemd[1]: Starting LSB: Updates /etc/resolv.conf 
from Android system props...
Nov 16 16:41:07 Mobile-C android-androresolvd[31643]: Cannot access system 
properties via ANDROID_PROPERTY_WORKSPACE envir
Nov 16 16:41:07 Mobile-C systemd[1]: android-androresolvd.service: Control 
process exited, code=exited status=255
Nov 16 16:41:07 Mobile-C systemd[1]: android-androresolvd.service: Failed with 
result 'exit-code'.
Nov 16 16:41:07 Mobile-C systemd[1]: Failed to start LSB: Updates 
/etc/resolv.conf from Android system props.

$ journalctl -xe
Nov 16 16:42:41 Mobile-C autosuspend[1727]:   File 
"/usr/lib/python3.6/http/client.py", line 1239, in request
Nov 16 16:42:41 Mobile-C autosuspend[1727]: self._send_request(method, url, 
body, headers, encode_chunked)
Nov 16 16:42:41 Mobile-C autosuspend[1727]:   File 
"/usr/lib/python3.6/http/client.py", line 1285, in _send_request
Nov 16 16:42:41 Mobile-C autosuspend[1727]: self.endheaders(body, 
encode_chunked=encode_chunked)
Nov 16 16:42:41 Mobile-C autosuspend[1727]:   File 
"/usr/lib/python3.6/http/client.py", line 1234, in endheaders
Nov 16 16:42:41 Mobile-C autosuspend[1727]: self._send_output(message_body, 
encode_chunked=encode_chunked)
Nov 16 16:42:41 Mobile-C autosuspend[1727]:   File 
"/usr/lib/python3.6/http/client.py", line 1026, in _send_output
Nov 16 16:42:41 Mobile-C autosuspend[1727]: self.send(msg)
Nov 16 16:42:41 Mobile-C autosuspend[1727]:   File 
"/usr/lib/python3.6/http/client.py", line 964, in send
Nov 16 16:42:41 Mobile-C autosuspend[1727]: self.connect()
Nov 16 16:42:41 Mobile-C autosuspend[1727]:   File 
"/usr/lib/python3/dist-packages/urllib3/connection.py", line 166, in co
Nov 16 16:42:41 Mobile-C autosuspend[1727]: conn = self._new_conn()
Nov 16 16:42:41 Mobile-C autosuspend[1727]:   File 
"/usr/lib/python3/dist-packages/urllib3/connection.py", line 150, in _n
Nov 16 16:42:41 Mobile-C autosuspend[1727]: self, "Failed to establish a 
new connection:

[Bug 1802814] Re: GPU lockup with Vega 64 (amdgpu)

** Attachment added: "output from avivotool"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1802814/+attachment/5211605/+files/regdump-lockup.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802814

Title:
  GPU lockup with Vega 64 (amdgpu)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1802814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1802814] Re: GPU lockup with Vega 64 (amdgpu)

** Attachment added: "output from avivotool"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1802814/+attachment/5211606/+files/regdump-normal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802814

Title:
  GPU lockup with Vega 64 (amdgpu)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1802814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1802814] [NEW] GPU lockup with Vega 64 (amdgpu)

Public bug reported:

This lockup is typically reproducible within 10-60 minutes running Dota
2, in either OpenGL or Vulkan mode. The application does not have
exclusive control of the display, and is running as a borderless window
in gdm's X desktop.

When this lockup occurs, the mouse cursor may still move but cannot
interact. The keyboard cannot interact, and mode lights (numlock) do not
toggle. Sounds continue playing smoothly, but sound effects of limited
duration will end naturally and nothing new will happen. The desktop no
longer updates on the secondary monitor.

I have dmesg and Xorg.0.log to attach. I'll also attach the output of
'sudo avivotool regs all', though I doubt its efficacy on this GPU and
it shows nothing but ''.

** Affects: ubuntu-drivers-common (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/1802814

Title:
  GPU lockup with Vega 64 (amdgpu)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1802814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1802814] Re: GPU lockup with Vega 64 (amdgpu)

** Attachment added: "dmesg-lockup.txt"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1802814/+attachment/5211603/+files/dmesg-lockup.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802814

Title:
  GPU lockup with Vega 64 (amdgpu)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1802814/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1802814] Re: GPU lockup with Vega 64 (amdgpu)