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
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
Created attachment 143415
libdrm_ignore_deadlock
--
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/1797882
Title:
At dual monitor intel_do_flush_locked failed: Resource deadlock
avoided
To
Created attachment 143414
fix intel_blit.c
fix error_patch2
--
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/1797882
Title:
At dual monitor intel_do_flush_locked failed: Resource deadlock
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
Issue https://gitlab.gnome.org/GNOME/mutter/issues/453 is added to
mutter
--
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/1795760
Title:
Xwayland crashed with SIGABRT in OsAbort() from
Because this bug no longer is marked as duplicate of #1745799, I now add
the bug-fix (tested by me for a long time) to this bug.
** Attachment added: "Patch"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1795760/+attachment/5231631/+files/error9_patch.txt
--
You received this
I created bug #1795760, which describes a Xwayland-abort and got the
status duplicate of 1745799.
Below is a part of the symbolic trace of the abort.
#7 0x004b6296 in xwl_log_handler (format=0xb7dc71ea "%s@%u: error %d: %s\n",
args=0xbf9c7994 "\027uܷ\255\001") at
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-X,
which is subscribed to mesa in Ubuntu.
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-X,
which is subscribed to mesa in Ubuntu.
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
*** This bug is a duplicate of bug 1745799 ***
https://bugs.launchpad.net/bugs/1745799
This is not a duplicate. It is a crash at OsAbort, but that is the only
coincidence with #1745799.
The cause is different.
It contains a working solution.
PLease do something with it and do not mark it as
*** This bug is a duplicate of bug 1745799 ***
https://bugs.launchpad.net/bugs/1745799
As stated above this bug report is not a duplicate and contains working code to
solve the bug.
Using this code doesn ot give any risk to the main stream of the code, it only
handles an exception.
I
*** This bug is a duplicate of bug 1745799 ***
https://bugs.launchpad.net/bugs/1745799
Sorry,
Code was not quite complete.
It misses freeing the error.
New version:
texture = COGL_TEXTURE (cogl_texture_2d_new_from_bitmap (bitmap));
cogl_texture_set_components (COGL_TEXTURE (texture),
*** This bug is a duplicate of bug 1745799 ***
https://bugs.launchpad.net/bugs/1745799
I do not think this is a duplicate of bug #1745799.
At this comment I will try to give a code to solve this bug.
My symbol Xwaylnd-crash shows the next trace:
#6 0x0062b600 in FatalError (f=0x63704e
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
16 matches
Mail list logo
