https://bugs.kde.org/show_bug.cgi?id=430501

            Bug ID: 430501
           Summary: kwin_wayland can't load wayland-org.kde.kwin.qpa and
                    won't start from CLI
           Product: kwin
           Version: git master
          Platform: Gentoo Packages
                OS: Linux
            Status: REPORTED
          Severity: critical
          Priority: NOR
         Component: wayland-generic
          Assignee: kwin-bugs-n...@kde.org
          Reporter: 1i5t5.dun...@cox.net
  Target Milestone: ---

git-master kwin_wayland just (within the last 2-3 days, I'm at a2c765800 ATM,
today's frameworks and the rest of plasma too) started failing to startup from
the CLI (dbus-run-session startplasma-wayland).  I'm presently running plasma/X
since plasma/wayland won't run.

By moving kwin_wayland to kwin_wayland.bin and replacing it with a wrapper
script that saves STDERR, I was able to get this

>>>

qt.qpa.plugin: Could not load the Qt platform plugin "wayland-org.kde.kwin.qpa"
in "" even though it was found.
This application failed to start because no Qt platform plugin could be
initialized. Reinstalling the application may fix this problem.

Available platform plugins are: minimal, offscreen, wayland-egl, wayland,
wayland-xcomposite-egl, wayland-xcomposite-glx, xcb, wayland-org.kde.kwin.qpa.

<<<

I had trouble associating that plugin string with an actual file, but
eventually, comparing the current kwin package to a backup, I see the current
version is missing /usr/lib64/qt5/plugins/platforms/KWinQpaPlugin.so.  The
(seemingly successful) build log has a bunch of KWinQpaPlugin hits, but none
for the .so.   Unless it was folded into kwin_wayland itself (step 888/918 does
seem to be linking a bunch of *.o files from KWinQpaPlugin.dir into
bin/kwin_wayland, maybe it was), that would be the problem.  But in the
still-separate case why wouldn't the *.so be built, and if it was folded-in,
why won't kwin_wayland load?

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to