*** This bug is a duplicate of bug 1011127 ***
https://bugs.launchpad.net/bugs/1011127
** This bug has been marked a duplicate of bug 1011127
Unable to connect to WLAN protected with WEP by using the intel 2200bg
--
You received this bug notification because you are a member of Desktop
** Tags added: kernel-key
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/908380
Title:
[ipw2200] nm-applet crashed with SIGABRT in g_assertion_message()
Status in “linux”
Just posting to say thanks very much for the ppa! My wireless can now
recognise WPA again.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/908380
Title:
[ipw2200] nm-applet
Thanks Jools. Works now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/908380
Title:
[ipw2200] nm-applet crashed with SIGABRT in g_assertion_message()
Status in “linux”
Thank you soo much Jools! Now I don't have to use Wicd anymore, it's
working great!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/908380
Title:
[ipw2200] nm-applet crashed
note for those with the problem of not being able to connect to a wpa
network on ipw2200 - I have put some packages on my a ppa -
https://launchpad.net/~jools/+archive/ipw2200 that use wext instead of
the nl80211 interface working around the problem. Would be nice if
network manager could have a
Small update, after installing the lastest upgrades per 2012-04-03 -
straight after a clean install, this problem hit my netbook test
install. I was able to fix it by installing the network-manager-gnome
package.
Ubuntu 12.04 LTS (Precise Pangolin) Beta 2 - Desktop - AMD64
Samsung n210
Intel Atom
All that these patches do is to avoid crashing because of the ipw2200
driver not listing capabilities. Since the capabilities are listed as
not supporting WPA (or anything, for that matter), the networks are
disabled in the menu.
You may be able to connect anyway by using the connect to hidden
Sorry a misunderstanding then. When I posted in #49 I was referring
earlier to the kernel not returning correct information about the
hardware - then you referenced some patches and I assumed you meant they
were a workaround (hence the comment about not having to git bisect).
Ill debug it in the
It's a related issue. The fact that this is missing from the kernel
module triggers a crash in nm-applet. We've fixed this since it's
obviously better to avoid crashing for no reason :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I built network-manager/network-manager-gnome packages with those
patches in, and I am still unable to connect to my wpa network (my
wireless network is disabled in the menu).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
aah, a fix in nm rather than a kernel fix. I'll give it a try thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/908380
Title:
[ipw2200] nm-applet crashed with SIGABRT in
I realise that fixing it in nm is the wrong way of course. sorry for my
previous message if it sounded unappreciative. Thanks for the work with
this issue so far.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
It should be fixed this week in NM, pending a freeze exception : the fix is
already upstream.
Le 20 mars 2012 07:11, Jools Wills jo...@oxfordinspire.co.uk a écrit :
I realise that fixing it in nm is the wrong way of course. sorry for my
previous message if it sounded unappreciative. Thanks for
excellent news - do you have any reference/commit id for the fix ? saves
me git bisecting to try and locate at what point it broke, which I was
considering doing this week.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=69247a00eacd00617acbf1dfcee8497437b8ad39
http://git.gnome.org/browse/network-manager-applet/commit/?id=4e8155122a0737977d3802314e5e0009d8d0c212
--
You received this bug notification because you are a member of Desktop
Packages,
Alan, make sure you upgrade properly. Right now you have packages
installed with different versions. The fixes to NetworkManager to *avoid
crashing* with ipw2200 have landed in Precise already; so running a full
upgrade will likely fix this.
This doesn't mean that everything is fixed however;
#47:
For me, Wicd manages to connect to WPA secured networks, so either it guesses
that the device supports it or it gets the info in another way.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
since this device does support wpa, isn't a quick workaround to override
what is returned until it is fixed in the kernel ? otherwise.
Considering precise release date, this needs to be fixed else
networkmanager is useless for anyone with one of these cards.
--
You received this bug notification
I have unfortunately little faith after a major issue I reported before
natty release, which the fix was relatively simple, was never done, and
is still broken and will remain so until natty is out of support, and
then closed, yet be broken for all users who ever tried natty :/
that's completely
~$ dpkg -l | grep network-manager
ii network-manager
0.9.3.995+git201203081848.bba834f-0ubuntu1~mtrudel2 network management
framework (daemon and userspace tools)
ii network-manager-gnome
0.9.3.995+git.20120313t141231.c89224f-0ubuntu1~mtrudel1
This bug was fixed in the package network-manager -
0.9.3.995+git201203081848.bba834f-0ubuntu1
---
network-manager (0.9.3.995+git201203081848.bba834f-0ubuntu1) precise;
urgency=low
* upstream snapshot 2012-03-08 18:48:46 (GMT) (LP: #950313)
+
** Branch linked: lp:ubuntu/network-manager
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/908380
Title:
[ipw2200] nm-applet crashed with SIGABRT in g_assertion_message()
network-manager-gnome:
Installed: 0.9.2.0+git.20120126t000800.5151959-0ubuntu4
Candidate: 0.9.2.0+git.20120126t000800.5151959-0ubuntu4
Version table:
*** 0.9.2.0+git.20120126t000800.5151959-0ubuntu4 0
500 http://fi.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
100
Ignore #44 - thought I had installed the fix, but that was not the case.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/908380
Title:
[ipw2200] nm-applet crashed with SIGABRT
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/908380
Title:
[ipw2200] nm-applet crashed with SIGABRT in g_assertion_message()
Status in
Peter: Thank you the tip.
My problem still exists though, and I'm not sure if I should report another
bug.
2012/3/13 Joseph Salisbury joseph.salisb...@canonical.com
** Tags removed: kernel-key
--
You received this bug notification because you are subscribed to a
duplicate bug report
Peter,
Sorry to hear that it did not work for you. I would file another bug if I were
you.
That is the only way to have experts look at the perticular problem and solve
it before Precise hits the marked.
-- Original Message --
Received: Tue, 13 Mar 2012 05:31:37 PM CET
From: Péter
There's a bit of work that can be done at the NetworkManager level to
avoid crashing when this kind of issue happen, so I've filed the task
for this now; and there's a package I just uploaded to the ~ubuntu-
desktop PPA: network-manager 0.9.3.995+git201203081848.bba834f-
0ubuntu1~mtrudel2; which
Gracias Mathieu
I installed your update, it is not crashing and I get a prompt telling
me that the avaialble wifi network needs a password, but it does not
offer a prompt to enter a password. If I try to edit the connection, I
get a message that the editor failed to initialize, No agents were
Well, the package for nm-applet is called network-manager-gnome so you
may want to check the version for that one. Perhaps the update wasn't
ready yet as it was uploaded later than nrtwork-manager.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Sucess!
Enabling the ~ubuntu-desktop PPA, installing network-manager-gnome (and
network-manager) from there and restarting allowed me to edit the
connection and enter the WEP password. Enough of a workaround for me...
--
You received this bug notification because you are a member of Desktop
Please confirm the version for network-manager and network-manager-
gnome, and also attach a screenshot of that notification if possible.
Also, have you rebooted after updating?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I installed the previous version of network-manager and the applet does
not crash anymore, but neither will it show me any available wifi
networks. It works using a USB tethered connection to my Android.
The previous version was found in /var/cache/apt/archives/
~$ sudo dpkg -i
Alan, this bug was reported in December with a much earlier version of
NetworkManager; (network-manager
0.9.2.0+git201112151936.6b31828-0ubuntu1), so it's not likely to be a
problem tied to these versions of NetworkManager.
--
You received this bug notification because you are a member of
The problem only popped up for me after installing updates a few days
ago, which is why I tried a previous version. On that note, I spoke too
soon, the applet has now disappeared, though the USB network still
works.
--
You received this bug notification because you are a member of Desktop
Something changed now. I have latest version of Precise daily(03-12).
Now all available Wifis are shown darkgray in the applet and i cannot select
one of them.
But i can still create a Wifi connection manually with the desired SSID. After
a reboot, i get automatically connected.
--
You
Philipp: that is how it has been for me recently. it shows my wireless
but I am unable to select it. Manually creating it works. Choosing to
connect to a hidden network crashes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Jools, and so we have gone full circle. What you experience was what I
experienced after which I sent a bug report. This bug report was marked as
duplicate and merged with another one.
-- Original Message --
Received: Mon, 12 Mar 2012 09:36:37 PM CET
From: Jools Wills
Another piece of information: Network Connections crashes if I try to edit
a wireless network's config that has no wireless key set yet. I get an
error message saying:
(this is in Hungarian for me, so I'm not sure what's the original:)
Error preparing the editor
No agents were available for this
Peter, first completely (including the password) configure your hidden
wifi network connection via 'Edit Connections' in networkmanager.
Once you have done this you can connect via the commandline with: sudo
iwconfig eth1 essid 'your hidden networkname' . This assumes that the
wifi interface is
The problem seems to be in parsing passphrase.
After I've changed passphrase on m AP (by deleting double '@@' it contained)
all works as charm.
Thus my bet is that some characters in passphrase make aplet crash. Can
anyone confirm it?
Maybe this bug should be also reviewed in security
My password contains only normal small letters, so here it's not the cause
of the problem.
2012/3/11 sieciobywatel 908...@bugs.launchpad.net
The problem seems to be in parsing passphrase.
After I've changed passphrase on m AP (by deleting double '@@' it
contained) all works as charm.
Thus
#18 Péter Trombitás,
That is an excellent description of my problem as well. I've only tested
12.04 beta1 from a live USB stick, but I have never before had any
troubles with wireless in Ubuntu since I started using it in 2008. The
ipw2200 driver is used and the adapter is called eth1 but that's
This is new in Precise. Going to try the upstream kernel now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/908380
Title:
[ipw2200] nm-applet crashed with SIGABRT in
Bug is reproducible in mainline kernel (3.3.0-030300rc6-generic).
** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Desktop
Hi,
So it seems that my problem I submitted another bug about is not this problem
though it has been marked as a duplicate. I'm not 100% sure though.
I tried to connect to a secured wifi during install, and nm-applet crashed, but
that network was remembered and set to autoconnect. Every time I
Péter describes my scenario also, down to the letter.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/908380
Title:
[ipw2200] nm-applet crashed with SIGABRT in
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/908380
Title:
[ipw2200] nm-applet crashed with SIGABRT
Péter, Jayson, you'll need to check at least what wireless device is in
use on your system. That's why it's prefered to file a separate bug
report, because in case of crashes Apport will pop up and ask you to
file one -- this can then be automatically marked as a duplicate.
Otherwise, please let
Hi Mathieu,
My original but was 945311
(https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/945311)
and it was filed automatically with Apport, and was marked as a duplicate of
this bug. Is there anything else I need to do on my end in regards to my
original bug report?
Jayson, nothing more to do for that bug report, it indeed is most likely
the same issue (sound similar from the description) though there is no
crash report now since it was marked as a duplicate by Launchpad. It's
most likely correct.
Now the steps needed is to figure out why this fails. I
It's ipw2200 here, too. I'll try the older kernels tomorrow or something.
Péter
2012/3/9 Mathieu Trudel-Lapierre mathieu...@gmail.com
Jayson, nothing more to do for that bug report, it indeed is most likely
the same issue (sound similar from the description) though there is no
crash report
Marking importance as high due to the number of duplicates.
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Importance: Medium = High
** Tags added: kernel-da-key kernel-key
--
You received this bug notification because you are a member of
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/908380
Title:
[ipw2200] nm-applet crashed with
Changed to confirmed in linux because it doesn't work with the latest
kernel either (at least for me).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/908380
Title:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.3 kernel[1] (Not a kernel in the daily directory). Once you've
tested the upstream kernel, please remove the 'needs-upstream-testing'
tag(Only that
Sorry I can't test the new kernel. I am running Precise from a USB
stick.
Regards..
On 08/03/12 20:32, Joseph Salisbury wrote:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.3 kernel[1] (Not a
Can other folks affected by this bug test the upstream kernel mentioned
in comment #13
Also, did this issue also happen in prior Ubuntu releases, or is this
new in Precise(12.04)?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
59 matches
Mail list logo
