Bug 426192 - Kinfocenter shows "Highlight Changed Settings" but there are no settings to be changed
Summary: Kinfocenter shows "Highlight Changed Settings" but there are no settings to b...
Status: RESOLVED DUPLICATE of bug 425964
Alias: None
Product: kinfocenter
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-04 21:43 UTC by guimarcalsilva
Modified: 2020-09-04 23:28 UTC (History)
3 users (show)

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


Attachments
KinfoCenter window (116.97 KB, image/png)
2020-09-04 21:43 UTC, guimarcalsilva
Details

Note You need to log in before you can comment on or make changes to this bug.
Description guimarcalsilva 2020-09-04 21:43:07 UTC
Created attachment 131423 [details]
KinfoCenter window

SUMMARY


I'm using the latest KDE Neon Unstable Edition (fully updated) and Kinfocenter is showing the new option "Highlight Changed Settings", but it makes no sense to have that option there since as far as I know there's no options to be changed, unlike the system settings app. I'm also using the system in PT-BR but the text is not translated, the same button is translated in system settings. I won't fill another bug report about the translation because I believe the button shouldn't be there anyway.

OBSERVED RESULT

Kinfocenter shows "Highlight Changed Settings".

EXPECTED RESULT

Kinfocenter shouldn't show that option. The option has no effect since there's no options to be changed in Kinfocenter.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma:5.19.80 
(available in About System)
KDE Frameworks Version: 5.74.0
Qt Version: 5.14.2
Kernel Version: 5.4.0-45-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-9400F CPU @ 2.90GHz
Memory: 3.8 GiB of RAM
Graphics Processor: SVGA3D; build: RELEASE; LLVM;
Comment 1 Patrick Silva 2020-09-04 23:28:52 UTC

*** This bug has been marked as a duplicate of bug 425964 ***