similar to: race conditions in dbus-1.2

Hi, since quite some time I encounter a problem which I believe is in the dbus plugin: Sometimes when I load or unload plugins by changing the configuration, all settings of all plugins are reset. At the same time, the following message appears multiple times in the terminal I started Compiz from (which makes me believe the problem is in the dbus plugin): A handler is already registered for the

What is this all about? Seems to be related to my attempt to load hplip-3.10.9 to support an HP Photosmart 3210 all-in-one for scanning through saned. from /var/log/messages: Jan 31 20:07:26 desk python: [2851]: error: dbus failed to load (python-dbus ver. 0.80+ required). Exiting... Jan 31 20:07:49 desk python: hp-systray[3402]: warning: Qt/PyQt 4 initialization failed. When I check for

For what its worth, I managed to get around the problem with a small patch on yum itself: --- ORIG/usr/lib/python2.6/site-packages/yum/yumRepo.py 2017-03-22 05:32:26.000000000 +0000 +++ NEW/usr/lib/python2.6/site-packages/yum/yumRepo.py 2018-02-14 09:14:04.879902463 +0000 @@ -863,6 +863,7 @@ class YumRepository(Repository, config.R text=text,

On 03/01/18 15:45, Danny Smit wrote: > Hi everyone, > > On CentOS 7 I'm running into an issue with the latest nvidia driver > from elrepo: kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 > This driver version seem to introduce issue in detecting video modes > when a monitor is connected using DVI. As soon as the machine attempts > to start X, nothing happens and the monitor goes

Hi, how can I enable a plugin from the command line? I know how to *activate* it from dbus, i.e. do the equivalent of pressing "Ctrl-F9" or whatever the hotkey is. But I don't know how to *enable* it, i.e. do the equivalent of clicking the "enabled" checkbox in compizconfig settings manager. Thanks! Carlo

On 06/01/18 12:00, Zube wrote: > On Sat Jan 06 12:27:22 PM, Danny Smit wrote: > >> I normally certainly prefer the stability of the long-lived releases. >> I noticed an update was just released of the long-lived release: >> 384.111. The notes for this release say: >> >> Fixed a regression that prevented displays connected via some >> types

I have installed 1.12.8-10.el8_2, but when trying to install dbus-devel it is not available for that version, only 1.12.8-9.el8, which is also not available. Suggestions? # yum list | grep dbus dbus.x86_64 1:1.12.8-10.el8_2 @BaseOS dbus-common.noarch 1:1.12.8-10.el8_2

Hi folks, after upgrading a Centos container (LXC) from 7.4 to 7.5 I got this: # systemctl status Failed to get D-Bus connection: Connection refused # busctl Failed to connect to bus: Connection refused # ps -ef | grep db[u]s dbus 55 1 0 Jul02 ? 00:00:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation # lsof -p 55 COMMAND PID

The big update caused one of the rare re-starts on my mail server, so I saw the startup messages that I had forgotten about. Oct 28 10:50:04 borg2 python: [3424]: warning: python-dbus not installed. Oct 28 10:50:04 borg2 python: hp-systray[3424]: warning: Qt/PyQt 4 initialization failed. Oct 28 10:50:04 borg2 python: hp-systray[3424]: error: hp-systray requires Qt4 GUI and DBus support.

When I trying to update 4.3 to 4.4 it fails updating dbus-glib because it couldn't remove dbus 0.22.12.EL.5 [root at prototipo ~]# yum update Setting up Update Process Setting up repositories update 100% |=========================| 951 B 00:00 base 100% |=========================| 1.1 kB 00:00 addons 100%

CentOS Errata and Security Advisory 2012:1261 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-1261.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: e7122caa753db24dfea9a7ecb266b6d5db218c5e340994115947fc8f6d4da5db dbus-1.2.24-7.el6_3.i686.rpm

CentOS Errata and Bugfix Advisory 2015:0871 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0871.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 154884ae0ff5a4a9ed7aff22f58bb5539f932f18ca469890a30193e10e21da45 dbus-1.2.24-8.el6_6.i686.rpm 1032a57d04f2f53d29f758562d5a58490ca395fdfa59b96d4a8845becbe9c601

CentOS Errata and Security Advisory 2019:1726 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:1726 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f5bb925a65b0e4ba5c51e2b6a76665c28a71af9a831fd613769643ea3a5b6516 dbus-1.2.24-11.el6_10.i686.rpm

On Dec 17, 2016, at 9:23 AM, geo.inbox.ignored <geo.inbox.ignored at gmail.com> wrote: > what i am now in wonder of is if there is any differance in file > between the 2 computers. > > ie, is there a differance between a 32 bit and 64 bit system's > /.dbus/sessions-bus/* file? > > as said, a web search nor reading thru pages, ie, faq, help, doc > pages at

CentOS Errata and Security Advisory 2007:0008 https://rhn.redhat.com/errata/RHSA-2007-0008.html The following updated files have been uploaded and are currently syncing to the mirrors: s390: updates/s390/RPMS/dbus-0.22-12.EL.8.s390.rpm updates/s390/RPMS/dbus-devel-0.22-12.EL.8.s390.rpm updates/s390/RPMS/dbus-glib-0.22-12.EL.8.s390.rpm updates/s390/RPMS/dbus-python-0.22-12.EL.8.s390.rpm

CentOS Errata and Bugfix Advisory 2019:0509 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0509 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 5a1dcf7e0ed2a515d157a18928ff43750331bedb71669a85ac7f9eccfcc23b30 dbus-1.10.24-13.el7_6.x86_64.rpm

CentOS Errata and Security Advisory 2020:2894 Important Upstream details at : https://access.redhat.com/errata/RHSA-2020:2894 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: f88bd838d89563321c366b251cbc62b30192c07f2ae42a69ca4a7bef46cbf389 dbus-1.10.24-14.el7_8.x86_64.rpm

Hi, Since today I can't start virt-manager anymore :-( Failed to connect to socket /tmp/dbus-yhDz4m8loi By the way the same message as I get from qdbus. There are no files called /tmp/dbus* on my system but some dbus applications are running: linux-dev:~# ps ax | grep dbus 1774 ? Ss 0:00 /usr/bin/dbus-daemon --system 2436 ? S 0:00 dbus-launch --autolaunch

CentOS Errata and Security Advisory 2007:0008 https://rhn.redhat.com/errata/RHSA-2007-0008.html The following updated files have been uploaded and are currently syncing to the mirrors: x86_64: dbus-0.22-12.EL.8.i386.rpm dbus-0.22-12.EL.8.x86_64.rpm dbus-devel-0.22-12.EL.8.x86_64.rpm dbus-glib-0.22-12.EL.8.i386.rpm dbus-glib-0.22-12.EL.8.x86_64.rpm dbus-python-0.22-12.EL.8.x86_64.rpm

CentOS Errata and Security Advisory 2005:102 https://rhn.redhat.com/errata/RHSA-2005-102.html The following updated files have been uploaded and are currently syncing to the mirrors: x86_64: dbus-0.22-12.EL.2.x86_64.rpm dbus-0.22-12.EL.2.i386.rpm dbus-devel-0.22-12.EL.2.x86_64.rpm dbus-glib-0.22-12.EL.2.x86_64.rpm dbus-glib-0.22-12.EL.2.i386.rpm dbus-python-0.22-12.EL.2.x86_64.rpm