similar to: virt-manager can't start because of a dbus problem

On 29/04/2019 22.01, Michal Privoznik wrote: > On 4/29/19 1:06 PM, lameventanas@gmail.com wrote: >> I want to run libvirtd as a special user, and allowing users that belong >> to a special group to connect via qemu+unix:///system (eg: unix socket). >> >> I did everything necessary to do so: created a libvirt user and group, >> added the libvirt user to the kvm

I?m trying to setup Spotlight with Tracker (2.3 from Ubuntu repo) backend in Ubuntu 20.04 and Samba 4.12.7. I?ve followed the wiki closely but every time I try to search I get this in the logs: [2020/10/02 10:43:42.078242, 0] ../../source3/rpc_server/mdssvc/mdssvc_tracker.c:403(mds_tracker_search_start) mds_tracker_search_start: no connection to Tracker [2020/10/02 10:43:42.079897, 0]

Yes, you are right. Listen, as the documentation is not very exaustive, can you explain briefly to me how a guest agent works? After installing it via the apt-get on the hypervisor (I am using ubuntu as host system) how can I create a script which would do this? That is waiting for an acpi signal and actually shut down the guest. And what other operation can you actually do with a guest agent? I

I've added configuration support to the dbus plugin. I haven't done much testing so let me know if you find any issues with it. You can find some usage examples in the dbus plugin code. This is what KDE needs for compiz configuration support but you can of course use it for other configuration systems too. E.g. writing a simple daemon that monitors a text file and use this dbus interface

=========== process 5496: arguments to dbus_connection_ref() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 2497. This is normally a bug in some application using the D-Bus library. org.freedesktop.DBus.Error.Spawn.ExecFailed: dbus-launch failed to autolaunch D-Bus session: PuTTY X11 proxy: wrong authentication protocol attemptedAutolaunch error:

On 12/17/2016 08:57 AM, Jonathan Billings wrote: > 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

On 12/17/2016 06:40 AM, Jonathan Billings wrote: > On Dec 16, 2016, at 4:29 PM, geo.inbox.ignored <geo.inbox.ignored at gmail.com> wrote: >> question is, how do i recreate, short of re-installing from .iso? > > > Why do you think you need these files in /root? > }} it is not that i think i need file in /root. file is located /.dbus/sessions-bus/* could be that i could

Hi, I am unsuccessfully trying to connect from host to containers dbus. Inside container dbus socket file is visible as /run/dbus/system_bus_socket. The problem is that /run is mounted as tmpfs in container (by systemd on container) and thus the directory content is not visible outside the container. Is there any way to make this file visible also outside the container? Regards, Piotrek

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

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

I was always annoyed that you couldn't terminate an action with dbus so I have written this patch which fixes that. Hopefully this can be included. I wrote the patch trying to repeat as little code as possible so I just added a boolean parameter to the dbusHandleActivateMessage and changed the name to dbusHandleActivateDeactivateMessage. You could probably change the deactivate parameter

Am I crazy for thinking about forwarding the DBUS session over an ssh connection much like the X session is forwarded? I've proven the concept with socat (to use the unix socket that dbus normally listens on rather than reconfiguring dbus to use a tcp socket) and it works just as expected. Any reason we wouldn't want openssh doing this natively? b.

FYI, I have put up a forum post [1] where I am going to maintain information about the netwm api for the dbus plugin. I have gone through the EWMH spec [2] and broken it down into a dbus compatible api, it seems to be good and roughly compatible with the existing compiz one. I think everything should be self explanitory, if there are any comments or if there is anything I have misunderstood or

During startup there is a message about a missing python-dbus. Querying rpm and yum tells me that nothing provides python-dbus and no such package exists. What do I need? Anne

Simon Matter via CentOS wrote: > >> We are seeing a problem that occurs ~5% of the time when rebooting > > I see such issues on a quite large multi user system but when this > happens, after forced restarts for kernel updates, I usually don't have > the time to analyze and play doctor on it. My "solution" now is to simply > reboot the server again in such a

Hi, I'm trying to configure samba 4.13.2 bot receive this messages Checking for dbus : not found vfs_snapper is enabled but prerequisite dbus-1 package not found. Use --with-shared-modules=!vfs_snapper to disable vfs_snapper support. (complete log in /srv/samba-4.13.2/bin/config.log) What is wrong?? try this: ./configure --enable-fhs --prefix=/usr --sbindir=/usr/sbin

Using latest git if you try to set an option to the value it already has you get an error like 'dbus_bindings.DBusException: Method "set" with signature "s" on interface "org.freedesktop.compiz" doesn't exist' and setting it to a new value actually changes the setting but dbus times out waiting for a reply saying so. Setting a list gives the method

greetings. while using rsync to copy /root/* from tower box to laptop computer, i accidentally over wrote .dbus/sessions-bus/[fn] on laptop computer. ran extensive web search, including; http://www.freedesktop.org/software/dbus/ to find how to replace or recreate file, only to find everything about what it does and why. question is, how do i recreate, short of re-installing from .iso?

We are seeing a problem that occurs ~5% of the time when rebooting CentOS 7.7 where systemd gets a 'Connection timed out' to D-Bus just after the D-Bus service starts - from 'journalctl -x' : ... Jan 21 16:09:59 linux7-7.mpc.local systemd[1]: Started D-Bus System Message Bus. -- Subject: Unit dbus.service has finished start-up -- Defined-By: systemd -- Support:

I am trying to use d-bus (client) inside a CGI perl environment where X11 DISPLAY is not set.