Package Details: popcorntime 0.4.5-1

Git Clone URL: (read-only, click to copy)
Package Base: popcorntime
Description: Stream movies from torrents. Skip the downloads. Launch, click, watch.
Upstream URL:
Licenses: GPL3
Submitter: ItachiSan
Maintainer: ItachiSan
Last Packager: ItachiSan
Votes: 52
Popularity: 0.114099
First Submitted: 2016-03-01 20:36
Last Updated: 2021-07-09 12:55

Pinned Comments

ItachiSan commented on 2018-07-24 21:01

You are free to report issues regarding the packaging here! Please read all the info of this message as they include quite some information.

Be aware that sometimes the package will fail to build because of outdated upstream and updated dependency, which will require me some time to test and solve the problem.

I do also have life stuff, packaging is a free-time activity.

I believe I have an issue that is Arch-related and not upstream related

I too found out only recently this way to debug the app (as of: 2021-06-13), which helps immensely.

Whenever reporting here or on the Github issues, please provide the output of the command:

popcorntime --enable-logging=stderr

In case you are forwarding the log to a file, as the log entries will end in stderr, remember to redirect stderr to stdout

popcorntime --enable-logging=stderr 2>&1 > my_output.log
Info regarding the package
  1. The package uses the sources available at: I am aware of the different clones and branches; I do still believe that this code is acceptable (not affected itself from malware).

  2. This package uses a custom NW.js build provided from the PopcornTime team; essentially, a custom compiled browser. While this won't affect you as it should be used only within the app, you are here informed that I have no power over this component.

  3. The above point stands as the official NW.js Chromium source lacks multiple modern codecs, such as AC3 and HEVC (H.265).

  4. Earlier this package used the official nw.js toolchain provided available at and the prebuilt FFmpeg library with additional codecs available at . This was because the nw.js toolchain provided by the PopcornTime team can not be proven as non-malware easily. However, due to point 3, this approach was reverted. You are free to use an older PKGBUILD with the appropriate variable updates to re-enable this, however you will miss support for recent codecs.

  5. In addition, the PKGBUILD won't point to the Git release reference but will also include important commits, for e.g. security reasons or providers changes.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

je-vv commented on 2021-07-24 01:58

One thing I noticed though, is that the AUR popcorntime package is using commit:

Whereas the 0.4.5 release is using commit:

The one used by the package, on master, is around 35 commits ahead of the one for release 0.4.5. Could it be @ItachiSan that you got an unstable commit?

Is it possible to use the released tarball instead of git commits? And if in need grab specific commits/patches for specific fixes, then do so? Like, for 0.4.5, use instead of a git commit:

And additional commits as patches as needed? At this point, the current commit used by the AUR package is not the one for 0.4.5, neither top of master. There might be some fixes ahead of it for its current behavior...

Thanks !

je-vv commented on 2021-07-24 01:39

It seems the issue from popcorntime is actually not being able to read at leas some of the configurations, such as the custo APIs... I installed popcorntime-bin, and the issue doesn't show up with popcorntime-bin, which means the configs seem fine, but I pretty much prefer using Arch/Artix built packages than *-bin ones. I have no clue why the built popcorntime can't read the configurations/preferences...

je-vv commented on 2021-07-13 05:53

@ItachiSan, it seems whenever starting popcorntime after the last upgrade (to 0.4.5-1), the license agreement is always shown. Also the custom API settings (required to specify * are always lost, so popcorntime can't be used (the change to the custom apis require popcorn to be restarted), since on start, the prior settings are lost. Any ways to fix or work this around? Thanks !

je-vv commented on 2021-06-21 00:56

Thanks @ItachiSan, actually I realized the api server was already an option one could select for movies and series. So pretty cool. Unfortunately it doesn't show up for anime, neither it works writing it as the server for anime. Anime seems to remain unreachable with whatever default server or with Any suggestion?

je-vv commented on 2021-06-15 23:00

Thanks @ItachiSan, I though that was part of the changes incorporated from the RU sources, hehe... My mistake. I'll try changing the API server URLs to and testing, later, when having some time, and then report back...

Thanks again !

ItachiSan commented on 2021-06-15 21:21

@je-vv you may be interested in this:

je-vv commented on 2021-06-15 01:52

Thanks @ItashiSan. Now the GUI shows up, :)

Unfortunately, it doesn't connect to anything, the GUI doesn't offer anything, and it keeps trying connecting somewhere but it remains trying forever, :(

So no joy with popcorntime yet...

ItachiSan commented on 2021-06-14 09:29

Update is out! This should fix all the recent issues.

The main problem (the disappeared GUI) was because of the nwjs step within gulpfile.js, which directly calls npm in order to check the required dependencies.

This worked well until npm v.7 which changed its npm ls behaviour, from showing all the dependencies to only the root level ones. This was fixed by adding --all=true to the npm command via the Gulp fixes patch.

I will also add as an edot to the pinned comment a way to output good logs :)

ItachiSan commented on 2021-06-13 22:48

@je-vv , I've tried to build as of now but got some major issues.

However, I have a gut feeling of where the issue lies.

Will update here soon (and hopefully also the package)

je-vv commented on 2021-06-10 22:21

@ItachiSan, btw, there's no need to patch to adjust the URLs anymore, that has been commited by upstream already:

And, the commit:

But, I believe top of master is way better, the last commit:

So, perhaps you just sync with latest commit on master, and you don't need to patch anymore...