Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] aqemu: v0.9.3 released from TBK's fork
Date: Sat, 30 Jan 2021 02:47:22 +0100	[thread overview]
Message-ID: <20210130014722.OsYM94DQzTSs3NDdkKWD1TcTZaER7eo_wfeF8ucIYaU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11056@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]

Closed issue by go2null on void-packages repository

https://github.com/void-linux/void-packages/issues/11056

Description:
### System

* xuname:  
  `Void 4.19.34_1 x86_64 GenuineIntel uptodate rrFFF`
* package:  
  `aqemu-0.9.2_1`

### Expected behavior

Running an image should work.

### Actual behavior

Get following errors
```
Error #1
(qemu-system-x86_64:5189): dbind-WARNING **: 06:53:52.966: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. 

Error #2
qemu-system-x86_64: Invalid parameter 'vlan' 
```

The image does not run.

### Steps to reproduce the behavior

1. Create an image
2. Run the image

### Notes

The [original](https://github.com/tobimensch/aqemu) repo has stalled since 2017.  KBH has [forked](https://github.com/TBK/aqemu) the repo and has just released [v0.9.3.](https://github.com/TBK/aqemu/releases/tag/v0.9.3)


      parent reply	other threads:[~2021-01-30  1:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11056@inbox.vuxu.org>
2021-01-30  1:47 ` ericonr
2021-01-30  1:47 ` ericonr [this message]

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=20210130014722.OsYM94DQzTSs3NDdkKWD1TcTZaER7eo_wfeF8ucIYaU@z \
    --to=ericonr@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).