SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have run into an issue with the "System Tray" widget after updating Plasma 5 "latest" build today.
It says
Code:
Error loading QML file: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:386:19: Type ExpandedRepresentation unavailable
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/ExpandedRepresentation.qml:134:9: PlasmoidPopupsContainer is not a type
Last edited by RadicalDreamer; 02-23-2020 at 10:26 AM.
Just FYI, after running slackpkg+ to upgrade AleinBOB's ktown kde/plasma to 5.18.1 this morning, I got this error in the system tray and no applet icons were displayed:
Code:
Error loading QML file: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:386:19: Type ExpandedRepresentation unavailable
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/ExpandedRepresentation.qml:134:9: PlasmoidPopupsContainer is not a type
I have run into an issue with the "System Tray" widget after updating Plasma 5 "latest" build today.
It says
Code:
Error loading QML file: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:386:19: Type ExpandedRepresentation unavailable
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/ExpandedRepresentation.qml:134:9: PlasmoidPopupsContainer is not a type
Just FYI, after running slackpkg+ to upgrade AleinBOB's ktown kde/plasma to 5.18.1 this morning, I got this error in the system tray and no applet icons were displayed:
Code:
Error loading QML file: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:386:19: Type ExpandedRepresentation unavailable
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/ExpandedRepresentation.qml:134:9: PlasmoidPopupsContainer is not a type
as PlasmoidPopupsContainer.qml and restarting KDE fixed the problem. The file is dated Feb. 18 @ 8:23 AM.
This is probably limited to my one machine. HTH anyway.
Argh! Bitten by the tar bug on Slackware 14.2 again!
I unpacked (explodepkg) and re-packaged (makepkg) the plasma-workspace to fix the startkwayland script in there. It has happened in the past that files in the package that - excluding leading slash - are 101 characters long, get truncated to 100 characters, thus losing the final "l" in the above case. you'll see plenty of that searching the Internet for "tar truncated 100 characters".
I'll re-build the plasma-workspace package to fix this.
Argh! Bitten by the tar bug on Slackware 14.2 again!
I unpacked (explodepkg) and re-packaged (makepkg) the plasma-workspace to fix the startkwayland script in there. It has happened in the past that files in the package that - excluding leading slash - are 101 characters long, get truncated to 100 characters, thus losing the final "l" in the above case. you'll see plenty of that searching the Internet for "tar truncated 100 characters".
I'll re-build the plasma-workspace package to fix this.
Thanks very much for the explanation and the quick fix, Eric.
K3b hates me again. I have set permissions to 4755 root.cdrom for cdrdao and cdrecord. growisofs is set to 0750 root.cdrom. It stops trying to burn a disc, telling me "cdrecord has no permission to open the device."
Code:
brw-rw----+ 1 root cdrom 11, 0 Feb 25 20:32 /dev/sr0
I can't change permissions in k3b to whatever it is recommending because: "Unable to execute the action: DBus Backend error: service start org.kde.k3b failed: Cannot launch daemon, file not found or permissions invalid." I have no idea how to make this stuff happy. Any suggestions?
K3b hates me again. I have set permissions to 4755 root.cdrom for cdrdao and cdrecord. growisofs is set to 0750 root.cdrom. It stops trying to burn a disc, telling me "cdrecord has no permission to open the device."
Code:
brw-rw----+ 1 root cdrom 11, 0 Feb 25 20:32 /dev/sr0
I can't change permissions in k3b to whatever it is recommending because: "Unable to execute the action: DBus Backend error: service start org.kde.k3b failed: Cannot launch daemon, file not found or permissions invalid." I have no idea how to make this stuff happy. Any suggestions?
Same here.
First thing I did was add my user to the cdrom group and reboot:
Argh! Bitten by the tar bug on Slackware 14.2 again!
I unpacked (explodepkg) and re-packaged (makepkg) the plasma-workspace to fix the startkwayland script in there. It has happened in the past that files in the package that - excluding leading slash - are 101 characters long, get truncated to 100 characters, thus losing the final "l" in the above case. you'll see plenty of that searching the Internet for "tar truncated 100 characters".
I'll re-build the plasma-workspace package to fix this.
Too bad we don't know someone who could update 14.2's tar package
KDE's Dolphin has always had this network services link that says
Code:
The KDNSSD library has been built without Zeroconf support.
if you click on it. Is this something useful and should it be built with it?
With the Jan KDE5/Plasma does anyone else get two volume controls?
When I first installed KDE5 at end of 2019, I also had two volume controls in system tray. One was the Plasma audio control and the other one was kmix. I uninstalled kmix package to keep only the Plasma volume control.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.