** Changed in: knetworkmanager
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.
https://bugs.launchpad.net/bugs/259278
Title:
knetworkmanager will no longer connect
--
Apologies again... This works for me so I'll unsubscribe.
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.
--
kubuntu-bugs mailing list
Apologies. I've had my email hacked. Please remove the above.
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.
--
kubuntu-bugs mailing
** Changed in: knetworkmanager (openSUSE)
Status: New = Fix Released
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.
--
** Changed in: knetworkmanager
Status: Confirmed = Won't Fix
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.
--
kubuntu-bugs
** Tags added: iso-testing
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
I can confirm mrvanes comment
This problem is still present in Jaunty, network-manager-kde
0.7svn864988-0ubuntu8. nm-applet works fine.
Trying with a Virgin Mobile Huawei E169 [detecting as a E620]
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.04
DISTRIB_CODENAME=jaunty
DISTRIB_DESCRIPTION=Ubuntu 9.04
** Branch linked: lp:ubuntu/karmic/knetworkmanager
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.
--
kubuntu-bugs mailing list
Jose,
Blacklisting acer_wmi worked brilliantly, thanks :)
Can confirm as today my wireless (WPA2) connects.
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to
Just today (8.30 GMT) I reinstalled Kubuntu Jaunty Alpha 4, and dist-upgraded
to the current state.
The network manager plasmoid still shows a greyed out wlan0 with an enable
switch, which will not turn on.
Am I missing something? - some people seem to have more luck than me.
I have tried sudo
This might be related to a rf-kill switch bug in iwl3945. It should work
if you start with rf-kill disabled (ie wireless enabled).
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which
Try adding blacklist acer-wmi to /etc/modprobe.d/blacklist, might fix
the issue.
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.
--
This problem is still present in Jaunty, network-manager-kde
0.7svn864988-0ubuntu8. nm-applet works fine.
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to
Yes, this one is back in jaunty. But wireless in jaunty seems pretty bad
right now. On my aspire one, besides knetwork manager no longer working
(again) ath5k drivers will keep roaming away from the AP when there is
more than one AP with the same SSID, and since cfg80211 has been updated
and no
Are you using knetworkmanger? I believe the KDE 4.2 includes a plasma
applet for interacting with network manager. Try adding an applet and
seeing if you can find a network manager related one. Please keep in
mind that I am not running Jaunty and don't know if it includes this
functionality.
On
Yes, Jaunty has quite usable plasma-widget-network-manager some time
now. I tried it a couple of weeks ago but wasn't impressed. It's
actually usable now and fixes the problems with knetworkmanager most
importantly!
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
I've been running the network-manager plasmoid for about a week. I've found
the following results:
1. WEP networks seem to work fine, whether they are DHCP or static-IP. I
still need a few tests on the static IP, but it *appears* to be working.
2. LEAP and PEAP networks do NOT work at all.
Jonathan: There is no info in the bug to indicate it's an API problem.
Perhaps the details should be edited to suit, and I can open a new bug.
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
See:
https://bugs.launchpad.net/ubuntu/+source/knetworkmanager/+bug/259278/comments/6
https://bugs.launchpad.net/ubuntu/+source/knetworkmanager/+bug/259278/comments/9
https://bugs.launchpad.net/ubuntu/+source/knetworkmanager/+bug/259278/comments/20
and
On Mon, Nov 24, 2008 at 12:45:50PM -, Jonathan Thomas wrote:
See:
https://bugs.launchpad.net/ubuntu/+source/knetworkmanager/+bug/259278/comments/6
https://bugs.launchpad.net/ubuntu/+source/knetworkmanager/+bug/259278/comments/9
grahamt: the knetworkmanager in the intrepid repos is a dummy package -
it doesn't do anything by itself, it just depends on netowrk-manager-kde
(which is knetworkmanager renamed). If you installed from a CD,
knetworkmanager shouldn't be installed, and installing it won't change
anything (unless
changing this back, since I'm using 1:0.7svn864988-0ubuntu1 and it's
still not working...
** Changed in: knetworkmanager (Ubuntu)
Status: Fix Released = Confirmed
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because
nominating for jaunty since network-manager-kde is the same version in
both, as is network-manager.
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
just checked out and compiled from svn from instructions at
http://en.opensuse.org/Projects/KNetworkManager#Download
Checked out revision 887865.
No joy.
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member
https://bugzilla.novell.com/show_bug.cgi?id=406635
same bug for OpenSUSE.
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Your bug is entirely different than this API change bug. They just
happen to have the same symptom, non-working wireless.
** Changed in: knetworkmanager (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: knetworkmanager (Ubuntu Intrepid)
Status: Confirmed = Fix Released
--
Grahamt method worked for me too. I installed KnetworkManager today again
(removing WICD at the same time) and now when I suspend to ram and change
networks it works fine.
If something breakes I let you know.
Thanks Grahamt.
--
knetworkmanager will no longer connect
Yo solucione el bug:
Visite la web de mi ISP y alli tenia tb la clave de acceso wifi en forma
hexadecimal. Edite la conexion y puse la constraseña en formato
hexadecimal y por fin fue¡¡¡
I resolved this bug:
I went to ISP web, and there I take a hexadecimal access. I use this
code to enter in
I had this bug, and I've resolved it (at least for me).
I'm using Kubuntu Intrepid with Proposed updates on a Acer Travelmate
520 with a Linksys Broadcom bcm43 PCMCIA wireless card.
This setup worked fine under Hardy, but I suffered from this bug after
upgrade to Intrepid.
A comment above
I'm also having this problem. Can see wireless connections, can't
connect.
02:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g
Wireless LAN Controller (rev 03)
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification
** Changed in: knetworkmanager
Status: Unknown = Confirmed
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.
--
kubuntu-bugs
Hi
I had the problem as well - NM didn't connect after suspend to ram or reboot.
Trylik, could you please check if it does reconnect properly now after suspend
to ram? Did You install the NM from official repos or somewhere else (link
please)?
For now as a workaround i use wicd which works
I have also a problem when connecting to my wireless device.
r
02:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2]
Network Connection (rev 05)
[EMAIL PROTECTED]:~$
[EMAIL PROTECTED]:~$ uname -a
Linux ubuntu 2.6.27-7-generic #1 SMP Fri Oct 24 06:42:44 UTC 2008 i686
@jacoor
well most of the times it manages to connect even after suspend to RAM,
but not all the time
for ex i have been at work and wpa wifi connection was active
then i moved to bluetooth hsdpa phone as internet source
then suspended to ram
then woken up at the cafe - no internet
then
** Bug watch added: KDE Bug Tracking System #130918
http://bugs.kde.org/show_bug.cgi?id=130918
** Also affects: knetworkmanager via
http://bugs.kde.org/show_bug.cgi?id=130918
Importance: Unknown
Status: Unknown
--
knetworkmanager will no longer connect
@trylik
Thanks for your answer - I tried everything with old version of NM (restarting
HAL, clearing config files, restarting networking)
and.. The only thing that worked from time to time was right key on tray icon,
disable wireless, wait a minute, enable and try to connect.
I think I will
This was probably already mentioned earlier, but what I have noticed is
that my wireless works just fine with DHCP and WEP/WPA networks, but if
the nm-applet (which is called network-manager-gnome in Ubuntu) is
installed knetworkmanager doesn't work, but nm-applet does. If
uninstalling nm-applet
I was going to install network-manager-gnome in place of network-
manager-kde, just to try to see if my situation is resolved. But as of
right now, installing the -gnome version of the applet also entails
installing additional packages such as libgweather, libsexy2, mobile-
it is working for me now
connectiong to WPA WEP as well
great job
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.
--
kubuntu-bugs
I have installed Kubuntu 8.10, including all updates, on an IBM ThinkPad R50p.
It has an Atheros wireless included (lspci:
02:02.0 Ethernet controller: Atheros Communications Inc. AR5212 802.11abg NIC
(rev 01)). knetworkmanager does not work for my wireless. I tested it with two
different
It seems that there does exist a knetworkmanager that is in sync with the new
API and that seems to solve this bug. But as of this writing, the Intrepid
package has not being updated to that release.
This bug should be open till then (BTW, confirmed here, sigh)
** Changed in: knetworkmanager
Oh, I was wrong, the package is already using the new upstream code.
According to the changelog of the the last update (October 26th) or
network-manager-kde the new GUI is in fact using the new NM API, still
it seems that some users have the problem.
--
knetworkmanager will no longer connect
I have a IPW2200 and it works when I get my associate with WPA2 PSK
and get my address with DHCP. I don't know about the other cases.
wt
On Sat, Nov 1, 2008 at 8:04 AM, mumismo [EMAIL PROTECTED] wrote:
Oh, I was wrong, the package is already using the new upstream code.
According to the
So is anyone still monitoring this (aside from those of us who can't get
it to work)? I still don't understand how we have 'fix released' - it's
STILL NOT WORKING.
I've attached the output of /var/log/daemon.log for attempts to connect
to my campus LEAP system from using two different wifi
Same at me, just that I have cable FTTH connection and not wireless. So I don't
know if this is the same problem.
It died yesterday and some time ago. The first time I managed to get it back on
with hard reset on my modem.
No even that doesn't help.
I'm using Kubuntu 8.10 RC.
It might not be a
Oh I remembered that it doesn't work on my Ubuntu live CD (7.04) so it's
probably not this bug...
But would still someone help me with my problem?
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of
the same problem is on my computer
first i installed mythubuntu 8.10
and everthing was ok (aetheros chipset by the way, what suprised me a
lot)
then i added kde4 but knetwork manager still is worth nothing, sadly
i can see networks but i cant connect, even pluging wired internet gives
nothing
I have kubuntu 8.10 beta 1 and have the same problem on my Thinkpad T42p
with Atheros Card. Network manager kde is not able to connect to
wireless LEAP that I have in my office. However, if I try to connect to
the same network manually by stopping network manager, I am able to
connect.
** Changed in: knetworkmanager (openSUSE)
Importance: Unknown = Undecided
Bugwatch: Novell/SUSE Bugzilla #429692 = None
Status: Fix Released = New
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a
I don't understand why the status of this bug has changed to fix released,
since as of today Intrepid update knetworkmanager keeps on not connecting to a
wired network with manual configuration, and the error message I can see in
syslog is the following:
Oct 21 09:52:46 eagle NetworkManager:
I'll second hardhu's comment - no connection on static IP OR on LEAP networks.
Does work on WEP with DHCP, though.
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to
Having similar problems here. Deleting .kde directory did not fix it. Latest
intrepid as of today.
However, I found that when I did a suspend to disk operation from the shutdown
menu, the suspend failed, but the wifi light came on on my laptop and
kdenetwork manager was able to connect straight
** Changed in: knetworkmanager (Ubuntu Intrepid)
Assignee: (unassigned) = Jonathan Riddell (jr)
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to
** Changed in: knetworkmanager (Ubuntu Intrepid)
Status: Confirmed = Fix Released
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Since updating, I no longer have an issue with knetworkmanager. Of
course, I'm using a Broadcom 4318 chipset for my wireless connection.
I'll be updating again today to verify that it's still connecting
without issues. Unfortunately, I have no way of testing on a secure
network at this time but
I don't think that KNetworkManager is detecting the cipher settings
properly for WPA enterprise -- I had to manually set PEAP as the key
type and untick the CCMP ciphers (the connection here only uses TKIP).
The old KDE3 version of KNetworkManager correctly detected these
settings.
--
Just finished updating. Still no issues with unsecure networks.
Unfortunately, I still have no secure network to test out on. But all
seems to work well with Broadcom driver.
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification
I have found that when I cannot connect to a secured wireless net,
removing my .kde directory and starting fresh fixes it. However, I do
kinda think that this is a less than ideal solution.
wt
On Wed, Oct 15, 2008 at 1:08 PM, TFrog [EMAIL PROTECTED] wrote:
Just finished updating. Still no
** Changed in: knetworkmanager (Ubuntu Intrepid)
Target: ubuntu-8.10-beta = ubuntu-8.10
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in
aptitude install nscd
this resolved my problem
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Tried today on a fresh intrepid beta install: it does work with wpa
encrypted wireless network and ip address assigned with dhcp, it doesn't
work with a wired network where ip address is statically set using
manual configuration.
** Changed in: knetworkmanager (Ubuntu Intrepid)
Status: Fix
I'm suffering from the same problem. I'm using Kubuntu Intrepid Beta
fully updated and I can't connect set the IP manually. It works fine if
I'm using DHCP. Reading the previous comments here, I tried installing
network-manager-gnome and using nm-applet to configure and connect to
the network.
More testing, here's what I got:
WEP/DHCP - Works!
WEP/Static IP - FAILS
hardwired/static IP - FAILS
LEAP (either ieee802.1X OR WPA Enterprise) - FAILS.
The LEAP I've tried BOTH under the iwl3945 built-in and under my USB
wireless (zd1211rw). Leap works under gnome nm-applet, DOES NOT WORK
under
On Wed, Oct 08, 2008 at 03:05:12PM -, charles.figura wrote:
Doesn't work AGAIN. Was fine this morning (hadn't shut off from last
night), but shut down, came in to work this morning, and the same old
crap all over again - it won't connect unless I plug in a cable - it's
not even trying.
Alexander -
/etc/network/interfaces just has the standard
auto lo
iface lo inet loopback
I was testing out on my *other* network as well - with static IP. I
could get neither the wired nor wireless to work there, no error
messages on dmesg. And, as before, it works fine under gnome's nm-
Doesn't work AGAIN. Was fine this morning (hadn't shut off from last
night), but shut down, came in to work this morning, and the same old
crap all over again - it won't connect unless I plug in a cable - it's
not even trying. Click on the network, the grey world icon flashes to
the gear and
I'm jumping into this a little late, but I'm running an up-to-date (as
of time of writing) Kubuntu Intrepid beta and I'm seeing the same thing.
When I try to connect to wireless, either thorough a new connection or
one I already set up, it stays as a grey globe and doesn't even attempt
to connect
I just downloaded a daily build of Intrepid a week ago and knetwork
manager is currently working. However, I do need to update it and see
if it continues to work. Will most likely do that tomorrow morning as I
have this on another drive not currently installed into my laptop. Of
course, like
So my latest note is this - I seem to be able to connect fine to my home
network - I'm connected now. But of the three networks I use at the
workplace (two WEP, one LEAP) it does not function. I'll try to post
/var/log/daemon.txt output tomorrow.
--
knetworkmanager will no longer connect
I don't have a problem connecting my problem is staying connected. It
seems at random times my connection fails and knetwork manager just
appears to be still connected. Is there a way to fix this, i have to
disable the wireless card and re-enable it every time this happens and
its beginning to
Seems fixed for me with iwl3945 driver; networkmanager successfully
connects to a WEP encrypted access point and the access point shows up
when clicking on the system tray.
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because
I had gotten knetworkmanager to work, but on upgrade to intrepid beta,
it failed again. Currently, if I left-click on the knetworkmanager tray
icon and select a valid network, the tray icon flashes to the gear icon
(working), but then reverts quickly to the grey globe icon, and will not
connect.
I have noticed that with my laptop when I suspend and resume that module
ath_pci needs to be unloaded and reloaded then ifconfig'ed up. Which
isn't really something knetworkmanager should be doing - just a heads up
for others who may still have issues connecting to wireless networks.
I'm going to
Works fine in Kubuntu Intrepid Beta. However, Knetworkmanager does not
show available wireless networks when you right click on systray icon.
It does list avilable wireless connections in the manually add
connection menu.
--
knetworkmanager will no longer connect
Okay - I just did a complete purge of network-manager, knetworkmanager,
network-manager-kde, network-manager-gnome, and libnm-glib0, reinstalled
all of them (but network-manager-gnome) and it seems to be working
correctly! Must have been some residual config somewhere.
--
knetworkmanager will
** Changed in: knetworkmanager (openSUSE)
Status: In Progress = Fix Released
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.
--
Works for me now!
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Yes, confirmed fixed. Thanks Jonathan.
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PROTECTED]
Me too! Good work, and thanks for working on this issue.
On Fri, Sep 26, 2008 at 11:28 PM, Markus Golser [EMAIL PROTECTED] wrote:
Works for me now!
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a direct
Still not working for me (manual wired configuration).
Using the gnome applet.
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.
--
Works with wired, wireless (WIFI) and USB 3G-modem.
However, autoconnection does not work for WIFI and USB 3G-modem.
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed
When I first tested it did not work. I was running nm-applet at the same
time, so I killed that and quit knetwork manager, then restarted
knetworkmanager.
That made it work.
Now I just have to figure out how to stop nm-applet from loading.
Thanks for all of your help.
--
knetworkmanager will
Thanks, everything is working for me.
I can't confirm that autoconnection doesn't work for WLAN as Sokraates says.
@ Michael Calabrese:
The only way I found is to remove/purge network-manager-gnome.
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received
This bug was fixed in the package knetworkmanager -
1:0.7svn864988-0ubuntu1
---
knetworkmanager (1:0.7svn864988-0ubuntu1) intrepid; urgency=low
* New upstream snapshot, now works with current NM API,
closes LP: #259278
-- Jonathan Riddell [EMAIL PROTECTED] Fri, 26 Sep 2008
I found the deb for the new knetworkmanager version, but it requires a
higher version of libxi6. Is there a deb for that as well that I can
install without breaking something else?
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug
** Bug watch added: Novell/SUSE Bugzilla #423493
https://bugzilla.novell.com/show_bug.cgi?id=423493
** Also affects: knetworkmanager (openSUSE) via
https://bugzilla.novell.com/show_bug.cgi?id=423493
Importance: Unknown
Status: Unknown
--
knetworkmanager will no longer connect
** Changed in: knetworkmanager (openSUSE)
Status: Unknown = Confirmed
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.
--
From upstream:
Just submitted a new KNetworkManager to STABLE that catches up with the new NM
API. Should appear in the next 11.1 beta.
Would be nice to get this in Intrepid too.
** Changed in: knetworkmanager (openSUSE)
Bugwatch: Novell/SUSE Bugzilla #423493 = Novell/SUSE Bugzilla #429692
** Changed in: knetworkmanager (openSUSE)
Status: Unknown = In Progress
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
With the new network-manager backend that was just released
(0.7~~svn20080908t183521+eni0-0ubuntu4) I am able to connect with
knetworkmanager.(which I think hasn't been updated)
Don't know if it is a fluke or not until I get home and try connecting
again :)
--
knetworkmanager will no longer
Unfortunately it still does not work for me dmesg shows:
[ 303.527405] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command.
[ 309.469508] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a command.
[ 310.115127] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a
I just tried it and found it doesn't work. However, the GNOME
nm-applet still seems to work.
wt
On Thu, Sep 25, 2008 at 5:46 PM, savasten [EMAIL PROTECTED] wrote:
Unfortunately it still does not work for me dmesg shows:
[ 303.527405] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a
** Tags added: regression-potential
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PROTECTED]
Same problem here Version: 1:0.7svn830754-0ubuntu3
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Bug confirmed on Intrepid Ibex Alpha6, fresh install on Thinkpad T42p 2373
with Intel WLAN
KNetworkManager does timeout on wireless connection, but cable connection works.
HTH
/Lophiomys
[EMAIL PROTECTED]:~$ uname -a
Linux T42pUXGA 2.6.27-3-generic #1 SMP Wed Sep 10 16:02:00 UTC 2008 i686
You know, I see that solid has some support for network manager. Is
there just some piece of software that wasn't added to Intrepid that
uses the Solid interface?
wt
On Sat, Sep 20, 2008 at 1:10 PM, lophiomys [EMAIL PROTECTED] wrote:
Bug confirmed on Intrepid Ibex Alpha6, fresh install on
** Changed in: knetworkmanager (Ubuntu Intrepid)
Target: intrepid-alpha-5 = ubuntu-8.10-beta
--
knetworkmanager will no longer connect
https://bugs.launchpad.net/bugs/259278
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager
Tested last revision (859085, 2008-09-09) from svn, doesn't work either.
Now, the funny thing: used the gnome applet in parallel which also tries to
connect but does not work. But it seams to get a little bit further because it
tries to connect and this is also indicated through knetworkmanager
So maybe some of you should install package network-manager-gnome
logout and loginto kde and then the applet is shown and try to connect
through this if at least this works.
If I uninstall network-manager-kde and install the network-manager-gnome
all is fine. I am using the latest SVN also.
Is
On Tue, Sep 16, 2008 at 03:20:16PM -, savasten wrote:
So maybe some of you should install package network-manager-gnome
logout and loginto kde and then the applet is shown and try to connect
through this if at least this works.
If I uninstall network-manager-kde and install the
1 - 100 of 139 matches
Mail list logo
