| Newsgroups |
gmane.linux.lfs.beyond.support |
| Message-ID |
<[email protected]> |
Am 16.06.25 um 18:28 schrieb dave kohler ([email protected] via
blfs-support Mailing List):
>>
>>
>>> Note the first 3 lines correspond to what sicarine and I have reported in
>>> earlier posts, occurring again under yet different initiating conditions.
>>> Apparently KDE does not tolerate the exporting of functions to the
>>> environment, or only allows symbols.
>> OK, I think we can ignore those lines. I see them, too but
>> Plasma-Wayland comes up just fine. Can you start Plasma-Wayland at all,
>> I mean not using sddm? To test this, log on in a VT and enter
>>
>> dbus-launch --exit-with-session $KF6_PREFIX/bin/startplasma
>>
>> If Plasma does not start, the problem would not be sddm but your Plasma
>> (-Wayland) installation.
>>
>> Rainer
>>
>
> Thanks Rainer!!
>
> I can confirm that sicarine was right, in that the GreeterEnvironment value
> must be a comma-list only and that no '\' chars are allowed when SDDM
> parses the line.
> After this correction I was able to determine that SDDM exited properly as
> it attempted to start KDE environments in either XWayland or Plasma-Wayland
> mode. I have been able to capture about 500 lines of journalctl output from
> this point forward in each of these test cases, and I can see that
> Plasma-Wayland is not starting correctly when I login as a non-root user,
> while XWayland performs correctly. I also have a comparable journalctl log
> from my Arch-KDE environment as an added help.
>
> This morning I have started comparing these journal logs to see what stands
> out as a problem.
> When I saw Rainer's last posted suggestion, I tried the command:
> dbus-launch --exit-with-session $KF6_PREFIX/bin/startplasma-wayland
> and discovered that it starts correctly!! when I launch it from the root
> account, but fails when I launch it from a non-root account, which is how
> SDDM would also launch the plasma session.
>
> I am suspicious that I have something configured in my root account that is
> not present in the non-root user accounts. In particular I see complaints
> in the journalctl log whenever I launch plasma from SDDM,
> kwin_wayland[720]: No backend specified, automatically choosing drm
You can ignore that line.
> kwin_wayland[720]: kwin_core: Failed to open drm node: "/dev/dri/card1"
> kwin_wayland[720]: kwin_wayland_drm: No suitable DRM devices have been found
If "/dev/dri/card1" actually exists (and I suppose it does), I suggest
to check whether sddm's PAM-configuration is according to the book.
> This group of log lines repeat several times before startplasma operation
> terminates with a failure.
>
>
> So at this moment /etc/X11/xorg.conf.d/ defines my two monitors correctly,
> but something else is causing the error at kwin_wayland[720] for my regular
> user account.
>
> If I am looking at the wrong failure, please advise. Also since the root
> account can successfully launch a plasma-wayland session, I would imagine
> that
> further discussion on this problem of mine should be moved to a new thread.
Right.
Rainer
--
http://lists.linuxfromscratch.org/sympa/info/blfs-support
Unsubscribe: See the above information page