FS#28850 - ntrack network status always Unconnected
Attached to Project:
Arch Linux
Opened by Christian Mollekopf (chrigi_1) - Saturday, 10 March 2012, 12:27 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 12 March 2012, 20:57 GMT
Opened by Christian Mollekopf (chrigi_1) - Saturday, 10 March 2012, 12:27 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 12 March 2012, 20:57 GMT
|
Details
Description:
The networkstatus in the kded module is always on Unconnected. This renders applications like kmail unusable (because you cannot send mail anymore), therefore the severity on high. I don't think the problem is on the kde upstream side, as I looked at that. It's likely in ntrack, no idea how to check that. I couldn't find any info on such a bug for ntrack so I'm assuming it's an arch-linux issue. As a workaround it's possible to force the online status: qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.setNetworkStatus ntrack 4 This command must be issued on every restart of kded4 (login usually). Additional info: * package version(s) ntrack 1:16-2, kde 4.8.1-1 I'm using networkmanager. Steps to reproduce: qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.status Returns always 1 (Unconnected). |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Monday, 12 March 2012, 20:57 GMT
Reason for closing: Fixed
Additional comments about closing: kdebase-runtime 4.8.1-2, dropped QNtrack support
Monday, 12 March 2012, 20:57 GMT
Reason for closing: Fixed
Additional comments about closing: kdebase-runtime 4.8.1-2, dropped QNtrack support
$ qdbus org.kde.kded /modules/networkstatus org.kde.Solid.Networking.status
4
Fresh install of kde 4.8 Arch x86_64, Broadcom brcmsmac module for Wifi, managed by NetworkManager.
I have another machine under Arch i686, updated from kde 4.7 (and previous) for which the issue is not present (Wifi through ipw2200, NetworkManger).