LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   All Things KDE5/Plasma for Slackware Users. (https://www.linuxquestions.org/questions/slackware-14/all-things-kde5-plasma-for-slackware-users-4175670109/)

USUARIONUEVO 08-18-2021 05:27 AM

Quote:

Originally Posted by drgibbon (Post 6276292)
Anyone else seeing this console spam after using xdg-open on the command line?
Code:

kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/desktop.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/desktop.so'"
kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/applications.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/applications.so'"


Yes i have same messages.

zeebra 08-18-2021 06:56 AM

NetworkManager... Connections. KDE.

So, I'm on Slackware 15rc1.. No worries, I can connect manually with wpa_supplicant I'm sure, that's not the issue. But I'm testing rc1 for everyday use, and I'm having a bit of an issue understanding how I'm suppose to connect wirelessly in KDE on rc1. NetworkManager IS installed (I did a full install), but it seems that "connections" (kde connections??) is just a front end for wpa_supplicant. However, it seems to be trying to go through NetworkManager but failing.

Quote:

Originally Posted by kde notifications
Failed to add connection name
The name org.freedesktop.NetworkManager was not provided to any .service file.

This ofcourse seems to imply that NetworkManager is dependent on systemd somewhow, or that a function of it is. I don't know much about NetworkManager to be honest.
So, looking at /etc.rc.d network manager is not executable and not enabled on startup. But, my question is kind of twofold. Is NetworkManager the "right way" of doing this in KDE on 15rc1? And I don't remember, is it given as a choice during install to activate it by default?

I don't seem to have a way to scan networks in KDE either, or a GUI way at all.
I know WICD was an option in Slackware 14.2 (in extras I think), but I didn't check this in 15rc1.

So, can someone clarify what the main method is, and perhaps why I don't have this by default (if it is NM). Perhaps give me some pointers as what I'm suppose to expect and suppose to do in regards to wireless in KDE on 15rc1.

Thanks.

chrisretusn 08-18-2021 08:38 AM

Quote:

Originally Posted by drgibbon (Post 6276292)
Anyone else seeing this console spam after using xdg-open on the command line?
Code:

kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/desktop.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/desktop.so'"
kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/applications.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/applications.so'"


Yes, the same.

cwizardone 08-18-2021 10:56 AM

Quote:

Originally Posted by zeebra (Post 6276313)
........
So, can someone clarify what the main method is, and perhaps why I don't have this by default (if it is NM). Perhaps give me some pointers as what I'm suppose to expect and suppose to do in regards to wireless in KDE on 15rc1.

Thanks.

Have you read section 4.8 of the Slackware-HOWTO?
You can find it here, http://slackware.oregonstate.edu/slackware64-current/

enorbet 08-18-2021 12:37 PM

You could try "nmtui" from command line. It's ncurses and a tad clunky but efficient and effective. That will tell you if it's installed and working at all.

richarson 08-18-2021 12:53 PM

Quote:

Originally Posted by drgibbon (Post 6276292)
Anyone else seeing this console spam after using xdg-open on the command line?
Code:

kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/desktop.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/desktop.so'"
kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/applications.so" "Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/kf5/kio/applications.so'"


Yep, though I don't know if it's a problem.

I also get:

Quote:

org.kde.kdegraphics.gwenview.lib: Unresolved mime type "image/x-mng"
org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-nikon-nrw"
org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-samsung-srw"
Edit to add: which I guess is irrelevant since I used xdg-open to open an image, you won't get that with other file types, sorry for the noise.

zeebra 08-18-2021 02:20 PM

Quote:

Originally Posted by cwizardone (Post 6276385)
Have you read section 4.8 of the Slackware-HOWTO?
You can find it here, http://slackware.oregonstate.edu/slackware64-current/

That's very helpful, thanks..

Regnad Kcin 08-19-2021 03:51 AM

Quote:

Originally Posted by enorbet (Post 6276418)
You could try "nmtui" from command line. It's ncurses and a tad clunky but efficient and effective. That will tell you if it's installed and working at all.

nmtui is a great tool and very helpful at times.

veeall 08-19-2021 10:32 AM

Does anybody know how to disable plasma systemtray so that tint2 would load tray icons?
Currently it says: 'tint2: another systray is running, cannot use systray'.

Or, in another scenario, if i'm launching kde apps inside other wm, they have huge fonts. I should somehow prelaunch kde xsettings daemon or something, so that plasma would still handle the hidpi scalings even in the other wm, but how?

onebuck 08-19-2021 10:35 AM

Member Response System Monitor
 
Hi,

Quote:

Originally Posted by Timothy Miller (Post 6258033)
plasma-systemmonitor has all the features of ksysguard and then quite a few additional. It has fully replaced ksysguard with 5.22 as the default.

I have been looking at the System Monitor but it seems that I need to do a lot of work to get this installed. I seem to be missing something here. On 14.2 I used Superkaramba with my own System-supervisor scheme to provide system information. I am wondering if I should attempt to convert mine to a Plasma widget. I would need to learn Plasma-widget semantics & syntax but unsure how difficult that would be.
Any pointer or links would be helpful. Sure I have duckduckgo my needs but if someone has an easier way of doing this then I'm all for that.
I am not lazy but my time is limited, do not want to take away from my golf. :)

Any help would be appreciate.
:hattip:

enorbet 08-19-2021 10:35 AM

veeall, are you using any compositor? Some WMs and most DEs can use them as well. For example XFCE behaves somewhat differently when KWin is used as the compositor. IIRC Fluxbox may allow such addition. Anyway it could be one way to get uniformity among different sessions.

zeebra 08-19-2021 11:14 AM

Quote:

Originally Posted by veeall (Post 6276722)
Does anybody know how to disable plasma systemtray so that tint2 would load tray icons?
Currently it says: 'tint2: another systray is running, cannot use systray'.

Maybe rightclick the clock and choose "edit panel", then remove the systray.

veeall 08-19-2021 12:31 PM

Quote:

Originally Posted by enorbet (Post 6276726)
veeall, are you using any compositor? Some WMs and most DEs can use them as well. For example XFCE behaves somewhat differently when KWin is used as the compositor. IIRC Fluxbox may allow such addition. Anyway it could be one way to get uniformity among different sessions.

I'm quite impressed with the new plasma desktop in slackware, but still contemplating to use just pieces of it within compiz-standalone or openbox, or would have used tint2 with compiz and 'spacefm --desktop' in kde by disabling just the panel and plasmashell and kwin, but i have no idea how to stop systemtray.

I have HiDPI monitor and dpi set in .Xresources 'Xft.dpi: 144', but it seems fonts on some kde apps are twice as big when running outside plasma desktop.



Quote:

Originally Posted by zeebra (Post 6276735)
Maybe rightclick the clock and choose "edit panel", then remove the systray.

Yes, i've tried that, systray still locked for tint2.



I remember having, in the past, some code in my openboxs autostart file for loading kde services or init or something in the background, but i have lost the config files since then.

zeebra 08-19-2021 02:21 PM

Quote:

Originally Posted by veeall (Post 6276769)
I remember having, in the past, some code in my openboxs autostart file for loading kde services or init or something in the background, but i have lost the config files since then.

That's weird. I was looking for it in kde services, but it's not it's own thing. I would think it's part of the plasma process and would dynamically remove itself from there if no longer present. Did you restart X etc?

veeall 08-19-2021 03:10 PM

Quote:

Originally Posted by zeebra (Post 6276794)
That's weird. I was looking for it in kde services, but it's not it's own thing. I would think it's part of the plasma process and would dynamically remove itself from there if no longer present. Did you restart X etc?

I need to check this again as new user with default settings. I've relaunched kde multiple times from init 3, with 'pkill plasmashell' and 'compiz --replace ...' in autostart with no panels etc, then launched tint2 from terminal and it always complained about another systray running. I should try with lxpanel too, just in case.


Edit: I got it working by launching compiz from a login script through systemsettingmanagers autostart, and removing 'xembedsniproxy.desktop' and 'org.kde.plasmashell.desktop' from /etc/kde/xdg/autostart/

I'm using 'spacefm --desktop &' and 'tint2 &' to provide for a panel and desktop icons and wallpaper instead of plasmashell.


All times are GMT -5. The time now is 03:08 AM.