Re: Network Manager patched on Ubuntu Karmic 9.10



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dan Williams wrote:
> On Wed, 2009-11-18 at 13:38 -0500, Ryan Novosielski wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Dan Williams wrote:
>>> On Wed, 2009-11-18 at 08:59 -0500, Ryan Novosielski wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> Dan Williams wrote:
>>>>> On Tue, 2009-11-17 at 16:17 -0500, Ryan Novosielski wrote:
>>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>>> Hash: SHA1
>>>>>>
>>>>>> Dan Williams wrote:
>>>>>>> On Wed, 2009-11-18 at 00:00 +0300, Louigi Verona wrote:
>>>>>>>> Hey, Dan!
>>>>>>>> Thanks for the advice. I am certainly keen on helping the community to
>>>>>>>> solve the problem, but the bug had been reported to launchpad with
>>>>>>>> like a dozen duplicates. The daily builds were suggested as partial
>>>>>>>> fix but since then I could get no information from anywhere and bug
>>>>>>>> reports on launchpad do not seem to be updated anymore. My friend was
>>>>>>>> asking me whether he should install Karmic and I couldn't say "yes",
>>>>>>>> since if his first GNU/Linux experience would be like that, I think
>>>>>>>> this would not be a good thing. So eventually I decided to contact
>>>>>>>> this mailing list directly, so that I can get some firsthand
>>>>>>>> information.
>>>>>>>>
>>>>>>>> My dream would be to get a new version of NM. Uninstall this one,
>>>>>>>> install this one and have it work normally like it did in 9.04 %) All
>>>>>>>> apps get bugs like this one sometimes - I am not complaining. I just
>>>>>>>> want to know if something is being done and if yes - when is a total
>>>>>>>> fix planned? To me it is a serious blocker.
>>>>>>> You can't realize that dream until we get some help in debugging the
>>>>>>> issue so that we can fix the problem.  We also can't do anything until
>>>>>>> users help us debug the problem by answering the questions that I've
>>>>>>> asked.
>>>>>>>
>>>>>>> Dan
>>>>>> I have another one for Karmic, and I can do that as well. I've noticed
>>>>>> that there does not seem to be any way to get it to pay any attention to
>>>>>> an Ad-Hoc network. When I'm in range, the network appears in the
>>>>>> knetworkmanager applet, but if I click on it, nothing happens (much the
>>>>>> same as a hidden network did in a case we'd discussed in the past). I'm
>>>>>> not sure what the debug info would say, but it should be interesting to
>>>>>> find out. It looks like absolutely nothing happens at all.
>>>>> Can I get some /var/log/NetworkManager output from that?  Based on that
>>>>> we can enable wpa_supplicant debugging and find out from there.
>>>> It's daemon.log for me. Looks like this is what happens:
>>>>
>>>> Nov 18 08:56:19 novosirj-laptop NetworkManager: <WARN>
>>>> wait_for_connection_expired(): Connection (2)
>>>> /org/freedesktop/NetworkManagerSettings/2 failed to activate (timeout):
>>>> (0) Connection was not provided by any settings service
>>>> Nov 18 08:56:48 novosirj-laptop NetworkManager: <WARN>
>>>> wait_for_connection_expired(): Connection (2)
>>>> /org/freedesktop/NetworkManagerSettings/2 failed to activate (timeout):
>>>> (0) Connection was not provided by any settings service
>>>> Nov 18 08:56:51 novosirj-laptop wpa_supplicant[1256]:
>>>> CTRL-EVENT-SCAN-RESULTS
>>>> Nov 18 08:56:51 novosirj-laptop wpa_supplicant[1256]: WPS-AP-AVAILABLE
>>>> Nov 18 08:57:00 novosirj-laptop NetworkManager: <WARN>
>>>> wait_for_connection_expired(): Connection (2)
>>>> /org/freedesktop/NetworkManagerSettings/2 failed to activate (timeout):
>>>> (0) Connection was not provided by any settings service
>>>> Nov 18 08:57:08 novosirj-laptop NetworkManager: <WARN>
>>>> wait_for_connection_expired(): Connection (2)
>>>> /org/freedesktop/NetworkManagerSettings/2 failed to activate (timeout):
>>>> (0) Connection was not provided by any settings service
>>>> Nov 18 08:57:20 novosirj-laptop NetworkManager: <WARN>
>>>> wait_for_connection_expired(): Connection (2)
>>>> /org/freedesktop/NetworkManagerSettings/2 failed to activate (timeout):
>>>> (0) Connection was not provided by any settings service
>>>>
>>>> Each one of those activate timeouts is a result of me clicking the
>>>> network and waiting 5-6 seconds. Didn't know to look in that log or I
>>>> would have Google'd this one sooner (which I'll do now to see if it gets
>>>> me anyplace).
>>> So this log indicates that the applet isn't creating the connection
>>> correctly and providing it to NetworkManager after you click the
>>> network.  Is this actually knetworkmanager, or is this the KDE4 widget?
>>> knetworkmanager itself (the old standalone applet) is no longer
>>> developed and only works with NM 0.7.x actually.
>> Things are a little confusing in Karmic and I didn't know quite what to
>> make of it (I also didn't know a 0.8.0 was ever released, though I guess
>> the version number would suggest that it's pre-release). While it
>> appears that the previous version (Jaunty, 9.04) used a widget, it seems
>> that Karmic uses KNetworkManager. When looking at my packages, I see:
>>
>> ii  plasma-widget-network-manager
>> 0.9~svn1029786+ag1-0ubuntu1                                Network
>> Management widget for KDE4 Plasma
>> ii  plasma-widget-networkmanagement
>> 0.9~svn1029786+ag1-0ubuntu1                                Network
>> Management widget for KDE4 Plasma
> 
> Ah, that looks like you're *not* using knetworkmanager, you're using the
> new plasma-enabled bits.  So that's good.  I'm talking about the really
> old KDE3 'knetworkmanager'.

I guess that's made somewhat confusing by virtue of the fact that it's
actually called KNetworkManager:

novosirj novosirj-laptop:~$ knetworkmanager -v
Qt: 4.5.2
KDE: 4.3.3 (KDE 4.3.3)
KNetworkManager: v0.9

But this is a new version, yes?

> In any case, you may want to file a bug with the KDE plasma NM component
> because I believe the problem lies there.  It's simply not creating the
> adhoc network configuration settings and proving them to NetworkManager
> after you click the menu item.

That's with NetworkManager or Ubuntu?

- --
 ---- _  _ _  _ ___  _  _  _
 |Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Systems Programmer II
 |$&| |__| |  | |__/ | \| _| |novosirj umdnj edu - 973/972.0922 (2-0922)
 \__/ Univ. of Med. and Dent.|IST/CST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAksEQrQACgkQmb+gadEcsb47VQCgn7wdAAxW7ezXFLEKYAdfr5Rx
9cQAmwYkat0vIQQRpvP0O93MVSlZpjKH
=NxYG
-----END PGP SIGNATURE-----
begin:vcard
fn:Ryan Novosielski
n:Novosielski;Ryan
org:UMDNJ;IST/AST
adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103
email;internet:novosirj umdnj edu
title:Systems Programmer II
tel;work:(973) 972-0922
tel;fax:(973) 972-7412
tel;pager:(866) 20-UMDNJ
x-mozilla-html:FALSE
version:2.1
end:vcard



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]