nm-applet confused by icon name changes during hardy-intrepid upgrade
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager-applet (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bug Description
Binary package hint: network-
It seems that nm-applet can get confused when its icons disappear
during an upgrade. This happened while testing an upgrade from
Xubuntu hardy to intrepid beta candidate ISO, but is probably not
restricted to Xubuntu.
The problem: during the upgrade, nm-applet put up a number of error
dialogs complaining that it could not access some of its necessary
resources. Everything seemed to work, otherwise.
The diagnosis: some icons have changed names from the hardy version
to the intrepid version. While the system upgrade was running, it
unpacked the new version of nm-applet, removing the old files, and
as a result the old icons went away. Result: nm-applet complains.
It seems that this would not have happened if I had not started
the upgrade pretty much immediately after logging in. If I had used
the system first for a while, I might have triggered nm-applet to
load the old icon already, and so nothing would have been a problem.
The problematic icons are nm-vpn-lock and nm-device-
The IRC discussion:
<liw> asac, when testing an upgrade of xubuntu from hardy to intrepid, I
get (at least) four windows saying "The NetworkManager applet could not
find some required resources. It cannot continue". (Make that five,
another popped up just now)
<liw> asac, does that sound familiar?
<asac> liw: you tried to manually restart things? or did you reboot?
<liw> asac, the ugprade is still running (six windows now)
<liw> asac, I haven't touched anything, except to move the windows so I
can count them (seven)
<asac> liw: so was NM already unpacked?
<liw> asac, how do you mean? it was running in the system from which I
started the upgrade
<liw> asac, this is under kvm, if that matters (though it shouldn't)
<asac> liw: what i wonder about is whether this happens before or after
the NM bits have been unpacked during upgrade
<liw> asac, hmm, I don't think I can figure that out anymore
<liw> asac, unless there's some log file I can grep for you
<liw> asac, this is a guess, but based on the timestamps in dpkg.log, I
would guess the problems started happening approximately when
network-
but my internal clock would indicate it is
<asac> liw: ok. strange that it happens in xubuntu.
<asac> liw: did the upgrade restart dbus or something?
<asac> liw: ok that error message comes from 0.7 applet
<asac> liw: this means that you restarted the applet
<asac> (if not you something else restarted it)
<asac> which must not happen
<asac> liw: maybe the xubuntu xsession does some magic to restart binaries?
<liw> asac, I don't know what xubuntu does, I just test this :)
<asac> cody-somerville: ^^
<cody-somerville> We don't do any magic
<asac> liw: can you see when the nm-applet process was started?
<liw> asac, long before the problems
<asac> liw: question is if it was started long before the unpack :)
<liw> (ps says it was started 14:26, problems started around 15:00)
<liw> unpack also approximately at 15:00
<asac> liw: so 14:26 is about the time you logged into xubuntu?
<liw> asac, yeah
<asac> liw: and you did nothing? e.g. not even tried to start the connection editor or something?
<liw> asac, nope, I only ran the upgrade command
<liw> (sudo update-manager -d -c)
<asac> mvo: does update-manager try to restart things?
<mvo> asac: restart what? firefox?
<asac> mvo: no restart nm-applet (which usually gets auto started by the
session)
<mvo> asac: no, it can't because the actual installation runs as root
<asac> mvo: myterious then. liw logged into xubuntu. ran upgrade and
without doing anything suddenly sees applet error dialogs from 0.7
<mvo> asac: however it seems that network manager kills the network when
it gets upgraded sometimes (or all th time?)
<asac> mvo: thats not done anymore
<asac> mvo: dbus restart could cause something though
<asac> but i dont see how it can restart the applet :(
<mvo> asac: we don't do that
<mvo> asac: it might be that the applet probably restarts itself (or
gets restarted by something like the session) because it crashes when
the new n-m gets installed
<liw> asac, if the applet has been running since I logged in and before
I started the upgrade, did it really get upgraded?
<asac> liw: yeah.
<asac> liw: my grep was bogus ... 0.6.6 applet will complain like that
too in some cases
<asac> liw: do you see if NM restarted was restarted?
<asac> (the daemon)
<liw> asac, it has also been running since 14:26, i.e., hasn't been
restarted, as far as I can see
<asac> liw: ok looks like it happens if NM tries to use icons that it
didnt use previously
<asac> liw: so most likely would just be the case if you have more or
less a fresh started session
<liw> asac, ok, that sounds reasonable; shall I continue with the
upgrade, then, or do you want me to grep for something more? also,
should I file a bug?
<asac> liw: you could strace -eopen -p PID
<asac> and tell me which file it tries to open when it complains
<liw> asac, the applet?
<asac> yeah
<asac> liw: we could consider to create compatibility links ... and then
see what other resources nm-applet would complain when the icons are
still available
<asac> maybe there would be a missing .glade resource too ... which
would be harder to fix
<liw> asac, I can't seem to be able to trigger the applet to open the
icon anymore, hmm
<liw> ah, no, got it now
<liw> asac, it's (at least)
/usr/share/
<liw> asac, though both now succeed, hmm
<asac> yeah those are not NM icons
<asac> liw: http://
<asac> those are the ones i suspect to be missing
<asac> liw: seems like the only one missing is vpn-lock
<asac> can you confirm that?
<asac> yeah thats vpn-active-lock now from what i can see
<liw> there is no file matching vpn-lock* under /usr/share/icons
<asac> liw: right
<asac> thats gone ... and thats why you get this
<asac> ln -s /usr/share/
/usr/share/
<asac> might be what we want
<liw> in fact, no icon matching vpn*
<liw> oh, nm-vpn*
<asac> liw: dpkg -L network-
<asac> liw: i will ask NM folks why that icon was renamed ;)
<asac> liw: everyother icon is there right?
<liw> asac, nm-device-
| Adam Portier (aportier) wrote | #1 |
| Changed in network-manager-applet: | |
| status: | New → Incomplete |
| to be removed (liw) wrote | #2 |
| Changed in network-manager-applet: | |
| status: | Incomplete → New |
| Jacqui (jacqui-russell) wrote | #3 |
| Changed in network-manager-applet: | |
| importance: | Undecided → High |
| milestone: | none → ubuntu-8.10 |
| status: | New → Triaged |
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in network-manager-applet: | |
| status: | Triaged → Fix Released |
| Alexander Sack (asac) wrote | #5 |
| to be removed (liw) wrote | #6 |
| Jamie Lokier (jamie-shareable) wrote | #7 |
| Jamie Lokier (jamie-shareable) wrote | #8 |
| Alexander Sack (asac) wrote Re: [Bug 277084] Re: nm-applet confused by icon name changes during hardy-intrepid upgrade | #9 |
| keneida (keneida) wrote | #10 |
| Jojo (kuzniarpawel) wrote | #11 |
| Jojo (kuzniarpawel) wrote | #12 |
| G J (g-jarnot) wrote | #13 |
| Alexander Sack (asac) wrote | #14 |
| Germán Poo-Caamaño (gpoo) wrote | #15 |
| Alexander Sack (asac) wrote | #16 |
| nick (swcodfather) wrote | #17 |
| tags: | added: iso-testing |
Hi, before I can move this up the pipeline, I need to get some more information so that the bug team can reproduce what happened. Do you have any logs from the install that you could put in this report. Also, what version of nm-applet does apt/Synaptic say you have?