Red Hat Bugzilla – Bug 482758
nm-applet randomly crashing when using wpa & ttls
Last modified: 2009-12-18 02:42:52 EST
Description of problem:
Same problem as the following bug except I'm using Fedora 10
nm-applet randomly crashes
Version-Release number of selected component (if applicable):
It crashes 3-5 times daily
Steps to Reproduce:
Use the wireless w/ wpa & ttls
Sometimes nm-applet will keep crashing as soon as I start it until I restart the network service.
I'll post the output from a terminal the next time it crashes.
Created attachment 330161 [details]
(nm-applet:26857): Gtk-CRITICAL **: gtk_list_store_get_value: assertion `VALID_ITER (iter, list_store)' failed
(nm-applet:26857): GLib-GObject-WARNING **: gtype.c:3940: type id `0' is invalid
(nm-applet:26857): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced
295c99b8-b771-d52c-61b86c10-550071ee is dumped
What specific version of NetworkManager RPMs? "rpm -qv NetworkManager" should tell you...
Does this happen while NetworkManager is connecting, or while it's already connected? If you re-start the applet after it has crashed (open a terminal, and type "nm-applet &", then "exit"), does the applet immediately crash again?
[djhedges@dj-laptop ~]$ rpm -qv NetworkManager
When it's already connected.
When I restart the application half the time it works.
Sometimes it crashes after it tries to connect. When this happens I restart the network service and then nm-applet and it works again.
I'm in a environment which I'm moving around a lot and roaming between access points.
I've noticed areas with a weak signal that would cause nm-applet to crash unless I moved somewhere else. It would loose signal and try to reconnect but consistently crash.
This is how I restart it, which usually fixes the problem.
su -c "service network restart && iwlist scan" && nm-applet & exit
Could you run the applet under gdb for me for a while so we can try to get a backtrace when it crashes?
a) start up a terminal
b) debuginfo-install NetworkManager-gnome
c) killall -TERM nm-applet
d) gdb /usr/bin/nm-applet
e) <wait till you get the (gdb) prompt>
f) type "continue"
Then, keep the terminal window open and wait for the applet to crash. Then when it crashes, you'll be back to the "(gdb)" prompt. Then, type "bt" to grab a backtrace, copy & paste that into a text document, and attach the backtrace to this bug. Let me know if you have any questions.
It won't start nm-applet
The program is not being run.
My fault, instead of "continue", it's "run". Sorry!
Created attachment 332237 [details]
Based on maintainer feedback, this bug has been triaged and I am setting this to assigned.
Fedora Bugzappers volunteer triage team
Is this still an issue with the latest NM update for F-10? NetworkManager-0.7.1-1.fc10 is the latest.
Can't comment on Fedora 10 but I haven't had the issue in Fedora 11. I'm not currently on my laptop so I can't look up the version I'm running but it's been stable since Beta.
Ok, then on F10 it should be fixed by this update:
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.