Re: Sddm cannot find breeze theme

"Rainer Fiebig" ([email protected] via blfs-support Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.beyond.support
Message-ID <[email protected]>
Am 15.06.25 um 16:50 schrieb dave kohler ([email protected] via
blfs-support Mailing List):
>> I'm wondering what symlinks you are talking about.  The only symlinks
>> that should be relevant in this matter are the ones in
>> - /usr/share/xsessions
>> - /usr/share/wayland-sessions
>>
>> You should verify that they exist and point to the right files.  See
>> "Installation of Plasma", section beginning with "If you did not set
>> $KF6_PREFIX to /usr, create symlinks..."
>>
>> If that doesn't help you you should perhaps post the
>> waylanThemeDir=d-section of
>> your sddm.conf.
>>
> 
> Sorry for the delayed response.
No problem, we all have more important things to do at times.

> I have confirmed that the symlinks in /usr/share/xsessions and
> /usr/share/wayland sessions were applied correctly.
> By comparison with the sddm example-config I see that I also  applied a
> modification in the ThemeDir path so that the Breeze
> theme could be found in the /opt/kf6 area. lastly I applied the suggested
> GreeterEnvironment value as suggested by sicarine.
That "GreeterEnvironment=" in your  sddm.conf  looks suspect to me.  It
has to be a comma-separated list but you have newlines in it.  It will
set the variable to a different value than intended.  You could check
this with
    echo "$GreeterEnvironment"

So I suggest to either leave the variable at its default (unset) or if
you think you really need it, remove the newlines or try line
continuation (\) to make it more readable:

GreeterEnvironment=QML2_IMPORT_PATH=/opt/kf6/lib/qml:/opt/qt6/qml,\
QT_PLUGIN_PATH=/opt/kf6/lib/plugins:/opt/kf6/lib/plugins/kcms:/usr/lib/plugins:/opt/qt6/plugins,\
XDG_DATA_DIRS=/usr/local/share:/usr/share:/opt/kf6/share,\
XDG_CONFIG_DIRS=/home/dave/.config/kdedefaults:/etc/xdg:/opt/kf6/etc/xdg,\
PATH=/usr/local/bin:/usr/bin:/opt/kf6/bin:/opt/qt6/bin

> 
> I believe that I initially had placed a symlink in
> the /usr/share/sddm/themes to point at the Breeze theme, but later realized
> I could
> add its /opt/kf6 location to the ThemeDir path in the sddm.conf file.
> 
> I have attached my entire sddm.conf file.
> 
> When I boot into this system, I see a 'normal' sddm screen where I have
> Plasma/Wayland operation selected. After I enter the
> password, The screen clears, I see some 10 or more lines of text flash by
> including at least one read line, then the screen clears again
> and I am back to seeing the sddm screen asking for a login.
> 
> Here is the entire content of the wayland-session.log file:
> kf.dbusaddons: Skipping syncing of environment variable
>  "BASH_FUNC_pathappend%%" as name contains unsupported characters
> kf.dbusaddons: Skipping syncing of environment variable
>  "BASH_FUNC_pathprepend%%" as name contains unsupported characters
> kf.dbusaddons: Skipping syncing of environment variable
>  "BASH_FUNC_pathremove%%" as name contains unsupported characters
> org.kde.startup: "kdeinit5_shutdown" QList() exited with code 255
> startplasma-wayland: Shutting down...
> startplasmacompositor: Shutting down...
> startplasmacompositor: Done.
> 
> 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.
Can't make anything of this.  Have you tried google with
"kf.dbusaddons: Skipping syncing of environment variable"?

Perhaps it's a side effect of that wrongly set GreeterEnvironment?

Rainer

> 
> I am guessing that the brief text output is coming from the kde startup,
> but have not yet discovered where there might be any other information
> providing details of the failure.
> 
>

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-support
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.