From: nerdyslacker <nerdyslacker@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: onboard-1.4.1_12 fails after upgrade python 3.12
Date: Thu, 19 Oct 2023 15:02:25 +0200 [thread overview]
Message-ID: <20231019130225.fBqsscykPTfuYcNVqOCQW-O5dOqvo3wPQfRs1BJ4zU0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46767@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
New comment by nerdyslacker on void-packages repository
https://github.com/void-linux/void-packages/issues/46767#issuecomment-1770945553
Comment:
> The syntax warnings do need to be fixed, but you can ignore them for now. As for the actual segfault, I cannot reproduce; onboard starts up just fine for me (using Sway).
when I look into logs the exact error is:
![void_log](https://github.com/void-linux/void-packages/assets/31778860/08cb23f7-ccd9-4ed0-a54b-f3c411f774f6)
but I am not sure what I can do with this.
tried this on my main system, from official live image and also a few void spins. same error everywhere.
next prev parent reply other threads:[~2023-10-19 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 21:53 [ISSUE] " nerdyslacker
2023-10-19 7:20 ` mhmdanas
2023-10-19 13:02 ` nerdyslacker [this message]
2023-10-19 14:39 ` sgn
2023-10-19 15:05 ` sgn
2023-10-20 2:37 ` [ISSUE] [CLOSED] " sgn
2023-10-20 10:01 ` MechDR
2023-10-20 10:02 ` MechDR
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=20231019130225.fBqsscykPTfuYcNVqOCQW-O5dOqvo3wPQfRs1BJ4zU0@z \
--to=nerdyslacker@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).