Description:
I recently updated by system and powered off. Today I rebooted to find that nm-applet wasn't starting via my .fluxbox/startup. So I tried to start it manually from command line and it gave the familiar "not allowed to own" error (as covered at http://wiki.archlinux.org/index.php/NetworkManager#Problems_starting_nm-applet_as_normal_user). It was an easy fix and I just followed the steps at that link, again. Then I thought: why am I doing this again? I check the PKGBUILD for networkmanager in the /var/abs/extra/networkmanager diretory and found that it only backs up etc/NetworkManager/nm-system-settings.conf. I assume this is related to how the *.pacnew/pacsave files are created? If so, shouldn't the networkmanager-related files in /etc/dbus-1/system.d/ also be backed up? Especially since overwriting these by upgrading wipes out potentially modified config files and kills nm-applet?

Of course, my own little workaround for now is to just keep the additions suggested at http://wiki.archlinux.org/index.php/NetworkManager#Problems_starting_nm-applet_as_normal_user in separate adjacent files, so the next time networkmanager updates, I can simply add the necessary lines back into the overwritten config files.

Additional info:
* package version: 0.8.1
* config and/or log files:
/etc/dbus-1/system.d/NetworkManager.conf
/etc/dbus-1/system.d/nm-applet.conf

Steps to reproduce:
pacman -Syu