Building the KDE4 for Slackware 15.0 in the KTown style - a build based on the PBSLACKS patches
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.
So I have put a new plasma-nm. I have found a case where ip address disappears also in my connections.
networkmanager devices don't update everything at all time. So I took in those cases the activeconnection object which have the ip address.
Last edited by BrunoLafleur; 06-11-2023 at 05:20 PM.
For some messages there is the xsession log which can be useful to know why connections appears or disappears.
I use it for debugging and I have added some messages in the source code of plasma-nm.
So I have put a new plasma-nm. I have found a case where ip address disappears also in my connections.
networkmanager devices don't update everything at all time. So I took in those cases the activeconnection object which have the ip address.
Yes, this one has more robust handling of showing the IP addresses.
However, the Available Connections still disappears. Yet, there's nothing to make to raise an eyebrow on ~/.xsession-errors
Are the /var/log messages for NetworkManager saying something about wirelessNetworkDisappeared because it is the reaction of a NetworkManager signal by the plasma-nm applet. Is there a reactivation signal the applet will not see ? In my wifi connections when they disappeared, they are reactivated when then signal comes back. I tested with a low signal connection (far from my wifi hotspot).
I also have little corrections to do but it will not impact this point.
I was just thinking that it maybe correlated with the kde powerdevil dameon and its panel. The one from KDE5 has option for wifi sleeping modes and the one for KDE4 have no such options. So there is probably some sort of default actions.
In my case non active available wifi connection deactivate after a 7' delay of inactivity. And reactivate when I do some activities but it take some time to reappear.
I was just thinking that it maybe correlated with the kde powerdevil dameon and its panel. The one from KDE5 has option for wifi sleeping modes and the one for KDE4 have no such options. So there is probably some sort of default actions.
In my case non active available wifi connection deactivate after a 7' delay of inactivity. And reactivate when I do some activities but it take some time to reappear.
Quote:
Originally Posted by BrunoLafleur
I think also that kde-workspace in which there is powerdevil don't know about networkmanager because that one is too new for the former.
I think I can manage to re-add the networkmanager support and modify powerdevil.
Considering that the NetworkManager integration, as patched by you, it's much more modern, I believe that makes sense this suspicion that the NetworkManager support on other packages may be obsolete for the current libnm-qt and plasma-nm.
BTW, from what I understand, some NetworkManager support bits are also in the kde-runtime.
Quote:
Originally Posted by BrunoLafleur
Also I have put a new version of plasma-nm with better support for IP adresses and so on.
I have seen it, and I have already added this latest patch to my build. I can confirm that it works better. Many thanks!
Last edited by LuckyCyborg; 06-14-2023 at 06:23 AM.
kdelibs for cmake update definitions of NeworkManager
kde-runtime which uses those update definitions
libnm-qt for adding parameters usefull to plasma-nm
plasma-nm in which I do some improvements for available wired connections in some cases.
in pbslacks as usual.
Last edited by BrunoLafleur; 06-17-2023 at 05:31 PM.
kdelibs for cmake update definitions of NeworkManager
kde-runtime which uses those update definitions
libnm-qt for adding parameters usefull to plasma-nm
plasma-nm in which I do some improvements for available wired connections in some cases.
in pbslacks as usual.
Many thanks for updates!
However, the Available Connections still disappears. And about this I have some supplementary comments...
Apparently, this is what I call a "stock bug" as it's present even on Slackware 14.2 with its native shipped KDE4. I have tried (to confirm this memory of mine) in the past days myself with a LiveSlak built on Slackware 14.2 - and it behaves the same.
HOWEVER, I do not remember if it was fixed by Slackware on -current after 14.2 release, as in these times I have been busy to play with the Plasma5 from the real KTown of Mr. Hameleers.
BUT, I remember (almost precisely) that this issue was NOT present on KUbuntu and/or openSUSE, which I have used in these old times mainly for KDE4 desktop. Yes, these distros patched (and still patches) the software like hell, BUT somehow they fixed this.
Maybe this is useful for you.
Last edited by LuckyCyborg; 06-17-2023 at 09:03 PM.
FWIW: Not a problem with your packages used with -current.
Great Wizard, you can confirm that on -current the WiFi connections which aren't on use (aka these Available Connections) are still displayed as a list after 15 minutes after a WiFi connection become active?
This would be a very useful information to have.
Last edited by LuckyCyborg; 06-18-2023 at 05:14 AM.
However, the Available Connections still disappears. And about this I have some supplementary comments...
Apparently, this is what I call a "stock bug" as it's present even on Slackware 14.2 with its native shipped KDE4. I have tried (to confirm this memory of mine) in the past days myself with a LiveSlak built on Slackware 14.2 - and it behaves the same.
HOWEVER, I do not remember if it was fixed by Slackware on -current after 14.2 release, as in these times I have been busy to play with the Plasma5 from the real KTown of Mr. Hameleers.
BUT, I remember (almost precisely) that this issue was NOT present on KUbuntu and/or openSUSE, which I have used in these old times mainly for KDE4 desktop. Yes, these distros patched (and still patches) the software like hell, BUT somehow they fixed this.
Maybe this is useful for you.
I don't think they fixed something here in KDE4. Because else we would have seen those patches on the Web.
It is more something from other dependencies like sleeping which are not deactivated with the same criteriums.
A lot of packages are involved here. I don't also know your real problem. Do you see some messages in /var/log/messages about connections disapearing ? The applet is following what NetworkManager is doing. But if there are differencies it can be the symptom of a signal not captured by the applet.
And the Plasma 5 applet is not very different from mine. I have taken all that is usefull for now.
Last edited by BrunoLafleur; 06-18-2023 at 06:04 AM.
I don't think they fixed something here in KDE4. Because else we would have seen those patches on the Web.
It is more something from other dependencies like sleeping which are not deactivated with the same criteriums.
A lot of packages are involved here. I don't also know your real problem. Do you see some messages in /var/log/messages about connections disapearing ? The applet is following what NetworkManager is doing. But if there are differencies it can be the symptom of a signal not captured by the applet.
And the Plasma 5 applet is not very different from mine. I have taken all that is usefull for now.
There's nothing useful on /var/log/messages regarding the WiFi connections disappearing. The lines bellow is the end of my log:
Code:
Jun 18 15:05:55 darkstar NetworkManager[4308]: <info> [1687089955.6572] policy: auto-activating connection 'netis_5G_EBC2C2' (f19a0ba1-b9bd-4bb5-8d5a-718766002417)
Jun 18 15:05:55 darkstar NetworkManager[4308]: <info> [1687089955.6579] device (wlan0): Activation: starting connection 'netis_5G_EBC2C2' (f19a0ba1-b9bd-4bb5-8d5a-718766002417)
Jun 18 15:05:55 darkstar NetworkManager[4308]: <info> [1687089955.6580] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 18 15:05:55 darkstar NetworkManager[4308]: <info> [1687089955.6584] manager: NetworkManager state is now CONNECTING
Jun 18 15:05:55 darkstar NetworkManager[4308]: <info> [1687089955.7814] device (wlan0): set-hw-addr: reset MAC address to 90:DE:80:62:38:60 (preserve)
Jun 18 15:05:56 darkstar NetworkManager[4308]: <info> [1687089956.3869] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 18 15:05:56 darkstar NetworkManager[4308]: <info> [1687089956.3874] device (wlan0): Activation: (wifi) access point 'netis_5G_EBC2C2' has security, but secrets are required.
Jun 18 15:05:56 darkstar NetworkManager[4308]: <info> [1687089956.3875] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 18 15:05:56 darkstar NetworkManager[4308]: <info> [1687089956.3883] device (wlan0): supplicant interface state: disconnected -> interface_disabled
Jun 18 15:05:56 darkstar NetworkManager[4308]: <info> [1687089956.4021] device (wlan0): supplicant interface state: interface_disabled -> disconnected
Jun 18 15:05:56 darkstar NetworkManager[4308]: <info> [1687089956.5765] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 18 15:05:56 darkstar NetworkManager[4308]: <info> [1687089956.5769] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 18 15:05:56 darkstar NetworkManager[4308]: <info> [1687089956.5772] device (wlan0): Activation: (wifi) connection 'netis_5G_EBC2C2' has security, and secrets exist. No new secrets needed.
Jun 18 15:05:56 darkstar NetworkManager[4308]: <info> [1687089956.5773] Config: added 'ssid' value 'netis_5G_EBC2C2'
Jun 18 15:05:56 darkstar NetworkManager[4308]: <info> [1687089956.5773] Config: added 'scan_ssid' value '1'
Jun 18 15:05:56 darkstar NetworkManager[4308]: <info> [1687089956.5773] Config: added 'bgscan' value 'simple:30:-70:86400'
Jun 18 15:05:56 darkstar NetworkManager[4308]: <info> [1687089956.5773] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256'
Jun 18 15:05:56 darkstar NetworkManager[4308]: <info> [1687089956.5773] Config: added 'auth_alg' value 'OPEN'
Jun 18 15:05:56 darkstar NetworkManager[4308]: <info> [1687089956.5773] Config: added 'psk' value '<hidden>'
Jun 18 15:05:56 darkstar kernel: wlan0: authenticate with 04:8d:38:eb:c2:c7
Jun 18 15:05:57 darkstar NetworkManager[4308]: <info> [1687089957.2554] device (wlan0): supplicant interface state: disconnected -> associating
Jun 18 15:05:57 darkstar kernel: wlan0: send auth to 04:8d:38:eb:c2:c7 (try 1/3)
Jun 18 15:05:57 darkstar kernel: wlan0: authenticated
Jun 18 15:05:57 darkstar kernel: wlan0: associate with 04:8d:38:eb:c2:c7 (try 1/3)
Jun 18 15:05:57 darkstar kernel: wlan0: RX AssocResp from 04:8d:38:eb:c2:c7 (capab=0x411 status=0 aid=2)
Jun 18 15:05:57 darkstar kernel: wlan0: associated
Jun 18 15:05:57 darkstar NetworkManager[4308]: <info> [1687089957.2694] device (wlan0): supplicant interface state: associating -> 4way_handshake
Jun 18 15:05:57 darkstar kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jun 18 15:05:57 darkstar NetworkManager[4308]: <info> [1687089957.2785] device (wlan0): supplicant interface state: 4way_handshake -> completed
Jun 18 15:05:57 darkstar NetworkManager[4308]: <info> [1687089957.2786] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "netis_5G_EBC2C2"
Jun 18 15:05:57 darkstar NetworkManager[4308]: <info> [1687089957.2787] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 18 15:05:57 darkstar NetworkManager[4308]: <info> [1687089957.2791] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Jun 18 15:05:57 darkstar NetworkManager[4308]: <info> [1687089957.2811] dhcp4 (wlan0): dhcpcd started with pid 6078
Jun 18 15:05:57 darkstar dhcpcd[6078]: dhcpcd-9.4.1 starting
Jun 18 15:05:57 darkstar dhcpcd[6079]: DUID 00:01:00:01:27:9c:a6:1b:d0:27:88:5b:db:c7
Jun 18 15:05:57 darkstar dhcpcd[6079]: wlan0: connected to Access Point: netis_5G_EBC2C2
Jun 18 15:05:57 darkstar dhcpcd[6079]: wlan0: IAID 80:62:38:60
Jun 18 15:05:57 darkstar dbus-daemon[6015]: [session uid=0 pid=6013] Activating service name='org.kde.kuiserver' requested by ':1.15' (uid=0 pid=6068 comm="kdeinit4: plasma-desktop [kdeinit] ")
Jun 18 15:05:57 darkstar dbus-daemon[6015]: [session uid=0 pid=6013] Successfully activated service 'org.kde.kuiserver'
Jun 18 15:05:58 darkstar dhcpcd[6079]: wlan0: rebinding lease of 192.168.1.5
Jun 18 15:05:59 darkstar dhcpcd[6079]: wlan0: leased 192.168.1.5 for 7200 seconds
Jun 18 15:05:59 darkstar NetworkManager[4308]: <info> [1687089959.0169] dhcp4 (wlan0): address 192.168.1.5
Jun 18 15:05:59 darkstar NetworkManager[4308]: <info> [1687089959.0171] dhcp4 (wlan0): plen 24 (255.255.255.0)
Jun 18 15:05:59 darkstar NetworkManager[4308]: <info> [1687089959.0172] dhcp4 (wlan0): gateway 192.168.1.1
Jun 18 15:05:59 darkstar NetworkManager[4308]: <info> [1687089959.0173] dhcp4 (wlan0): lease time 7200
Jun 18 15:05:59 darkstar NetworkManager[4308]: <info> [1687089959.0174] dhcp4 (wlan0): nameserver '192.168.100.1'
Jun 18 15:05:59 darkstar NetworkManager[4308]: <info> [1687089959.0175] dhcp4 (wlan0): nameserver '8.8.8.8'
Jun 18 15:05:59 darkstar NetworkManager[4308]: <info> [1687089959.0176] dhcp4 (wlan0): nameserver '192.168.1.1'
Jun 18 15:05:59 darkstar NetworkManager[4308]: <info> [1687089959.0177] dhcp4 (wlan0): state changed unknown -> extended, address=192.168.1.5
Jun 18 15:05:59 darkstar NetworkManager[4308]: <info> [1687089959.0190] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 18 15:05:59 darkstar dbus-daemon[4275]: [system] Activating service name='org.freedesktop.nm_dispatcher' requested by ':1.1' (uid=0 pid=4308 comm="/usr/sbin/NetworkManager ") (using servicehelper)
Jun 18 15:05:59 darkstar dbus-daemon[4275]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 18 15:05:59 darkstar NetworkManager[4308]: <info> [1687089959.0423] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 18 15:05:59 darkstar NetworkManager[4308]: <info> [1687089959.0426] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jun 18 15:05:59 darkstar NetworkManager[4308]: <info> [1687089959.0432] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 18 15:05:59 darkstar NetworkManager[4308]: <info> [1687089959.0440] manager: NetworkManager state is now CONNECTED_SITE
Jun 18 15:05:59 darkstar NetworkManager[4308]: <info> [1687089959.0441] policy: set 'netis_5G_EBC2C2' (wlan0) as default for IPv4 routing and DNS
Jun 18 15:05:59 darkstar NetworkManager[4308]: <info> [1687089959.1437] device (wlan0): Activation: successful, device activated.
Jun 18 15:05:59 darkstar NetworkManager[4308]: <info> [1687089959.1445] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 18 15:06:00 darkstar dbus-daemon[6015]: [session uid=0 pid=6013] Activating service name='org.gtk.vfs.Daemon' requested by ':1.63' (uid=0 pid=6279 comm="/usr/lib64/firefox/firefox --sm-client-id 101a0219")
Jun 18 15:06:00 darkstar dbus-daemon[6015]: [session uid=0 pid=6013] Successfully activated service 'org.gtk.vfs.Daemon'
Jun 18 15:06:01 darkstar dbus-daemon[6015]: [session uid=0 pid=6013] Activating service name='org.freedesktop.portal.Desktop' requested by ':1.63' (uid=0 pid=6279 comm="/usr/lib64/firefox/firefox --sm-client-id 101a0219")
Jun 18 15:06:01 darkstar dbus-daemon[6015]: [session uid=0 pid=6013] Activating service name='org.freedesktop.portal.Documents' requested by ':1.77' (uid=0 pid=6347 comm="/usr/libexec/xdg-desktop-portal ")
Jun 18 15:06:01 darkstar dbus-daemon[6015]: [session uid=0 pid=6013] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.78' (uid=0 pid=6352 comm="/usr/libexec/xdg-document-portal ")
Jun 18 15:06:01 darkstar dbus-daemon[6015]: [session uid=0 pid=6013] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
Jun 18 15:06:01 darkstar dbus-daemon[6015]: [session uid=0 pid=6013] Successfully activated service 'org.freedesktop.portal.Documents'
Jun 18 15:06:01 darkstar dbus-daemon[6015]: [session uid=0 pid=6013] Activating service name='org.freedesktop.secrets' requested by ':1.77' (uid=0 pid=6347 comm="/usr/libexec/xdg-desktop-portal ")
Jun 18 15:06:01 darkstar dbus-daemon[6015]: [session uid=0 pid=6013] Successfully activated service 'org.freedesktop.secrets'
Jun 18 15:06:01 darkstar dbus-daemon[6015]: [session uid=0 pid=6013] Successfully activated service 'org.freedesktop.portal.Desktop'
Jun 18 15:06:01 darkstar dbus-daemon[6015]: [session uid=0 pid=6013] Activating service name='org.a11y.Bus' requested by ':1.60' (uid=0 pid=6279 comm="/usr/lib64/firefox/firefox --sm-client-id 101a0219")
Jun 18 15:06:01 darkstar dbus-daemon[6015]: [session uid=0 pid=6013] Successfully activated service 'org.a11y.Bus'
However, after some time when is made this connection to 'netis_5G_EBC2C2' (wlan0) the Available Connections disappeared and NOTHING is logged on /var/log/messages.
BTW, this 'netis_5G_EBC2C2' comes from a Netis router used as B/G/N/AC WiFi access-point and Ethernet switch with 4 outputs, and its WLAN is connected to the output of a VPN covered Ethernet connection of the main 4G router - which is in fact a x86_64 mini-PC dedicated for this business.
Permit me to note (again) that I have multiple USB WiFi dongles, with various performances and chipsets - from 150Mbps to 867Mbps, and I have various (honestly junkware) computers. Heck, I have even 3 different WiFi access-points in my house, one being under VPN, the other 2 not.
All my hardware combinations behave in the same way: on Slackware 15.0, after some time the Available Connections will disappear on the KDE4 sessions. While the Wayland or X11 Plasma5 sessions seems to keep them just fine.
Last edited by LuckyCyborg; 06-18-2023 at 07:59 AM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,167
Rep:
Quote:
Originally Posted by cwizardone
Quote:
Originally Posted by LuckyCyborg View Post
............However, the Available Connections still disappears.......
FWIW: Not a problem with your packages used with -current.
Quote:
Originally Posted by LuckyCyborg
....you can confirm that on -current the WiFi connections which aren't on use (aka these Available Connections) are still displayed as a list after 15 minutes after a WiFi connection become active? .......
My apologies. I misread your message.
I rarely use WiFi.
When connected via WiFi, the available WiFi connections disappear.
When connected via hardwire, the 'available connections" including available Wifi connections, do not disappear.
BTW, when connected via WiFi, the applet shows a small read red "x" which means I'm not connected, when, as I said, I am connected.
Again, my apologies.
As Bette Davis once said, "This getting old is not for the faint of heart."
Last edited by cwizardone; 06-18-2023 at 11:38 AM.
Reason: Typo.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
