startup fails - nm-applet cannot find some required resources

[Nikolaus Rath]

I just installed network-manager and network-manager-gnome. Unfortunately I'm not able to do anything with them. There's no new entry in the System menu, no new applet in the "add to panel" dialog and starting nm-applet from the commandline results in an error message "nm-applet cannot find some required ressources".

[diegoe (diegoe-deactivatedaccount-deactivatedaccount)]

This might be already solved. There were issues with dh_iconcache.
You might also been suffering https://launchpad.net/distros/ubuntu/+source/network-manager/+bug/5364

[Nikolaus Rath (nikratio)]

I just upgraded the whole system and the problem still persists. I also tried starting with --sm-disable as it was mentioned in the other bug. Apart from that, I didn't notice any connection between the bugs..

[Jun Kobayashi (jkbys)]

Same problem occured. I just installed Dapper with daily-live 20060522.2 iso image, and apt-get update, dist-upgrade, and install "Network Manager" with "Add/Remove Applications".

An error dialog with message "The NetworkManager applet could not find some required resources. It cannot continue." appeared when nm-applet is launched.

I think nm-applet might not be able to find essential icons.

The following is console output:

** (nm-applet:27645): WARNING **: Icon nm-vpn-lock missing: Icon 'nm-vpn-lock' not present in theme

(nm-applet:27645): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(nm-applet:27645): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(nm-applet:27645): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(same line printed 53 times)

[Jun Kobayashi (jkbys)]

Strange to say, no problem occures on another PC which has ran dapper for about 2 months.
This might be because this PC has icon cache for nm-applet.

[Jun Kobayashi (jkbys)]

This problem is same as Bug #37128, and can be fixed with the following command:
  gtk-update-icon-cache -f /usr/share/icons/hicolor/

It seems that this command is launched in postinst script, but it had no effect on my PC.

[Sebastian Breier (tomcat42)]

I can confirm this on a completely fresh dapper RC install.

[Tom (tom-ranson)]

Just did a fresh install of Dapper RC 1 and I had the same issue with Network Manager after installing:

network-manager
network-manager-gnome

I can also confirm that

gtk-update-icon-cache -f /usr/share/icons/hicolor/

fixes this issue.

[Tom Taylor (scraplab)]

I just did an install of Dapper Final, and this problem still persists. The solution above fixes it however.

[Ante Karamatić (ivoks)]

Could you paste output of:

grep DefaultDepth /etc/X11/xorg.conf

[Tom Taylor (scraplab)]

tom@tom-laptop:~$ grep DefaultDepth /etc/X11/xorg.conf
        DefaultDepth 24

[Nikolaus Rath (nikratio)]

[0] nokile:~$ grep DefaultDepth /etc/X11/xorg.conf
        DefaultDepth 24

[Aaron Whitehouse (aaron-whitehouse)]

I just installed Dapper Final and have this problem. I had this issue with the RC as well. See Bug #6473.

[Aaron Whitehouse (aaron-whitehouse)]

I just uninstalled the package, disabled the CD as a repo, reinstalled the package from the server (apparently the same version) and now it seems to work.

[Sebastian Breier (tomcat42)]

Afaik, nobody who had nm installed before had this particular problem; You uninstalled it, then reinstalled it, so the icon cache was most probably still up-to-date and so nm worked right away.

[Aaron Whitehouse (aaron-whitehouse)]

Hi Sebastian,
I'm not 100% sure what you mean. It wasn't working on this machine (implying that the icon cache wasn't okay) and uninstalling and reinstalling from the repo fixed it.

[Sebastian Breier (tomcat42)]

Ah, alright... :)
I thought you had installed it, then fixed the icon cache, then reinstalled it. In that case it would have worked anyway.
Sorry for the misunderstanding. ;)

[Aaron Whitehouse (aaron-whitehouse)]

No problem :). I thought that may have been the case.

[Sebastian Breier (tomcat42)]

This got fixed for dapper, but now exists in edgy. I just installed nm on a fresh edgy knot-3 install, and it had exactly the same error. I suggest the same fix should be applied again.

[Sebastian Breier (tomcat42)]

The manual fix for dapper (gtk-update-icon-cache -f /usr/share/icons/hicolor/) works in edgy as well, just tried it. :)

[zdzichu (zdzichu-gmail)]

I've reported duplicate bug about this issue in 6.10 beta and was asked for more information.
I can only add that I'm using Tango icon theme, not Human.

[Andy Lee (andy-andylee)]

I've come across this bug in both 6.06 and 6.06.1 - I'm going to try Edgy Beta now... but I'm guessing from the posts above that nm-applet is going to have issues again.

[Xirtam (xirtam1985)]

I can confirm the bug with current egdy + all updates.

[Aaron Whitehouse (aaron-whitehouse)]

+1 for this bug occurring on Edgy RC and +1 for

sudo gtk-update-icon-cache -f /usr/share/icons/hicolor/

fixing it.

[Aaron Whitehouse (aaron-whitehouse)]

If it helps, I have installed knot 1, 2, 3, Beta and the RC from CD and only had this bug on the RC. I don't know if that means that it is a regression or (what seems more likely) just chance.

[Xirtam (xirtam1985)]

I'm disappointed :(
The bug still exists in edgy final...

[Aaron Whitehouse (aaron-whitehouse)]

+1 for this bug being in Edgy Final. The fix works.

[Aaron Whitehouse (aaron-whitehouse)]

It looks to me as though Bug #45609 and Bug #6473 are duplicates of Bug #37128.