[Bug 1797882]
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 Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1797882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided
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 Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1797882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_
I did at #14 again, set verification-done-bionic for this fix, as requested. Again it disappears. I now tested the fix 3 times (once for cosmic and twice for bionic). This time I did the same test as at #8. Whatever you do it was the last time I test this bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1795774 Title: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_offscreen_effect_paint() from clutter_actor_continue_paint() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_
Problem could not be reproduced, because it was hidden by bug #1795774. After installation from proposed, the problem was solved: root@gert-laptop:/etc/apt# dpkg -s libmutter-2-0 | grep Version Version: 3.28.3+git20190124-0ubuntu18.04.2 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1795774 Title: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_offscreen_effect_paint() from clutter_actor_continue_paint() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect
Problem reproduced with old version: gert@gert-laptop:~$ dpkg -s libmutter-2-0 | grep Version Version: 3.28.3-2~ubuntu18.04.2 Apr 19 14:41:11 gert-laptop gnome-shell[991]: CoglError set over the top of a previous CoglError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Sliced texture size of 2560 x 1024 not possible with max waste set to -1 Apr 19 14:41:11 gert-laptop org.gnome.Shell.desktop[991]: double free or corruption (fasttop) Apr 19 14:41:11 gert-laptop org.gnome.Shell.desktop[991]: == Stack trace for context 0x1ab5838 == Apr 19 14:41:47 gert-laptop org.gnome.Shell.desktop[991]: (EE) Apr 19 14:41:47 gert-laptop org.gnome.Shell.desktop[991]: Fatal server error: Apr 19 14:41:47 gert-laptop org.gnome.Shell.desktop[991]: (EE) failed to read Wayland events: Broken pipe Apr 19 14:41:47 gert-laptop org.gnome.Shell.desktop[991]: (EE) Apr 19 14:41:47 gert-laptop gnome-session-binary[983]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 After installation from proposed, the problem was solved: root@gert-laptop:/etc/apt# dpkg -s libmutter-2-0 | grep Version Version: 3.28.3+git20190124-0ubuntu18.04.2 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790525/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_
Verification succeeded. Problem solved ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1795774 Title: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_offscreen_effect_paint() from clutter_actor_continue_paint() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect
Verification succeeded. Problem solved. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790525/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect
Sorry, I missed the previous request to verify at bionic. Bionic is my basic Ubuntu. I only use cosmic for test. At the past I installed cosmic only to verify the wayland-patch for old Intel-graphics. This worked but I got a lot of other problems with unstable starting of ubuntu, caused by wayland and plymouth. At bionic I recently have installed the same (proposed by me) patches as at cosmic, which worked. I will verify the official proposed fix at bionic as requested and report here. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790525/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797882]
Created attachment 143415 libdrm_ignore_deadlock -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1797882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797882]
Created attachment 143414 fix intel_blit.c fix error_patch2 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1797882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797882]
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 Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1797882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect
** Tags added: cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790525/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_
Reinstalled current libmutter. With dual monitor horizontal aside this problem could not be reproduced because logon-session crashes before showing logon-screen, (caused by bug #1790525). Installed proposed version: apt list libmutter-3-0 Listing... Done libmutter-3-0/cosmic-proposed,now 3.30.2-1~ubuntu18.10.3 i386 [installed] No crash anymore when trying to suspend at logon-screen. Problem is solved by proposed package. No new other problems detected. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1795774 Title: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_offscreen_effect_paint() from clutter_actor_continue_paint() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect
** Tags removed: cosmic verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790525/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect
Reinstalled current libmutter. With dual monitor horizontal aside this gives Feb 1 22:26:58 Gert2 gnome-shell[1038]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints Feb 1 22:26:58 Gert2 gnome-shell[1038]: CoglError set over the top of a previous CoglError or uninitialized memory.#012This indicates a bug in someone's code. You must ensure an error is NULL before it's set.#012The overwriting error message was: Sliced texture size of 2560 x 1024 not possible with max waste set to -1 Logon-session crashes before showing logon-screen. Installed proposed version: apt list libmutter-3-0 Listing... Done libmutter-3-0/cosmic-proposed,now 3.30.2-1~ubuntu18.10.3 i386 [installed] Problem is solved by proposed package. No new other problems detected. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790525/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795760] Re: Xwayland crashed with SIGABRT in OsAbort() from ... from FatalError("wl_surface@429: error 2: Failed to create a texture for surface 429: Failed to create texture 2d due to size/form
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
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1795760
Title:
Xwayland crashed with SIGABRT in OsAbort() from ... from
FatalError("wl_surface@429: error 2: Failed to create a texture for
surface 429: Failed to create texture 2d due to size/format
constraints\n")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795760/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795760] Re: Xwayland crashed with SIGABRT in OsAbort() from ... from FatalError("wl_surface@429: error 2: Failed to create a texture for surface 429: Failed to create texture 2d due to size/form
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 bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1795760
Title:
Xwayland crashed with SIGABRT in OsAbort() from ... from
FatalError("wl_surface@429: error 2: Failed to create a texture for
surface 429: Failed to create texture 2d due to size/format
constraints\n")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795760/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided
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 Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided
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 Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided
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 Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided
** Description changed: 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'" + 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 + 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) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797882] [NEW] At dual monitor intel_do_flush_locked failed: Resource deadlock avoided
Public bug reported: 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) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug cosmic i386 wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height() from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_offscreen_e
Problem can be solved at update_fbo() within clutter/clutter/clutter-
offscreen-effect.c
In this case at update_fbo a texture should be alocated with width 2560 which
is greater than maximal size 2048 of graphics cards.
Offscreen-effect does not support sliced textures, so this is impossible and
fails.
Crash occurs because no texture is allocated but a framebuffer is present at
priv->offscreen.
Code to free the framebuffer at priv->offscreen should be moved upwards at
update_fbo, because it also should be executed in case texture allocation fails.
This leads to the fillowing proposed code:
if (priv->texture != NULL)
{
cogl_handle_unref (priv->texture);
priv->texture = NULL;
}
if (priv->offscreen != NULL)
{
cogl_handle_unref (priv->offscreen);
priv->offscreen = NULL;
}
priv->texture =
clutter_offscreen_effect_create_texture (self, fbo_width, fbo_height);
if (priv->texture == NULL)
return FALSE;
cogl_pipeline_set_layer_texture (priv->target, 0, priv->texture);
priv->fbo_width = fbo_width;
priv->fbo_height = fbo_height;
priv->offscreen = cogl_offscreen_new_to_texture (priv->texture);
Remember bug 1790525 also should be solved (which often causes an earlier
crash), to make the solution complete.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1795774
Title:
gnome-shell crashed with SIGSEGV in cogl_texture_get_height() from
clutter_offscreen_effect_real_paint_target() from
clutter_offscreen_effect_paint_texture() from
clutter_offscreen_effect_paint() from clutter_actor_continue_paint()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1795774/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795089] Re: Gnome-shell crashes if dual monitor connected
** Package changed: evince (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1795089 Title: Gnome-shell crashes if dual monitor connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1795089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795089] [NEW] Gnome-shell crashes if dual monitor connected
Public bug reported:
THis contains a fresh install of Ubuntu 18.10 to verify the solution at bug
1727356, for Intel-graphic-cards,
which do not support OpenGL 2.1 or higher.
This solution works.
A fresh install does not contain any monitors.xml file, to describe the dual
monitor-configuration.
I try to connect an internal laptop-monitor LVDS1 with maximal density 1280 x
800 and an external monitor VGA1
with density 1280 x 1024.
Display-manager gdm3 by default configures the external monitor at the right
side of the laptop-monitor.
This results into a logical screen of 2560 x 1024.
THe graphics card only supports a maximal width and height of 2048.
Therefore textures, that are too large, are splitted into multiple slices,
that fit.
Unfortunately this is not always done, causing textures of size 2560 x 1024 not
being allocated and crashing.
A quick and dirty hardcoded solution limiting the width to 2048
eliminates the crashes:
At cogl/cogl/cogl-texture-2d-sliced.c module setup_spans:
/* Negative number means no slicing forced by the user */
if (max_waste <= -1)
{
CoglSpan span;
if (max_width > 2048)
max_width = 2048;
At cogl/cogl/driver/gl/cogl-texture-2d-gl.c routine allocate_from_bitmap:
internal_format =
_cogl_texture_determine_internal_format (tex, cogl_bitmap_get_format (bmp));
if (width > 2048)
width = 2048;
In fact the external monitor is physically positioned above the laptop-monitor
and this is the configuration we want.
This results into a logical screen of 1280 x 1824 within the limits of the
graphics card.
To get this configuration the file monitors.xml was copied to $HOME/.config and
to /var/lib/gdm3/.config (to configure login screen).
By default Ubuntu 18.10 uses gdm3 with wayland at the login-screen and gdm3
without wayland after login.
Display-manager gdm3 with wayland ignores this monitors.xml file. To make the
file also usable for wayland the
must be copied with VGA-1 i.s.o.
VGA1 and
LVDS-1 i.s.o. LVDS1 .
Curious!@#$#.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: evince 3.30.0-2
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic i686
ApportVersion: 2.20.10-0ubuntu11
Architecture: i386
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 29 01:41:55 2018
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug cosmic i386
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1795089
Title:
Gnome-shell crashes if dual monitor connected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1795089/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect
Proposed solution:
As the stacktrace below shows the problem is caused by module
cogl_texture_new_with_size at cogl/cogl/deprecated/cogl/auto-texture.c .
This module is trying to create a texture with size 2560 x 1024, which is by
default is configured by gdm3 with wayland for 2 monitors.
This is not supported by graphics-card, causing error "Failed to create texture
2d due to size/format constraints".
The error is freed by cogl_texture_new_with_size, but the variable skip_error
is not set to NULL by the call to cogl_error_free (because the parameter is a
copy).
Then module tries to allocate a slice with max_waste -1. This also fails,
causing error "Sliced texture size of 2560 x 1024 not possible with max waste
set to -1".
Module cogl_set_error complains about the skip_error not being NULL with
message "CoglError set...", but does not set a new value to skip_error.
Also the second error is programmed to be freed by cogl_error_free at
cogl_texture_new_with_size, that in this way tries to free the same memory
twice. This causes the crash "double free or corruption (fasttop)", unless by
accident the same memory-address is allocated again.
To solve, the statement skip_error = NULL; should be added:
cogl_texture_new_with_size (unsigned int width,
unsigned int height,
CoglTextureFlags flags,
CoglPixelFormat internal_format)
{
CoglTexture *tex;
CoglError *skip_error = NULL;
_COGL_GET_CONTEXT (ctx, NULL);
if ((_cogl_util_is_pot (width) && _cogl_util_is_pot (height)) ||
(cogl_has_feature (ctx, COGL_FEATURE_ID_TEXTURE_NPOT_BASIC) &&
cogl_has_feature (ctx, COGL_FEATURE_ID_TEXTURE_NPOT_MIPMAP)))
{
/* First try creating a fast-path non-sliced texture */
tex = COGL_TEXTURE (cogl_texture_2d_new_with_size (ctx, width, height));
_cogl_texture_set_internal_format (tex, internal_format);
if (!cogl_texture_allocate (tex, _error))
{
cogl_error_free (skip_error);
skip_error = NULL;
This solution is tested and solves the problem during startup and for right
corner click.
Stacktrace with modulenames/linenumbers:
Package: gnome-shell 3.30.0-1ubuntu2
Stacktrace:
#0 0xb7ef9d41 in __kernel_vsyscall ()
#1 0xb6a4e512 in __libc_signal_restore_set (set=0xbfcb8a0c) at
../sysdeps/unix/sysv/linux/internal-signals.h:84
set = {__val = {0, 0, 1482184750, 5789784, 2237142784, 273, 273,
3080022123, 3080956952, 16, 3080959932, 16, 3080023695, 16, 3217787612,
3066097232, 3080956952, 3080959932, 19876880, 3217787612, 3080285386, 11, 0,
3080023577, 3080285340, 3080956952, 16, 3080959932, 3080016471, 3217788168, 0,
3217787712}}
pid =
tid =
ret = 0
#2 0xb6a4e512 in __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
set = {__val = {0, 0, 1482184750, 5789784, 2237142784, 273, 273,
3080022123, 3080956952, 16, 3080959932, 16, 3080023695, 16, 3217787612,
3066097232, 3080956952, 3080959932, 19876880, 3217787612, 3080285386, 11, 0,
3080023577, 3080285340, 3080956952, 16, 3080959932, 3080016471, 3217788168, 0,
3217787712}}
pid =
tid =
ret = 0
#3 0xb6a382b6 in __GI_abort () at abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0xb7996077 ,
sa_sigaction = 0xb7996077 }, sa_mask = {__val = {3080956952,
3060745084, 3080120357, 3217787880, 3060745084, 3217788000, 32868, 20347328, 0,
28984448, 2237142784, 3060745084, 3080120310, 3080956952, 3080956952,
3217788408, 1024, 31097824, 3080018485, 3060691022, 16, 3060756628, 0, 3, 4096,
3065078356, 2, 3066019840, 4096, 3217788168, 3064530671, 0}}, sa_flags = 4096,
sa_restorer = 0x3}
sigs = {__val = {32, 0 }}
#4 0xb6a9074c in __libc_message (action=do_abort, fmt=) at
../sysdeps/posix/libc_fatal.c:181
ap =
fd = 2
list =
nlist =
cp =
written =
#5 0xb6a975dd in malloc_printerr (str=str@entry=0xb6ba525c "double free or
corruption (fasttop)") at malloc.c:5336
#6 0xb6a98e6f in _int_free (av=, p=,
have_lock=) at malloc.c:4216
idx = 6
old =
old2 =
size =
fb =
nextchunk =
nextsize =
nextinuse =
prevsize =
bck =
fwd =
__PRETTY_FUNCTION__ = "_int_free"
#7 0xb7954290 in g_free () at /usr/lib/i386-linux-gnu/libglib-2.0.so.0
#8 0xb7938c53 in g_error_free () at /usr/lib/i386-linux-gnu/libglib-2.0.so.0
#9 0xb66d7058 in cogl_error_free (error=0x16cba70) at cogl-error.c:45
#10 0xb66db62c in cogl_texture_new_with_size (width=2560, height=1024,
flags=COGL_TEXTURE_NO_SLICING, internal_format=COGL_PIXEL_FORMAT_RGBA__PRE)
at deprecated/cogl-auto-texture.c:121
tex = 0x1da83e0
skip_error = 0x16cba70
ctx =
#11 0xb6e9a618 in clutter_offscreen_effect_real_create_texture
(effect=0x23c3b00,
[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect
Extra info: 1.The syslog at a crash shows next error. Probably memory management at an errormemssage is not correct. Also look at the size 2560 x 1024 Sep 08 00:18:35 Gert2 gnome-shell[2141]: CoglError set over the top of a previous CoglError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Sliced texture size of 2560 x 1024 not possible with max waste set to -1 Sep 08 00:18:35 Gert2 org.gnome.Shell.desktop[2141]: double free or corruption (fasttop) Sep 08 00:18:35 Gert2 org.gnome.Shell.desktop[2141]: GNOME Shell crashed with signal 6 2.It looks like the problem in an older problem. At least at Ubuntu 18.04 with display manager lightdm the same crash occurs if no monitors.xml is present and dual monitor is present. 3.It looks like the problem is caused by the different sizes of the monitors. At startup gdm3 detects next sizes for laptop-monitor and external monitor: Sep 9 20:22:54 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (--) intel(0): Output LVDS1 using initial mode 1280x800 on pipe 1 Sep 9 20:22:54 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (--) intel(0): Output VGA1 using initial mode 1280x1024 on pipe 0 If at logon there is no monitors.xml file for the user, gdm3 by default tries to configure the external VGA1-monitor at the right of the laptop LVDS1-monitor. This fails, probably because the vertical size 800 of LVDS1 is smaller than 1024 for VGA1. gdm3 retries, which is causing a loop until VDA1-monitor is disconnected (see next log): Sep 9 20:23:05 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): resizing framebuffer to 1280x800 Sep 9 20:23:13 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): resizing framebuffer to 2560x1024 Sep 9 20:23:13 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): switch to mode 1280x1024@60.0 on VGA1 using pipe 0, position (1280, 0), rotation normal, reflection none Sep 9 20:23:18 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): resizing framebuffer to 1280x800 Sep 9 20:23:27 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): resizing framebuffer to 2560x1024 Sep 9 20:23:27 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): switch to mode 1280x1024@60.0 on VGA1 using pipe 0, position (1280, 0), rotation normal, reflection none 4.If monitors.xml is present with configuration of VGA1 above LVDS1, dual monitors can be used. Also in this case it is not possible to graphically configure via the displays arrangement the configuration with above sizes and VGA1 right of LVDS1. 5. A correct monitors.xml-file does not totally solve the problem. Frequently the start if Ubuntu hangs completely before showing the logon-screen. It is showing a character screen with next last line. [ OK ] Started GNOME Display Manager. Syslog gives next lines then: Sep 9 00:40:47 Gert2 gnome-shell[1309]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1573]: reference to undefined property "MetaWindowXwayland" Sep 9 00:40:47 Gert2 gnome-shell[1309]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints Sep 9 00:40:47 Gert2 gnome-shell[1309]: CoglError set over the top of a previous CoglError or uninitialized memory.#012This indicates a bug in someone's code. You must ensure an error is NULL before it's set.#012The overwriting error message was: Sliced texture size of 2560 x 1024 not possible with max waste set to -1 Sep 9 00:40:47 Gert2 org.gnome.Shell.desktop[1309]: double free or corruption (fasttop) Sep 9 00:40:48 Gert2 org.gnome.Shell.desktop[1309]: (EE) failed to read Wayland events: Connection reset by peer Sep 9 00:40:48 Gert2 gnome-session[1290]: gnome-session-binary[1290]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Sep 9 00:40:48 Gert2 gnome-session-binary[1290]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6 Sep 9 00:40:48 Gert2 gnome-session-binary[1290]: Unrecoverable failure in required component org.gnome.Shell.desktop 6. If at the logon-screen the arrow at upper right corner is clicked (to exit), also the system hangs with character-screen and same kind of error at syslog. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1790525/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1787957] Re: Ubuntu 18.04 login page not shown after upgrade
*** This bug is a duplicate of bug 1727356 *** https://bugs.launchpad.net/bugs/1727356 Daniel, Thanks for the soon reply. I use now lightdm with display manager gdm3 and WaylandEnable=false. I can startup but the logon-screen is not stable if dual monitor is used. Screens are repeatingly repainted with and without the second monitor and the display of the external monitor contains some extra info from the laptop-screen. But I can logon!!! Also I got 2 crashes on gnome-shell, but cannot reproduce. I will add comment to 1727356 as soon as I know more. Gert On 08/21/2018 04:04 AM, Daniel van Vugt wrote: > *** This bug is a duplicate of bug 1727356 *** > https://bugs.launchpad.net/bugs/1727356 > > Thank you for taking the time to report this bug and helping to make > Ubuntu better. This particular bug has already been reported and is a > duplicate of bug 1727356, so it is being marked as such. Please look at > the other bug report to see if there is any missing information that you > can provide, or to see if there is a workaround for the bug. > Additionally, any further discussion regarding the bug should occur in > the other report. Feel free to continue to report any other bugs you may > find. > > > ** This bug has been marked a duplicate of bug 1727356 > Login screen never appears on early generation Intel GPUs (Core2 and Atom > etc) > > ** This bug is no longer a duplicate of bug 1727356 > Login screen never appears on early generation Intel GPUs (Core2 and Atom > etc) > > ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) > > ** This bug has been marked a duplicate of bug 1727356 > Login screen never appears on early generation Intel GPUs (Core2 and Atom > etc) > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1787957 Title: Ubuntu 18.04 login page not shown after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1787957/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
