On Wed, 19 Jul 2023 19:41:52 +0200 Rene Engelhard <r...@debian.org> wrote:
> tag 1041490 + moreinfo > > thanks > > > Hi, > > > Am 19.07.23 um 19:05 schrieb Jonathan Leivent: > > * What led up to the situation? > > > > Attempt to run libreoffice in a Wayland compositor desktop without > > XWayland support > > What happens then? I get the error: "Gdk-Message: 19:20:01.316: Error reading events from display: Invalid argument" > > > > > * What exactly did you do (or not do) that was effective (or > > ineffective)? > > > > Disabled the libreoffice AppArmor profiles > > Which one? I disabled them all, but I think the only one that needs disabling is the oosplash one. That one includes the X abstraction, but no wayland abstraction. The others include the gnome abstraction which includes the wayland abstraction, so they get it indirectly. > > 2 profiles are in complain mode. > libreoffice-oosplash > libreoffice-soffice That's an excelent point. Why then did it fail and was so easily fixed by using aa-disable? I just assumed immediately when I saw that the oosplash profile includes the X abstraction but not the wayland abstraction (or any other that would pull in the wayland abstraction indirectly, like gnome) that this caused my failure. Are there apparmor issues with it causing failures even though in complain mode? That would be a much more serious bug. I can attempt to replicate the situation with some other debug settings if you know of any I can use. > > Those who would matter during startup (as you imply below) are only > in complain mode, not enforcing.. > > > * What outcome did you expect instead? > > > > Yes. > > That answer doesn't fit the question :) Sorry - I read the question as "Was the outcome what you expected" for some reason. The answer here should be that the outcome was that I successfully started libreoffice after aa-disabling the libreoffice apparmor profiles, and that was what I expected.
