[opensuse] Another NetworkManager problem...?
I've sifted through the various 11.4 NetworkManager issues, and didn't find anything like the minor annoyance I'm having. I've got a clean desktop install of 11.4/KDE4 from the 64 bit LiveCD. I've ran all the updates and added a few Community Repos. I've set Networking to use NetworkManager (for a regular wired NIC) - I've done this because I use VPNs, and NetworkManager is a nice easy way to switch VPNs on/off. If the system is set to use ifup, then network is always working on boot. If the system is set to use NetworkManager, then network is not enabled after a boot. If I click on the NetworkManager widget, I have no networking options at all. If I go into the NetworkManager config, I can only access the VPN tab. All other tabs are greyed out. If I go to YaST, Network, and set it back to Traditional ifup, then network comes up immediately. I can then switch it back to NetworkManager, and network stays working, and I've got full access to all features of the NetworkManager until the next logout/reboot when I lose network again until I manually cycle it to Traditional and back to NetworkManager. So.... any thoughts on solving this one? It's a minor inconvenience since I don't restart or logout often, but.... it's something I'd like to resolve if I can. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday, March 27, 2011 04:05:52 pm C wrote:
I've sifted through the various 11.4 NetworkManager issues, and didn't find anything like the minor annoyance I'm having.
I've got a clean desktop install of 11.4/KDE4 from the 64 bit LiveCD. I've ran all the updates and added a few Community Repos. I've set Networking to use NetworkManager (for a regular wired NIC) - I've done this because I use VPNs, and NetworkManager is a nice easy way to switch VPNs on/off.
If the system is set to use ifup, then network is always working on boot. If the system is set to use NetworkManager, then network is not enabled after a boot. If I click on the NetworkManager widget, I have no networking options at all. If I go into the NetworkManager config, I can only access the VPN tab. All other tabs are greyed out.
If I go to YaST, Network, and set it back to Traditional ifup, then network comes up immediately. I can then switch it back to NetworkManager, and network stays working, and I've got full access to all features of the NetworkManager until the next logout/reboot when I lose network again until I manually cycle it to Traditional and back to NetworkManager.
So.... any thoughts on solving this one? It's a minor inconvenience since I don't restart or logout often, but.... it's something I'd like to resolve if I can.
C, Not sure it if related, but do you have plasmoid-networkmanagement installed instead of KNetworkManager? According to <http://en.opensuse.org/SDB:KDE_upgrade> plasmoid-networkmanagement should be used from KDE45 onwards, but I've done several installs of 11.4 and I always get KNetworkManager instead. Not sure if it will help, but it might. -- Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Mar 28, 2011 at 00:29, Don Raboud wrote:
If I go to YaST, Network, and set it back to Traditional ifup, then network comes up immediately. I can then switch it back to NetworkManager, and network stays working, and I've got full access to all features of the NetworkManager until the next logout/reboot when I lose network again until I manually cycle it to Traditional and back to NetworkManager.
So.... any thoughts on solving this one? It's a minor inconvenience since I don't restart or logout often, but.... it's something I'd like to resolve if I can.
Not sure it if related, but do you have plasmoid-networkmanagement installed instead of KNetworkManager?
According to
<http://en.opensuse.org/SDB:KDE_upgrade>
plasmoid-networkmanagement should be used from KDE45 onwards, but I've done several installs of 11.4 and I always get KNetworkManager instead.
Not sure if it will help, but it might.
I double checked, and it's using the plasmoid instead of KNetwork manager - possibly because it was a clean install vs upgrade? I like the plasmoid (offers a LOT more information about your conenction) over the old KNetworkManager. I wonder... I'll have ot go poke the bug reports to see ifthere is a known issue with the plasmoid... oddly though, I'm using the same install on my laptop, and there the plasmoid is working fine to manage VPNs, wired NIC and WiFi. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 28 March 2011 at 11:06:53 (GMT+2) C <smaug42@gmail.com> wrote:
On Mon, Mar 28, 2011 at 00:29, Don Raboud wrote:
If I go to YaST, Network, and set it back to Traditional ifup, then network comes up immediately. I can then switch it back to NetworkManager, and network stays working, and I've got full access to all features of the NetworkManager until the next logout/reboot when I lose network again until I manually cycle it to Traditional and back to NetworkManager.
So.... any thoughts on solving this one? It's a minor inconvenience since I don't restart or logout often, but.... it's something I'd like to resolve if I can.
Not sure it if related, but do you have plasmoid-networkmanagement installed instead of KNetworkManager?
According to
<http://en.opensuse.org/SDB:KDE_upgrade>
plasmoid-networkmanagement should be used from KDE45 onwards, but I've done several installs of 11.4 and I always get KNetworkManager instead.
Not sure if it will help, but it might.
I double checked, and it's using the plasmoid instead of KNetwork manager - possibly because it was a clean install vs upgrade? I like the plasmoid (offers a LOT more information about your conenction) over the old KNetworkManager. I wonder... I'll have ot go poke the bug reports to see ifthere is a known issue with the plasmoid... oddly though, I'm using the same install on my laptop, and there the plasmoid is working fine to manage VPNs, wired NIC and WiFi.
C.
What's the name of this widget? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Mar 28, 2011 at 11:07, Stan Goodman wrote:
Not sure it if related, but do you have plasmoid-networkmanagement installed instead of KNetworkManager?
[snip]
What's the name of this widget?
It shows up in YaST as plasmoid-networkmanagement. (see the relevant part of Don's comment above) I got it as part of the default KDE4 install off the openSUSE 11.4 KDE LiveCD - I didn't have to select it or manually install it. Oddly... I don't remember getting the widget when I did a DVD install of 11.4. Hmmm.. maybe it's time to test that at home tonight. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 28 March 2011 at 15:31:05 (GMT+2) C <smaug42@gmail.com> wrote:
On Mon, Mar 28, 2011 at 11:07, Stan Goodman wrote:
Not sure it if related, but do you have plasmoid-networkmanagement installed instead of KNetworkManager?
[snip]
What's the name of this widget?
It shows up in YaST as plasmoid-networkmanagement. (see the relevant part of Don's comment above) I got it as part of the default KDE4 install off the openSUSE 11.4 KDE LiveCD - I didn't have to select it or manually install it.
It did not install on the v11.4 (clean install) laptop here; the checkmark in YaST is open, no mark. So, at least in my case, what has been so troublesome here is knetworkmanager. I'll try installing the "plasmoid" thing when I'm back in a couple of weeks, when the inevitable disruptions won't be a critical problem. If this "plasmoid" is a kde4 widget, like other kde4 widgets that would be listed in "Add other widgets", why does it appear only in YaST, rather than in "Add other widgets" where I looked for it unsucccessfully?
Oddly... I don't remember getting the widget when I did a DVD install of 11.4. Hmmm.. maybe it's time to test that at home tonight.
C.
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 28/03/11 14:48, Stan Goodman wrote: > On Monday 28 March 2011 at 15:31:05 (GMT+2) C<smaug42@gmail.com> wrote: >> [snip] >> It shows up in YaST as plasmoid-networkmanagement. (see the relevant >> part of Don's comment above) I got it as part of the default KDE4 >> install off the openSUSE 11.4 KDE LiveCD - I didn't have to select it >> or manually install it. > It did not install on the v11.4 (clean install) laptop here; the > checkmark in YaST is open, no mark. Odd if true; it is definitely "recommended" by patterns-openSUSE-kde4_basis, which is what you get if you choose KDE at install time. So it should always be present on any clean install. > So, at least in my case, what has > been so troublesome here is knetworkmanager. I'll try installing the > "plasmoid" thing when I'm back in a couple of weeks, when the inevitable > disruptions won't be a critical problem. > > If this "plasmoid" is a kde4 widget, like other kde4 widgets that would > be listed in "Add other widgets", why does it appear only in YaST, > rather than in "Add other widgets" where I looked for it > unsucccessfully? The "add widgets" only has access to widgets you've got installed on your local system already. You can get widgets/plasmoids onto your machine system-wide via traditional package managers OR per-user by GHNS - the "Get New Widgets" button in the "Add other widgets" dialogue. plasmoid-networkmanagement is provided via rpm as it's a pretty core part of the desktop. Regards, Tejas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
... and the plasmoid leaves a black blotch on my screen with a red "X" and the message This object could not be created for the following reason: Could not find requested component: org.kde.networkmanagement While I understand that I don't know know what to do about it. -- Few problems cannot be solved by proper application of high explosives. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 28/03/11 12:52, Anton Aylward wrote:
... and the plasmoid leaves a black blotch on my screen with a red "X" and the message
This object could not be created for the following reason:
Could not find requested component: org.kde.networkmanagement
While I understand that I don't know know what to do about it.
That looks to me like some package is missing You need NetworkManager-kde4 NetworkManager-kde4-libs plasmoid-networkmanagement Tejas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Tejas Guruswamy said the following on 03/28/2011 08:11 AM:
On 28/03/11 12:52, Anton Aylward wrote:
... and the plasmoid leaves a black blotch on my screen with a red "X" and the message
This object could not be created for the following reason:
Could not find requested component: org.kde.networkmanagement
While I understand that I don't know know what to do about it.
That looks to me like some package is missing You need NetworkManager-kde4 NetworkManager-kde4-libs plasmoid-networkmanagement
Yes. I paid attention when I installed the plasmoid just now and those were included. I've also verified that with 'zypper search' and 'rpm -qa | egrep ....' Except ... # zypper install NetworkManager-kde4 Loading repository data... Reading installed packages... Resolving package dependencies... Problem: NetworkManager-kde4-0.9.svn1192577-8.10.i586 conflicts with plasmoid-networkmanagement provided by plasmoid-networkmanagement-0.9.svn1192577-8.10.i586 Solution 1: Following actions will be done: deinstallation of plasmoid-networkmanagement-0.9.svn1192577-8.10.i586 install NetworkManager-kde4-libs-0.9.svn1192577-8.10.i586 (with vendor change) openSUSE --> obs://build.opensuse.org/KDE Solution 2: do not install NetworkManager-kde4-0.9.svn1192577-8.10.i586 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 28/03/11 13:35, Anton Aylward wrote:
Tejas Guruswamy said the following on 03/28/2011 08:11 AM:
... and the plasmoid leaves a black blotch on my screen with a red "X" and the message
This object could not be created for the following reason:
Could not find requested component: org.kde.networkmanagement
While I understand that I don't know know what to do about it. That looks to me like some package is missing You need NetworkManager-kde4 NetworkManager-kde4-libs
On 28/03/11 12:52, Anton Aylward wrote: plasmoid-networkmanagement Yes. I paid attention when I installed the plasmoid just now and those were included. I've also verified that with 'zypper search' and 'rpm -qa | egrep ....'
Except ...
# zypper install NetworkManager-kde4 Loading repository data... Reading installed packages... Resolving package dependencies...
Problem: NetworkManager-kde4-0.9.svn1192577-8.10.i586 conflicts with plasmoid-networkmanagement provided by plasmoid-networkmanagement-0.9.svn1192577-8.10.i586 Solution 1: Following actions will be done: deinstallation of plasmoid-networkmanagement-0.9.svn1192577-8.10.i586 install NetworkManager-kde4-libs-0.9.svn1192577-8.10.i586 (with vendor change) openSUSE --> obs://build.opensuse.org/KDE Solution 2: do not install NetworkManager-kde4-0.9.svn1192577-8.10.i586 My mistake, if you're using the plasmoid you don't need NetworkManager-kde4, the conflict is correct.
If you've got plasmoid-networkmanagement and NetworkManager-kde4-libs installed correctly (be sure to check their versions match exactly, and they're from the same repo as the rest of your KDE install), you should have the files /usr/share/kde4/services/kded/networkmanagement.desktop /usr/lib/kde4/kded_networkmanagement.so providing your missing service "org.kde.networkmanagement". Can you check they exist / are readable / etc? Another thing to check is if you open KDE System Settings, and choose (the rather mysteriously named) "Information Sources", does selecting "NetworkManager" as the backend make a difference? Tejas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Tejas Guruswamy said the following on 03/28/2011 09:25 AM:
[snip] My mistake, if you're using the plasmoid you don't need NetworkManager-kde4, the conflict is correct.
If you've got plasmoid-networkmanagement and NetworkManager-kde4-libs installed correctly (be sure to check their versions match exactly, and they're from the same repo as the rest of your KDE install),
I get # rpm -q -a | grep -i networkmanage NetworkManager-kde4-libs-0.9.svn1192577-8.10.i586 plasmoid-networkmanagement-0.9.svn1192577-8.10.i586 .... so that looks OK.
you should have the files /usr/share/kde4/services/kded/networkmanagement.desktop
Yes, its there, is readable and looks fine
/usr/lib/kde4/kded_networkmanagement.so
# file /usr/lib/kde4/kded_networkmanagement.so /usr/lib/kde4/kded_networkmanagement.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped # ls -l /usr/lib/kde4/kded_networkmanagement.so -rwxr-xr-x 1 root root 13912 2011-02-23 02:39 /usr/lib/kde4/kded_networkmanagement.so which seems OK
providing your missing service "org.kde.networkmanagement". Can you check they exist / are readable / etc?
So that's not the problem.
Another thing to check is if you open KDE System Settings, and choose (the rather mysteriously named) "Information Sources", does selecting "NetworkManager" as the backend make a difference?
Odd that, yes. It says that its using NetworkManager 0.7 NOT 0.9 -- Public confidence in the integrity of the Government is indispensable to faith in democracy; and when we lose faith in the system, we have lost faith in everything we fight and spend for. Adlai E. Stevenson Jr. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 28/03/11 15:12, Anton Aylward wrote:
[snip] My mistake, if you're using the plasmoid you don't need NetworkManager-kde4, the conflict is correct.
If you've got plasmoid-networkmanagement and NetworkManager-kde4-libs installed correctly (be sure to check their versions match exactly, and they're from the same repo as the rest of your KDE install), I get # rpm -q -a | grep -i networkmanage NetworkManager-kde4-libs-0.9.svn1192577-8.10.i586
Tejas Guruswamy said the following on 03/28/2011 09:25 AM: plasmoid-networkmanagement-0.9.svn1192577-8.10.i586 ....
so that looks OK.
you should have the files /usr/share/kde4/services/kded/networkmanagement.desktop Yes, its there, is readable and looks fine /usr/lib/kde4/kded_networkmanagement.so # file /usr/lib/kde4/kded_networkmanagement.so /usr/lib/kde4/kded_networkmanagement.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, stripped # ls -l /usr/lib/kde4/kded_networkmanagement.so -rwxr-xr-x 1 root root 13912 2011-02-23 02:39 /usr/lib/kde4/kded_networkmanagement.so
which seems OK
providing your missing service "org.kde.networkmanagement". Can you check they exist / are readable / etc? So that's not the problem.
Another thing to check is if you open KDE System Settings, and choose (the rather mysteriously named) "Information Sources", does selecting "NetworkManager" as the backend make a difference? Odd that, yes.
It says that its using NetworkManager 0.7
NOT 0.9 It says the same on my working system, so that's not the issue. Sorry, I'm stumped. I don't know where you're getting your KDE packages from - maybe try switching back to vanilla 11.4 + KDE 4.6.0? If all the packages are correct the next debugging step is digging into KDE internals - see if you can catch Will S's attention (maybe on the kde list).
Tejas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Mar 28, 2011 at 09:44, C wrote:
On Mon, Mar 28, 2011 at 00:29, Don Raboud wrote:
If I go to YaST, Network, and set it back to Traditional ifup, then network comes up immediately. I can then switch it back to NetworkManager, and network stays working, and I've got full access to all features of the NetworkManager until the next logout/reboot when I lose network again until I manually cycle it to Traditional and back to NetworkManager.
So.... any thoughts on solving this one? It's a minor inconvenience since I don't restart or logout often, but.... it's something I'd like to resolve if I can.
Not sure it if related, but do you have plasmoid-networkmanagement installed instead of KNetworkManager?
According to
<http://en.opensuse.org/SDB:KDE_upgrade>
plasmoid-networkmanagement should be used from KDE45 onwards, but I've done several installs of 11.4 and I always get KNetworkManager instead.
Not sure if it will help, but it might.
I double checked, and it's using the plasmoid instead of KNetwork manager - possibly because it was a clean install vs upgrade? I like the plasmoid (offers a LOT more information about your conenction) over the old KNetworkManager. I wonder... I'll have ot go poke the bug reports to see ifthere is a known issue with the plasmoid... oddly though, I'm using the same install on my laptop, and there the plasmoid is working fine to manage VPNs, wired NIC and WiFi.
No progress on this yet. I'm still having an issue with the Network Manager plasmoid - haven't tried switching back to the old KNetworkManager (I'd rather use the plasmoid). A second machine running the same basic 11.4/KDE4 install is not showing the same issue.... so I'm still stumped on this C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, Mar 29, 2011 at 10:00, C wrote:
On Mon, Mar 28, 2011 at 09:44, C wrote:
On Mon, Mar 28, 2011 at 00:29, Don Raboud wrote:
If I go to YaST, Network, and set it back to Traditional ifup, then network comes up immediately. I can then switch it back to NetworkManager, and network stays working, and I've got full access to all features of the NetworkManager until the next logout/reboot when I lose network again until I manually cycle it to Traditional and back to NetworkManager.
So.... any thoughts on solving this one? It's a minor inconvenience since I don't restart or logout often, but.... it's something I'd like to resolve if I can.
Not sure it if related, but do you have plasmoid-networkmanagement installed instead of KNetworkManager?
According to
<http://en.opensuse.org/SDB:KDE_upgrade>
plasmoid-networkmanagement should be used from KDE45 onwards, but I've done several installs of 11.4 and I always get KNetworkManager instead.
Not sure if it will help, but it might.
I double checked, and it's using the plasmoid instead of KNetwork manager - possibly because it was a clean install vs upgrade? I like the plasmoid (offers a LOT more information about your conenction) over the old KNetworkManager. I wonder... I'll have ot go poke the bug reports to see ifthere is a known issue with the plasmoid... oddly though, I'm using the same install on my laptop, and there the plasmoid is working fine to manage VPNs, wired NIC and WiFi.
No progress on this yet. I'm still having an issue with the Network Manager plasmoid - haven't tried switching back to the old KNetworkManager (I'd rather use the plasmoid). A second machine running the same basic 11.4/KDE4 install is not showing the same issue.... so I'm still stumped on this
Hmmmm.... I've reinstalled everything on a second computer - clean install from the 11.4 KDE LiveCD, and the NetworkManager plasmoid definitely does not work after boot (but will work if you manually cycle the network after startup) if you set to use NetworkManager instead of Traditional ifup. If I switch back to the old KNetworkManager, everything works as expected. I can open a bug report... any suggestions for what log files to include? Is no one else seeing this? C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Mar 30, 2011 at 21:34, C wrote:
I've reinstalled everything on a second computer - clean install from the 11.4 KDE LiveCD, and the NetworkManager plasmoid definitely does not work after boot (but will work if you manually cycle the network after startup) if you set to use NetworkManager instead of Traditional ifup. If I switch back to the old KNetworkManager, everything works as expected.
I can open a bug report... any suggestions for what log files to include?
Is no one else seeing this?
Nevermind... I did one more dig in bugzilla and found the relevant bug report.... https://bugzilla.novell.com/show_bug.cgi?id=623193 C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Anton Aylward -
C -
Don Raboud -
Stan Goodman -
Tejas Guruswamy