dbus issues
https://gitlab.freedesktop.org/dbus/dbus/-/issues
2018-11-19T15:42:21Z
https://gitlab.freedesktop.org/dbus/dbus/-/issues/214
Drop chdir("/") in dbus-launch
2018-11-19T15:42:21Z
Bugzilla Migration User
Drop chdir("/") in dbus-launch
## Submitted by David King
Assigned to **D-Bus Maintainers**
**[Link to original bug (#106987)](https://bugs.freedesktop.org/show_bug.cgi?id=106987)**
## Description
In RHEL 7, Paul Gozart came across some unexpected behaviour in...
## Submitted by David King
Assigned to **D-Bus Maintainers**
**[Link to original bug (#106987)](https://bugs.freedesktop.org/show_bug.cgi?id=106987)**
## Description
In RHEL 7, Paul Gozart came across some unexpected behaviour in gedit when run as a regular user, where the save dialog used the root path ("/") as the default location. This was traced down by Ray Strode to gedit in newer RHEL 7 versions being launched by dbus activation (as most GNOME applications are, if they use GApplication), and the dbus-daemon used for the session bus in RHEL being launched with dbus-launch (by gnome-session, as systemd is not used as a user session manager in RHEL 7).
There is a chdir("/") call in dbus-launch with the following justification:
/* We chdir ("/") since we are persistent and daemon-like, and fork
* again so dbus-launch can reap the parent. However, we don't
* setsid() or close fd 0 because the idea is to remain attached
* to the tty and the X server in order to kill the message bus
* when the session ends.
*/
Arguably, this is not the best behaviour for a tool that is only used to run session buses, which are scoped to the lifetime of the user's session (with some exceptions, of course), and given the pervasive use of dbus-launch by session managers to start dbus-daemon as a session bus, I think that it is best to drop the chdir() call entirely.
Version: git master
### See also
* https://bugzilla.redhat.com/show_bug.cgi?id=1470310
https://gitlab.freedesktop.org/dbus/dbus/-/issues/199
Fix dbus-send not returning an error exit code in case an error occured and -...
2018-10-15T13:28:21Z
Bugzilla Migration User
Fix dbus-send not returning an error exit code in case an error occured and --print-reply is not set
## Submitted by Ralf Habacker `@rhabacker`
Assigned to **D-Bus Maintainers**
**[Link to original bug (#105380)](https://bugs.freedesktop.org/show_bug.cgi?id=105380)**
## Description
## Submitted by Ralf Habacker `@rhabacker`
Assigned to **D-Bus Maintainers**
**[Link to original bug (#105380)](https://bugs.freedesktop.org/show_bug.cgi?id=105380)**
## Description
https://gitlab.freedesktop.org/dbus/dbus/-/issues/178
It would be nice if dbus-send also accepted "--user"
2018-10-15T14:30:24Z
Bugzilla Migration User
It would be nice if dbus-send also accepted "--user"
## Submitted by Danny Milosavljevic
Assigned to **D-Bus Maintainers**
**[Link to original bug (#101375)](https://bugs.freedesktop.org/show_bug.cgi?id=101375)**
## Description
Created attachment 131848
dbus-send: Add "--user"
**...
## Submitted by Danny Milosavljevic
Assigned to **D-Bus Maintainers**
**[Link to original bug (#101375)](https://bugs.freedesktop.org/show_bug.cgi?id=101375)**
## Description
Created attachment 131848
dbus-send: Add "--user"
**Patch 131848**, "dbus-send: Add "--user"":
[dbus-send-user-bus.patch](/uploads/1c0b79719e29aa41783f9a978c7e159f/dbus-send-user-bus.patch)
Version: 1.10
https://gitlab.freedesktop.org/dbus/dbus/-/issues/166
Different parameter usage design of dbus-monitor
2018-10-15T14:52:43Z
Bugzilla Migration User
Different parameter usage design of dbus-monitor
## Submitted by Ralf Habacker `@rhabacker`
Assigned to **D-Bus Maintainers**
**[Link to original bug (#99809)](https://bugs.freedesktop.org/show_bug.cgi?id=99809)**
## Description
Most dbus related command line tools provides comm...
## Submitted by Ralf Habacker `@rhabacker`
Assigned to **D-Bus Maintainers**
**[Link to original bug (#99809)](https://bugs.freedesktop.org/show_bug.cgi?id=99809)**
## Description
Most dbus related command line tools provides command line parameter with additional args in the form --`<key>`=`<value>`, which dbus-monitor uses --`<key>` `<value>`
e.g see --address parameter in the following help pages:
dbus-daemon [--version] [--session] [--system] [--config-file=FILE] [--print-address[=DESCRIPTOR]] [--print-pid[=DESCRIPTOR]] [--introspect] [--address=ADDRESS] [--nopidfile] [--nofork] [--fork] [--systemd-activation]
versus
Usage: dbus-monitor [--system | --session | --address ADDRESS] [--monitor | --profile ] [watch expressions]
Version: 1.10
https://gitlab.freedesktop.org/dbus/dbus/-/issues/165
Mismatch in documentation of dbus-send parameter --bus, --peer and --address
2018-10-15T13:43:54Z
Bugzilla Migration User
Mismatch in documentation of dbus-send parameter --bus, --peer and --address
## Submitted by Ralf Habacker `@rhabacker`
Assigned to **D-Bus Maintainers**
**[Link to original bug (#99808)](https://bugs.freedesktop.org/show_bug.cgi?id=99808)**
## Description
dbus-send command line help prints
Usage: dbus-s...
## Submitted by Ralf Habacker `@rhabacker`
Assigned to **D-Bus Maintainers**
**[Link to original bug (#99808)](https://bugs.freedesktop.org/show_bug.cgi?id=99808)**
## Description
dbus-send command line help prints
Usage: dbus-send [--help] [--system | --session | --bus=ADDRESS | --peer=ADDRESS] [--dest=NAME] [--type=TYPE] [--print-reply[=literal]] [--reply-timeout=MSEC] `<destination object path>` `<message name>` [contents ...]
while the man page prints out
dbus-send [--system | --session | --address=ADDRESS] [--dest=NAME] [--print-reply [=literal]] [--reply-timeout=MSEC] [--type=TYPE] OBJECT_PATH INTERFACE.MEMBER [CONTENTS...]
....
--address=ADDRESS
Send to ADDRESS.
It differs in the parameter --bus, --address and --peer.
Looking at the implementation of dbus-send there are all mentioned parameters supported:
if ((strstr (arg, "--bus=") == arg) || (strstr (arg, "--peer=") == arg) || (strstr (arg, "--address=") == arg))
{
if (arg[2] == 'b') /* bus */
{
is_bus = TRUE;
}
else if (arg[2] == 'p') /* peer */
{
is_bus = FALSE;
}
else /* address; keeping backwards compatibility */
{
is_bus = FALSE;
}
address = strchr (arg, '=') + 1;
if (address[0] == '\0')
{
fprintf (stderr, "\"--peer=\" and \"--bus=\" require an ADDRESS\n");
usage (1);
}
except that --address looks to be outdated and could not be used to connect to a bus. In the opposite dbus-monitor provides connecting to a bus using --address.
Version: 1.10
https://gitlab.freedesktop.org/dbus/dbus/-/issues/156
wid can be used without initialisation in dbus-launch.c
2018-10-15T13:47:30Z
Bugzilla Migration User
wid can be used without initialisation in dbus-launch.c
## Submitted by René J.V. Bertin
Assigned to **D-Bus Maintainers**
**[Link to original bug (#97924)](https://bugs.freedesktop.org/show_bug.cgi?id=97924)**
## Description
Going over the code I after noticing that dbus-launch set DB...
## Submitted by René J.V. Bertin
Assigned to **D-Bus Maintainers**
**[Link to original bug (#97924)](https://bugs.freedesktop.org/show_bug.cgi?id=97924)**
## Description
Going over the code I after noticing that dbus-launch set DBUS_SESSION_BUS_WINDOWID to an invalid wid, I see that the wid variable can indeed be used without having been initialised.
IMHO, either dbus-launch.c should initialise the wid variable to 0 at declaration, or x11_get_address() should be modified as such:
diff --git a/tools/dbus-launch-x11.c b/tools/dbus-launch-x11.c
index a09444b..d79b4a7 100644
--- a/tools/dbus-launch-x11.c
+++ b/tools/dbus-launch-x11.c
@@ -305,10 +305,10 @@ x11_get_address (char **paddress, pid_t *pid, long *wid)
/* locate the selection owner */
owner = XGetSelectionOwner (xdisplay, selection_atom);
- if (owner == None)
- return TRUE; /* no owner */
if (wid != NULL)
*wid = (long) owner;
+ if (owner == None)
+ return TRUE; /* no owner */
/* get the bus address */
result = XGetWindowProperty (xdisplay, owner, address_atom, 0, 1024, False,
Version: git master
https://gitlab.freedesktop.org/dbus/dbus/-/issues/60
Feature request: support for file descriptors in dbus-send
2018-10-15T14:28:04Z
Bugzilla Migration User
Feature request: support for file descriptors in dbus-send
## Submitted by Elizabeth Jones `@ellyjones`
Assigned to **D-Bus Maintainers**
**[Link to original bug (#43557)](https://bugs.freedesktop.org/show_bug.cgi?id=43557)**
## Description
Created attachment 54161
Patch against dbus-1.4....
## Submitted by Elizabeth Jones `@ellyjones`
Assigned to **D-Bus Maintainers**
**[Link to original bug (#43557)](https://bugs.freedesktop.org/show_bug.cgi?id=43557)**
## Description
Created attachment 54161
Patch against dbus-1.4.12 to add this feature.
dbus-send(1) cannot currently send file descriptors, although the underlying dbus protocol can. Add support for same, with a new syntax "fd:`<n>`".
Patch attached.
**Patch 54161**, "Patch against dbus-1.4.12 to add this feature.":
[dbus-1.4.12-send-unix-fd.patch](/uploads/3d03d8321d0bc1cff43b7f112dfda3eb/dbus-1.4.12-send-unix-fd.patch)
Version: 1.5