[Ubuntu-x-swat] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2021-01-28 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag

[Ubuntu-x-swat] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2021-01-28 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag

[Ubuntu-x-swat] [Bug 1909334] Re: bug

2021-01-28 Thread Alex Murray
Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it. Submitting the bug about the proper source package is essential. For help see

[Ubuntu-x-swat] [Bug 1910665] Re: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit

2021-01-28 Thread Apport retracing service
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1910665 Title: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to

[Ubuntu-x-swat] [Bug 1910665] Re: package nvidia-dkms-390 390.138-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit

2021-01-28 Thread Alex Murray
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross

[Ubuntu-x-swat] [Bug 1910736] Re: package libnvidia-compute-390 (not installed) failed to install/upgrade: paylaşılan '/etc/OpenCL/vendors/nvidia.icd' dosyasının üzerine yazılmaya çalışılıyor, dosya l

2021-01-28 Thread Alex Murray
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross

[Ubuntu-x-swat] [Bug 1913493] Re: pc

2021-01-28 Thread Alex Murray
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross

[Ubuntu-x-swat] [Bug 1905953] Re: Xorg crash

2021-01-28 Thread Launchpad Bug Tracker
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu.

[Ubuntu-x-swat] [Bug 1913613] Re: [nvidia] [amdgpu] Second monitor is detected but has no signal

2021-01-28 Thread Daniel van Vugt
Thanks for the bug report. It appears the affected monitor is connected to the Nvidia GPU, but your system doesn't seem to have the Nvidia driver loaded properly. This might be an installation issue or it might be an incompatibility between needing 'modeset' enabled for the amdgpu driver, and

[Ubuntu-x-swat] [Bug 1913613] Re: Second monitor is detected but has no signal

2021-01-28 Thread Daniel van Vugt
Here's the decoded EDID of the affected monitor on HDMI-1-0: EDID version: 1.3 Manufacturer: BNQ Model 30926 Serial Number 21573 Made in week 3 of 2015 Digital display Maximum image size: 53 cm x 30 cm Gamma: 2.20 DPMS levels: Off RGB color display Default (sRGB) color space is primary color

[Ubuntu-x-swat] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2021-01-28 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag

[Ubuntu-x-swat] [Bug 1913613] Re: Second monitor is detected but has no signal

2021-01-28 Thread Jon
** Description changed: xrandr Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384 eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm -1920x1080 59.93*+ 39.99 -1680x1050 59.93 -1280x1024 59.93 -

[Ubuntu-x-swat] [Bug 1913613] [NEW] Second monitor is detected but has no signal

2021-01-28 Thread Jon Fernandez Bedia
Public bug reported: xrandr Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384 eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 59.93*+ 39.99 1680x1050 59.93 1280x1024 59.93 1440x900

Re: [Ubuntu-x-swat] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2021-01-28 Thread Coiby Xu
On Mon, Jan 25, 2021 at 07:03:55PM -, Adam Felson wrote: >Before I grab'n'build 5.11, I'd like to know if my issue is similar. >I have a lenovo ideapad 730s. >The touchpad works fine for pointing, single, double and triple clicks. >I have tried both the synaptics and libinput drivers. It's

Re: [Ubuntu-x-swat] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2021-01-28 Thread Coiby Xu
On Thu, Jan 21, 2021 at 01:05:48PM -, Joe Zhou wrote: >Lenovo R7000P Laptop. Sadly, still not a good solution. The touch pad >now works with kernel 5.11.0, but it has problem with Nvidia GPU and the >brightness control is not working. I can have Nvidia GPU working and >manually do some fixes

[Ubuntu-x-swat] [Bug 1912706] Re: Ubuntu 21.04 QEMU virgl Couldn't find current GLX or EGL context

2021-01-28 Thread Sebastien Bacher
We don't really have anyone knowing the libeproxy details in desktop so I'm not sure we are going to be able to provide more useful details. It works fine here on intel hardware, it could be an issue with the ati driver or the kernel... @Von, does the example command line Christian gave fail for

[Ubuntu-x-swat] [Bug 1912706] Re: Ubuntu 21.04 QEMU virgl Couldn't find current GLX or EGL context

2021-01-28 Thread Christian Ehrhardt 
Yeah that is what I thought - Thanks for confirming Von! My search engine use on this case found a few but no really related issues either. If you happen to stumble over one please let me know. Since it works fine for me I have to hope for the Desktop team taking a look from the libepoxy POV