[Ubuntu-x-swat] [Bug 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes

2020-08-05 Thread Daniel van Vugt
To test kernel 5.8 you need to download all these packages EXCEPT the
"lowlatency" ones:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8/amd64/

and then install them all at once:

  sudo dpkg -i *.deb

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

Title:
  i915 does not expose vendor-specific extended HDMI timings/modes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Missing required logs.

2020-08-05 Thread Ubuntu Kernel Bot
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1890418

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  i915 does not expose vendor-specific extended HDMI timings/modes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes

2020-08-05 Thread Daniel van Vugt
The attachment in comment #10 confirms the problem is happening at a low
level in the kernel. Although Xorg could override that if it was smart
enough. In theory you can do it manually but would need to become an
expert at crafting modeline entries to get it working. I don't know how
myself. If that's possible then the data you need is in comment #7.

Obviously Windows 10 demonstrates that it is possible to support this
monitor with this HDMI port. Only Linux does not yet...

As a workaround, if you have a USB-C port and an appropriate
cable/adapter then you might be able to use the DisplayPort on the
monitor. If that works then it should give different timings and might
provide the 4K option... also at 60Hz instead of just 30Hz.


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

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => New

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

Title:
  i915 does not expose vendor-specific extended HDMI timings/modes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes

2020-08-05 Thread Leo Ramakersuca
I found the information, at section 3.4 of the manual
https://dlcdnets.asus.com/pub/ASUS/LCD%20Monitors/PB287/PB287Q_English.pdf
where VESA / IBM Modes Support Timing (DP/HDMI) reaches 4k but CEA-861
Formats Supported Timing (HDMI/MHL) only reach 1920

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

Title:
  i915 does not expose vendor-specific extended HDMI timings/modes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes

2020-08-05 Thread Leo Ramakersuca
Regarding HDMI version the spec which I gave a link to claims;
True Resolution : 3840x2160 at 60Hz (DisplayPort) ,3840x2160 at 30Hz (HDMI) 

Some while ago I was researching this issue and found a specification
page on the ASUS website which showed two formats for declaring the
frame rate, one extended only to the 1920 value while the other went to
the full 4K. From this I deduced that perhaps windows uses one report
format while linux uses the other. I cannot locate that page now, it may
have been taken down.

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

Title:
  i915 does not expose vendor-specific extended HDMI timings/modes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes

2020-08-05 Thread Leo Ramakersuca
Thanks for your work

I just bought and tried a new 4K hdmi cable, with no change. I noticed
that the monitor has TWO inputs, HDMI and HDMI/MHL (it had been plugged
into HDMI) but switching this to HDMI/MHL gave no result.

I am using MATE but the same issue occurs in several flavours of Ubuntu
that I have tried.

I dont know how to try the new kernel at 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8/ as you requested. If I 
attempt to ask Gdebi to load the 
linux-image-unsigned-5.8.0-050800-generic_5.8.0-050800.202008022230_amd64.deb 
package from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8/amd64/ it 
fails with unmet dependencies. 

kernel-modes.txt is attached

** Attachment added: "kernel-modes.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890418/+attachment/5399129/+files/kernel-modes.txt

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

Title:
  i915 does not expose vendor-specific extended HDMI timings/modes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1875113] Re: OpenGL not detected (Intel Ivy Bridge + Nvidia GeForce GT 635M)

2020-08-05 Thread Daniel van Vugt
Please open your own new bug by running:

  ubuntu-bug gnome-shell

This bug should stay closed.

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Opinion => Invalid

** Changed in: xorg-server (Ubuntu)
   Status: Opinion => Invalid

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Invalid => Won't Fix

** Changed in: xorg-server (Ubuntu)
   Status: Invalid => Won't Fix

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

Title:
  OpenGL not detected (Intel Ivy Bridge + Nvidia GeForce GT 635M)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1875113/+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 1875113] Re: OpenGL not detected (Intel Ivy Bridge + Nvidia GeForce GT 635M)

2020-08-05 Thread Jhosman Lizarazo
I'm too affected, please review.

Thanks

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Expired => Opinion

** Changed in: xorg-server (Ubuntu)
   Status: Expired => Opinion

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

Title:
  OpenGL not detected (Intel Ivy Bridge + Nvidia GeForce GT 635M)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1875113/+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 1826786] Re: High CPU usage of the Xorg process

2020-08-05 Thread Daniel van Vugt
> I mean that xorg is working and using 50%of the cou without
purpose.When I have just close fire fox.

When this happens please:

1. Run 'top' and check if any other processes are using more than 10%
CPU.

2. Look carefully at your screen and tell us if any part is constantly
changing, like any performance graphs etc.

3. Run:

   sudo apt-get install mesa-utils
   glxinfo > glxinfo.txt

   and attach the file 'glxinfo.txt' here.


** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  High CPU usage of the Xorg process

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1826786/+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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes

2020-08-05 Thread Daniel van Vugt
Please also run this command:

  grep . /sys/class/drm/*/modes > kernel-modes.txt

and attach the resulting text file here.

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

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  i915 does not expose vendor-specific extended HDMI timings/modes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes

2020-08-05 Thread Daniel van Vugt
This might have been fixed in the Intel graphics driver in a newer
kernel. Can you please test this one?

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8/

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

Title:
  i915 does not expose vendor-specific extended HDMI timings/modes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Re: External monitor will not display to 4k

2020-08-05 Thread Daniel van Vugt
Actually the problem might just be that the Linux kernel doesn't
understand extended vendor-specific display timings. I've decoded your
monitor's EDID and it reveals that 3840x2160 30Hz is mentioned:

edid-decode (hex):

00 ff ff ff ff ff ff 00 04 69 a3 28 24 51 00 00 
0e 1b 01 03 80 3e 22 78 3a 1c b5 a3 57 4f a0 27 
0d 50 54 bf ef 00 d1 c0 81 40 81 80 95 00 b3 00 
71 4f 81 c0 01 01 04 74 00 30 f2 70 5a 80 b0 58 
8a 00 6d 55 21 00 00 1a 02 3a 80 18 71 38 2d 40 
58 2c 45 00 6d 55 21 00 00 1e 00 00 00 fd 00 1e 
50 18 a0 1e 00 0a 20 20 20 20 20 20 00 00 00 fc 
00 41 53 55 53 20 50 42 32 38 37 51 0a 20 01 83 

02 03 2c f1 51 01 02 03 11 12 13 04 14 05 0e 0f 
1d 1e 1f 90 20 22 23 09 17 07 83 01 00 00 6d 03 
0c 00 20 00 00 3c 20 00 60 01 02 03 56 5e 00 a0 
a0 a0 29 50 30 20 35 00 6d 55 21 00 00 1e e2 68 
00 a0 a0 40 2e 60 30 20 36 00 6d 55 21 00 00 1a 
01 1d 00 bc 52 d0 1e 20 b8 28 55 40 6d 55 21 00 
00 1e 8c 0a d0 90 20 40 31 20 0c 40 55 00 6d 55 
21 00 00 18 00 00 00 00 00 00 00 00 00 00 00 5e 



EDID version: 1.3
Manufacturer: ACI Model 10403 Serial Number 20772
Made in week 14 of 2017
Digital display
Maximum image size: 62 cm x 34 cm
Gamma: 2.20
DPMS levels: Off
Undefined display color type
First detailed timing is preferred timing
Color Characteristics
  Red:   0.6367, 0.3408
  Green: 0.3115, 0.6250
  Blue:  0.1542, 0.0537
  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)
640x48066.667 Hz   4:335.000 kHz  30.240 MHz (Apple)
640x48072.809 Hz   4:337.861 kHz  31.500 MHz (DMT)
640x48075.000 Hz   4:337.500 kHz  31.500 MHz (DMT)
800x60056.250 Hz   4:335.156 kHz  36.000 MHz (DMT)
800x60060.317 Hz   4:337.879 kHz  40.000 MHz (DMT)
800x60072.188 Hz   4:348.077 kHz  50.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)
   1024x76870.069 Hz   4:356.476 kHz  75.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)
Standard Timings
   1920x1080   60.000 Hz  16:967.500 kHz 148.500 MHz (DMT)
   1280x96060.000 Hz   4:360.000 kHz 108.000 MHz (DMT)
   1280x1024   60.020 Hz   5:463.981 kHz 108.000 MHz (DMT)
   1440x90059.887 Hz  16:10   55.935 kHz 106.500 MHz (DMT)
   1680x1050   59.954 Hz  16:10   65.290 kHz 146.250 MHz (DMT)
   1152x86475.000 Hz   4:367.500 kHz 108.000 MHz (DMT)
   1280x72060.000 Hz  16:945.000 kHz  74.250 MHz (DMT)
Detailed mode: Clock 297.000 MHz, 621 mm x 341 mm
   3840 4016 4104 4400 (176  88 296)
   2160 2168 2178 2250 (  8  10  72)
   +hsync -vsync
   VertFreq: 30.000 Hz, HorFreq: 67.500 kHz
Detailed mode: Clock 148.500 MHz, 621 mm x 341 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 Range Limits
  Monitor ranges (GTF): 30-80 Hz V, 24-160 kHz H, max dotclock 300 MHz
Display Product Name: ASUS PB287Q
Has 1 extension block
Checksum: 0x83



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
40 bytes of CTA data blocks
  Video Data Block
  640x48059.940 Hz   4:331.469 kHz  25.175 MHz (VIC   1)
  720x48059.940 Hz   4:331.469 kHz  27.000 MHz (VIC   2)
  720x48059.940 Hz  16:931.469 kHz  27.000 MHz (VIC   3)
  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)
 1280x72060.000 Hz  16:945.000 kHz  74.250 MHz (VIC   4)
 1920x1080i  50.000 Hz  16:928.125 kHz  74.250 MHz (VIC  20)
 1920x1080i  60.000 Hz  16:933.750 kHz  74.250 MHz (VIC   5)
 1440x48059.940 Hz   4:331.469 kHz  54.000 MHz (VIC  14)
 1440x48059.940 Hz  16:931.469 kHz  54.000 MHz (VIC  15)
 1440x57650.000 Hz   4:331.250 kHz  54.000 MHz (VIC  29)
 1440x57650.000 Hz  16:931.250 kHz  54.000 MHz (VIC  30)
 1920x1080   50.000 Hz  16:956.250 kHz 148.500 MHz (VIC  31)
 1920x1080   60.000 Hz  16:967.500 kHz 148.500 MHz (VIC  16, native)
 1920x1080   24.000 Hz  16:927.000 kHz  74.250 MHz (VIC  32)
 1920x1080   30.000 Hz  16:933.750 kHz  74.250 MHz (VIC  34)
  Audio Data Block
Linear PCM, max channels 2
  Supported sample rates (kHz): 96 48 44.1 32
  Supported sample sizes (bits): 24 20 16
  Speaker Allocation Data Block
Speaker map:
  FL/FR - 

[Ubuntu-x-swat] [Bug 1890418] [NEW] External monitor will not display to 4k

2020-08-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have a Toshiba radius 11 laptop which has a 4 k native screen. I have
connected an Asus PB287Q 28" external monitor (https://www.asus.com/us
/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays
the full 4K resolution when running under windows10 but will only reach
a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just
dual booting. Under Monitor Preferences this monitor is detected as an
"Ancor Communications inc 28" and the monitor preferences provides a
number of resolution steps up to 1920. If I issue "xrandr --addmode
HDMI-1 3840x2160" this resolution is added to the monitor preferences
pick list but attempting to apply it results in "the selected
configuration for displays could not ..." message

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


** Tags: focal
-- 
External monitor will not display to 4k
https://bugs.launchpad.net/bugs/1890418
You received this bug notification because you are a member of Ubuntu-X, which 
is subscribed to xorg-server in Ubuntu.

___
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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)

2020-08-05 Thread Daniel van Vugt
** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  VGA image is ghosted and stretched (LG L1953S)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890436/+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 1890436] Status changed to Confirmed

2020-08-05 Thread Ubuntu Kernel Bot
This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  VGA image is ghosted and stretched (LG L1953S)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890436/+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 1772588] Re: Remove obsolete X11 drivers from the archive

2020-08-05 Thread Steve Langasek
Removing packages:
xserver-xorg-input-void 1:1.4.1-1build3 in groovy
xserver-xorg-input-void 1:1.4.1-1build3 in groovy amd64
xserver-xorg-input-void 1:1.4.1-1build3 in groovy arm64
xserver-xorg-input-void 1:1.4.1-1build3 in groovy armhf
xserver-xorg-input-void 1:1.4.1-1build3 in groovy ppc64el
xserver-xorg-input-void 1:1.4.1-1build3 in groovy riscv64
xserver-xorg-input-void 1:1.4.1-1build3 in groovy s390x
xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy amd64
xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy arm64
xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy armhf
xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy ppc64el
xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy riscv64
xserver-xorg-input-void-dbgsym 1:1.4.1-1build3 in groovy s390x
Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603
Remove [y|N]? y


** Changed in: xserver-xorg-input-void (Ubuntu)
   Status: New => Fix Released

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

Title:
  Remove obsolete X11 drivers from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1890436] Re: VGA image is ghosted and stretched (LG L1953S)

2020-08-05 Thread Daniel van Vugt
This looks like a signalling problem. There doesn't seem to be any
corruption in the image. Only the signal to the monitor doesn't
correctly match the frequencies that the monitor requires.

As a workaround please try selecting 'Ubuntu on Wayland' from the login
screen.

Please also try a different VGA cable if you can.


** Summary changed:

- Screen corruption with multi monitor setup
+ VGA image is ghosted and stretched (LG L1953S)

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

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

Title:
  VGA image is ghosted and stretched (LG L1953S)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890436/+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 1890411] Re: Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

2020-08-05 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Tags added: bionic

** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1890411/+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 1890436] Re: Screen corruption with multi monitor setup

2020-08-05 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (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/1890436

Title:
  Screen corruption with multi monitor setup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1890436/+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 1890436] [NEW] Screen corruption with multi monitor setup

2020-08-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:


Hello, last week I was digging in the BIOS of my PC at work since I tried to 
see if there is a way to update the dbx for secure boot. Since there was no 
option to perform this task, I modified some settings. In detail, I disabled 
CSM in BIOS and that's when hell broke loose!

To get an idea about the hardware, the Lenovo machine isn't running the
latest BIOS as its updater is broken and won't update it within win or
its ISO image. It uses the previous version released by its
manufacturer.

The machine has an XGA VGA monitor and a WQHD DP monitor. When CSM is enabled 
the DP monitor is lit first and then the VGA one prior OS loading. When CSM is 
disabled it goes the other way around. The VGA monitor is lit and the DP one 
opens up during OS load. With CSM disabled the VGA monitor is the primary one 
and it is corrupted as you can see on the pictures I have attached.
Interestingly printing screens within Ubuntu does not capture the corruption 
problem I am getting as you can see on the pictures I have also attached. 
Neither X log contains anything useful. The issue is repeatable on every boot.

As I have seen on other bug reports, I have enabled DRM debug, captured
the dmesg using a huge buffer to get it and have uploaded it as well. I
hope that it will help you track this issue down and fix it soon. Since
I will be away some days for vacation, I will have physical access to it
till this Friday and will get back to work at the 24th of August. In the
mean time, I hope that someone will pinpoint the root cause of it and
prepare a patch.

Since this machine is running w10 2004, it should be noted that in win I
do not get any corruption at all either in CSM mode or UEFI mode.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CasperVersion: 1.445
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug  5 11:30:51 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[17aa:3083]
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 3209C54
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed 
maybe-ubiquity quiet splash ---
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/17/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 9SKT9BAUS
dmi.board.name: MAHOBAY
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9BAUS:bd07/17/2018:svnLENOVO:pn3209C54:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrNotDefined:cvnLENOVO:ct3:cvrNone:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: 3209C54
dmi.product.sku: LENOVO_MT_3209
dmi.product.version: ThinkCentre M92p
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-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 corruption focal third-party-packages ubuntu
-- 
Screen corruption with multi monitor setup
https://bugs.launchpad.net/bugs/1890436
You received this bug notification because you are a member of Ubuntu-X, which 
is subscribed to xorg in Ubuntu.

___
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 1890411] Re: Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

2020-08-05 Thread Ronald Hecht
Was wrong package

** Package changed: apport (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890411/+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 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values

2020-08-05 Thread TreviƱo
Marking this verified again, as it was verified as fixed in version
3.36.4-0ubuntu0.20.04.1 (see [1] and [2]), so given that the changes in
.2 [3] do not affect this behavior, we can safely consider it already
verified.

[1] https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/comments/30
[2] https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/comments/31
[3] 
https://launchpadlibrarian.net/490341554/mutter_3.36.4-0ubuntu0.20.04.1_3.36.4-0ubuntu0.20.04.2.diff.gz


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

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

Title:
  [nvidia] Screen turns off when trying to set some fractional scaling
  values

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/+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 1890411] [NEW] Xorg crashes when starting gdm3. Bug in libgl1-mesa-dri.

2020-08-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When ubuntu starts up, gdm3 does not start due to a crash in the the
xserver:

[  1271.342] (II) SELinux: Disabled on system
[  1271.346] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[  1271.346] (II) AIGLX: enabled GLX_ARB_create_context
[  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_profile
[  1271.346] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[  1271.346] (II) AIGLX: enabled GLX_INTEL_swap_event
[  1271.346] (II) AIGLX: enabled GLX_SGI_swap_control
[  1271.346] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[  1271.346] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[  1271.346] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[  1271.346] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[  1271.346] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[  1271.346] (II) AIGLX: Loaded and initialized i965
[  1271.346] (II) GLX: Initialized DRI2 GL provider for screen 0
[  1271.348] (II) modeset(0): Damage tracking initialized
[  1271.348] (II) modeset(0): Setting screen physical size to 508 x 317
[  1271.352] (EE) 
[  1271.352] (EE) Backtrace:
[  1271.352] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5649b579bacd]
[  1271.352] (EE) 1: /usr/lib/xorg/Xorg (0x5649b55e3000+0x1bc869) 
[0x5649b579f869]
[  1271.352] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f5c7d0a5000+0x128a0) [0x7f5c7d0b78a0]
[  1271.352] (EE) 3: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e8652) [0x7f5c784e2652]
[  1271.352] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x8e877f) [0x7f5c784e277f]
[  1271.352] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x122916) [0x7f5c77d1c916]
[  1271.352] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x1189bc) [0x7f5c77d129bc]
[  1271.352] (EE) 7: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x109c1b) [0x7f5c77d03c1b]
[  1271.352] (EE) 8: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x279558) [0x7f5c77e73558]
[  1271.352] (EE) 9: /usr/lib/x86_64-linux-gnu/dri/i965_dri.so 
(0x7f5c77bfa000+0x2796e3) [0x7f5c77e736e3]
[  1271.352] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so 
(0x7f5c79937000+0x1a1ab) [0x7f5c799511ab]
[  1271.352] (EE) 11: /usr/lib/xorg/Xorg (0x5649b55e3000+0x13ed03) 
[0x5649b5721d03]
[  1271.352] (EE) 12: /usr/lib/xorg/Xorg (miPaintWindow+0x22f) [0x5649b577fd1f]
[  1271.352] (EE) 13: /usr/lib/xorg/Xorg (miWindowExposures+0x112) 
[0x5649b577fa62]
[  1271.352] (EE) 14: /usr/lib/xorg/Xorg (0x5649b55e3000+0xa9c41) 
[0x5649b568cc41]
[  1271.352] (EE) 15: /usr/lib/xorg/Xorg (MapWindow+0x114) [0x5649b5665d04]
[  1271.352] (EE) 16: /usr/lib/xorg/Xorg (0x5649b55e3000+0x56e79) 
[0x5649b5639e79]
[  1271.352] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) 
[0x7f5c7ccd5b97]
[  1271.352] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x5649b5623b8a]
[  1271.352] (EE) 
[  1271.352] (EE) Segmentation fault at address 0x4
[  1271.352] (EE) 
Fatal server error:
[  1271.352] (EE) Caught signal 11 (Segmentation fault). Server aborting
[  1271.352] (EE) 
[  1271.352] (EE) 

As i965_dri.so is part of the libgl-mesa-dri package I downgraded this
specific package from version 20.0.8-0ubuntu1~18.04.1 back to
19.2.8-0ubuntu0~18.04.3.

This solves the problem. So I suspect that the problem is in this
specific package.

My machine is (uname):
4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 
x86_64 GNU/Linux

(lspci)
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller 
(rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation H81 Express LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 
6-port SATA Controller 1 [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus 
Controller (rev 05)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 0c)

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

-- 
Xorg 

[Ubuntu-x-swat] [Bug 1890307] Re: [vmwgfx] Screen resolution change not possible (AMD/VirtualBox)

2020-08-05 Thread snow
I manged to change the resolution. Scaling works also. But the screen
blinks all the time. Only in full screen modus it is OK.

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

Title:
  [vmwgfx] Screen resolution change not possible (AMD/VirtualBox)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1890307/+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 1890390] Re: Xorg freeze

2020-08-05 Thread Daniel van Vugt
When the problem happens, can you still move the mouse cursor?

Also, next time a freeze happens please reboot and then run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.


** Tags added: nouveau

** Summary changed:

- Xorg freeze
+ [nouveau] Xorg freeze

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  [nouveau] Xorg freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890390/+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 1890390] Re: [nouveau] Xorg freeze

2020-08-05 Thread Daniel van Vugt
Also, it looks like your Nvidia GPU is supported by the latest Nvidia
drivers. I recommend opening the 'Additional Drivers' app and installing
the latest proprietary Nvidia driver. It's generally more reliable (and
better performing) than the open source 'nouveau' driver you are using.

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

Title:
  [nouveau] Xorg freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890390/+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 1890307] Re: [vmwgfx] Screen resolution change not possible (AMD/VirtualBox)

2020-08-05 Thread snow
I use Kubuntu. I think there is no option to change the windows manager
there.

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

Title:
  [vmwgfx] Screen resolution change not possible (AMD/VirtualBox)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1890307/+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 1890390] [NEW] Xorg freeze

2020-08-05 Thread Shantanu Bhat
Public bug reported:

The screen freezes especially when I am using Zoom. If I minimise the
Zoom window or shorten it to a small size, the screen does not freeze.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug  5 16:41:20 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Very infrequently
GraphicsCard:
 NVIDIA Corporation GK107GL [Quadro K600] [10de:0ffa] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: NVIDIA Corporation GK107GL [Quadro K600] [10de:094b]
InstallationDate: Installed on 2020-04-07 (119 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: Dell Inc. Precision T1700
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=60b287f6-f7bb-4e75-a4b3-61468b59150b ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.asset.tag: MU00042259
dmi.board.name: 04JGCK
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.asset.tag: MU00042259
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd06/06/2013:svnDellInc.:pnPrecisionT1700:pvr01:rvnDellInc.:rn04JGCK:rvrA02:cvnDellInc.:ct15:cvr:
dmi.product.name: Precision T1700
dmi.product.sku: Precision T1700
dmi.product.version: 01
dmi.sys.vendor: Dell 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.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 freeze 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/1890390

Title:
  Xorg freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1890390/+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 1890307] Re: [vmwgfx] Screen resolution change not possible (AMD/VirtualBox)

2020-08-05 Thread Daniel van Vugt
Try selecting 'Ubuntu on Wayland' from the login screen. Is that more
usable?

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

Title:
  [vmwgfx] Screen resolution change not possible (AMD/VirtualBox)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1890307/+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 1890384] Re: Xorg crash

2020-08-05 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

** Summary changed:

- Xorg crash
+ Crash

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

Title:
  Crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1890384/+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 1890307] Re: [vmwgfx] Screen resolution change not possible (AMD/VirtualBox)

2020-08-05 Thread snow
Yes, I could resize the window which did not change the resolution.
After updates today morning the screen is blinking permanently after
reboot quite quickly. It is difficult to do anything.

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

Title:
  [vmwgfx] Screen resolution change not possible (AMD/VirtualBox)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1890307/+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 1890384] [NEW] Xorg crash

2020-08-05 Thread andre
Public bug reported:

ls -l /var/crash

backport-iwlwifi-dkms.0.crash
_opt_google_chrome_chrome.1000.crash
_usr_bin_gnome-control-center.1000.crash

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-111.112-generic 4.15.18
Uname: Linux 4.15.0-111-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug  5 09:12:04 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 backport-iwlwifi, 7906: added
 rtl8812au, 5.6.4.2~ppa: added
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 510 [1043:8694]
InstallationDate: Installed on 2018-12-21 (592 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 1c4f:0026 SiGma Micro Keyboard
 Bus 001 Device 003: ID 062a: Creative Labs Optical mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-111-generic 
root=UUID=239295ef-655d-4e9d-986a-bc396201c864 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/22/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3408
dmi.board.asset.tag: Default string
dmi.board.name: H110M-K
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3408:bd09/22/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
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.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 crash 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/1890384

Title:
  Xorg crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1890384/+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