[Touch-packages] [Bug 1797882]

2019-09-02 Thread Gert van de Kraats
I am currently using Debian 10 Buster with Wayland.
This problem is not existing anymore at this release.
Wayland no longer uses an extra fence register if dual monitor is used.

The wrong reservation of fence registers at intel_blit.c still exists, but does 
not harm, because the limit of 14 usable fence registers is very safe.
A limit of 15 might be possible, if reservation at intel_blit.c is unbugged.

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

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

Status in Mesa:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  Using ubuntu wayland with dual monitors, configured above each other.
  Dock is configured at both displays, not hiding.
  Icons for "terminal" and "libreofffice Writer" are present at the dock.

  Start terminal on primary screen by mouseclick on dock.
  Start libreoffice Writer on primary screen by mouseclick on dock.
  Terminate libreoffice Witer by mouseclick on X.
  Repeat the starting and stopping of Writer.

  Login-screen will appear. Syslog shows:
  Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked 
failed: Resource deadlock avoided
  Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from 
display: Connection reset by peer
  Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main 
process exited, code=exited, status=1/FAILURE

  This problem doesnot occur in a dual monitor-session without wayland.
  It also doesnot occur, if only one monitor used with wayland
  It also doesnot occur, if the dock is only present at the primary screen.
  It also doesnot occur if second started application is present at the dock 
and doesnot add an icon to the dock (as libreoffice does).

  All other dual monitor/dock configurations seem to have this problem.

  No idea if this is helpful info, but the used graphics card does not support 
OpenGL version 2.1:
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 
2.1 or later.
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor, falling back to sw

  glxinfo:
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 18.2.2
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 13:25:10 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided

2019-07-28 Thread Gert van de Kraats
Unfortunatelu no new flavor of Ubuntu is supporting 32 bits anymore.
Therefore I had to install Debian 10 (Buster).

Wayland at Debian is running without severe problems.
This problem also is not existing anymore, because Wyland is no longer using an 
extra fence register if a dual monitor is used.
I suppose this means also at some release of Ubuntu the problem will disappear.

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

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

Status in Mesa:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  Using ubuntu wayland with dual monitors, configured above each other.
  Dock is configured at both displays, not hiding.
  Icons for "terminal" and "libreofffice Writer" are present at the dock.

  Start terminal on primary screen by mouseclick on dock.
  Start libreoffice Writer on primary screen by mouseclick on dock.
  Terminate libreoffice Witer by mouseclick on X.
  Repeat the starting and stopping of Writer.

  Login-screen will appear. Syslog shows:
  Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked 
failed: Resource deadlock avoided
  Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from 
display: Connection reset by peer
  Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main 
process exited, code=exited, status=1/FAILURE

  This problem doesnot occur in a dual monitor-session without wayland.
  It also doesnot occur, if only one monitor used with wayland
  It also doesnot occur, if the dock is only present at the primary screen.
  It also doesnot occur if second started application is present at the dock 
and doesnot add an icon to the dock (as libreoffice does).

  All other dual monitor/dock configurations seem to have this problem.

  No idea if this is helpful info, but the used graphics card does not support 
OpenGL version 2.1:
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 
2.1 or later.
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor, falling back to sw

  glxinfo:
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 18.2.2
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 13:25:10 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1797882]

2019-02-20 Thread Gert van de Kraats
Created attachment 143414
fix intel_blit.c

fix error_patch2

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

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

Status in Mesa:
  Confirmed
Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Using ubuntu wayland with dual monitors, configured above each other.
  Dock is configured at both displays, not hiding.
  Icons for "terminal" and "libreofffice Writer" are present at the dock.

  Start terminal on primary screen by mouseclick on dock.
  Start libreoffice Writer on primary screen by mouseclick on dock.
  Terminate libreoffice Witer by mouseclick on X.
  Repeat the starting and stopping of Writer.

  Login-screen will appear. Syslog shows:
  Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked 
failed: Resource deadlock avoided
  Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from 
display: Connection reset by peer
  Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main 
process exited, code=exited, status=1/FAILURE

  This problem doesnot occur in a dual monitor-session without wayland.
  It also doesnot occur, if only one monitor used with wayland
  It also doesnot occur, if the dock is only present at the primary screen.
  It also doesnot occur if second started application is present at the dock 
and doesnot add an icon to the dock (as libreoffice does).

  All other dual monitor/dock configurations seem to have this problem.

  No idea if this is helpful info, but the used graphics card does not support 
OpenGL version 2.1:
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 
2.1 or later.
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor, falling back to sw

  glxinfo:
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 18.2.2
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 13:25:10 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1797882]

2019-02-20 Thread Gert van de Kraats
Created attachment 143415
libdrm_ignore_deadlock

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

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

Status in Mesa:
  Confirmed
Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Using ubuntu wayland with dual monitors, configured above each other.
  Dock is configured at both displays, not hiding.
  Icons for "terminal" and "libreofffice Writer" are present at the dock.

  Start terminal on primary screen by mouseclick on dock.
  Start libreoffice Writer on primary screen by mouseclick on dock.
  Terminate libreoffice Witer by mouseclick on X.
  Repeat the starting and stopping of Writer.

  Login-screen will appear. Syslog shows:
  Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked 
failed: Resource deadlock avoided
  Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from 
display: Connection reset by peer
  Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main 
process exited, code=exited, status=1/FAILURE

  This problem doesnot occur in a dual monitor-session without wayland.
  It also doesnot occur, if only one monitor used with wayland
  It also doesnot occur, if the dock is only present at the primary screen.
  It also doesnot occur if second started application is present at the dock 
and doesnot add an icon to the dock (as libreoffice does).

  All other dual monitor/dock configurations seem to have this problem.

  No idea if this is helpful info, but the used graphics card does not support 
OpenGL version 2.1:
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 
2.1 or later.
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor, falling back to sw

  glxinfo:
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 18.2.2
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 13:25:10 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1797882]

2019-02-20 Thread Gert van de Kraats
Some more investigation, understanding and adding 2 other possible fixes for 
the problem.
The problem occurs at Ubuntu 18.10 only at gdm3 with wayland using dual monitor.
It is not occuring with wayland at single monitor.
It totally doesnot occur if gdm3 is not using wayland.
At ubuntu 18.04 the same problem exists with wayland, but is not occurring so 
often.

At ubuntu 18.10 with wayland and dual monitor the user session immediately 
aborts, if 16 or more favorites are allocated at the dock.
For some reason wayland seems to use one extra fence register at dual monitor.
It is noticed at dual monitor, that gdm3 with wayland uses 2 calls to 
clutter_stage_cogl_redraw_view for 2 logical screens for every call to 
clutter_stage_cogl_redraw; gdm3 without wayland does only one call to 
clutter_stage_cogl_redraw_view for 1 logical screen.

The crash occurs at intel_batchbuffer_flush. Always the last batch at such a 
flush is coming from function emit_copy_blit and intelClearWithBlit at 
src/mesa/drivers/dri/i915/intel_blit.c. At the call to 
dri_bufmgr_check_aperture_space they indicate to use zero fence registers, but 
in fact they use one. This violates the limit of 14, causing a crash at dual 
monitor.
So the call to dri_bufmgr_check_aperture_space must be postponed, until the 
needed fence register is added in the middle of the batch-generation and then 
the batch-actions must be undone, a flush is called and batch is regenerated 
again.
For this function intel_batchbuffer_emit_reset is added.
This also is done for function intel_miptree_set_alpha_to_one, although I never 
saw a call of this function.
See fix error3_patch2.txt.

Another (dirty) solution is to decrement the availablity and just continue.
This gives somewhere a failure, but I could not see a failing layout.
See fix error3_patch3.txt.

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

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

Status in Mesa:
  Confirmed
Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Using ubuntu wayland with dual monitors, configured above each other.
  Dock is configured at both displays, not hiding.
  Icons for "terminal" and "libreofffice Writer" are present at the dock.

  Start terminal on primary screen by mouseclick on dock.
  Start libreoffice Writer on primary screen by mouseclick on dock.
  Terminate libreoffice Witer by mouseclick on X.
  Repeat the starting and stopping of Writer.

  Login-screen will appear. Syslog shows:
  Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked 
failed: Resource deadlock avoided
  Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from 
display: Connection reset by peer
  Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main 
process exited, code=exited, status=1/FAILURE

  This problem doesnot occur in a dual monitor-session without wayland.
  It also doesnot occur, if only one monitor used with wayland
  It also doesnot occur, if the dock is only present at the primary screen.
  It also doesnot occur if second started application is present at the dock 
and doesnot add an icon to the dock (as libreoffice does).

  All other dual monitor/dock configurations seem to have this problem.

  No idea if this is helpful info, but the used graphics card does not support 
OpenGL version 2.1:
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 
2.1 or later.
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor, falling back to sw

  glxinfo:
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 18.2.2
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 13:25:10 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' 

[Touch-packages] [Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided

2018-12-19 Thread Gert van de Kraats
Mesa-bug:
https://bugs.freedesktop.org/show_bug.cgi?id=109102


** Bug watch added: freedesktop.org Bugzilla #109102
   https://bugs.freedesktop.org/show_bug.cgi?id=109102

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

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Using ubuntu wayland with dual monitors, configured above each other.
  Dock is configured at both displays, not hiding.
  Icons for "terminal" and "libreofffice Writer" are present at the dock.

  Start terminal on primary screen by mouseclick on dock.
  Start libreoffice Writer on primary screen by mouseclick on dock.
  Terminate libreoffice Witer by mouseclick on X.
  Repeat the starting and stopping of Writer.

  Login-screen will appear. Syslog shows:
  Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked 
failed: Resource deadlock avoided
  Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from 
display: Connection reset by peer
  Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main 
process exited, code=exited, status=1/FAILURE

  This problem doesnot occur in a dual monitor-session without wayland.
  It also doesnot occur, if only one monitor used with wayland
  It also doesnot occur, if the dock is only present at the primary screen.
  It also doesnot occur if second started application is present at the dock 
and doesnot add an icon to the dock (as libreoffice does).

  All other dual monitor/dock configurations seem to have this problem.

  No idea if this is helpful info, but the used graphics card does not support 
OpenGL version 2.1:
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 
2.1 or later.
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor, falling back to sw

  glxinfo:
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 18.2.2
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 13:25:10 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797882/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided

2018-12-18 Thread Gert van de Kraats
Without solving this problem, wayland cannot be used after logon, when
using dual monitor. The sesssion stops very easy and often. Work is
lost; you have to logon again. E.g. the simple switching between 2
overlapping windows causes the end of the session.

I changed src/mesa/drivers/dri/i915/intel_batchbuffer.c to force a coredump in 
this case. The stacktrace is added to this bug-report.
Linenumbers might deviate a little bit because of extra coding of tracing.
The deadlock always occurs at cogl_onscreen_swap_buffers calling cogl_flush(), 
at the first journal-batch-flush for the offscreen-framebuffer.

The deadlock disappeared as soon as cogl is compiled with disabled batching!
To minimize this disabling of batching, I made a very dirty but working patch, 
which is attached to this bug.
At program clutter_stage_cogl_redraw_view  routine paint_stage is called for 
the "Unclipped stage paint".
This call is manipulated to flush immedately the first journal-entry of the 
default onscreen framebuffer.
This is done by misusing and changing program cogl_framebuffer_set_viewport and 
by changing _cogl_journal_flush.
Apparenly this early flushing causes a lock to be set which avoids the deadlock.

I do not know how to see which locks are held and by which process, so I
cannot solve the root-cause of thhe problem, but I assume some extra
lock must be set in this case to avoid deadlock.

With this dirty patch combined with other suggested (simple) patches at 
#1790525, #1795774 and #1795760 wayland can be run without any problems on dual 
monitor and "old" intel graphic card.
It performs better than lightdm, specially if the monitors are positioned aside 
of each other.


** Attachment added: "dirty_patch.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1797882/+attachment/5223253/+files/dirty_patch.txt

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

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Using ubuntu wayland with dual monitors, configured above each other.
  Dock is configured at both displays, not hiding.
  Icons for "terminal" and "libreofffice Writer" are present at the dock.

  Start terminal on primary screen by mouseclick on dock.
  Start libreoffice Writer on primary screen by mouseclick on dock.
  Terminate libreoffice Witer by mouseclick on X.
  Repeat the starting and stopping of Writer.

  Login-screen will appear. Syslog shows:
  Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked 
failed: Resource deadlock avoided
  Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from 
display: Connection reset by peer
  Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main 
process exited, code=exited, status=1/FAILURE

  This problem doesnot occur in a dual monitor-session without wayland.
  It also doesnot occur, if only one monitor used with wayland
  It also doesnot occur, if the dock is only present at the primary screen.
  It also doesnot occur if second started application is present at the dock 
and doesnot add an icon to the dock (as libreoffice does).

  All other dual monitor/dock configurations seem to have this problem.

  No idea if this is helpful info, but the used graphics card does not support 
OpenGL version 2.1:
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 
2.1 or later.
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor, falling back to sw

  glxinfo:
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 18.2.2
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 13:25:10 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted 

[Touch-packages] [Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided

2018-12-18 Thread Gert van de Kraats
Trace

** Attachment added: "trace at forced coredump"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1797882/+attachment/5223254/+files/wayland_stacktrace.txt

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

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Using ubuntu wayland with dual monitors, configured above each other.
  Dock is configured at both displays, not hiding.
  Icons for "terminal" and "libreofffice Writer" are present at the dock.

  Start terminal on primary screen by mouseclick on dock.
  Start libreoffice Writer on primary screen by mouseclick on dock.
  Terminate libreoffice Witer by mouseclick on X.
  Repeat the starting and stopping of Writer.

  Login-screen will appear. Syslog shows:
  Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked 
failed: Resource deadlock avoided
  Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from 
display: Connection reset by peer
  Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main 
process exited, code=exited, status=1/FAILURE

  This problem doesnot occur in a dual monitor-session without wayland.
  It also doesnot occur, if only one monitor used with wayland
  It also doesnot occur, if the dock is only present at the primary screen.
  It also doesnot occur if second started application is present at the dock 
and doesnot add an icon to the dock (as libreoffice does).

  All other dual monitor/dock configurations seem to have this problem.

  No idea if this is helpful info, but the used graphics card does not support 
OpenGL version 2.1:
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 
2.1 or later.
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor
  Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize 
glamor, falling back to sw

  glxinfo:
  OpenGL vendor string: VMware, Inc.
  OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits)
  OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2
  OpenGL core profile shading language version string: 3.30
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 18.2.2
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
  OpenGL ES profile extensions:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic i686
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 13:25:10 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797882/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1799038] Re: Ubuntu 18.10 does not suspend on lid close

2018-11-29 Thread Gert van de Kraats
I have the same problem on a fresh installed 18.10 for 32-bits, but only if 
external monitor is connected.
Indeed this is a well known peoblem at internet.

sudo journalctl -b -u systemd-logind  with debugging on 
(systemd.log-level=debug) without external monitor shows succeeding suspend:
Nov 29 16:56:04 Gert2 systemd-logind[438]: Lid closed
Nov 29 16:56:04 Gert2 systemd-logind[438]: device-enumerator: scan all dirs
Nov 29 16:56:04 Gert2 systemd-logind[438]:   device-enumerator: scanning 
/sys/bus
Nov 29 16:56:04 Gert2 systemd-logind[438]:   device-enumerator: scanning 
/sys/class
Nov 29 16:56:04 Gert2 systemd-logind[438]: Failed to open configuration file 
'/etc/systemd/sleep.conf': No such file or directory
Nov 29 16:56:04 Gert2 systemd-logind[438]: Suspending...

sudo journalctl -b -u systemd-logind  with debugging on 
(systemd.log-level=debug) with connected external monitor shows refusing 
suspend:
Nov 29 15:05:58 Gert2 systemd-logind[426]: Lid closed.
Nov 29 15:05:58 Gert2 systemd-logind[426]: device-enumerator: scan all dirs
Nov 29 15:05:58 Gert2 systemd-logind[426]:   device-enumerator: scanning 
/sys/bus
Nov 29 15:05:58 Gert2 systemd-logind[426]:   device-enumerator: scanning 
/sys/class
Nov 29 15:05:58 Gert2 systemd-logind[426]: External (1) displays connected.
Nov 29 15:05:58 Gert2 systemd-logind[426]: Refusing operation, as it is turned 
off.
Nov 29 15:05:58 Gert2 systemd-logind[426]: device-enumerator: scan all dirs
Nov 29 15:05:58 Gert2 systemd-logind[426]:   device-enumerator: scanning 
/sys/bus
Nov 29 15:05:58 Gert2 systemd-logind[426]:   device-enumerator: scanning 
/sys/class
Nov 29 15:05:58 Gert2 systemd-logind[426]: External (1) displays connected.
Nov 29 15:05:58 Gert2 systemd-logind[426]: Refusing operation, as it is turned 
off.
Nov 29 15:05:59 Gert2 systemd-logind[426]: Got message type=method_call 
sender=:1.238 destination=:1.3 path=/org/freedesktop/login1/session/_32 
interface=org.freedesktop.login1.Session member=ReleaseDevice cookie=154 
reply_cookie=0 signature=uu error-name=n/a error-message=n/a
Nov 29 15:05:59 Gert2 systemd-logind[426]: Sent message type=signal sender=n/a 
destination=:1.238 path=/org/freedesktop/login1/session/_32 
interface=org.freedesktop.login1.Session member=PauseDevice cookie=227 
reply_cookie=0 signature=uus error-name=n/a error-message=n/a
Nov 29 15:05:59 Gert2 systemd[1]: systemd-logind.service: Got notification 
message from PID 426 (FDSTOREREMOVE=1, FDNAME=session-2-device-13-71)
Nov 29 15:05:59 Gert2 systemd[1]: systemd-logind.service: Got explicit request 
to remove fd 174 (session-2-device-13-71), closing.
Nov 29 15:05:59 Gert2 systemd-logind[426]: Sent message type=method_return 
sender=n/a destination=:1.238 path=n/a interface=n/a member=n/a cookie=228 
reply_cookie=154 signature=n/a error-name=n/a error-message=n/a
Nov 29 15:05:59 Gert2 systemd-logind[426]: device-enumerator: scan all dirs
Nov 29 15:05:59 Gert2 systemd-logind[426]:   device-enumerator: scanning 
/sys/bus
Nov 29 15:05:59 Gert2 systemd-logind[426]:   device-enumerator: scanning 
/sys/class
Nov 29 15:05:59 Gert2 systemd-logind[426]: External (1) displays connected.
Nov 29 15:05:59 Gert2 systemd-logind[426]: Refusing operation, as it is turned 
off.
Nov 29 15:06:10 Gert2 systemd-logind[426]: Lid opened.

The command systemd-inhibit --list shows next entry as soon as an external 
monitor is attached to the laptop.
 Who: gert (UID 1000/gert, PID 2342/gsd-power)
What: handle-lid-switch
 Why: Multiple displays attached
Mode: block

So program gsd-power is responsible for inhibiting the handling of the
lid-switch.  The suspend-action will not occcur. This is not
configurable and I think that is ridiculous.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1799038

Title:
  Ubuntu 18.10 does not suspend on lid close

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After an upgrade to Ubuntu 18.10 suspend to RAM due to closing the lid
  on notebooks does not work any more.

  The machine goes to suspend mode but wakes up immediately due to some
  events (can be network, or others).

  In 18.04 this issue was fixed (we had the same situation with any
  version since 14.04).

  Seems a regression.

  Mitigation reports suggesting to change /etc/systemd/logind.conf are WRONG. 
The changes do NOTHING.
  One might spare the time to experiment.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: systemd 239-7ubuntu10
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 21 11:55:48 2018
  InstallationDate: Installed on 2018-04-30 (174 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux 

[Touch-packages] [Bug 1787957] [NEW] Ubuntu 18.04 login page not shown after upgrade

2018-08-20 Thread Gert van de Kraats
Public bug reported:

As suggested by ubuntu an upgrade was started from 16.04 to 18.04.
Although it was a 32-bit upgrade and release notes tell 32-bit is not possible 
anymore, this upgrade succeeded.
But at the restart the login page was not shown and mouse/keyboard did not work.

Probably the problem was caused by the error at syslog:
Aug 19 23:34:11 gert-laptop org.gnome.Shell.desktop[959]: glamor: EGL version 
1.4 (DRI2):
Aug 19 23:34:11 gert-laptop org.gnome.Shell.desktop[959]: Require OpenGL 
version 2.1 or later.
Aug 19 23:34:11 gert-laptop org.gnome.Shell.desktop[959]: Failed to initialize 
glamor
Aug 19 23:34:11 gert-laptop org.gnome.Shell.desktop[959]: Failed to initialize 
glamor, falling back to sw

Surprisingly login was possible by using recovery mode, then start "network" 
and finally pressing Ctrl-C. 
Ubuntu was running successfully, but the external monitor was ignored.

Version of OpenGL seems to be 3.0:
glxinfo | grep OpenGL
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 6.0, 128 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.5
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 18.0.5
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:

Problem could be solved by using one of the  
other *ubuntu's or  the ugly xfce4, I tried.

The most simple solution is reconfigure lightdm to use display manager
lightdm instead of gdm3 by starting : dpkg-reconfigure lightdm.

Ubuntu now works. 
Version of OpenGL now seems to be 1.4 (same as at 16.04 release):
glxinfo | grep OpenGL
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) 945GM x86/MMX/SSE2
OpenGL version string: 1.4 Mesa 18.0.5
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 18.0.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16


Also the dual screen problems from 16.04 seem to be completely solved now.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: i386
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 20 15:55:22 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Dell Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [1028:01c2]
   Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics 
Controller [1028:01c2]
InstallationDate: Installed on 2010-09-01 (2910 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
LightdmGreeterLogOld:
 ** Message: Starting lightdm-gtk-greeter 2.0.1 (Jun 17 2015, 00:46:44)
 ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
 ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf
 
 ** (lightdm-gtk-greeter:1839): WARNING **: [PIDs] Failed to execute command: 
upstart
MachineType: Dell Inc. Latitude D620
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=45c32f72-ec04-4f85-acbe-f4a86c5b374a ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/11/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0TD761
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd04/11/2006:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0TD761:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D620
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev