[neon] [Bug 389281] qml errors persist in systemsettings5 making it unusable.
https://bugs.kde.org/show_bug.cgi?id=389281 --- Comment #7 from skrappjaw --- Created attachment 110032 --> https://bugs.kde.org/attachment.cgi?id=110032&action=edit systemsettings5 is broken also. something is amiss... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 389281] qml errors persist in systemsettings5 making it unusable.
https://bugs.kde.org/show_bug.cgi?id=389281 skrappjaw changed: What|Removed |Added Summary|plasma audio settings are |qml errors persist in |barren, but pavu sees all |systemsettings5 making it |devices.|unusable. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 389281] plasma audio settings are barren, but pavu sees all devices.
https://bugs.kde.org/show_bug.cgi?id=389281 skrappjaw changed: What|Removed |Added Severity|major |critical -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 389281] plasma audio settings are barren, but pavu sees all devices.
https://bugs.kde.org/show_bug.cgi?id=389281
--- Comment #6 from skrappjaw ---
I also have this happening in my main machine install now after latest update.
This is the output of systemsettings5 when I move to the look and feel options.
reating the cache for: "kcm:style.desktop"
Already in database? true
First update : QDateTime(2018-01-21 14:54:59.000 EST
Qt::TimeSpec(LocalTime))
Last update : QDateTime(2018-01-21 14:57:22.000 EST
Qt::TimeSpec(LocalTime))
After the adjustment
Current score : 3
First update : QDateTime(2018-01-21 14:54:59.000 EST
Qt::TimeSpec(LocalTime))
Last update : QDateTime(2018-01-21 14:57:22.000 EST
Qt::TimeSpec(LocalTime))
Interval length is 0
New score : 4
ResourceScoreUpdated: "23472dc0-22f7-4d66-a4b8-56217d37744e"
"org.kde.systemsettings" "kcm:style.desktop"
KActivitiesStats( 0x1794230 ) ResultModelPrivate::onResultScoreUpdated result
added: "kcm:style.desktop" score: 4 last: 1516564873 first: 1516564499
: QML QQuickLayoutAttached: Binding loop detected for property
"minimumHeight"
: QML QQuickLayoutAttached: Binding loop detected for property
"minimumHeight"
org.kde.kcoreaddons: Error loading plugin "kcm_lookandfeel" "The shared library
was not found."
Plugin search paths are ("/usr/lib/x86_64-linux-gnu/qt5/plugins", "/usr/bin")
The environment variable QT_PLUGIN_PATH might be not correctly set
"file:///usr/share/kpackage/kcms/kcm_lookandfeel/contents/ui/main.qml"
"Error loading QML file.\n28: module \"org.kde.kcm\" is not installed\n"
Creating the cache for: "kcm:kcm_lookandfeel.desktop"
Already in database? true
First update : QDateTime(2018-01-21 14:54:59.000 EST
Qt::TimeSpec(LocalTime))
Last update : QDateTime(2018-01-21 14:57:25.000 EST
Qt::TimeSpec(LocalTime))
After the adjustment
Current score : 2
First update : QDateTime(2018-01-21 14:54:59.000 EST
Qt::TimeSpec(LocalTime))
Last update : QDateTime(2018-01-21 14:57:25.000 EST
Qt::TimeSpec(LocalTime))
Interval length is 0
New score : 3
ResourceScoreUpdated: "23472dc0-22f7-4d66-a4b8-56217d37744e"
"org.kde.systemsettings" "kcm:kcm_lookandfeel.desktop"
KActivitiesStats( 0x1794230 ) ResultModelPrivate::onResultScoreUpdated result
added: "kcm:kcm_lookandfeel.desktop" score: 3 last: 1516564876 first:
1516564499
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 389281] plasma audio settings are barren, but pavu sees all devices.
https://bugs.kde.org/show_bug.cgi?id=389281 --- Comment #5 from skrappjaw --- Seems like other settings are also broken. I went to set some auto mounts for storage, and non of those options were there. More qml errors. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 389281] plasma audio settings are barren, but pavu sees all devices.
https://bugs.kde.org/show_bug.cgi?id=389281 --- Comment #4 from skrappjaw --- How does one get this module installed? My main machine had no issue with this. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 389281] plasma audio settings are barren, but pavu sees all devices.
https://bugs.kde.org/show_bug.cgi?id=389281 --- Comment #2 from skrappjaw --- KActivitiesStats( 0x4c31f90 ) ResultModelPrivate::onResultScoreUpdated result added: "applications:org.kde.ksysguard.desktop" score: 0 last: 1516544866 first: 1516544866 file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/AppletConfiguration.qml:284:21: QML StackView: Binding loop detected for property "height" "file:///usr/share/kpackage/kcms/kcm_pulseaudio/contents/ui/main.qml" "Error loading QML file.\n24: module \"org.kde.kcm\" is not installed\n" file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/ConfigurationKcmPage.qml:43: TypeError: Type error file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/AppletConfiguration.qml:284:21: QML StackView: Binding loop detected for property "height" file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/ConfigurationKcmPage.qml:43: TypeError: Type error -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 389281] New: plasma audio settings are barren, but pavu sees all devices.
https://bugs.kde.org/show_bug.cgi?id=389281 Bug ID: 389281 Summary: plasma audio settings are barren, but pavu sees all devices. Product: plasma-pa Version: 5.11.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: skrapp...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 110029 --> https://bugs.kde.org/attachment.cgi?id=110029&action=edit Screen shot of the issue. plasma app vs pavucontrol I am working on an audio tutorial on a fresh install of KDEneon. But, it is kind of difficult when the default app for changing the audio settings in pulse is broken. I have to install an oustide app that does not integrate with plasma in order to change the audio settings. Screenshot included. -- You are receiving this mail because: You are watching all bug changes.
