fedora-kde / SIG

#119 A config directory is being created on the root directory
Opened by mustafam. Modified

Open
Close Issue

On fresh installation of Fedora KDE, there is a config directory on the root:
/.config/ (not in any home or root home)

I tried to disable sddm service before first boot, and the /.config/ was still created on first boot, so it is not sddm's fault.

I disabled initial-setup and the directory was not created, the unit log shows that among other things, it starts kwin_x11

Maybe running kwin_x11 without some environment variables is causing the problem.

I installed openSUSE, Neon, and Kubuntu, and none of them have this directory.

In the meeting, other members mentioned they have the same /.config/ on systems other than Fedora, I don't know why but maybe they once ran kwin_x11 from the command line?

Do you think, should I report against upstream kwin? initial-setup?

What environment variables are involved according to your experience?

I can attach the full log of initial-setup.service if you need it.

Has anyone checked if this happens on other installs. In particular, do we see it with a minimal install where we add KDE on afterwards?

It shouldn't happen because we don't have the firstboot invocation triggering it.

This tickles a memory of us hitting a similar issue years ago in the kde4 era, I'll dig and see if I can find the old bug about it. This may be it,
https://bugzilla.redhat.com/show_bug.cgi?id=498809
Edited by rdieter

Found a better upstream bug,
https://bugs.kde.org/show_bug.cgi?id=249217

In short, possible issue when $HOME and/or $XDG_CONFIG_HOME is not defined.
Edited by rdieter

Has anyone checked if this happens on other installs. In particular, do we see it with a minimal install where we add KDE on afterwards?

I installed LXQt spin and installed Plasma on it, no /.config/ was created.

As Neal said, it is triggered by initial-setup on firstboot.

You can see the scripts here:
/usr/libexec/initial-setup/firstboot-windowmanager
/usr/libexec/initial-setup/run-initial-setup

I think this is probably an upstream kwin bug, but we may want to implement a workaround in initial-setup. But I guess a better question is why is is initial setup running? We don't have anything configured for initial setup in the first place.

As @ngompa said, "why is is initial setup running?"
Anyone knows if we need "initial setup"?

Duplicate: https://pagure.io/fedora-kde/SIG/issue/119

We need initial setup to do OEM installs but right now work on this is stalled.

I don't know what upstream can do if $HOME and $XDG_CONFIG_HOME are not defined, I think initial-setup is responsible for this.

We are considering removing initial-setup to replace it by KDE Initial System Setup.

Is kwin_wayland is being run as root in this scenario?

Yes.

Metadata Update from @timaeos:
- Issue set to the milestone: Future Release

I did a recent installation of Fedora KDE and didn't see this anymore. Can someone else confirm that this is fixed?

If this isn't an issue anymore, then that means we can use this even on Kinoite.

To note, it probably was fixed when we moved Anaconda Initial Setup to run on kwin's Wayland mode rather than running on X11 like it was before.

Note that initial-setup still worked on Kinoite. It just gave a weird error message on boot.

If we think that the KISS effort is unlikely to happen, we could re-add initial-setup and fix Anaconda's configuration to make it work properly as an EOM install.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.