From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] openbazaar fails to run
Date: Thu, 07 Jul 2022 04:14:12 +0200 [thread overview]
Message-ID: <20220707021412.b2M73sAvGV3DPA9Jx_tWccdrr9w_IqCqhWaG75k3MNs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35126@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
Closed issue by RunningDroid on void-packages repository
https://github.com/void-linux/void-packages/issues/35126
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Void 5.15.14_1 x86_64 GenuineIntel uptodate rrmFFFFFFFFFFFFFF
* package:
openbazaar-1.1.13_2
nodejs-16.13.2_2
icu-libs-70.1_1
### Expected behavior
openbazaar runs, maybe draws a window.
### Actual behavior
openbazaar dies via SIGABRT after printing this on stdout:
```
[13122:0119/204315:FATAL:content_main_runner.cc(691)] Check failed: base::i18n::InitializeICU().
#0 0x000001e5855e <unknown>
#1 0x000001e6e25b <unknown>
#2 0x000001221720 <unknown>
#3 0x0000012205ba <unknown>
#4 0x000003479633 main
#5 0x7f238bb8fe0a <unknown>
#6 0x000000579189 <unknown>
```
### Steps to reproduce the behavior
Run openbazaar in a terminal
next prev parent reply other threads:[~2022-07-07 2:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 1:52 [ISSUE] " RunningDroid
2022-06-22 2:14 ` github-actions
2022-07-07 2:14 ` github-actions [this message]
2022-07-07 2:30 ` RunningDroid
2022-07-08 18:35 ` RunningDroid
2022-07-09 0:55 ` RunningDroid
2022-07-09 1:50 ` RunningDroid
2022-07-09 3:27 ` RunningDroid
2023-08-06 3:34 ` [ISSUE] [CLOSED] " 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=20220707021412.b2M73sAvGV3DPA9Jx_tWccdrr9w_IqCqhWaG75k3MNs@z \
--to=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).