I haven't modified any file laid down by either of those packages. The
only dbus-related command I even ever manually entered was related to
autorun. Is it enough to just reinstall the packages? Because I just
did aptitude reinstall network-manager network-manager-gnome and it
did not solve my prob
On Wed, Feb 20, 2008 at 05:29:15PM -, drink wrote:
> I deny that it works for me. I am using ipw3945 to connect to an AP
> WITHOUT any WEP or WPA, so maybe it's a different bug. But the point is,
> nm-applet can not join networks UNLESS I RUN IT AS ROOT. Then it can
> attach as it is supposed t
I deny that it works for me. I am using ipw3945 to connect to an AP
WITHOUT any WEP or WPA, so maybe it's a different bug. But the point is,
nm-applet can not join networks UNLESS I RUN IT AS ROOT. Then it can
attach as it is supposed to. Otherwise, I have to sudo dhclient eth1 (my
ipw3945 lives th
I can confirm that it works correctly now, i.e. NM connects itself to
the network after giving it the keyring password.
--
[ipw3945] nm-applet doesn't work unless I start dhclient manually
https://bugs.launchpad.net/bugs/127649
You received this bug notification because you are a member of Ubuntu
wpa for ipw3945 should be fixed in gutsy now:
network-manager (0.6.5-0ubuntu9) gutsy; urgency=low
* debian/patches/series: disable 41o_completely_deactivate_stage1.patch
for tribe-4
-- Alexander Sack <[EMAIL PROTECTED]> Tue, 7 Aug 2007 12:36:37 +0200
#
network-manager (0.6.5-0ubu
i guess this is a network-manager bug.
** Summary changed:
- nm-applet doesn't work unless I start dhclient manually
+ [ipw3945] nm-applet doesn't work unless I start dhclient manually
** Changed in: network-manager (Ubuntu)
Sourcepackagename: network-manager-applet => network-manager
Sta
