dbus issues
https://gitlab.freedesktop.org/dbus/dbus/-/issues
2023-10-29T14:54:50Z
https://gitlab.freedesktop.org/dbus/dbus/-/issues/483
Windows on ARM64 (aarch64-w64-mingw32) support
2023-10-29T14:54:50Z
Brecht Sanders
Windows on ARM64 (aarch64-w64-mingw32) support
I tried to build dbus 1.15.8 natively on Windows on ARM64 (aarch64-w64-mingw32) using LLVM+MinGW-w64 and noticed building dbus/dbus-backtrace-win.c failed because this platform was not supported yet.
I was able to build after the patch ...
I tried to build dbus 1.15.8 natively on Windows on ARM64 (aarch64-w64-mingw32) using LLVM+MinGW-w64 and noticed building dbus/dbus-backtrace-win.c failed because this platform was not supported yet.
I was able to build after the patch below, but I'm not a 100% sure it is accurate for this platform as the sf.Addr* lines are just based on educated guesses from my part.
```
patch -ulbf dbus/dbus-backtrace-win.c << EOF
@@ -113,2 +113,10 @@
sf.AddrStack.Mode = AddrModeFlat;
+#elif defined(_M_ARM64)
+ dwImageType = IMAGE_FILE_MACHINE_ARM64;
+ sf.AddrPC.Offset = context.Pc;
+ sf.AddrPC.Mode = AddrModeFlat;
+ sf.AddrFrame.Offset = context.Sp;
+ sf.AddrFrame.Mode = AddrModeFlat;
+ sf.AddrStack.Offset = context.Sp;
+ sf.AddrStack.Mode = AddrModeFlat;
#else
EOF
```
https://gitlab.freedesktop.org/dbus/dbus/-/issues/462
windows-meson-mingw-ucrt64 failing since 2023-06-06: Could not detect Ninja v...
2023-06-13T13:02:04Z
Simon McVittie
windows-meson-mingw-ucrt64 failing since 2023-06-06: Could not detect Ninja v1.8.2 or newer
On 2023-05-16 I re-enabled Windows CI, and it passed: https://gitlab.freedesktop.org/dbus/dbus/-/commit/a6654eae7f842ee9fd94cafb6ce1ffd98df2bdf5/pipelines?ref=master
Since 2023-06-06, CI is failing in the `windows-meson-mingw-ucrt64` jo...
On 2023-05-16 I re-enabled Windows CI, and it passed: https://gitlab.freedesktop.org/dbus/dbus/-/commit/a6654eae7f842ee9fd94cafb6ce1ffd98df2bdf5/pipelines?ref=master
Since 2023-06-06, CI is failing in the `windows-meson-mingw-ucrt64` job: https://gitlab.freedesktop.org/dbus/dbus/-/jobs/43178395
```
ERROR: Could not detect Ninja v1.8.2 or newer
A full log can be found at C:\Users\Administrator\runner\builds\dbus\dbus\build\meson-logs\meson-log.txt
```
https://gitlab.freedesktop.org/dbus/dbus/-/blob/master/tools/docker/windows/Dockerfile explicitly installs `ninja` using msys64, so it should be there. In https://gitlab.freedesktop.org/dbus/dbus/-/jobs/43178370, ninja-1.11.1-1 was installed.
It seems we also have an older version of Ninja:
```
Found ninja-1.8.2 at C:\BuildTools\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja\ninja.EXE
```
I don't know which one the dbus build is meant to be using.
Please could someone who understands Windows look into this?
If we can't make this reliable, then we should disable this CI job so that only the reliable jobs are gating new contributions. I don't have enough time available for dbus maintenance to be able to afford to spend it on debugging an OS I don't use.
/cc @elmarco @rhabacker
https://gitlab.freedesktop.org/dbus/dbus/-/issues/400
Tests that run dbus-daemon time out when run on Windows on Gitlab-CI
2022-06-28T12:15:02Z
Simon McVittie
Tests that run dbus-daemon time out when run on Windows on Gitlab-CI
Several tests run a `dbus-daemon` as a subprocess:
* `test/dbus-daemon.c`
* `test/dbus-daemon-eavesdrop.c`
* `test/header-fields.c`
* `test/monitor.c`
* (plus some more that are not applicable on Windows, therefore either skip all test-...
Several tests run a `dbus-daemon` as a subprocess:
* `test/dbus-daemon.c`
* `test/dbus-daemon-eavesdrop.c`
* `test/header-fields.c`
* `test/monitor.c`
* (plus some more that are not applicable on Windows, therefore either skip all test-cases or are not compiled at all)
When the dbus test suite is run by the `windows vs15-64 cmake` CI job (building and running x64 binaries on real Windows using CMake and Visual Studio 15), `dbus-daemon*` and `monitor` are skipped, with comment "a few tests timeout on gitlab runner for unknown reason" (added in !218 by @elmarco).
`test/header-fields.c` is not built by CMake at all, only by Autotools (and now Meson). That's out of scope here: it would be an easy fix if someone wants to enable that, but perhaps not worth it if we're intending to remove CMake in favour of Meson.
The `windows msys64 ucrt64 cmake` CI job (building and running x64 binaries on real Windows using MSYS for the build and UCRT for the binaries under test) doesn't run any tests, so we don't know whether it would succeed or not. Again, that's out of scope here, and possibly not worth it if CMake is on its way out. I suspect the answer is that these four tests would time out.
When we tried building and running the dbus test suite with Meson on !303 (this time building and running x86 binaries on real Windows using MSYS for the build and UCRT for the binaries under test, and building and running x64 binaries on real Windows using Visual Studio 15), these four tests also time out in those configurations.
Someone who likes Windows should investigate whether these tests run successfully on a developer's Windows machine (other than on Gitlab-CI) and whether they can be made to run successfully on Gitlab-CI. For now, I'm going to skip them in Meson builds, for parity with CMake.
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/220
--enable-relocation support breaks assumptions made by mingw32-install-post.sh
2018-11-15T13:29:45Z
Bugzilla Migration User
--enable-relocation support breaks assumptions made by mingw32-install-post.sh
## Submitted by Ralf Habacker `@rhabacker`
Assigned to **D-Bus Maintainers**
**[Link to original bug (#107662)](https://bugs.freedesktop.org/show_bug.cgi?id=107662)**
## Description
Created attachment 141245
fix-order-of-dbus-1.pc...
## Submitted by Ralf Habacker `@rhabacker`
Assigned to **D-Bus Maintainers**
**[Link to original bug (#107662)](https://bugs.freedesktop.org/show_bug.cgi?id=107662)**
## Description
Created attachment 141245
fix-order-of-dbus-1.pc.patch
Cross building dbus from git master with autotools for windows fails because of two issues
1.cross pkg-config 0.28 is confused to not have prefix= in the first line of dbus-1.pc
2. relocation support in configure.ac does not recognize --exec_prefix expanded to ${prefix} and --libdir to ${prefix}/lib
For both issues a related patch has been appended.
~~**Patch 141245**~~, "fix-order-of-dbus-1.pc.patch":
[fix-order-of-dbus-1.pc.patch](/uploads/711e79dd42873d93b2ef29685083b6b4/fix-order-of-dbus-1.pc.patch)
Version: git master
https://gitlab.freedesktop.org/dbus/dbus/-/issues/187
dbus-1.13 release for Windows
2018-10-15T13:41:00Z
Bugzilla Migration User
dbus-1.13 release for Windows
## Submitted by Ralf Habacker `@rhabacker`
Assigned to **D-Bus Maintainers**
**[Link to original bug (#103435)](https://bugs.freedesktop.org/show_bug.cgi?id=103435)**
## Description
This task is intended to track required task for...
## Submitted by Ralf Habacker `@rhabacker`
Assigned to **D-Bus Maintainers**
**[Link to original bug (#103435)](https://bugs.freedesktop.org/show_bug.cgi?id=103435)**
## Description
This task is intended to track required task for the DBus 1.12 release on Windows.
Currently the following tasks comes into my mind or has been raised by others:
1. Specify minimal supported os version and compiler
2. complete open bugs (for example [bug 99751](https://bugs.freedesktop.org/show_bug.cgi?id=99751))
2. Update website
3. Make binary packages for Windows (packages are currently in preparation at https://build.opensuse.org/project/show/home:rhabacker:branches:windows:mingw:win32:unstable)
4. Find a download location for binary packages e.g. https://dbus.freedesktop.org/releases/win or something else if not possible [1]
5. ....
[1] obs would also be possible in theory by using the following search https://software.opensuse.org/package/mingw32-dbus-1-portable?search_term=mingw32-dbus-1-portable for portable packages or https://software.opensuse.org/package/mingw32-dbus-1-portable?search_term=mingw32-dbus-1-installer for exe installer or specifing a direct link to a package but is currently limited to having 7z files or exe installer inside a rpm container. A fix requires to add a new "raw" repository format to obs which would make it possible to place the native packages into a sub dir of https://download.opensuse.org. If this is not possible or will be too much work, or may be rejected by the obs maintainer a release script is required to unpack the native packages and prepare the release as it has been done for KMyMoney (see https://cgit.kde.org/kmymoney.git/tree/maintainer/release-windows-packages)
Version: git master
https://gitlab.freedesktop.org/dbus/dbus/-/issues/150
W32: dbus does not support SSPI-based authentication mechanisms
2019-05-31T18:24:51Z
Bugzilla Migration User
W32: dbus does not support SSPI-based authentication mechanisms
## Submitted by LRN
Assigned to **D-Bus Maintainers**
**[Link to original bug (#96577)](https://bugs.freedesktop.org/show_bug.cgi?id=96577)**
## Description
As discussed on dbus@lists.freedesktop.org ML, dbus could use
an actual O...
## Submitted by LRN
Assigned to **D-Bus Maintainers**
**[Link to original bug (#96577)](https://bugs.freedesktop.org/show_bug.cgi?id=96577)**
## Description
As discussed on dbus@lists.freedesktop.org ML, dbus could use
an actual OS-supported authentication on Windows (EXTERNAL on Windows
is a hack, DBUS_COOKIE_SHA1 has obvious drawbacks).
### Depends on
* [Bug 99512](https://bugs.freedesktop.org/show_bug.cgi?id=99512)
https://gitlab.freedesktop.org/dbus/dbus/-/issues/89
Running dbus as windows service
2022-03-25T16:02:00Z
Bugzilla Migration User
Running dbus as windows service
## Submitted by Ralf Habacker `@rhabacker`
Assigned to **D-Bus Maintainers**
**[Link to original bug (#68741)](https://bugs.freedesktop.org/show_bug.cgi?id=68741)**
## Description
Created attachment 84892
Add dbus service helper a...
## Submitted by Ralf Habacker `@rhabacker`
Assigned to **D-Bus Maintainers**
**[Link to original bug (#68741)](https://bugs.freedesktop.org/show_bug.cgi?id=68741)**
## Description
Created attachment 84892
Add dbus service helper application
The append patches implements a basic implementation for running dbus as windows service, which has been requested.
**Patch 84892**, "Add dbus service helper application":
[0001-Add-windows-service-handler.patch](/uploads/5a0962c3d5e267fea527e3c2e3042106/0001-Add-windows-service-handler.patch)
Version: 1.5
### Depends on
dbus should definitely not be used across privilege boundaries on Windows until it is in a security-supportable state, which means issues like #45 need to be fixed first.