From: eoli3n <eoli3n@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] gns3
Date: Fri, 05 May 2023 23:06:37 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43766@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
New issue by eoli3n on void-packages repository
https://github.com/void-linux/void-packages/issues/43766
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.4_1 x86_64 GenuineIntel notuptodate rrrmFFFF
### Package(s) Affected
ubridge
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
nop
### Expected behaviour
vpcs to start in gns3 without error
### Actual behaviour
When I try to start a vpcs, i get that error
### Steps to reproduce
1. install gns3-gui, gns3-server, ubridge, vpcs
2. run gns3
3. add a vpcs
4. start it
next reply other threads:[~2023-05-05 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 21:06 eoli3n [this message]
2023-05-06 19:53 ` gns3 : could not start vpcs eoli3n
2023-05-06 20:36 ` eoli3n
2023-05-23 2:09 ` sgn
2023-05-23 15:44 ` eoli3n
2024-05-15 18:15 ` [ISSUE] [CLOSED] " classabbyamp
2024-05-15 18:15 ` classabbyamp
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-43766@inbox.vuxu.org \
--to=eoli3n@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).