From: Linux for blind general discussion <blinux-list@redhat.com>
To: <blinux-list@redhat.com>
Subject: Dbus issues when running Fedora 31 for ARM64 Bit platform
Date: Wed, 19 Feb 2020 19:41:29 +0100 [thread overview]
Message-ID: <B99ECC0C5B4C4DA9A0EBA3735E38BF98@DESKTOPN6LG1HQ> (raw)
Dear suers and developers,
My name is Janusz Chmiel. I Am new mailing list member from Czech
Republic. I do not see at all. Fedora distribution is fascinating Me for
several years. And because I have been very satisfied with this distribution
when I have used it with my Toshiba Satellite L650 D laptop, I have decided
to try it out on my Huavei !) mate lite mobile phone. This mobile phone run
Android 8.0 and I Am running Fedora by using Termux, Proot and special
script.
Unfortunately for Me, I have got in to very complex issues with Dbus.
dbus-launch app name &
simply do not work at all.
Please does somebody of you know, if there is some technique, article which
would describe how to setup Dbus and dbus-x11 so it would run even on chroot
environment by using Termux, Proot and Android device?
Or unfortunately, Dbus version which is The part of Fedora 31 ARM64 Bit
contain Dbus binarz which have been compiled by The way that it will never
support this software environment?
I can install manz applications but Dbus do not work and it is verz
important to use inter process communication.
Thank zou verz much for zours help.
With kindness regards.
Janusz Chmiel
next reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion [this message]
` Linux for blind general discussion
` Linux for blind general discussion
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=B99ECC0C5B4C4DA9A0EBA3735E38BF98@DESKTOPN6LG1HQ \
--to=blinux-list@redhat.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).