[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 'verification-needed-groovy' to 'verification-failed-
groovy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

To manage notifications about this bug go to:
https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[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 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

** Tags added: verification-needed-groovy

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

To manage notifications about this bug go to:
https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[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 https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

** Changed in: xorg (Ubuntu)
   Status: New => Invalid

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

Title:
  bug

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[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
  install/upgrade: installed nvidia-dkms-390 package post-installation
  script subprocess returned error exit status 10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1910665/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[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 privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
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
  install/upgrade: installed nvidia-dkms-390 package post-installation
  script subprocess returned error exit status 10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1910665/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[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 privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
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/1910736

Title:
  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 libnvidia-
  compute-390:amd64 paketinin diğer örneklerinden farklı

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1910736/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[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 privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  pc

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[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.
https://bugs.launchpad.net/bugs/1905953

Title:
  Xorg crash

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[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 needing 'modeset' disabled for the nvidia driver. I'm
actually not sure what the best way is to support such a combination.

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460
(Ubuntu)

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

Title:
  [nvidia] [amdgpu] Second monitor is detected but has no signal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1913613/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[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 space
First detailed timing is preferred timing
Color Characteristics
  Red:   0.6416, 0.3339
  Green: 0.3339, 0.6240
  Blue:  0.1523, 0.0498
  White: 0.3134, 0.3291
Established Timings I & II
720x40070.082 Hz   9:531.467 kHz  28.320 MHz (IBM)
640x48059.940 Hz   4:331.469 kHz  25.175 MHz (DMT)
640x48075.000 Hz   4:337.500 kHz  31.500 MHz (DMT)
800x60060.317 Hz   4:337.879 kHz  40.000 MHz (DMT)
800x60075.000 Hz   4:346.875 kHz  49.500 MHz (DMT)
832x62474.551 Hz   4:349.726 kHz  57.284 MHz (Apple)
   1024x76860.004 Hz   4:348.363 kHz  65.000 MHz (DMT)
   1024x76875.029 Hz   4:360.023 kHz  78.750 MHz (DMT)
   1280x1024   75.025 Hz   5:479.976 kHz 135.000 MHz (DMT)
   1152x87075.062 Hz 192:145  68.681 kHz 100.000 MHz (Apple)
Standard Timings
   1920x1080   60.000 Hz  16:967.500 kHz 148.500 MHz (DMT)
   1280x72060.000 Hz  16:945.000 kHz  74.250 MHz (DMT)
   1280x80059.810 Hz  16:10   49.702 kHz  83.500 MHz (DMT)
   1280x1024   60.020 Hz   5:463.981 kHz 108.000 MHz (DMT)
   1600x90060.000 Hz  16:960.000 kHz 108.000 MHz (DMT, RB)
   1680x1050   59.954 Hz  16:10   65.290 kHz 146.250 MHz (DMT)
Detailed mode: Clock 148.500 MHz, 531 mm x 299 mm
   1920 2008 2052 2200 ( 88  44 148)
   1080 1084 1089 1125 (  4   5  36)
   +hsync +vsync
   VertFreq: 60.000 Hz, HorFreq: 67.500 kHz
Display Product Serial Number: Y1F02711SL0
Display Range Limits
  Monitor ranges (GTF): 50-76 Hz V, 30-83 kHz H, max dotclock 170 MHz
Display Product Name: BenQ GL2460
Has 1 extension block
Checksum: 0x86



CTA-861 Extension Block Revision 3
Underscans PC formats by default
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
1 native detailed modes
30 bytes of CTA data blocks
  Video Data Block
 1920x1080   60.000 Hz  16:967.500 kHz 148.500 MHz (VIC  16, native)
 1920x1080i  60.000 Hz  16:933.750 kHz  74.250 MHz (VIC   5)
 1280x72060.000 Hz  16:945.000 kHz  74.250 MHz (VIC   4)
  720x48059.940 Hz  16:931.469 kHz  27.000 MHz (VIC   3)
  720x48059.940 Hz   4:331.469 kHz  27.000 MHz (VIC   2)
  640x48059.940 Hz   4:331.469 kHz  25.175 MHz (VIC   1)
  720x57650.000 Hz   4:331.250 kHz  27.000 MHz (VIC  17)
  720x57650.000 Hz  16:931.250 kHz  27.000 MHz (VIC  18)
 1280x72050.000 Hz  16:937.500 kHz  74.250 MHz (VIC  19)
 1920x1080i  50.000 Hz  16:928.125 kHz  74.250 MHz (VIC  20)
 1440x480i   59.940 Hz   4:315.734 kHz  27.000 MHz (VIC   6)
 1440x480i   59.940 Hz  16:915.734 kHz  27.000 MHz (VIC   7)
 1440x576i   50.000 Hz   4:315.625 kHz  27.000 MHz (VIC  21)
 1440x576i   50.000 Hz  16:915.625 kHz  27.000 MHz (VIC  22)
 1920x1080   50.000 Hz  16:956.250 kHz 148.500 MHz (VIC  31)
  Audio Data Block
Linear PCM, max channels 2
  Supported sample rates (kHz): 48 44.1 32
  Supported sample sizes (bits): 24 20 16
  Vendor-Specific Data Block, OUI 0x000c03 (HDMI)
Source physical address 1.0.0.0
  Speaker Allocation Data Block
Speaker map:
  FL/FR - Front Left/Right
Detailed mode: Clock 148.500 MHz, 531 mm x 299 mm
   1920 2008 2052 2200 ( 88  44 148)
   1080 1084 1089 1125 (  4   5  36)
   +hsync +vsync
   VertFreq: 60.000 Hz, HorFreq: 67.500 kHz
Detailed mode: Clock 74.250 MHz, 531 mm x 299 mm
   1920 2008 2052 2200 ( 88  44 148)
540  542  547  562 (  2   5  15)
   +hsync +vsync
   VertFreq: 60.000i Hz, HorFreq: 33.750 kHz
Detailed mode: Clock 74.250 MHz, 531 mm x 299 mm
   1280 1390 1430 1650 (110  40 220)
720  725  730  750 (  5   5  20)
   +hsync +vsync
   VertFreq: 60.000 Hz, HorFreq: 45.000 kHz
Detailed mode: Clock 27.000 MHz, 531 mm x 299 mm
720  736  798  858 ( 16  62  60)
480  489  495  525 (  9   6  30)
   -hsync -vsync
   VertFreq: 59.940 Hz, HorFreq: 31.469 kHz
Checksum: 0xe7


** Tags added: amdgpu hybrid nvidia

** Summary changed:

- Second monitor is detected but has no signal
+ [nvidia] [amdgpu] Second monitor is detected but has no signal

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

Title:
  [nvidia] [amdgpu] Second monitor is detected but has no signal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/

[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 'verification-needed-xenial' to 'verification-failed-
xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

To manage notifications about this bug go to:
https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[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  
-1440x900  59.93  
-1280x800  59.93  
-1280x720  59.93  
-1024x768  59.93  
-800x600   59.93  
-640x480   59.93  
+    1920x1080 59.93*+  39.99
+    1680x1050 59.93
+    1280x1024 59.93
+    1440x900  59.93
+    1280x800  59.93
+    1280x720  59.93
+    1024x768  59.93
+    800x600   59.93
+    640x480   59.93
  HDMI-1-0 connected (normal left inverted right x axis y axis)
-1920x1080 60.00 +  59.9450.00  
-1680x1050 59.95  
-1600x900  60.00  
-1280x1024 75.0260.02  
-1280x800  59.81  
-1280x720  60.0059.9450.00  
-1024x768  75.0360.00  
-800x600   75.0060.32  
-720x576   50.00  
-720x480   59.94  
-640x480   75.0059.9459.93
+    1920x1080 60.00 +  59.9450.00
+    1680x1050 59.95
+    1600x900  60.00
+    1280x1024 75.0260.02
+    1280x800  59.81
+    1280x720  60.0059.9450.00
+    1024x768  75.0360.00
+    800x600   75.0060.32
+    720x576   50.00
+    720x480   59.94
+    640x480   75.0059.9459.93
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78
  Uname: Linux 5.4.0-64-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.32.03  Sun Dec 27 
19:00:34 UTC 2020
-  GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.32.03  Sun Dec 27 
19:00:34 UTC 2020
+  GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  BootLog:
-  
+ 
  CompositorRunning: None
  Date: Thu Jan 28 16:52:43 2021
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
-  nvidia, 460.32.03, 5.4.0-64-generic, x86_64: installed
-  rtl8821ce, 5.5.2.1, 5.4.0-42-generic, x86_64: installed
-  rtl8821ce, 5.5.2.1, 5.4.0-64-generic, x86_64: installed
+  nvidia, 460.32.03, 5.4.0-64-generic, x86_64: installed
+  rtl8821ce, 5.5.2.1, 5.4.0-42-generic, x86_64: installed
+  rtl8821ce, 5.5.2.1, 5.4.0-64-generic, x86_64: installed
  GraphicsCard:
-  NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Device [1043:109f]
-  Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Device [1043:18f1]
+  NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Device [1043:109f]
+  Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Device [1043:18f1]
  InstallationDate: Installed on 2021-01-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
  ProcEnviron:
-  LANGUAGE=es
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=es_ES.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=es
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=es_ES.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic 
root=UUID=a4e7f6c4-6b4b-46b3-b120-84a8805ac9dd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX505DT.315
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX505DT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.315:bd09/22/2020:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMP

[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  59.93  
   1280x800  59.93  
   1280x720  59.93  
   1024x768  59.93  
   800x600   59.93  
   640x480   59.93  
HDMI-1-0 connected (normal left inverted right x axis y axis)
   1920x1080 60.00 +  59.9450.00  
   1680x1050 59.95  
   1600x900  60.00  
   1280x1024 75.0260.02  
   1280x800  59.81  
   1280x720  60.0059.9450.00  
   1024x768  75.0360.00  
   800x600   75.0060.32  
   720x576   50.00  
   720x480   59.94  
   640x480   75.0059.9459.93

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78
Uname: Linux 5.4.0-64-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.32.03  Sun Dec 27 19:00:34 
UTC 2020
 GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
ApportVersion: 2.20.9-0ubuntu7.21
Architecture: amd64
BootLog:
 
CompositorRunning: None
Date: Thu Jan 28 16:52:43 2021
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 460.32.03, 5.4.0-64-generic, x86_64: installed
 rtl8821ce, 5.5.2.1, 5.4.0-42-generic, x86_64: installed
 rtl8821ce, 5.5.2.1, 5.4.0-64-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:109f]
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:18f1]
InstallationDate: Installed on 2021-01-27 (0 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
ProcEnviron:
 LANGUAGE=es
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic 
root=UUID=a4e7f6c4-6b4b-46b3-b120-84a8805ac9dd ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/22/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FX505DT.315
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX505DT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.315:bd09/22/2020:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: TUF Gaming
dmi.product.name: TUF Gaming FX505DT_FX505DT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic corruption ubuntu

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

Title:
  Second monitor is detected but has no signal

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


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 been a while since 
>I was comparing them;  IIRC, I'm currently running the synaptics driver as 
>libinput didn't have scrolling/coasting working.
>
>My problem is that palm detection and pressure sensitivity do not work.
>This makes the laptop pretty much unusable as it is almost impossible to
>do any text entry without the insertion point jumping to wherever the
>pointer was left.
>
>Might the 5.11 kernel fix it?

Your issue sounds different to this one. But you needn't to build the
kernel to see if the solution here works for you. You can try #189. If
it works for you, then 5.11 could also fix your issue. You may also want
to give https://github.com/coiby/standalone_i2c_hid a try.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

To manage notifications about this bug go to:
https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


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 to enable brightness control with 5.8.0, though
>touch pad is not working.

Newer kernels must have caused regression about brightness control.

You can follow the bug description and #189 to fix the touchpad with 5.8.0,
then you can have both Nvidia GPU and touchpad working.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

To manage notifications about this bug go to:
https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[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 you?

$ qemu-system-x86_64 -machine ubuntu,vmport=off -cpu host -accel kvm
-smp 2 -m 1G -device virtio-mouse -device virtio-keyboard -device
virtio-vga,virgl=on -display gtk,gl=on -usb -nodefaults -monitor vc

if it's failing, could you add your 'journalctl -b 0 log' after getting
the issue?

any chance you could try booting with an older kernel to see if that
makes a difference?

** Changed in: libepoxy (Ubuntu)
   Status: New => Incomplete

** Changed in: libepoxy (Ubuntu)
   Importance: Undecided => High

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

Title:
  Ubuntu 21.04 QEMU virgl Couldn't find current GLX or EGL context

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[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 what might be wrong here.

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

Title:
  Ubuntu 21.04 QEMU virgl Couldn't find current GLX or EGL context

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp