修了三天了，绝了
我看我就是没有缘分和智力，还是趁早转行当厨子吧
当个厨子每天至少还能给自己烧份热饭，不用坐在宿舍等冷炒饭
不BB了
这次不作死从外部安装了，老老实实从商店装
10kb/s我也忍了，球球你让我进环境吧
我tm
这又是什么
org.freedesktop.PolicyKit.Error.NotAuthorized: ('system-bus-name', {'name': ':1.100'}): org.debian.apt.install-or-remove-packages
我怎么就没有权限了
不气不气不气
网上给的答案先试试
在图形界面安装或执行一些操作时需要用到root权限，然而这时权限窗口出现闪退的情况，提示错误为：
org.freedesktop.PolicyKit.Error.NotAuthorized: (‘system-bus-name’, {‘name’: ‘:1.159’}): org.debian.apt.install-or-remove-packages
这时只需要安装
sudo apt-get install policykit-1 policykit-1-gnome
就可以看到认证窗口了。正在读取软件包列表... 完成
正在分析软件包的依赖关系树
正在读取状态信息... 完成
policykit-1 已经是最新版 (0.105-14.1)。
policykit-1 已设置为手动安装。
policykit-1-gnome 已经是最新版 (0.105-2ubuntu2)。
policykit-1-gnome 已设置为手动安装。
下列软件包是自动安装的并且现在不需要了：
libllvm3.8 libpango1.0-0 libpangox-1.0-0 libqmi-glib1 ubuntu-core-launcher
使用'sudo apt autoremove'来卸载它(它们)。
升级了 0 个软件包，新安装了 0 个软件包，要卸载 0 个软件包，有 0 个软件包未被升级。没吊用啊
重启以后vmtool又挂了
遇到您没有权限执行此操作的问题
终于解决了
重装没用但是我在这里留个底
sudo apt-get update && sudo apt-get install policykit-1 policykit-1-gnome解决的方法是：
gksu software-center完整文章：
================================
This instance of the problem might be caused by a bug; I recommend considering reporting this as a bug in PolicyKit.
However, this problem can occur with or without a bug, for example, as a consequence of manual PolicyKit configuration changes (or deinstallation). Therefore, it merits an answer here.
This is happening because the PolicyKit service is not running. Here's a couple ways to fix this:
Make sure the necessary PolicyKit packages are installed.
Open a Terminal (Ctrl+Alt+T) and run:
sudo apt-get update && sudo apt-get install policykit-1 policykit-1-gnome
Then reboot and see if the problem is fixed. (Logging out and back in might fix the problem too.)
Run the Software Center with gksu/gksudo instead of PolicyKit.
If that doesn't work, you can still run the Software Center by working around the problem. PolicyKit is one way an authorized user (typically an administrator) can perform actions as root in a typically configured Ubuntu system, but it is not the only way. sudo is the other.
For graphical programs, running them with sudo directly often will work (as in Thomas's answer). But it is not recommended, primarily because it can cause the non-root user's configuration files to become owned by root.
- For graphical programs that don't store configuration files in a user's home directory, this doesn't matter. But most do, and the Software Center is no exception. (It uses
~/.config/software-center, where~is your home directory.)
So it's recommended to use a non-graphical frontend instead: gksu/gksudo, or (if you're running Kubuntu) kdesudo.
So, press Alt+F2 and run:
gksu software-center
(This works in all desktop environments, not just Unity, though of course it looks different in others.)
Then you'll be prompted for your password. Enter it, and the Software Center will run as root.
Please note that this is a little different from the way Software Center usually runs. Ordinarily, it runs as a normal user, and uses PolicyKit to perform actions as root just when it is needed. It would be non-trivial to get it to use gksu/gksudo or kdesudo to do that.
But running it as root typically works fine and causes no problems.
Other graphical utilities can be run as root with graphical sudo frontends, too.
The problem itself doesn't appear related specifically to the Software Center--any program that uses PolicyKit will fail. Some, like users-admin, cannot be run successfully as root. But most can. Here's how to do it, for some of the commonly used utilities:
Software Sources —
gksu software-properties-gtk
(In Kubuntu:kdesudo software-propertiies-kde)Software Updater (called Update Manager before 12.10) —
gksu update-manager
(If you just want to install updates normally, though, you may be able to do that without becoming root at all, as there is a separate service that allows this.)System Settings... —
gksu gnome-control-center