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
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
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
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.
To reproduce the problem at bionic I had to uninstall the cryptsetup-package
and use DeviceTimeout 1 at /etc/plymouth/plymouthd.cfg.
After installing plymouth:i386 0.9.3-1ubuntu7.18.04.2, the problem disappeared.
Problem solved.
--
You received this bug notification because you are a member of
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with SIGSEGV in /sbin/plymouthd:11
Installed packages plymouth and libplymouth4 from cosmic-proposed.
e.g: Get:1 http://archive.ubuntu.com/ubuntu cosmic-proposed/main i386 plymouth
i386 0.9.3-1ubuntu10.1
To test the fix I verified plymouth and drm-modules are not present at
initramfs.
This causes intel drm to be initiated after
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with SIGSEGV in /sbin/plymouthd:11
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795774
Title:
gnome-shell
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790525
Title:
gnome-shell
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
Created attachment 143414
fix intel_blit.c
fix error_patch2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797882
Title:
At dual monitor intel_do_flush_locked failed: Resource deadlock
avoided
Created attachment 143415
libdrm_ignore_deadlock
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797882
Title:
At dual monitor intel_do_flush_locked failed: Resource deadlock
avoided
To manage
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
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
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
** Tags removed: cosmic verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790525
Title:
gnome-shell assert failure: double free or
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795760
Title:
Xwayland crashed with SIGABRT in OsAbort() from ... 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
Bugs, which is subscribed to 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
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
Bugs, which is subscribed to Ubuntu.
*** 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
Mathieu,
I have to decline. I do not think the Ubuntu-world is waiting for my
newbie Mail-address.
Gert
On 12/6/18 5:25 PM, Mathieu Trudel-Lapierre wrote:
> Sorry, we don't see it there. The emails are re-jiggled by Launchpad.
>
> If you prefer, you can send it to me directly (cyphermox AT
Hello Mathieu,
I hope you can see the sender mail-address.
Thanks for your cooperation.
It is nice to be able to contribute a little bit to Ubuntu/Linux.
Gert
On 12/4/18 8:43 PM, Mathieu Trudel-Lapierre wrote:
> Gert, could you provide us with an email address so we can correctly
> attribute
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
Sorry, previous information wrong.
At upgraded 18.04 I have cryptsetup and crypsetup-bin, not cryptsetup-initramfs.
At fresh 18.10 I have no package from cryptsetup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No.
I have cryptsetup and crypsetup-bin, not cryptsetup-initramfs.
For checking a fix for gnome-wayland I did a fresh install of 32-bits 18.10
from a "mini" (because no image available for 32-bits).
Apparently this does not automatically install cryptsetup-initramfs.
It is rather strange,
The patch I described before solves the problem, but for some reason plymouth
does not attach the second renderer to the keyboard. Therefore switching to
text-mode by pressing escape-key does not work.
To make this work variable manager->local_console_managed must be set to false.
This causes
I do not have access to upstream and also have no idea what to add
there.
I have the impression the root cause of the plymouth crash is a configuration
problem.
I compared Ubuntu 18.04, upgraded from 16.04, with the fresh install of 18.10.
At 18.10 file
I do not have access to upstream and also have no idea what to add
there.
I have the impression the root cause of the plymouth crash is a configuration
problem.
I compared Ubuntu 18.04, upgraded from 16.04, with the fresh install of 18.10.
At 18.10 file
Same problem as described before.
To force I use timeout 1 and theme fade-in. But same problem also occurred at
my PC with the default timeout 5, as was on the trace.
I will upload the crashdump (which by default was ignored by apport).
Routine ply_renderer_free does a hard free of renderer. So
I think, I still get old stuff from 15-10
gert@Gert2:/var/cache/apt/archives$ dpkg -c
libplymouth4_0.9.3-1ubuntu11~mtrudel4_i386.deb
drwxr-xr-x root/root 0 2018-10-15 16:36 ./
drwxr-xr-x root/root 0 2018-10-15 16:36 ./lib/
drwxr-xr-x root/root 0 2018-10-15 16:36
Problem not solved.
I think I got 4 problems:
1)
I think the second ppa (*mtrudel2*) has exacly same contents as the first one.
At least the binaries and shared loadlibraries have the same time stamp (15
october).
So this will not contain the last version.
2)
I have the idea the shared
*** 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
Proposing next improved code
At src/libply-splash-core/ply-device-manager.c
1) at
create_devices_for_subsystem (ply_device_manager_t *manager,
const char *subsystem)
change
found_device = create_devices_for_udev_device (manager, device);
into
Unfortunately again it crashes, logging on with gdm3, both with and
without wayland.
The crash seems to be at the same place.
Syslog:
Oct 16 16:04:13 Gert2 systemd[1]: plymouth-start.service: Main process exited,
code=dumped, status=11/SEGV
Oct 16 16:04:13 Gert2 gdm3[710]: error: unexpectedly
** 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
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
*** 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
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
At my laptop it happens at (almost) every start.
FYI I attach a symbolic trace
** Attachment added: "symbolic trace of crash after released fix"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+attachment/5197512/+files/stack1.txt
--
You received this bug notification
Unfortunately the fix does not solve the problem and still crashes.
ProblemType: Crash
Architecture: i386
Date: Thu Oct 4 16:54:33 2018
DistroRelease: Ubuntu 18.10
ExecutablePath: /sbin/plymouthd
ExecutableTimestamp: 1538408760
MachineType: Dell Inc. Latitude D620
Package: plymouth
** Package changed: evince (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795089
Title:
Gnome-shell crashes if dual monitor connected
To manage notifications about
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
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
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 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
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
53 matches
Mail list logo
