From: Calandracas606 <Calandracas606@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] codeblocks: doesn't start
Date: Mon, 11 Dec 2023 17:52:12 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47691@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 693 bytes --]
New issue by Calandracas606 on void-packages repository
https://github.com/void-linux/void-packages/issues/47691
Description:
### Is this a new report?
Yes
### System Info
Void 6.5.13_1 x86_64 GenuineIntel uptodate rFFFFFFF
### Package(s) Affected
codeblocks-20.03_6
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
codeblocks application launches
### Actual behaviour
codeblocks application fails to start with error:
codeblocks: macrosmanager.cpp:111: void MacrosManager::Reset(): Assertion `m_RE_Unix.IsValid()' failed.
### Steps to reproduce
1. run "codeblocks" from the terminal
2. crash
next reply other threads:[~2023-12-11 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 16:52 Calandracas606 [this message]
2023-12-12 14:36 ` sgn
2023-12-12 15:01 ` sgn
2023-12-12 15:59 ` [ISSUE] [CLOSED] " sgn
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-47691@inbox.vuxu.org \
--to=calandracas606@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).