dbus issues
https://gitlab.freedesktop.org/dbus/dbus/-/issues
2022-07-13T19:09:39Z
https://gitlab.freedesktop.org/dbus/dbus/-/issues/397
Deprecate / remove WinCE support
2022-07-13T19:09:39Z
Marc-André Lureau
Deprecate / remove WinCE support
Unless I am proved wrong, WinCE is nearing its EOL. Support will end sometime next year (https://docs.microsoft.com/en-us/lifecycle/products/windows-embedded-compact-2013)
What would be the process to actually remove WinCE support from ...
Unless I am proved wrong, WinCE is nearing its EOL. Support will end sometime next year (https://docs.microsoft.com/en-us/lifecycle/products/windows-embedded-compact-2013)
What would be the process to actually remove WinCE support from DBus?
(fwiw, meson doesn't support wince for !303)
https://gitlab.freedesktop.org/dbus/dbus/-/issues/168
make recommended system service naming mandatory
2018-10-15T13:43:32Z
Bugzilla Migration User
make recommended system service naming mandatory
## Submitted by Simon McVittie
Assigned to **D-Bus Maintainers**
**[Link to original bug (#99874)](https://bugs.freedesktop.org/show_bug.cgi?id=99874)**
## Description
dbus-daemon currently has the following unintended behaviour f...
## Submitted by Simon McVittie
Assigned to **D-Bus Maintainers**
**[Link to original bug (#99874)](https://bugs.freedesktop.org/show_bug.cgi?id=99874)**
## Description
dbus-daemon currently has the following unintended behaviour for system services whose filenames are not the canonical name (the well-known name + ".service"):
* Parse whichever service came first in readdir() order (might be the canonical name, or any other name[1]).
* Silently ignore any others.
* If the one that got parsed has a SystemdService set, use that for activation.
* If the one that got parsed does not have a SystemdService set, use the setuid helper for activation - but the setuid helper will load the file that has the canonical name instead (!), or if there is none, activation will fail.
When Bug #99825 lands, [1] will at least become a warning.
For the development branch, I think we should consider tightening this to: if the name is not canonical, just fail to load it. After Bug #99825, this would be easy to do.
Version: git master
### Depends on
* [Bug 99825](https://bugs.freedesktop.org/show_bug.cgi?id=99825)
https://gitlab.freedesktop.org/dbus/dbus/-/issues/167
consider warning when session services have the wrong name
2018-10-15T13:43:42Z
Bugzilla Migration User
consider warning when session services have the wrong name
## Submitted by Simon McVittie
Assigned to **D-Bus Maintainers**
**[Link to original bug (#99873)](https://bugs.freedesktop.org/show_bug.cgi?id=99873)**
## Description
Best practice for D-Bus session services is to define the serv...
## Submitted by Simon McVittie
Assigned to **D-Bus Maintainers**
**[Link to original bug (#99873)](https://bugs.freedesktop.org/show_bug.cgi?id=99873)**
## Description
Best practice for D-Bus session services is to define the service com.example.Foo in a file named com.example.Foo.service. This ensures that it is unambiguous which one is started: the one that is first in directory search order (this is not 100% reliable until one of the patches from Bug #99825 lands).
dbus-daemon could warn if a service is encountered that does not satisfy that constraint. However, this is currently wrong in a lot of software <https://lintian.debian.org/tags/dbus-session-service-wrong-name.html> so we should probably get some of those fixed first.
The cost of obeying that constraint is that if two software packages are deliberately providing implementations of the same well-known bus name, they will have file conflicts. However, this does not seem a whole lot worse than the current situation, where whichever one appears first in readdir() order is chosen, which I'm fairly sure is not what the software author intended.
Version: git master
### Depends on
* [Bug 99825](https://bugs.freedesktop.org/show_bug.cgi?id=99825)