dbus issueshttps://gitlab.freedesktop.org/dbus/dbus/-/issues2023-05-27T07:19:05Zhttps://gitlab.freedesktop.org/dbus/dbus/-/issues/5no way to exit a dbus server without creating a race condition2023-05-27T07:19:05ZBugzilla Migration Userno way to exit a dbus server without creating a race condition## Submitted by Allison Lortie `@desrt`
Assigned to **D-Bus Maintainers**
**[Link to original bug (#11454)](https://bugs.freedesktop.org/show_bug.cgi?id=11454)**
## Description
i believe that it is sane to have some dbus services ...## Submitted by Allison Lortie `@desrt`
Assigned to **D-Bus Maintainers**
**[Link to original bug (#11454)](https://bugs.freedesktop.org/show_bug.cgi?id=11454)**
## Description
i believe that it is sane to have some dbus services exit (for example, after a period of activity). as far as i can tell (and from some simple testing) there is absolutely no way to do this without creating a race condition.
if a message is delivered to the server just as it is exiting then the message becomes lost forever and the client receives a timeout error.
ideally, for the activation case the server should be reactivated and the message resent. for the non-activation case, the client should receive the same error message that they receive if the server is not running (since a timeout error indicates that probably the server has become wedged).
see the attached example.
Version: 1.5https://gitlab.freedesktop.org/dbus/dbus/-/issues/4maybe see whether strict aliasing would be a performance improvement2023-05-27T07:19:05ZBugzilla Migration Usermaybe see whether strict aliasing would be a performance improvement## Submitted by Pacho Ramos
Assigned to **D-Bus Maintainers**
**[Link to original bug (#10599)](https://bugs.freedesktop.org/show_bug.cgi?id=10599)**
## Description
When I compile dbus I get:
dbus-launch-x11.c:313: warning: deref...## Submitted by Pacho Ramos
Assigned to **D-Bus Maintainers**
**[Link to original bug (#10599)](https://bugs.freedesktop.org/show_bug.cgi?id=10599)**
## Description
When I compile dbus I get:
dbus-launch-x11.c:313: warning: dereferencing type-punned pointer will break strict-aliasing rules
dbus-launch-x11.c:326: warning: dereferencing type-punned pointer will break strict-aliasing rules
Thanks a lot
Version: 1.5https://gitlab.freedesktop.org/dbus/dbus/-/issues/3assertion failure looks likely on re-opening disconnected shared connection2023-05-27T07:19:05ZBugzilla Migration Userassertion failure looks likely on re-opening disconnected shared connection## Submitted by Havoc Pennington
Assigned to **D-Bus Maintainers**
**[Link to original bug (#9020)](https://bugs.freedesktop.org/show_bug.cgi?id=9020)**
## Description
In dbus_connection_open() we don't return a disconnected conne...## Submitted by Havoc Pennington
Assigned to **D-Bus Maintainers**
**[Link to original bug (#9020)](https://bugs.freedesktop.org/show_bug.cgi?id=9020)**
## Description
In dbus_connection_open() we don't return a disconnected connection from the
shared hash, instead opening a new connection. We then insert the newly-opened
connection into the hash, which should replace the old one.
However, in connection_forget_shared_unlocked() we assert() if the connection
is not in the hash. The replaced/disconnected connection won't be in the hash
by my reading of the code.
I think our connect/disconnect handling could really use a nice test case...
maybe create the test bus, then have a client that tries opening various
shared/private connections and on client exit do a dbus_shutdown() and check
for leaks.
Version: 1.5https://gitlab.freedesktop.org/dbus/dbus/-/issues/2enable -Wtype-limits or document why not2023-05-27T07:19:05ZBugzilla Migration Userenable -Wtype-limits or document why not## Submitted by frederic heem
Assigned to **D-Bus Maintainers**
**[Link to original bug (#8164)](https://bugs.freedesktop.org/show_bug.cgi?id=8164)**
## Description
dbus doesn't compile with -Wall -Werror with gcc version 4.1.1 20...## Submitted by frederic heem
Assigned to **D-Bus Maintainers**
**[Link to original bug (#8164)](https://bugs.freedesktop.org/show_bug.cgi?id=8164)**
## Description
dbus doesn't compile with -Wall -Werror with gcc version 4.1.1 20060525 (Red
Hat 4.1.1-1)
Here are some examples:
dbus-marshal-header.c: In function '_dbus_header_toggle_flag':
dbus-marshal-header.c:1429: warning: pointer targets in assignment differ in
signedness
dbus-marshal-header.c: In function '_dbus_header_get_flag':
dbus-marshal-header.c:1450: warning: pointer targets in assignment differ in
signedness
Version: 1.5https://gitlab.freedesktop.org/dbus/dbus/-/issues/1D-BUS messages lost when auto-activating2023-05-27T07:19:04ZBugzilla Migration UserD-BUS messages lost when auto-activating## Submitted by Kimmo Hämäläinen
Assigned to **D-Bus Maintainers**
**[Link to original bug (#896)](https://bugs.freedesktop.org/show_bug.cgi?id=896)**
## Description
I made a simple D-BUS server which writes a line into a file whe...## Submitted by Kimmo Hämäläinen
Assigned to **D-Bus Maintainers**
**[Link to original bug (#896)](https://bugs.freedesktop.org/show_bug.cgi?id=896)**
## Description
I made a simple D-BUS server which writes a line into a file when it receives a
message and a client which sends 100 messages to the server with the
auto-activate flag up in every one of them. The server is not initially running
(it's supposed to be activated by the first message). The D-BUS system bus is
used and proper .service and .conf files are installed for the server.
When the client is run, one of the two things happen:
1) D-BUS system bus crashes (the server is not activated).
2) Another(!) D-BUS system bus appears to ps command's listing and the server is
activated, but the server does not receive any of the 100 messages.
In case of 2) happened and the client is run again, the server receives all the
100 messages (but there's still two D-BUS system buses running, according to ps).
Version: 1.5
### Blocking
* [Bug 52372](https://bugs.freedesktop.org/show_bug.cgi?id=52372)