Bug 389646 - Syslog 100's thousands of lines with kdeinit5 / KConfigIni errors
Summary: Syslog 100's thousands of lines with kdeinit5 / KConfigIni errors
Status: REPORTED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-30 16:12 UTC by Ski
Modified: 2021-04-07 07:22 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
rofi-breeze-dark.theme file (2.29 KB, application/x-theme)
2020-10-26 01:58 UTC, Justin Zobel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ski 2018-01-30 16:12:00 UTC
Not sure what category to put this problem in..

KDE Plasma: 5.8.7
KDE Frameworks version: 5.32.0
Mageia 6, x86_64
Clean install.


My syslog file is multi-GB in file size, filling up with the following nonsense with 10's thousands of lines generated per boot..

kdeinit5[15348]: "KConfigIni: In file whatever, line 1: " Invalid entry (missing '=')
kdeinit5[15348]: "KConfigIni: In file whatever, line 2: " Invalid entry (missing '=')
.. etc
.. etc
kdeinit5[15348]: "KConfigIni: In file whatever, line 684: " Invalid entry (missing '=')
Comment 1 Christoph Feck 2018-02-14 22:08:08 UTC
If you would be more specific in which config files the errors appear, we might be able to fix it.
Comment 2 Christoph Feck 2018-03-01 01:05:44 UTC
If you can provide the information requested in comment #1, please add it.
Comment 3 Ski 2018-03-14 17:53:53 UTC
Sorry for the delay in replying.

The problem text is put into /var/log/syslog and /var/log/messages, both become huge with the error, and if not caught, can make the system unstable, or hard to reboot when it eventually fills up /var .

There is a "temporary" workaround, but not an acceptable one. You can move all the text files out of the user's home directory, and put it in any sub-directory, but the bug remains.
Comment 4 Christoph Feck 2018-03-14 18:27:59 UTC
In the bug description, you replaced the config file name with "In file whatever". Unless you show us the actual file names, we cannot proceed with this issue.
Comment 5 Ski 2018-03-14 19:33:03 UTC
(In reply to Christoph Feck from comment #4)
> In the bug description, you replaced the config file name with "In file
> whatever". Unless you show us the actual file names, we cannot proceed with
> this issue.

Sorry, I edited a bit too much out of the original report in the file names.

The file can be named "whatever.txt" - the bug is the same whatever the text file name actually is. It only affects text files, and looks like it only specifically affects .txt extension, as no other text files (config etc) are shown in the log files.
Comment 6 Christoph Feck 2018-03-30 16:44:49 UTC
So to understand you correctly, something tries to open regular text files as configuration files, and this surely leeds to parsing errors.

If you can reproduce this, could you use 'ps -x' in Konsole to find out which application or process actually does this? The information "kdeinit[15348]" unfortunately only reveals the process ID.
Comment 7 Ski 2018-04-06 09:02:52 UTC
It's taken few days for the bug to re-appear, but below is the result of "ps -x", redirected into a text file, where even that text file caused the error text to get logged into syslog!

ps -x
https://pastebin.com/TeHXDbGg

And the syslog entries because of this "ps -x" text file..

Apr  6 09:43:33 local kdeinit5[7223]: "KConfigIni: In file /home/someuser/Running stuff with logging text files in syslog - 20180406.txt, line 1: " Invalid entry (missing '=')
Apr  6 09:43:33 local kdeinit5[7223]: "KConfigIni: In file /home/someuser/Running stuff with logging text files in syslog - 20180406.txt, line 2: " Invalid entry (missing '=')
Apr  6 09:43:33 local kdeinit5[7223]: "KConfigIni: In file /home/someuser/Running stuff with logging text files in syslog - 20180406.txt, line 3: " Invalid entry (missing '=')
Apr  6 09:43:33 local kdeinit5[7223]: "KConfigIni: In file /home/someuser/Running stuff with logging text files in syslog - 20180406.txt, line 4: " Invalid entry (missing '=')
etc. etc.
Comment 8 Christoph Feck 2018-04-26 22:21:05 UTC
Log from comment #7 says 7223 is dolphin process; reassigning for further inspection.
Comment 9 Justin Zobel 2020-10-26 01:58:55 UTC
Created attachment 132744 [details]
rofi-breeze-dark.theme file

Can confirm this is still occurring on Dolphin from git master.

This install of KDE Neon is less than 2 days old and has thousands of lines already.

grep KConfigIni /var/log/syslog  | wc -l
7217

Seems my rofi config isn't liked for parsing Oct 25 18:55:09 justin-desktop dolphin[9988]: kf.config.core: "KConfigIni: In file /media/justin/Data EXT4/Backup-2020-10-25-Move-to-KDENeon/rofi-breeze-dark.theme, line 34: " Invalid entry (missing '=')

Have attached file for reference so it can be debugged easier.
Comment 10 Michael Kutschall 2021-04-07 07:22:23 UTC
- KDE Plasma: 5.21.3
- KDE Frameworks version: 5.80.0
- Arch Linux

I have the same issue with `application/x-theme` files but not with `.txt`.

I don't think it's a bug with Dolphin as editing and saving a file with Kate or Nano triggers the error as well.
Upon opening a theme file, Dolphin gives a hint though:

> The Desktop-File /path/test.theme has no entry "Type=..."

in addition to the 

    ... Invalid entry (missing '=')

messages from the Plasma instance.

Renaming a `*.theme` file to whatever, `*.txt`, `*.themes` or `*.json` avoids all error messages.

It happens with whatever filename-ending I assign to `application/x-theme`, though I haven't tested it for any other types.

When I go to
> System Settings > Applications > File Association

and move `*.theme` to `application/json` the problem dissapears.

If on the other hand I assign a dummy-ending like `*.test` to `x-theme`, now *they* get parsed for invalid entries to a desktop file.

To me it seems the problem is some instance trying to parse a subset of file-types as desktop-configuration-files.

This instance iterates 3 or usually 4 times over the whole file, line by line checking for invalid key-value assignments of `*.ini` files or rather `*.desktop` files as the error message from dolphin suggests.

I hope this helps and someone knows in which region of the codebase such things happen.