public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Problem with installation of Octave
Date: Tue, 08 Jan 2019 12:24:00 -0000	[thread overview]
Message-ID: <4f2b3749-c9da-a2f3-740b-07f541740e99@gmail.com> (raw)
In-Reply-To: <CAMCbSMpqUM9Ffn7tcqyfHBJb7J5BKx8zex534r0xdqFpiUdA6g@mail.gmail.com>

Am 08.01.2019 um 03:49 schrieb Arjen Markus:
> Hello,
>
> when I updated my installation of Cygwin with Octave (4.2.2 to be
> precise) and tried running it (while having an X server running), I
> ran into a problem with D-bus:
>
> D-Bus library appears to be incorrectly set up; failed to read machine
> uuid: Failed to open "/etc/machine-id": No such file or directory See
> the manual page for dbus-uuidgen to correct this issue.
>
> Apparently, installing Octave was not enough, I had to install D-bus
> separately. When I had done that, the problem was gone. I guess this
> is an omission in the dependencies for Octave. Note: this problem
> occurred both with and without the GUI that Octave comes with (octave
> --no-gui gave the same error messages).
>
> Kind regards,
>
> Arjen Markus
>

Hi Arjen,
noted, however I see that dbus shoud be pulled by xinit

Are you using the X server without xinit ?

Regards
Marco




---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2019-01-08 12:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 11:49 Arjen Markus
2019-01-08 12:24 ` Marco Atzeri [this message]
2019-01-08 12:41   ` Arjen Markus
2020-02-07 21:47     ` Jay Abel
2020-02-08  5:43       ` Marco Atzeri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4f2b3749-c9da-a2f3-740b-07f541740e99@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).