similar to: [PATCH] Descriptions for dbus when plugin not loaded

I've started work on a rewrite of sorts for the dbus plugin that changes how it listens/responds to messages to make it possible to generate introspection data. The main changes are registering every plugin, screen, option, etc with dbus_connection_register_object_path and using libxml2 to generate the introspection data. This more or less works I just need to hook up the rest of the methods

I was writing a simple plugin a while ago which just sets the paint values on inactive windows. The plugin is very simple and the main part is below. When I load this plugin it blocks dbus and fuse plugins so that they only reply to requests when the active window changes. Is there anything obvious here that would cause that? static Bool inactivePaintWindow (CompWindow *w, const

I seem to be having problems with the latest dbus code. Here is a backtrace. This is happening at startup. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 47449612229888 (LWP 28353)] 0x00002b27b87991c0 in strlen () from /lib/libc.so.6 (gdb) bt #0 0x00002b27b87991c0 in strlen () from /lib/libc.so.6 #1 0x00002aaaac1b0657 in dbus_watch_handle () from

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

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

I have written an initial flat file configuration backend for Compiz. At the moment it is using FAM for monitoring of files (it can be compiled without monitoring support for now). It is working fine but there are a couple of problems. 1. It looks like I should use addFileWatch rather than directly accessing FAM, is this correct? I notice dbus uses addFileWatch rather than

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

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

I'm trying to use custom functions for loaderLoadPlugin and loaderUnloadPlugin to register/unregister plugin paths in the dbus plugin as needed but I need to get access to a CompDisplay or DbusDisplay in order to do so. Is there any way to get access to this? -- Travis Watkins http://www.realistanew.com

Here are my patches to add extra shapes to the annotate plugin. I have also added dbus support and made a few things configurable. The new tools available are Line, Rectangle and Circle, the original is called Brush. There is no selection line at the moment because I do not understand OpenGL yet. Hopefully these patches can be added and something added later. There is an extra action called

Here is my python loader plugin which loads plain python scripts as full plugins. There is not much documentation, but I have included a few examples to get you going. triangle - Just a basic plugin which shows a triangle on a button press. This shows using ctypes to pass values from compiz to the python opengl bindings. basiczoom - Zooms in on the screen (basically) inactive - This is a port

This patch adds support for getMetadata to plugins. It could probably use better strings for "core". I need this for my dbus-based configuration GUI. -- Travis Watkins http://www.realistanew.com -------------- next part -------------- A non-text attachment was scrubbed... Name: add_plugin_metadata.patch Type: text/x-patch Size: 2511 bytes Desc: not available Url :

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

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

Hallo, I was wondering if there is a good place where one can find more information about the the methods exported on the dbus by the different plugins. And especially the required parameters. I have play around quite a bit and tried to use the "org.freedesktop.DBus.Introspectable.Introspect" method to get more information about the objects, but I was not really lucky in finding what I

Hi folks, For ubuntu specs and for a better desktop integration of compiz, I made some patchs and plugins. Focus prevention is now in main stream, and really better can i made :) First the workspace and terminal keybinding patch. Since my last email I updated the patch. http://gandalfn.club.fr/ubuntu/compiz-patch/91-workspaces-terminal-keybindings.patch It adds the support for vertical

Attached is a quick patch which adds a logging framework to compiz. I think it should be fairly self explanitory. I think it should allow plugin writers to extend it for any purpose, but I would appreciate any feedback or comments before going any further. Regards Mike -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: logging.diff Url:

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:

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

--- plugins/dbus.c | 54 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 54 insertions(+), 0 deletions(-) diff --git a/plugins/dbus.c b/plugins/dbus.c index 46ded89..664fbf1 100644 --- a/plugins/dbus.c +++ b/plugins/dbus.c @@ -47,6 +47,7 @@ static CompMetadata dbusMetadata; #define COMPIZ_DBUS_LIST_MEMBER_NAME "list" #define