Created attachment 1282783 [details] bad-looking text of Energy Information in KInfoCenter Description of problem: In the Fedora 25 KDE spin, text in the "Energy Consumption Statistics" and "File Index Monitor" panel of KInfoCenter looks bad. Version-Release number of selected component (if applicable): 5.9.5 How reproducible: Steps to Reproduce: 1. Launch Info Center or enter kinfocenter in a terminal 2. Choose "Energy Consumption Statistics" or "File Index Monitor" from the left-hand navigation. Actual results: The text in the panel has varying thickness and pixel glitches. See attached screenshot. Expected results: The text should look OK, as it does in e.g. the "About System" and "Memory" panels. Additional info: If I start the panel from the command line with `kcmshell5 kcm_energyinfo`, it outputs org.kde.kcoreaddons: Error loading plugin "kcm_energyinfo" "The shared library was not found." Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin") The environment variable QT_PLUGIN_PATH might be not correctly set Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion file:///usr/lib64/qt5/qml/QtQuick/Controls/ComboBox.qml:567: TypeError: Cannot read property '__dropDownStyle' of null file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:227:9: QML Binding: Binding loop detected for property "value" QQmlExpression: Expression file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:460:43 depends on non-NOTIFYable properties: Solid::Battery::serial file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:119:9: QML ColumnLayout: Binding loop detected for property "width" file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:119:9: QML ColumnLayout: Binding loop detected for property "width" file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/Graph.qml:64: TypeError: Cannot read property 'x' of undefined while if I enter `kcmshell5 about-distro` (a panel that looks fine), there is no console output.
for posterity, 1. do other kinfocenter sections/tabs appear ok (ie, only energy or most others too)? 2. what video card/driver are you using? (It's possibly related to hw accelerated text rendering)
(In reply to Rex Dieter from comment #1) > 1. do other kinfocenter sections/tabs appear ok (ie, only energy or most > others too)? Everything not prefixed "kcm" looks fine started with `kcmshell5 $name`: about-distro autostart bluedeviladapters bluedevildevices bluedevilglobal cache clock colors componentchooser cookies cursortheme desktop desktoppath device_automounter_kcm devinfo dma emoticons filetypes fontinst fonts formats icons interrupts ioports joystick kamera keys kde-gtk-config khotkeys kwalletconfig5 kwincompositing kwindecoration kwinoptions kwinrules kwinscreenedges kwinscripts kwintabbox mouse netpref nic opengl powerdevilactivitiesconfig powerdevilglobalconfig powerdevilprofilesconfig proxy screenlocker smb smbstatus solid-actions spellchecking standard_actions style translations user_manager useragent wayland webshortcuts workspaceoptions xserver These things prefixed "kcm" also looked fine: kcm_kaccounts kcm_kdeconnect kcm_keyboard kcm_kscreen kcm_ktp_integration_module kcm_memory kcm_networkmanagement kcm_pci kcm_phonon kcm_plasmasearch kcm_printer_manager kcm_sddm kcm_sslkcm_systemd kcm_touchpad kcmaccess kcmkded kcmlaunch kcmnotify kcmsmserver kcmusb kcmview1394 These all had bad-looking text on both my laptop and external monitor: kcm_desktoptheme kcm_energyinfo kcm_fileindexermonitor kcm_lookandfeel kcm_pulseaudio kcm_splashscreen kcmkwineffects All the bad-looking ones complain similarly, e.g.: 'org.kde.kcoreaddons: Error loading plugin "kcm_fileindexermonitor" "The shared library was not found." ' > 2. what video card/driver are you using? (It's possibly related to hw > accelerated text rendering) I think it's Intel integrated graphics. The opengl kcmshell5 module says Direct Rendering (GLX) 3D Accelerator is Unknown, Renderer is Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2). EGL blank, GLX is Mesa Project and SGI version 1.4, GLU is version 1.3. Xorg.0.log includes [ 26.917] (II) LoadModule: "intel" [ 26.917] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so [ 26.921] (II) Module intel: vendor="X.Org Foundation" [ 26.921] compiled for 1.18.99.901, module version = 2.99.917 [ 26.921] Module class: X.Org Video Driver [ 26.921] ABI class: X.Org Video Driver, version 23.0 I thought I had zoomed the second display to look better. But kcm_kscreen > Scale Display says both screens are scaled 1.1.
One other question I had on irc unanswered (as far as I can tell), do you use any customized fonts or font-related settings/configuration?
(In reply to Rex Dieter from comment #3) > do you use any customized fonts or font-related settings/configuration? I'm not sure. I installed Fedora 25 KDE spin late in the beta period. I restored some files from another computer running Kubuntu, but I believe not ~/.config. I found the following ~/.config/*font* files: /home/spage/.config/fontconfig is an empty directory ==> /home/spage/.config/kcmfonts <== [General] forceFontDPI=105.60000000000001 ==> /home/spage/.config/kfontinstuirc <== [Main Settings] GroupSplitterSizes=152,501 PreviewSplitterSizes=280,220 I moved .config/kcmfonts away and still had glitchy font appearance in those kcm settings panels; I opened Fonts and set its "Force fonts DPI" to 123 and had larger glitchy fonts. I just noticed plasma-discover also has glitchy font appearance! (I usually use dnf or the software updates notification.) Dolphin and KWrite look fine. I wonder what the glitchy apps and settings modules have in common.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.