Bug 334227 - KSystemLog configure settings can not be changed
Summary: KSystemLog configure settings can not be changed
Status: RESOLVED WORKSFORME
Alias: None
Product: KSystemLog
Classification: Applications
Component: general (other bugs)
Version First Reported In: 20.08
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Nicolas Ternisien
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-02 13:22 UTC by Lee Loncosky
Modified: 2024-09-29 03:58 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lee Loncosky 2014-05-02 13:22:02 UTC
Attempting to change settings via the configuration settings menu does not work. The "apply" and "ok" icon buttons are greyed out and no changes to the settings are possible. 
I think this must be related to another bug here https://bugs.kde.org/show_bug.cgi?id=322793.

Reproducible: Always

Steps to Reproduce:
1. open ksystemlog
2. attempt to configure the settings
3.
Actual Results:  
You can not configure settings.

Expected Results:  
You should be able to change settings per user.
Comment 1 Andrew Crouthamel 2018-11-11 04:34:48 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-21 04:28:43 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 peter.pearce99 2019-01-20 15:54:52 UTC
I can confirm the description of this bug. Bug is valid.

Version 18.04.3

Operating System: Fedora 29
KDE Plasma Version: 5.14.4
Qt Version: 5.11.3
KDE Frameworks Version: 5.53.0
Kernel Version: 4.19.15-300.fc29.x86_64
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 7.7 GiB of RAM
Comment 4 peter.pearce99 2019-01-21 12:54:43 UTC
No change with 18.12.1
Comment 5 Emanuel Helmke 2021-02-10 13:45:12 UTC
I can also confirm the description of this bug. Bug is still valid.

Version 20.08.1

Operating System: Fedora 33
KDE Plasma Version: 5.20.5
Qt Version: 5.15.2
KDE Frameworks Version: 5.78.0
Kernel Version: 5.10.13-200.fc33.x86_64
OS Type: 64-bit
Processors: AMD Ryzen 5 2600
Memory: 31.37 GiB of RAM
Comment 6 Justin Zobel 2023-01-01 04:11:45 UTC
Can confirm on 22.12.0. Downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=2139893
Comment 7 Cherkah 2024-07-14 09:48:31 UTC
+10 for this bug

Operating System: EndeavourOS 
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2
Kernel Version: 6.9.9-arch1-1 (64-bit)
Graphics Platform: Wayland
Comment 8 Chao Feng 2024-09-28 12:20:39 UTC
It works for me on Arch Linux. Maybe it is related to ~/.config/ksystemlogrc configuration file. Please do below step to confirm:
1. Close ksystemlog
2. Move old file to backup name, such as:
mv ~/.config/ksystemlogrc ~/.config/ksystemlogrc.back

Maybe you could past the old file here to let others to check.
Comment 9 Justin Zobel 2024-09-29 03:58:59 UTC
I can no longer confirm this bug running ksystemlog from git master. Since two users are no longer able to confirm I am going to close this bug report. If you are still experiencing this on a recent version, please reopen the report.