DBus daemon settings bound to compilation machine

Bug #1386080 reported by Pedro A. Aranda on 2014-10-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Undecided
Unassigned

Bug Description

When I launch Inkscape from the CLI, I get the following message:

Failed to execute message bus daemon /Volumes/magenta/mp-trunk/quartz/bin/dbus-daemon: No such file or directory. Will try again without full path.

In System Preferences->System, the Inkscape data are located at

/Volumes/magenta/mp-trunk/src/inkscape-repo/mptrunk-quartz-osxmenu/inst-osxapp/share

And cannot be changed

su_v (suv-lp) wrote :

Please always provide information about OS/platform and Inkscape version (see Inkscpae menu 'Help > About Inkscape') when reporting bugs.

AFAICT the reporter uses an unofficial experimental OS X application package [1] - reports related to those custom packages do not belong into the bug tracker (yet).

On 2014-10-27 09:55 (+0200), Pedro A. Aranda wrote:
> When I launch Inkscape from the CLI, I get the following message:
>
> Failed to execute message bus daemon /Volumes/magenta/mp-
> trunk/quartz/bin/dbus-daemon: No such file or directory. Will try again
> without full path.

1) The console warnings from the dbus-launch binary are harmless to the best of my knowledge: they do neither result in launch failure of inkscape itself, nor prevent usage of the experimental dbus scripting API or of dbus/gvfs-based features (Import Clip Art) nor otherwise negatively affect usage of the relocatable self-contained application bundle.

Missing relocation support for dbus itself is an upstream issue (dbus and gvfs currently are a pain for OS X packaging when aiming for self-contained application bundles without requiring an installer for services to be managed via launchd, outside of the application bundle and not part of the native system).

2) OS X application bundles of ported software are difficult to optimize for CLI usage (not their primary use case either). Command line usage should have improved a lot already with the osxmenu packages compared to known limiations with the official packages for Mac OS X as tracked e.g. in bug #435812.

> In System Preferences->System, the Inkscape data are located at
> (…)
> And cannot be changed

Why do you have to? (The configured prefix at compile time of the inkscape binary has no effect on the bundled dbus binaries).

Proposing to close this report as 'Invalid' for now - the report is not based on official packages nor on one of the official branches (trunk, stable release branch).

Apart from that - I will take a look whether there's an easy way to silence the warnings from the dbus-launch binary; the fact that Inkscape shows the compiled-in original prefix/install path in the preferences is a cosmetic issue (it is not an indication that relocation support of the application bundle is fundamentally broken).

--
[1] https://code.launchpad.net/~suv-lp/inkscape/osxmenu

su_v (suv-lp) on 2014-10-27
tags: added: cli dbusapi gtk-osx packaging
su_v (suv-lp) wrote :

Latest upload (0.91+devel+osxmenu r12859) should no longer output the warnings from dbus-launch to the console.

Closing - does not concern official branch/package.

Changed in inkscape:
status: New → Invalid
su_v (suv-lp) on 2017-01-12
tags: added: gtk-quartz
removed: gtk-osx
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers