From: Sarah Morgensen <iskarian@mgsn.dev>
To: Fulbert <fulbert@bluewin.ch>
Cc: 50433@debbugs.gnu.org
Subject: bug#50433: shotcut 21.06.29 missing bin files
Date: Mon, 06 Sep 2021 19:06:31 -0700 [thread overview]
Message-ID: <86h7exi1g8.fsf@mgsn.dev> (raw)
In-Reply-To: <38e80545-027e-f7d3-a544-7931f2a4ebd9@bluewin.ch> (fulbert@bluewin.ch's message of "Mon, 6 Sep 2021 18:39:16 +0200 (9 hours, 20 minutes, 59 seconds ago)")
Hello,
Thanks for your report.
Fulbert <fulbert@bluewin.ch> writes:
> Hello,
>
> shotcut 21.06.29 (guix ce65f2b) appears to have missing bin files. When trying
> to export a video, the status of the task is "failed" inside the GUI, and below
> is the debug message on the terminal.
>
> [Debug ] <MeltJob::start>
> "/gnu/store/qz8nr42ax7k3v0cysmh6afhmy93vvj82-shotcut-21.06.29/bin/melt-7
> -verbose -progress2 -abort xml:%2Ftmp%2Fshotcut-xNVrrX.mlt"
> [Info ] <AbstractJob::onFinished> job failed with 127
>
> And here is the content of the bin directory :
>
> $ ls -la $(dirname $(realpath $(which shotcut)))
> total 3248
> dr-xr-xr-x 2 root root 4096 1 janv. 1970 .
> dr-xr-xr-x 4 root root 4096 1 janv. 1970 ..
> -r-xr-xr-x 2 root root 1840 1 janv. 1970 shotcut
> -r-xr-xr-x 2 root root 1401 1 janv. 1970 .shotcut-real
> -r-xr-xr-x 2 root root 3308600 1 janv. 1970 ..shotcut-real-real
I compared this to the release binaries and there really is just the one
'shotcut' executable. I think you're correct that the '127' error is
due to it not finding an executable, but I think that's happening
because shotcut got double-wrapped (or wrapped incorrectly).
Unfortunately I'm not knowledgeable with qt-wrapping so I can't help any
further, but I hope that helps!
--
Sarah
next prev parent reply other threads:[~2021-09-07 2:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 16:39 bug#50433: shotcut 21.06.29 missing bin files Fulbert
2021-09-07 2:06 ` Sarah Morgensen [this message]
2021-09-07 12:27 ` Fulbert
2021-11-10 2:07 ` Leo Famulari
2021-11-17 2:43 ` Vinicius Monego
2021-12-27 0:10 ` Vinicius Monego
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86h7exi1g8.fsf@mgsn.dev \
--to=iskarian@mgsn.dev \
--cc=50433@debbugs.gnu.org \
--cc=fulbert@bluewin.ch \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).