KNetwork Manager - System Tray
Tags:
None
Registered Member 
|
Hi everyone...
This is continuation of a post that is already being discussed. Due to some technical reason page 2 is not getting loaded (The forum administrator can have a look at it). So I'm left with no option but to start the remaining as a new post. I'll post the corresponding links in both the post. To view the former part of the topic visit. viewtopic.php?f=18&t=97416 Those of you who came from the old post read ahead
Last edited by melvinjose86 on Wed Nov 02, 2011 6:27 am, edited 1 time in total.
|
|
Registered Member
|
hi,
This is the screenshot  The xsession-errors file (please download the .txt file) http://download1356.mediafire.com/2yelq7c49drg/5ob38ml0fjdarub/xsession.txt |
|
Registered Member
|
Here is one of the problems:
kded(1984) Kded::loadModule: Could not load library "kded_networkmanagement" . [ "Cannot load library /usr/lib/kde4/kded_networkmanagement.so: (/usr/lib/kde4/kded_networkmanagement.so: undefined symbol: _ZN19NotificationManagerC1EP14ConnectionListP7QObject)" ] Object::connect: No such signal QDBusAbstractInterface::Changed() Your Plasma NM package is broken. You must check if you are using old NetworkManager-kde4 package with a new plasmoid-networkmanagement package, that could cause that kind of problem.
Software engineer at Petrobrás http://www.petrobras.com.br/en/about-us/
KDE's Network Management maintainer |
|
Registered Member
|
Hats off... you fished that information out of that whole lot of text.
That can very well be the possibility. And I think I can find it by looking in my package manager. And here is some information I have
And for some clarification, I have a serious doubt regarding that NetworkManager still being there even though the plasmoid version is installed. However trying to uninstall it gives me the warning that the plasmoid version will also be uninstalled... |
Administrator
|
The issue is in the Networkmanager-kde4-libs, which is a very old version. Ensure that they're up to date. Since you're on openSUSE, what does "zypper info NetworkManager-kde4-libs" say?
"Violence is the last refuge of the incompetent."
 Plasma FAQ maintainer - Plasma programming with Python |
|
Registered Member
|
Well this is what i got
|
|
Registered Member
|
I just deleted everything that has to do with network manager.. installed the stock from DVD, ran an update. replaced the monolithic one with the plasmoid.
Also I just updated Network-manager-kde4-libs to Version: 0.9.svn20110829-8.1 Nothing of this has solved my problem. If can't have a solution may be I'll statisfy myself with what I had. Frustrated with the way kde releases updates.. why can't we have backward compatiablity.... if we can't have, then update the entire package including all the dependencies. Well, I feel like joining those who call linux a non-user friendly thing. .. I'm sorry for putting it all down... hope you understand my frustration ... wrestling with this for he last one week and things have just gone worse from bad. |
|
Registered Member
|
Look, it was Opensuse guys that created those packates, not KDE and fore sure it was not me or any other Plasma NM developer. I have seen several people having problems with packages created by distributions, specialy by Opensuse and (K)Ubuntu, who insist in shipping very outdated packages even though they are full of already fixed bugs. The package NetworkManager-kde4-libs -0.9.svn1192577-7.2 for example, it is one year old! I myself fixed about 60 bugs since that package were created, including several crashes. It does not help anybody Opensuse letting that package be easily found by any Opensuse user.
You are also using NetworkManager 0.8.2, Plasma NM for NetworkManager 0.8 is unmaintained. Please upgrade to NetworkManager 0.9, which the instructions I gave to you in this post viewtopic.php?f=18&t=97416#p206166 is about. If you really want to fix this once and for all drop the Opensuse package and compile Plasma NM yourself. Most people who tried compiling by theirselves do not have problems anymore. The fact that Opensuse splits Plasma NM into several packages creates a mess when you use several repositories with several different versions of Plasma NM.
Software engineer at Petrobrás http://www.petrobras.com.br/en/about-us/
KDE's Network Management maintainer |
|
Registered Member
|
I had done the update you proposed in the link... thats when when the Network Manager wouldn't start and then you asked me for that screenshot and xsession-errors.
Now I have installed the stock from the DVD as I had nothing else to do... Could you suggest what I do next ... .. ..and if possible the links to download these packages. .. (I have only one internet connection which I'm using- mobile broadband). so you may prefer to have me download all the packages and then update with the packages I could download and keep so that I can go through the whole process with out a connection to the internet Thanks a lot.. And I'll start a post in the opensuse forums regarding the issue of old packages you mentioned... hope we can find a solution to it.... 
|
|
Registered Member
|
I think the easier solution is compile Plasma NM yourself. You can download the latest version from the link in my blog http://lamarque-lvs.blogspot.com/2011/1 ... -0895.html and compile it like this:
tar jxf networkmanagement-0.8.95.tar.bz2 mkdir networkmanagement_0.8.95_build cd networkmanagement_0.8.95_build cmake -DCMAKE_INSTALL_PREFIX=/usr ../networkmanagement-0.8.95 make make install Or you can try again to upgrade to a newer package from Opensuse repository. Using the very outdated version from Opensuse 11.4 DVD is just going to cause you more troubles. There are literally dozens of bugs in the Plasma NM from that DVD that were already been fixed, there is no point in insisting in using it.
Software engineer at Petrobrás http://www.petrobras.com.br/en/about-us/
KDE's Network Management maintainer |
|
Registered Member
|
I did what you posted and when the system restarted it told me "the system doesn' allow to make DBUS ...something like that. Please contact your administrator or distribution. and that the network manager won't start automatically in the future.
Is there way to fix this.. or we can roll back and start over again.. |
|
Registered Member
|
I gave you two options (recompile Plasma NM yourself or upgrade the opensuse packages), which one of those two you did? Send me the log file with the complete error message. Error messages are not that usefull if they are cut in half.
Software engineer at Petrobrás http://www.petrobras.com.br/en/about-us/
KDE's Network Management maintainer |
|
Registered Member
|
I had upgraded the opensuse packages much before.
so this is what I did... uninstalled the existing network manager and complied what I got from the link you gave me... I'll send you the log files soon... |
|
Registered Member
|
Hi,
The error message was shown only once. It does not appear anymore and the network manager does not start nonetheless. . As far as I can remember it said that its not allowed make changes to D-Bus Permissions/ specify D-Bus path (i don't remember exactly). It also said that Network Manger will not start automatically in the future, contact your administrator or distribution. Thats all I can recall about the error message. I am attaching a link to the error file. http://199.91.154.19/p06sishrxclg/vnmbad4fydvjhle/xsession-errors.txt |
|
Registered Member
|
The Plasma NM debug messages are disabled in your .xsession-errors. You can enable them using the kdebugdialog command. After launching kdebugdialog search for the string network and enable all checkbox that appears.
If NetworkManager does not start then you have a big problem. Are you sure you configured Yast2 to use NetworkManager to manage connections?
Software engineer at Petrobrás http://www.petrobras.com.br/en/about-us/
KDE's Network Management maintainer |
Bookmarks
Who is online
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]
