Bugzilla – Bug 134829
NetworkManager shows 'disconnected' icon when connected
Last modified: 2006-01-24 19:45:47 UTC
I'm currently on a wireless network managed by Network Manager. The network status on the main menu corretly shows my state. Howerver the NM tray icon is the plug with the red line through it. It should instead be the blue bars of signal strength. I'm not sure what caused the icon to go bad. I have done a couple of suspends. It could be related to that.
*** Bug 136029 has been marked as a duplicate of this bug. ***
*** Bug 137403 has been marked as a duplicate of this bug. ***
I have just reproduced with resuming after suspend instead of booting. After the resume I usualy (not allways though) issue `/etc/init.d/networkmanager restart', this time the applet shows disconnected even the card is set up and working.
You should not need to restart NM with more recent powersave daemons, which run a script that sends a DBUS signal to NM, notifying it of the suspend/resume (to which it responds appropriately). Also, can everyone experiencing this bug please see if you can reproduce it with NM 0.5.1cvs20051208? Particularly, I am interested (right now) if you see the problem on boot still.
Happened again with 0.5.1cvs20051209-2 after reboot, then after resume the icon was right.
Noted. Thank you.
*** Bug 138056 has been marked as a duplicate of this bug. ***
I hate this bug with the passion of one thousand fires.
Heh - of course, the suspemd/resume stuff is also particularly flakey wrt. VPNs - which (it seems) inevitably flake / need re-starting when you resume - but perhaps I'm confused /me uses only SL10.0 as yet.
People who see this all of the time (Bart, et al): Once 0.5.1cvs20060112 pops out of autobuild, can you confirm if this is still an issue and still an issue as often? Thanks!
Ping, ping, ping! Any luck? Are we riding high and fast with the latest versions? 0.5.1cvs20060117 is newest and I bet my pet cat this bug is fixed. Confirm or refute?
My cat is well groomed and knows several tricks. Her four main tricks include: - Consistently uses a litter box - Very good at chasing a ball of yarn - Seductive meow - Can fly and see through walls The cat is yours if you can reproduce this bug on 0.5.1cvs20060118. If you cannot -- well, then -- I think this bad boy is fixed!
Robert, could you clarify that last trick? I'm not sure whether to read it as "can fly / see through walls" or "can fly through walls / see through walls".
Mr. teichmann wants to know if the cat can: - fly through walls "cause that is [cobe]ing impressive"
Indeed, that trick was written with a bit of ambiguity. The cat possesses two separate powers: the gift of flight and the gift of seeing through walls. To be clear, the cat cannot fly through walls. At least not without a weak wall, a good tailwind, and plenty of room to accelerate. Make no mistake, this is one special cat. Kelli Frame The Cat, her full name, can be yours if you can reproduce this bug!
This isn't an easy thing to test, at least not until beta1 is ready. The new NetworkManager-gnome needs libexpat.so.1. libexpat.so.0 is present on the system. If I try to upgrade expat there are about 100 things on the system that need the old expat.
The magical-cat release: http://primates.ximian.com/~rml/misc/ Rebuilt against libexpat.so.0.
Due to a legal injunction and name dispute brought on by a party who shall remain nameless, the cat has been renamed to Kelly Phraigm. Nonetheless, the offer still stands: the cat is yours if you can reproduce the bug.
Do I get Kelly Phraigm if the magic-cat release crashes, or refuses to start? That's what I'm seeing.
What exactly is happening? Is this the applet or the daemon? If the former, is the latter running? The initscripts changed. You need an updated sysconfig package and NETWORKMANAGER=yes in /etc/sysconfig/network/config (I don't know how recent your setup is). You can just run the daemon manually, too. And, no, you don't get the cat (yet)!
(In reply to comment #16) > This isn't an easy thing to test, at least not until beta1 is ready. > The new NetworkManager-gnome needs libexpat.so.1. libexpat.so.0 is present on > the system. If I try to upgrade expat there are about 100 things on the system > that need the old expat. You can just install the new expat instead of upgrade (rpm -ivh instead of -Uvh)
--forcing all the file conflicts won't break anything? (expat)
As long as you keep both (-i not -U), it is fine. You just need the --force because some files overlap. I would make sure to install the newer expat second, so you get its headers and such.
Well - (un)fortunately - this now works perfectly for me in B1 - however, I suspect this is because the relevant driver was updated so it correctly senses whether the cable is connected; rather than testing the case where that data in not present (or perhaps I'm smoking crack ;-)
Meeks - this bug was caused by a race internal to nm-applet, not faulty carrier detection code (although you could have been seeing another bug). So if you never see the wrong icon now, everything should be fixed. I'm going to let Bart be the final arbitrator of the bug, though.
Meow, hello Bart, my name is Kelly Phraigm The Cat. I have a vert soft coat of fur and have been declawed. I can fly and see through wood. I also love to have my belly scratched. My mother was a tabby and my father was siamese. This gives me several favorable cat traits. I always use my litter box. I prefer hand-fileted tuna steaks cooked to rare and covered in a red wine demiglase. I don't like hot milk. I prefer Fifi-brand water in my water dish. If possible, the dish should be made of gold. I do not have rabbies. I like to watch Oprah, so please leave the TV on during the day. Meow, I can be yours if you can reproduce this bug!
someone can reopen it if it's not fixed.
Created attachment 64845 [details] screenshot of broken NM in main menu. Same bug or different bug?
Ahh, look how bad you want the cat! ;-) Different bug, unrelated -- and the gnome-main-menu guys are aware.