解决ERROR:dbus.proxies:Introspect error on :1.65:/org/freedesktop/PackageKit: dbus.exceptions.

最新推荐文章于 2025-06-26 09:07:24 发布
最新推荐文章于 2025-06-26 09:07:24 发布
阅读量5.4k 收藏
点赞数
CC 4.0 BY-SA版权
分类专栏： 随笔 文章标签： yum
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/weixin_37968633/article/details/75635196
本文介绍了在使用yum安装pcre和pcre-devel时遇到的ERROR:dbus.proxies:Introspect错误。解决方案是检查依赖性，若非必需可删除该包，从而解决问题。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

yum安装yum install -y pcre pcre-devel时报错

ERROR:dbus.proxies:Introspect error on :1.65:/org/freedesktop/PackageKit: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

解决办法：
首先我们这个包:

#命令
rpm -qa | grep Package

#查看结果
PackageKit-glib-0.5.8-13.el6.i686
PackageKit-yum-plugin-0.5.8-13.el6.i686
PackageKit-yum-0.5.8-13.el6.i686
PackageKit-0.5.8-13.el6.i686
PackageKit-glib-devel-0.5.8-13.el6.i686
PackageKit-gtk-module-0.5.8-13.el6.i686
PackageKit-device-rebind-0.5.8-13.el6.i686

可以看到这组包依赖性很小,所以我们应该如果不需要可以删除它。

yum remove PackageKit*

然后就ok了

firewalld dbus接口使用指南
期待幸福
10-10 1044
firewalld，一个基于动态区的iptables/nftables守护程序，自2009年左右开始开发，最新版本 - 防火墙0.6.3 - 发布于2018年10月11日。主要的开发人员是托马斯·沃纳，他目前为红帽公司工作。这是因为费多拉 18 的默认防火墙机制， 随后在 Rhel7 和 Centos 7 中。 防火墙比旧的 iptable 机制有许多优势。值得注意的是，它解决了 iptable 要求每次更改时重新启动防火墙的问题，从而中断了任何状态连接。它还提供了丰富的深思熟虑的 D-Bus 方法、信号和
NetworkManager：freedesktop.org信息库的只读镜像。 请针对freedesktop.org提出拉取请求
02-22
NetworkManager是Linux操作系统中用于管理网络连接的重要工具，它由freedesktop.org社区开发并维护。这个项目的主要目标是提供一个统一、用户友好的接口来处理各种网络连接，包括有线、无线、移动宽带等。在Linux...
YUM安装报错：ERROR:dbus.proxies
weixin_34356555的博客
10-24 313
问题：使用yum install somexx -y的时候，执行到Installed products updated.报如下错误：ERROR:dbus.proxies:Introspect error on :1.261:/org/freedesktop/PackageKit: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.N...
Waydroid项目常见问题：DBus会话启动错误分析与解决
最新发布
gitblog_07022的博客
06-26 441
Waydroid项目常见问题：DBus会话启动错误分析与解决 问题现象 在使用Waydroid项目时，用户执行waydroid session start命令后出现DBus相关的错误提示："ERROR: org.freedesktop.DBus.Error.NoReply: Did not receive a reply"。错误信息表明DBus会话总线未能正常响应，导致Wayd...
【问题】yum安装软件报错ERROR:dbus.proxies
weixin_34037515的博客
08-22 679
转自：Yum安装报错:ERROR:dbus.proxies 环境： [红帽企业Linux.6.4.服务器版].rhel-server-6.4-x86_64-dvd(ED2000.COM).iso 安装时选用Software Development Workstation 问题描述： yum安装DHCP服务时输出 [root@localhost yum.repos.d]# y...
The name org.freedesktop.PackageKit was not provided by any .service files
bianhuaHYQ的博客
03-19 783
【代码】【无标题】
记录一次Linux Firewalld防火墙故障排查的案例Error：Action org.fedoraproject.FirewallD1.config.info is not registered
热门推荐
watermelonbig的专栏
04-26 1万+
1、故障现象在一个生产服务器上，系统为CentOS7.3，防火墙使用的是系统默认的firewalld。偶然发现，在执行以下防火墙管理命令时，报错如下：# firewall-cmd --list-allError: Action org.fedoraproject.FirewallD1.config.info is not registered虽然查看防火墙配置规则列表的命令报错了，但其它的规则配置...
dbus-java:freedesktop.org提供的Java DBus库的改进版本（https
05-02
dbus-java 的改进版本，与Java 8兼容。... 将DBus界面从org.freedesktop移至org.freedesktop.dbus.interfaces 模块化dbus-java（ ，感谢 ） 如果建立DBus连接出错，则DBusConnection.getConnection（DBusBusTy
运行后出现如下错误：GDBus.Error:org.freedesktop.DBus.Error.UnknownInterface: No such interface 'com.deepin.filemanager.filedialog' at object path '/com/deepin/filemanager/filedialog'
06-12
他们提到了错误：`Exec=/home/%u/create_date_folder.sh%U`无法传递参数，并且在尝试使用DBus时出现错误：`GDBus.Error:org.freedesktop.DBus.Error.UnknownInterface'com.deepin.filemanager.filedialog'`。...
(.venv) root@lujh:/xhs-toolkit# /usr/bin/google-chrome [5740:5761:0625/221740.246042:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5761:0625/221740.248003:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5761:0625/221740.249531:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5761:0625/221740.250569:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5761:0625/221740.370044:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5761:0625/221740.415397:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5758:0625/221740.478293:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5761:0625/221740.523936:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5761:0625/221740.524261:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5740:0625/221740.648013:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [5740:5740:0625/221740.648556:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [5740:5761:0625/221740.649404:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5740:0625/221740.651613:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [5740:5740:0625/221740.666140:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [5740:5781:0625/221740.667402:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5740:0625/221740.691384:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [5740:5740:0625/221740.694212:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [5740:5777:0625/221740.695388:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5740:0625/221740.708898:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [5740:5778:0625/221740.709739:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5740:0625/221740.717343:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: [5740:5778:0625/221740.718130:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [5740:5740:0625/221740.725801:ERROR:dbus/object_proxy.cc:590] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: WARNING: All log messages before absl::InitializeLog() is called are written to STDERR I0000 00:00:1750861062.663657 5758 voice_transcription.cc:58] Registering VoiceTranscriptionCapability [5740:5740:0625/221806.050232:ERROR:chrome/browser/ui/webui/new_tab_page/new_tab_page_handler.cc:1353] NewTabPage loaded into a non-browser-tab context
06-26
在启动容器时，可能需要挂载/run/dbus目录，例如：```bashdockerrun-it--rm-v/tmp/.X11-unix:/tmp/.X11-unix-v/run/dbus:/run/dbus--namechromegoogle-chrome```如果上述步骤不能解决问题，可能需要考虑重新安装...
Ubuntu下关于Warning DBuserror.org.freedesktop.DBUS.Error.NoReply的解决方法
anranbing3284的博客
03-27 3556
在VM下一直用Ubuntu用得好好的，可是很久没有用之后发现不能访问Windows共享了，重装了N次也不行，在网上查资料，只说是samba的安装有问题，按照很多资料所说的安装了samba，samba-common和samba-client还是失败，郁闷了几天。 不过用访问Windows共享的方法时会反馈一个错误，Warning DBuserror.org.freedesktop.DBU...
Linux执行防火墙命令报错或者失效
hgx455的博客
02-09 4673
在执行firewall-cmd相关命令时报错，例如执行firewall-cmd --state 查看状态时无法查看。此时应该重新安装dbus包，执行yum install dbus 或者yum update dbus。再次执行firewall-cmd --state发现配置命令已经可以正常使用。然重新启动dbus,执行systemctl restart dbus。在系统重启以及升级firewalld版本后发现问题依旧存在。根据报错，怀疑dbus包存在问题。
Linux CentOS7 防火墙及常用端口
qq_14931217的博客
03-15 796
可能是由于dbus包存在问题，可以使用yum install dbus或者yum update dbus进行下载和更新dbus包。更新之后，使用systemctl restart dbus重启dbus。
Linux系统firewalld防火墙的应用实操（禁止屏蔽海外国外IP访问）
08-16 9274
Linux系统firewalld防火墙的应用实操（禁止屏蔽海外国外IP访问）
linux启动守护进程失败,Ubuntu Linux设置守护进程时出错的解决
weixin_39554290的博客
04-29 1176
Ubuntu系统使用源从7.10升级到8.04后，启动并在用户登录后，界面无响应5分钟左右后，弹出出错信息：启动GNOME设置守护进程时出错主题、声音或者背景设置等可能不会正常工作。最后的错误信息是：Did not receive a reply. Possible causes include: the remote application did not send a reply, the m...
linux dbus安装卸载,Linux安装yum时提示ERROR:dbus错误如何解决？
weixin_39896617的博客
05-09 1060
Linux系统操作中，yum源安装的时候提示ERROR:dbus错误，很多人遇到这个问题就不知道要如何处理了，其实解决的方法很简单，下面小编就给大家介绍下Linux安装yum时报错ERROR:dbus的解决方法，一起来学习下吧。问题：使用yum install somexx -y的时候，执行到Installed products updated.报如下错误：ERROR:dbus.proxies:I...
CentOS下使用yum命令安装计划任务程序crontab
无知人生，记录点滴
09-28 1万+
概述利用“任务计划”，可以将任何脚本、程序或文档安排在某个最方便的时间运行。通俗的讲就是定时执行某个脚本、程序。常见用途定时关机 定时检查更新 定时对系统配置、数据库、日志进行备份 定时清理垃圾文件检测是否已安装# crontab -bash: crontab: command not found执行 crontab 命令如果报 command not found，就表明没有安装.开始安装#
Error org.freedesktop.DBus.Error.AccessDenied: Sender is not authorized to send message
04-04
好的，我现在需要处理用户提出的关于“Error org.freedesktop.DBus.Error.AccessDenied: Sender is not authorized to send message”的问题。用户之前询问过类似的D-Bus错误，所以可能需要延续之前的解决方案，但...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值