Project

General

Profile

Bug #3057

[plasma-systemmonitor] QQmlApplicationEngine failed to load component

avalos - 2 months ago - . Updated about 2 months ago.

Status:
unconfirmed
Priority:
bug
Assignee:
-
% Done:

0%


Description

  • steps to reproduce:
    # pacman -Syu
    $ plasma-systemmonitor
    
  • expected result:
    It should open without problem.
  • actual result:
    Instead, it shows the following output:
QQmlApplicationEngine failed to load component
file::/main.qml:17:1: plugin cannot be loaded for module "org.kde.ksysguard.page": Cannot load library /usr/lib/qt/qml/org/kde/ksysguard/page/libPagePlugin.so: (/usr/lib/qt/qml/org/kde/ksysguard/page/libPagePlugin.so: undefined symbol: _ZN9KSysGuard20SensorFaceController13setShouldSyncEb)

History

#1

Updated by bill-auger 2 months ago

this may be fixed now - kio needed an upgrade, which was done
yesterday - i dont have KDE installed though

#2

Updated by avalos about 2 months ago

Even after kio was updated, and after a system reboot, plasma-systemmonitor still doesn't run. It used to throw that error message, but even before I updated kio, it stopped showing any output and simply not running.

#3

Updated by bill-auger about 2 months ago

avalos posted this backtrace to an upstream bug report - unfortunately it is not very interesting

https://bugs.kde.org/show_bug.cgi?id=439503

GNU gdb (GDB) 10.2
...
Reading symbols from plasma-systemmonitor...
(No debugging symbols found in plasma-systemmonitor)
(gdb) run
Starting program: /usr/bin/plasma-systemmonitor 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7ffff0f8b640 (LWP 164876)]
[New Thread 0x7fffebf78640 (LWP 164877)]
[Thread 0x7fffebf78640 (LWP 164877) exited]
[Thread 0x7ffff14aaa80 (LWP 164872) exited]
[Inferior 1 (process 164872) exited normally]
(gdb) bt
No stack.
#4

Updated by avalos about 2 months ago

Not sure what fixed it exactly, but after a reboot, the problem was gone. libksysguard was updated to 5.22.3 today, but I remember rebooting after that and the problem didn't go away.

Also available in: Atom PDF