From: xyzz <xyzz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] renderdoc cannot run remote server on android
Date: Wed, 10 Feb 2021 17:53:30 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28630@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
New issue by xyzz on void-packages repository
https://github.com/void-linux/void-packages/issues/28630
Description:
### System
* xuname:
Void 5.10.14_1 x86_64 AuthenticAMD uptodate rrrrmdFFFFFFFFF
* package:
renderdoc-1.10_1
### Expected behavior
No error is displayed and remote server runs.
### Actual behavior
When trying to connect to a device, an error message is displayed
### Steps to reproduce the behavior
Start qrenderdoc with a debuggable android device attached. On bottom left select the android device:
it will try to connect for a while then display the above error message.
next reply other threads:[~2021-02-10 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 16:53 xyzz [this message]
2021-02-10 17:23 ` ericonr
2021-02-24 9:13 ` faulesocke
2021-02-25 17:01 ` xyzz
2022-05-03 2:14 ` github-actions
2022-05-17 2:14 ` [ISSUE] [CLOSED] " github-actions
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28630@inbox.vuxu.org \
--to=xyzz@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 NNTP newsgroup(s).