[Ubuntu-x-swat] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)

2020-06-05 Thread Noctis Bennington
Apparently this happens to Ubuntu 18.04.4 and 19.10 (and obviously on
20.04). But on 18.04.1 the second monitor works perfectly. Windows 10
too.

This seems like a mistake or bug on the Mesa/Kernel.

At the moment, I'll be on 18.04.1 but updated.

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

Title:
  Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS
  Laptop)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+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 1876882] Re: Backport packages for 18.04.5 HWE stack

2020-06-05 Thread Gianfranco Costamagna
Hello, this broke virtualbox builds.

gcc -c -O2 -g -pipe -Wshadow -Wall -Wextra -Wno-missing-field-initializers 
-Wno-unused -Wno-trigraphs -fdiagnostics-show-option -Wno-unused-parameter 
-Wlogical-op -Wno-variadic-macros -Wno-long-long -Wunused-variable 
-Wunused-function -Wunused-label -Wunused-parameter -Wmissing-prototypes 
-Wstrict-prototypes -Wmissing-declarations 
-Werror-implicit-function-declaration -Wno-variadic-macros -O2 -mtune=generic 
-fno-omit-frame-pointer -fno-strict-aliasing -fvisibility=hidden 
-DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT -fPIC 
-Wno-overlength-strings  -include /<>/include/iprt/linux/symvers.h 
-fno-stack-protector -m64 -I/<>/src/VBox/GuestHost/OpenGL/include 
-I/<>/out/obj/VBoxOGLgen -I/<>/out/obj/VBoxEGL/dtrace 
-I/<>/include -I/<>/out -DVBOX -DVBOX_OSE 
-DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_REM -DVBOX_WITH_RAW_MODE -DRT_OS_LINUX 
-D_FILE_OFFSET_BITS=64 -DRT_ARCH_AMD64 -D__AMD64__ -DVBOX_WITH_DEBUGGER 
-DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" 
-DRTPATH_APP_PRIVATE_ARCH=\"/usr/lib/virtualbox\" 
-DRTPATH_SHARED_LIBS=\"/usr/lib/virtualbox\" 
-DRTPATH_APP_DOCS=\"/usr/share/doc/virtualbox\" -DIN_RING3 -DVBOX_WITH_DTRACE 
-DVBOX_WITH_DTRACE_R3 -DIN_GUEST -DIN_GUEST_R3 -DIN_RT_R3 -DGC_ARCH_BITS=64 
-DPIC -DVBOX_WITH_HGCM -DLOG_USE_C99 -DRT_WITHOUT_EXEC_ALLOC -DLinux=1 
-D_GNU_SOURCE -Wp,-MD,/<>/out/obj/VBoxEGL/egl.o.dep 
-Wp,-MT,/<>/out/obj/VBoxEGL/egl.o -Wp,-MP -o 
/<>/out/obj/VBoxEGL/egl.o 
/<>/src/VBox/Additions/common/crOpenGL/egl.c
In file included from 
/<>/src/VBox/Additions/common/crOpenGL/glx.c:32:0:
/<>/src/VBox/Additions/common/crOpenGL/dri_glx.h:114:35: error: 
conflicting types for ‘glXQueryGLXPbufferSGIX’
 extern DECLEXPORT(int) VBOXGLXTAG(glXQueryGLXPbufferSGIX)
   ^
/<>/src/VBox/Additions/common/crOpenGL/dri_glx.h:31:27: note: in 
definition of macro ‘VBOXGLXTAG’
  #define VBOXGLXTAG(Func) Func
   ^~~~
In file included from /usr/include/GL/glx.h:328:0,
 from 
/<>/src/VBox/GuestHost/OpenGL/include/chromium.h:99,
 from 
/<>/src/VBox/Additions/common/crOpenGL/glx.c:26:
/usr/include/GL/glxext.h:861:6: note: previous declaration of 
‘glXQueryGLXPbufferSGIX’ was here
 void glXQueryGLXPbufferSGIX (Display *dpy, GLXPbufferSGIX pbuf, int attribute, 
unsigned int *value);
  ^~
kmk_builtin_append -n "/<>/out/obj/VBoxOGL/context.o.dep" "" 
"/<>/src/VBox/Additions/common/crOpenGL/context.c:" ""
kBuild: Creating directory /<>/out/obj/pam_vbox/
kmk_builtin_mkdir -p -- /<>/out/obj/pam_vbox/
kBuild: Compiling pam_vbox - 
/<>/src/VBox/Additions/common/pam/pam_vbox.cpp => 
/<>/out/obj/pam_vbox/pam_vbox.o
kmk_builtin_rm -f -- /<>/out/obj/pam_vbox/pam_vbox.o.dep 
/<>/out/obj/pam_vbox/pam_vbox.o  
g++ -c -O2 -g -pipe -pedantic -Wshadow -Wall -Wextra 
-Wno-missing-field-initializers -Wno-unused -Wno-trigraphs 
-fdiagnostics-show-option -Wno-unused-parameter -Wlogical-op   
-Wno-variadic-macros -Wno-long-long -Wunused-variable -Wunused-function 
-Wunused-label -Wunused-parameter  -Wno-overloaded-virtual -Wno-variadic-macros 
-O2 -mtune=generic -fno-omit-frame-pointer -fno-strict-aliasing 
-fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT 
-fvisibility-inlines-hidden   -fno-exceptions -fPIC -fno-exceptions -include 
/<>/include/iprt/linux/symvers.h -fno-stack-protector -m64 
-I/<>/out/obj/pam_vbox/dtrace -I/<>/include 
-I/<>/out -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS 
-DVBOX_WITH_REM -DVBOX_WITH_RAW_MODE -DRT_OS_LINUX -D_FILE_OFFSET_BITS=64 
-DRT_ARCH_AMD64 -D__AMD64__ -DVBOX_WITH_DEBUGGER -DVBOX_WITH_HARDENING 
-DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" 
-DRTPATH_APP_PRIVATE_ARCH=\"/usr/lib/virtualbox\" 
-DRTPATH_SHARED_LIBS=\"/usr/lib/virtualbox\" 
-DRTPATH_APP_DOCS=\"/usr/share/doc/virtualbox\" -DIN_RING3 -DVBOX_WITH_DTRACE 
-DVBOX_WITH_DTRACE_R3 -DIN_GUEST -DIN_GUEST_R3 -DIN_RT_R3 -DGC_ARCH_BITS=64 
-DPIC -DLOG_TO_BACKDOOR -DVBOX_WITH_HGCM -DVBOX_WITH_GUEST_PROPS -DLOG_USE_C99 
-DRT_WITHOUT_EXEC_ALLOC 
-Wp,-MD,/<>/out/obj/pam_vbox/pam_vbox.o.dep 
-Wp,-MT,/<>/out/obj/pam_vbox/pam_vbox.o -Wp,-MP -o 
/<>/out/obj/pam_vbox/pam_vbox.o 
/<>/src/VBox/Additions/common/pam/pam_vbox.cpp
In file included from 
/<>/src/VBox/Additions/common/crOpenGL/glx.c:32:0:
/<>/src/VBox/Additions/common/crOpenGL/glx.c:766:28: error: 
conflicting types for ‘glXQueryGLXPbufferSGIX’
 DECLEXPORT(int) VBOXGLXTAG(glXQueryGLXPbufferSGIX)(Display *dpy, GLXPbuffer 
pbuf,
^
/<>/src/VBox/Additions/common/crOpenGL/dri_glx.h:31:27: note: in 
definition of macro ‘VBOXGLXTAG’
  #define VBOXGLXTAG(Func) Func
   ^~~~
In file included from /usr/include/GL/glx.h:328:0,
 from 
/<>/src/VBox/GuestHost/OpenGL/include/chromium.h:99,
 from 
/<>/src/VBox/Additions/common/crOpenGL/glx.c:26:
/usr/include/GL/glxext.h:861:6: note: previous declaration of 

[Ubuntu-x-swat] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

2020-06-05 Thread jman6495
Sadly, adding Option "EnablePageFlip" "off" doesn't appear to resolve
the issue on the 3500U, however i've made quite a few modifications on
this install.

I'll give it a go on a fresh install this evening and get back to you.

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

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

2020-06-05 Thread Daniel van Vugt
Please try editing /etc/gdm3/custom.conf and uncomment:

  #WaylandEnable=false

so it is:

  WaylandEnable=false

Then reboot.

** Summary changed:

- Xorg freeze
+ [bochs_drm/VESA] Xorg freeze

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

** Summary changed:

- [bochs_drm/VESA] Xorg freeze
+ [bochs_drm] Booting gets stuck with corrupt graphics

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

** Changed in: mutter (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/1882216

Title:
  [bochs_drm] Booting gets stuck with corrupt graphics

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1882216/+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 1882212] Re: Cursor blinks/flickers on screen refresh (only on built in monitor)

2020-06-05 Thread Daniel van Vugt
It appears you're using Intel graphics with the modesetting driver, so
you should always have a hardware cursor.

It also appears you're using 200% scaling on one monitor. Could you
please try:

 * Disabling fractional scaling in Settings.

 * Using a scaling factor of 100%, briefly.

 * Selecting 'Ubuntu on Wayland' from the login screen.

** Tags added: cursor xrandr-scaling

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

** Changed in: mutter (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/1882212

Title:
  Cursor blinks/flickers on screen refresh (only on built in monitor)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1882212/+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 1573959] Re: On-screen text disappears after suspend

2020-06-05 Thread Timo Suoranta
I am affected as well:

$ uname -a
Linux tsuoranta-lnx 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

$ lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106 [GeForce GTX 
1060 6GB] [10de:1c03] (rev a1)

$ lsb_release -d
Description:Ubuntu 20.04 LTS

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

Title:
  On-screen text disappears after suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1573959/+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 1882212] Re: Cursor blinks/flickers on screen refresh (only on built in monitor)

2020-06-05 Thread Lorenzo Callegari
** Summary changed:

- Cursor blinks on screen refresh (only on built in monitor)
+ Cursor blinks/flickers on screen refresh (only on built in monitor)

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

Title:
  Cursor blinks/flickers on screen refresh (only on built in monitor)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882212/+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 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights

2020-06-05 Thread Tim Mueller
Ah, that makes much sense. If you are having problems you could help
yourself. ;)

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

Title:
  [vmwgfx] Gnome Desktop only starting with root rights

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882102/+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 1882212] Re: Cursor blinks on screen refresh (only on built in monitor)

2020-06-05 Thread Lorenzo Callegari
** Summary changed:

- Arrow blinks on screen refresh (only on built in monitor)
+ Cursor blinks on screen refresh (only on built in monitor)

** Description changed:

  I have a double monitor setup, my laptop has a built-in 4k screen and my 
external is 1080p.
- When I use the mouse on the external screen the arrow indicator has no 
problem but when I go on the built-in monitor the arrow indicator will blink 
(disappear and reappear) every time there is some kind of refresh on either 
screen (e.g. I type something or something is displaying text in the terminal).
+ When I use the mouse on the external screen the cursor has no problem but 
when I go on the built-in monitor the pointer will blink (disappear and 
reappear) every time there is some kind of refresh on either screen (e.g. I 
type something or something is displaying text in the terminal).
  
  My current display settings are:
  Display Mode: Join Displays
  Primary Display: either doesn't make any difference
  
  Built in display:
  - Orientation: Landscape
  - Resolution: 3840x2160
  - Refresh Rate: 60,00Hz
  - Scale: 200%
  - Fractional Scaling: ON
  
  External Display:
  - Orientation: Landscape
  - Resolution: 1920x1080
  - Refresh Rate: 60,00Hz
  - Scale: 100%
  - Fractional Scaling: ON
  
  Ubuntu release: 20.04 LTS
  Xorg version: 1:7.7+19ubuntu14
- Expected behavior: Arrow doesn't blink
- Current behavior: Arrow blinks
+ Expected behavior: Pointer doesn't blink
+ Current behavior: Pointer blinks
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  5 10:27:31 2020
  DistUpgraded: 2020-04-24 10:45:52,182 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
-  nvidia, 440.64, 5.4.0-31-generic, x86_64: installed
-  nvidia, 440.64, 5.4.0-33-generic, x86_64: installed
+  nvidia, 440.64, 5.4.0-31-generic, x86_64: installed
+  nvidia, 440.64, 5.4.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
-Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080]
-Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
+  Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
+    Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080]
+    Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
  InstallationDate: Installed on 2019-07-04 (336 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=acb2d85b-81be-4cf8-8e76-5abca360479b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago)
  dmi.bios.date: 04/17/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  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.:bvrN501VW.307:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N501VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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.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-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

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

Title:
  Cursor blinks on screen refresh (only on built in monitor)

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

___
Mailing list: 

[Ubuntu-x-swat] [Bug 1882216] [NEW] Xorg freeze

2020-06-05 Thread Tim Mueller
Public bug reported:

When booting on a VPS connected via VNC at first the text messages via
boot are displayed. Then the resolution changes several times (VNC size
changes) and after a lot of resolution changes it gets stuck in a
corrupd graphic design. The cursor is still blinking but alt+Fx does
also not work.

Using sudo service gdm3 stop and sudo startx is working. Due to the fact
that the VNC console is completely frozen and this is hosted at a
provider I have to use a separate putty session to stop gdm and starting
a new gui session which is then displayed in the VNC.

This problem does not exist with Ubuntu 18.04 LTS. It does not matter if
I use a fresh installed Ubuntu 20.04 or an upgraged 18.04 LTS to 20.04
LTS. On a second VPS the problem is similar but not the same. The second
one does not get totally frozen. There is still no GUI when booting but
it ends up in a purple uniform screen even the text mode is purple (the
first VPS ends up a blueish screen with blue vertical lines).

On the second VPS it is possible to switch to shell (purple style) and
executing the abovementioned commands directly without a second putty
session. But the behavior is basically similar for both VPS.

When using sudo reboot the second VPS displays text again and the first
only some graphic trash. So basically they have both the same behavior
but on the first the graphics are totally destroyed even text is not
working anymore. The Funny thing is that startx is still working but
after clothng the startx session the graphic trash is shown again.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Fri Jun  5 10:39:59 2020
DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte 
keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird 
vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der 
Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des 
Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem 
anderen Prozess verwendet?)
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed
 rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Device [1234:] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc. Device [1af4:1100]
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=UUID=4bffe67b-531d-4b96-b192-538defc6d4a0 ro nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-04-26 (39 days ago)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-4.1
dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-4.1
dmi.sys.vendor: QEMU
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 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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 false-gpu-hang focal freeze third-party-packages 
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/1882216

Title:
  Xorg freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882216/+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 1882212] [NEW] Cursor blinks on screen refresh (only on built in monitor)

2020-06-05 Thread Lorenzo Callegari
Public bug reported:

I have a double monitor setup, my laptop has a built-in 4k screen and my 
external is 1080p.
When I use the mouse on the external screen the arrow indicator has no problem 
but when I go on the built-in monitor the arrow indicator will blink (disappear 
and reappear) every time there is some kind of refresh on either screen (e.g. I 
type something or something is displaying text in the terminal).

My current display settings are:
Display Mode: Join Displays
Primary Display: either doesn't make any difference

Built in display:
- Orientation: Landscape
- Resolution: 3840x2160
- Refresh Rate: 60,00Hz
- Scale: 200%
- Fractional Scaling: ON

External Display:
- Orientation: Landscape
- Resolution: 1920x1080
- Refresh Rate: 60,00Hz
- Scale: 100%
- Fractional Scaling: ON

Ubuntu release: 20.04 LTS
Xorg version: 1:7.7+19ubuntu14
Expected behavior: Arrow doesn't blink
Current behavior: Arrow blinks

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun  5 10:27:31 2020
DistUpgraded: 2020-04-24 10:45:52,182 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 440.64, 5.4.0-31-generic, x86_64: installed
 nvidia, 440.64, 5.4.0-33-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
InstallationDate: Installed on 2019-07-04 (336 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: ASUSTeK COMPUTER INC. N501VW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=acb2d85b-81be-4cf8-8e76-5abca360479b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-24 (41 days ago)
dmi.bios.date: 04/17/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N501VW.307
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N501VW
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.:bvrN501VW.307:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: N
dmi.product.name: N501VW
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
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.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-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 focal 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/1882212

Title:
  Cursor blinks on screen refresh (only on built in monitor)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882212/+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 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights

2020-06-05 Thread Daniel van Vugt
I am using multi-user.target because I am compiling gnome-shell from
scratch, for development. So also run it manually.

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

Title:
  [vmwgfx] Gnome Desktop only starting with root rights

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882102/+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 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights

2020-06-05 Thread Tim Mueller
You are using multi user target because you like to or also having some
kind of problems?

If I use (which means removing the if else)
exec /usr/libexec/gnome-session-binary --systemd "$@" 
the result is the same. Still the same message for missing permission.

And with
exec /usr/libexec/gnome-session-binary --builtin "$@"
the result is identical.

I thought maybe it's good to sort out this error first and if there are
no problems without starting GUI without root rights than maybe a second
bug report for boot to gui. But I can also open another bug report now.
I'm not sure if this bugs / problems are connected in any way or not.

With 18.04 I did not have this kind of errors on both machines. The
funny thing is: On my Raspberry Pi 4b it is working from start (ok, this
is a special distribution for special hardware so it should run).

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

Title:
  [vmwgfx] Gnome Desktop only starting with root rights

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882102/+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 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen

2020-06-05 Thread Daniel van Vugt
Note the original bug report here is not using the 'intel' driver, and
in fact you probably shouldn't be using it either. The 'intel' driver is
old, unsupported and buggy. The default 'modesetting' driver is what we
recommend so if you have a file named '20-intel.conf' it should probably
be deleted.

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

Title:
  [Intel Braswell] Cursor gets stuck on left side of the screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1767654/+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 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights

2020-06-05 Thread Daniel van Vugt
BTW, the failing line 29 of script is systemd-related:

if [ -d "${XDG_RUNTIME_DIR}/systemd" ]; then
  exec /usr/libexec/gnome-session-binary --systemd "$@"
else
  exec /usr/libexec/gnome-session-binary --builtin "$@"
fi

So I wonder if you just need to remove ${XDG_RUNTIME_DIR}/systemd ?

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

Title:
  [vmwgfx] Gnome Desktop only starting with root rights

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882102/+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 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights

2020-06-05 Thread Daniel van Vugt
> if I try to boot directly to GUI the resolution changes several times
... and then get's stuck.

That sounds like an interesting separate bug which we might be able to
fix or explain. Please open a new bug for that if you can.

> I now switched both VPS to multi user target insted of graphical boot

By chance I am also using multi-user.target right now. But 'startx'
works for me.

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

Title:
  [vmwgfx] Gnome Desktop only starting with root rights

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882102/+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 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen

2020-06-05 Thread Anton Panduru
I found a fix for the issues on kde, as I am running kubuntu 20.04, all
credit goes to the original poster.

My contribution was only to change the DRI setting to 3 not "false"
because this caused slowdown.

https://forum.manjaro.org/t/how-i-fixed-my-tearing-and-graphical-issues-
completely-manjaro-kde/108390

** Attachment added: "20-intel.conf"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+attachment/5380581/+files/20-intel.conf

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

Title:
  [Intel Braswell] Cursor gets stuck on left side of the screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1767654/+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 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

2020-06-05 Thread Pietrek B.
It's also worth mentioning that using "EnablePageFlip" "off" causes serious 
screen tearing when interacting with the desktop... Switching KWin's 
compositing engine to xrender helps the tearing somewhat, but still - this is 
terrible.
That platform (Raven Ridge) has been around for over two years now and Linux 
still can't support it properly.

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+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 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights

2020-06-05 Thread Tim Mueller
To be clear - I have not found an edit option:
-stop service gdm3
-start service gdm3
+sudo service gdm3 stop
+sudo service gdm3 start

This will not result in something visible in the VNC. sudo startx does.

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

Title:
  [vmwgfx] Gnome Desktop only starting with root rights

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882102/+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 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights

2020-06-05 Thread Tim Mueller
Can you log in normally from the login screen? Is it only an issue with
'startx'?

No, if I try to boot directly to GUI the resolution changes several
times (I can see that via VNC which is available at boot time for the
VPS because the VNC size is changing several times) and then get's
stuck. This happens on two different VPS. I have upgraded from 18.04
LTS. But this error is not connected to the update. I also tried to use
a fresh install and the result was the same. Which means there is no
login screen on both machines.

If it get's stuck the beavior is different on both VPS even if I copy
everything except /sys /run /proc (which means the same installation is
used) one VPS gets stuck in a purple screen and it is possible to change
to command line via Alt+F. The other one ends up in a blueish screen
with lines and a blinking cursor but this one is totally stuck. I added
two screenshots of that.

Sometimes I see the desktop for a part of a socond between the
resolution changes. I also tried to set a fixed resolution but was not
sucessfull because the switching is still happening. If I stop the gdm
serrvice startx with root is possible afterwards. IT took me a while to
realize this because at first I thought I should focus on the GUI boot
problem.

I now switched both VPS to multi user target insted of graphical boot.
If I use stop service gdm3 and start service gdm3 the result is the same
like described above. XRDP combined with remote desktop is also only
working via root login.

Also please run:
  ls -l /usr/libexec/gnome-session-binary
ls -l /usr/libexec/gnome-session-binary
-rwxr-xr-x 1 root root 334664 Mar 26 13:22 /usr/libexec/gnome-session-binary

On tests with xrdp I also saw some other errors in syslog which are more 
detailed as the gnome session permission error which does not seem to be the 
root cause:
May 27 18:34:59 systemd[587724]: at-spi-dbus-bus.service: Failed to execute 
command: Permission denied
May 27 18:34:59 systemd[587724]: at-spi-dbus-bus.service: Failed at step EXEC 
spawning /usr/libexec/at-spi-bus-launcher: Permission denied
May 27 18:34:59 systemd[1678]: at-spi-dbus-bus.service: Main process exited, 
code=exited, status=203/EXEC

I have seen some oher useers with this kind of problem which switched
off at-spi-dbus-bus.service. I tried that and ended up with. That's
where I stopped trying and switched at-spi-dbus-bus.service to start
agein like before. Which means I'm now on standard settings after
upgrade again:

dbus-daemon[642845]: [session uid=0 pid=642843] Activating service 
name='org.freedesktop.systemd1' requested by ':1.20' (uid=0 pid=642800 
comm="/usr/libexec/gnome-session-binary --builtin " label="unconfined")
May 27 19:49:30 dbus-daemon[642845]: [session uid=0 pid=642843] Activated 
service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 
exited with status 1
May 27 19:49:30 org.gtk.vfs.Daemon[642897]: A connection to the bus can't be 
made
May 27 19:49:30 gnome-control-c[646635]: gnome-control-center-search-provider: 
Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.
May 27 19:49:30 seahorse[643522]: seahorse: Fatal IO error 11 (Die Ressource 
ist zur Zeit nicht verfügbar) on X server :0.
May 27 19:49:30 org.gnome.Chara[646649]: 
org.gnome.Characters.BackgroundService: Fatal IO error 11 (Die Ressource ist 
zur Zeit nicht verfügbar) on X server :0.
May 27 19:49:30 gnome-calendar[643523]: gnome-calendar: Fatal IO error 11 (Die 
Ressource ist zur Zeit nicht verfügbar) on X server :0.
May 27 19:49:30 systemd[1]: root-.cache-gvfs.mount: Succeeded.
May 27 19:49:30 systemd[225333]: root-.cache-gvfs.mount: Succeeded.
May 27 19:49:30 org.gnome.Shell.CalendarServer[643029]: 
gnome-shell-calendar-server[643029]: Lost (or failed to acquire) the name 
org.gnome.Shell.CalendarServer - exiting
May 27 19:49:30 systemd[1678]: root-.cache-gvfs.mount: Succeeded.
May 27 19:49:30 systemd[1679]: root-.cache-gvfs.mount: Succeeded.
May 27 19:49:30 org.gtk.vfs.Daemon[643591]: A connection to the bus can't be 
made
May 27 19:49:30 org.gtk.vfs.Daemon[643694]: A connection to the bus can't be 
made

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

Title:
  [vmwgfx] Gnome Desktop only starting with root rights

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