Search Criteria
Package Details: freetube 0.17.1-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/freetube.git (read-only, click to copy) |
|---|---|
| Package Base: | freetube |
| Description: | An open source desktop YouTube player built with privacy in mind. |
| Upstream URL: | https://freetubeapp.io |
| Licenses: | AGPL3 |
| Submitter: | picokan |
| Maintainer: | picokan |
| Last Packager: | picokan |
| Votes: | 42 |
| Popularity: | 0.58 |
| First Submitted: | 2020-10-02 22:19 (UTC) |
| Last Updated: | 2022-08-12 09:05 (UTC) |
Latest Comments
picokan commented on 2022-05-15 13:28 (UTC)
@dwango This doesn't seem to be a freetube specific error. It could be related to these problems:
https://alt.os.linux.mageia.narkive.com/ARnQCpG3/xdg-settings-error-message-in-chromium-re-zoom#
https://bbs.archlinux.org/viewtopic.php?id=256377
dwango commented on 2022-05-10 22:39 (UTC)
Does not start and gives the following exit message:
xdg-settings: default-url-scheme-handler not implemented for xfceAndyRTR commented on 2022-04-20 18:04 (UTC)
I also suggest to stick to the version that upstream suggests and supports even somehting newer looks basically working (and might fail somewhere else). When it fails to start after your last attempt make sure there's no hanging electron process pending. I had to kill the hanging ps.
je-vv commented on 2022-04-20 01:56 (UTC) (edited on 2022-04-20 01:56 (UTC) by je-vv)
Actually freetube is working just fine with system electron 17, so I see no reason to go with an even older electron version.
hedgepigdaniel commented on 2022-04-20 00:11 (UTC)
You need to use Electron 16, not 17. You can check the required version in the Freetube sources, for example for the current 0.16.0: https://github.com/FreeTubeApp/FreeTube/blob/v0.16.0-beta/package.json#L111
And even if it doesn't open, there might be other causes for that which should be investigated separately. I'd suggest to start by using the correct version of electron that Freetube has been tested with, and then investigate other problems.
inototen commented on 2022-04-18 13:31 (UTC) (edited on 2022-04-18 14:07 (UTC) by inototen)
@PutridPete where exactly should I change for electron17? I changed it in the PKGBUILD and the in freetube.sh but nothing changed, it still not opening. I've tried with other electron versions too, but have the same result.
PutridPete commented on 2022-04-04 23:08 (UTC) (edited on 2022-04-04 23:09 (UTC) by PutridPete)
What I did was edit the PKGBUILD and scripts so it pulls a dependency on electron17 package and then rebuilt it. Make sure freetube.sh contains
exec electron17 /usr/lib/freetube/app.asar "$@"instead of justelectronwithout the 17. Works fine for me thus far.golden_lemur commented on 2022-04-04 20:44 (UTC)
freetube 0.16.0-1 does not work for me in electron v18.0.1
yochananmarqos commented on 2022-04-04 19:35 (UTC)
@MattTriesLinux: It works fine with
electron17.MattTriesLinux commented on 2022-04-04 19:14 (UTC)
https://github.com/FreeTubeApp/FreeTube/issues/2163#issuecomment-1087645677electron 18 seems to be giving issues to FreeTube and making it impossible to open it, as per suggestion of the dev this package should switch to only using the supported electron version (16)hedgepigdaniel commented on 2022-03-29 13:24 (UTC)
@pikohan I resolved the issues by changing flags related to ozone/wayland (not sure that there was an issue in freetube in particular).
The latest release of electron is now 17, and that does not work for me (with my flags related to ozone/wayland) - but the officially supported electron16 does.
You can see freetube-wayland package for an example of fixing the electron version. It's a simple matter of replacing "electron" in the dependency and launch script with "electron16".
picokan commented on 2022-02-17 18:52 (UTC)
@hedgepigdaniel So far I've been letting it go with electron's latest version, but there has been widespread problems with a major update of electron breaking freetube and I might go with your suggestion. However, if you and DarknessKiller both can't use it with the officially supported electron 16, something is off. Can you use the freetube binary from the website? If not, what errors does it give you? These might be good things to report upstream.
hedgepigdaniel commented on 2022-02-12 03:57 (UTC)
In case it isn't clear: I also can't open the app with Electron 16.
hedgepigdaniel commented on 2022-02-12 03:57 (UTC) (edited on 2022-02-12 04:09 (UTC) by hedgepigdaniel)
@pikohan could you change the dependency (and binary in freetube.sh) to electron16 rather than electron?
Generally apps are not compatible with different major versions of Electron, because that's when breaking changes are made in Electron. You can check the version of electron that Freetube is tested with by looking at the dependency in package.json. For example in this version 0.16.0 its 16 (not later version when they are released): https://github.com/FreeTubeApp/FreeTube/blob/3ec646870963f6a27cbfa6d49fe12ea3b659c6a4/package.json#L111
It might work sometimes with a different version but really it's on Freetube to test/update to the latest Electron.
EDIT: I was wrong to say the latest requires electron15 - its actually electron16. But still good to make that change so that when electron17 is released in Arch it doesn't break.
DarknessKiller commented on 2021-11-25 00:36 (UTC)
After the electron update I can't open the app. It was solved rebuilding the app using electron15 and replacing it in the pkgbuild.
picokan commented on 2021-11-24 21:53 (UTC)
@DarknessKiller What problems are you having that could be because of electron 16?
yochananmarqos commented on 2021-11-24 21:08 (UTC)
@DarknessKiller: It works fine for me.
DarknessKiller commented on 2021-11-24 20:27 (UTC)
Electron was updated to v16 and isn't supported by freetube.
yochananmarqos commented on 2021-10-20 01:39 (UTC) (edited on 2021-10-20 01:40 (UTC) by yochananmarqos)
@G3ro: Oops. I fixed the typo in my paste.
G3ro commented on 2021-10-19 20:24 (UTC)
@yochananmarqos
I tried your proposed changes and it shows an error when starting "freetube": "Error launching app Unable to find Electron app at /usr/lib/freetube/app.asar
Cannot find module '/usr/lib/freetube/app.asar' Require stack: - /usr/lib/electron13/resources/default_app.asar/main.js "
I notice that the created package does not include "app.asar", so the following line does not seem to work the right way: "install -Dm644 build/linux-unpacked/resources/app.asar "$pkgdir/usr/lib/$pkgname" "
In the previous package "app.asar" is a subsidiary of "/usr/lib/freetube".
yochananmarqos commented on 2021-10-18 20:44 (UTC)
yarnis now used to fetch dependencies/usr/share/licenses/common/, no need to install it againfreetube.shshould runexec electron13 /usr/lib/freetube/app.asar "$@", see Electron package guidelinesExample PKGBUILD
je-vv commented on 2021-09-22 21:47 (UTC)
Thanks @picokan, yes, after finally getting the newer electron13, things work back.
picokan commented on 2021-09-22 10:17 (UTC)
@je-vv The harfbuzz update is the culprit: https://github.com/harfbuzz/harfbuzz/commit/d700646c33af53afcabe564e9943565d58e1192a.
They removed legacy code, and the function electron is complaining about is one of them. However, FreeTube is still working for me, and I did have an electron13 update yesterday when you say you haven't had one since the 14th of September. You may want to try to update electron13 by changing to a different mirror if the one you are on still hasn't gotten that update.
It's still weird that you got the harfbuzz update without the electron13 update, but all you need is to update to fix this.
je-vv commented on 2021-09-22 03:32 (UTC)
@picokan, after Today's upgrade (I upgrade every day or so), freetube stopped launching:
I rebuilt it, just in case that would fix it, but it didn't, I kept having the same issue, :( BTW, weird enough, electron13 didn't upgrade, it hadn't since Sept 14th. From yesterday, I got upgraded:
And from Today's upgrade:
I can't see what package upgrade could have broken freetube, perhaps the gtk3 or harfbuzz upgrades, no idea...
At any rate, not sure what can be wrong, any hints on how to fix it? As mentioned, rebuilding doesn't help, :(
picokan commented on 2021-09-10 08:14 (UTC)
That problem must come from the combination of AUR helper bugs and Manjaro not having an electron13 package. Using only makepkg on Arch, the PKGBUILD pulls the correct electron13 package from community and installs.
If this is happening to you, you should consider reporting this bug to your AUR helper's issue tracker.
je-vv commented on 2021-09-09 22:18 (UTC)
hmm, I do have the "community" provided electron13, essentially because "element" also depends on "electron13", and when getting the "freetube" upgrades, there's NO attempt whatsoever to grab electron13 from AUR. Perhaps what some are experiencing is due to the AUR helper of choice? I use "aurutils", which does things pretty close to the manual process of makepkg...
cb474 commented on 2021-09-09 20:24 (UTC)
My system doesn't have electron14 installed yet either. But I don't understand why the pkgbuild for freetube depends on a version of electron13 in AUR, when there is still a version of electron13 available in the community repo. Why not use that version?
hazardfrog commented on 2021-09-09 07:28 (UTC)
I've the same problem as cb474. I suspect that this happens because our official electron package is still on version 13.x and this package requires the AUR package electron13 and does not check the version of the official electron package. I'm using Manjaro 21.1.2, which may explain why I don't have electron 14 installed.
cb474 commented on 2021-09-08 21:57 (UTC) (edited on 2021-09-08 21:57 (UTC) by cb474)
When I try to build I get this error:
Error: Failed to commit transaction: conflicting files: - electron13-bin: /usr/bin/electron13 already exists in filesystem (owned by electron)
If electron13 is a dependency and I already have electron13 on my system, then why does the Freetube pkgbuild try to install electron13 separately from AUR and fail?
picokan commented on 2021-09-08 08:37 (UTC)
Sorry for the multiple updates in quick succession, but Arch very recently changed the electron package to be using version 14, which has caused multiple bugs in Freetube.
The default version of electron in Freetube (e.g. for pre-compiled binaries) is likely to be changed back to 13, and I'm also changing the diff files and dependencies here to use it.
6543 commented on 2021-05-19 13:09 (UTC)
deleting the .npm or node_modules ... and so on did not have any efect, i updated & build the freetube-bin myselfe ... this works
picokan commented on 2021-05-19 08:22 (UTC)
@willemw I understand, thank you for pointing that out.
willemw commented on 2021-05-19 06:51 (UTC)
@je-vv: Hi. Both freetube-bin and freetube-git already define that they cannot be installed together (side-by-side) with another freetube package that provides "freetube". It is redundant to define that exclusion again the other way (for packages providing "freetube-bin" and "freetube-git") in the freetube package.
je-vv commented on 2021-05-19 06:39 (UTC)
@willemw, why? I might want to try one instead of the other, for some reason, and I find it pretty convenient uninstalling the prior one installed prior to installing the new package. Don't you think? Also, they might (I'm not sure) share owned files and dirs, which without uninstalling, for sure might be problematic...
willemw commented on 2021-05-19 06:04 (UTC)
freetube-bin, freetube-git in conflicts are redundant.
je-vv commented on 2021-05-18 22:55 (UTC)
@Popolon, I guess that's on buil, right? If so, perhaps you can try newer 0.13.0, and before building, cleaning ~/.npm...
je-vv commented on 2021-05-18 22:53 (UTC)
@6543, I'm also building on artix, and I have no issues building. Could it be you have old js libs in ~/.npm that are affecting your build? Perhaps removing entirely that dir might help if it exists.
6543 commented on 2021-05-18 21:11 (UTC) (edited on 2021-05-18 21:17 (UTC) by 6543)
cant build this package :/
Popolon commented on 2021-05-07 10:31 (UTC)
I found this file instead not sure this is the same:
picokan commented on 2021-05-01 14:23 (UTC) (edited on 2021-05-01 14:50 (UTC) by picokan)
The most recent error that kept Freetube from compiling was due to a new version of nodejs breaking something. For the mean time, freetube and freetube-git will use node-lts-fermium as a dependency instead.
picokan commented on 2021-04-26 09:34 (UTC)
@Renfield Compilation is failing on my machine even when compiling manually. This looks like it's a bug from the program itself, I'll try contacting the developer.
Renfield commented on 2021-04-25 14:01 (UTC)
I'm getting a lot of errors with this package. Here are the first of them:
je-vv commented on 2021-03-31 00:08 (UTC)
@picokan, could you please use
--cache "${srcdir}/npm-cache"on every npm command, so that the FS doesn't get polluted when building? Thanks !alium commented on 2021-03-30 08:09 (UTC)
you can´t remove system´s electron from PKGBUILD and after call system´s electron to run freetube ;-)
users must install it or you should remove call electron at start ;-)
AndyRTR commented on 2021-03-20 10:45 (UTC)
'electron' runtime dependency is missing. Freetube fails to start if it's not installed.
picokan commented on 2021-03-15 19:51 (UTC)
@marcih Looking at it again, I see that the
npm ERR! cc: error: unrecognized command-line option ‘-m64’indicates that, for whatever reason, electron's trying to build an x86_64 binary, which won't work on your aarch64 cpu. I'm very curious, but I don't have a cpu to test if this also fails on building from the git repo. I don't know why it wouldn't work using the PKGBUILD, I don't think I changed anything that would force an x64 build.marcih commented on 2021-03-14 14:14 (UTC) (edited on 2021-03-14 14:15 (UTC) by marcih)
@picokan Thanks for the update! As for my build failure, I have made no changes to your PKGBUILD. I tried clean building 0.12.0-2 just now with the same result:
picokan commented on 2021-03-13 19:31 (UTC) (edited on 2021-03-13 19:31 (UTC) by picokan)
@marcih Thank you for all of the information. Unfortunately, I don't know what's causing
sh -c node-gyp rebuild. If you made changes to the PKGBUILD to fix some of my errors you may have accidentally written something that leads to that error. As for the sed command, the purpose was to have the freetube package use the system electron if available, and I thought that sed was necessary as I saw it being used on one of the packages mentioned here. After re-reading it and a bit of testing, I've changed the way it's done to something that won't stop working as intended as soon as Freetube changes it's target electron version or the system electron package is updated. Lastly, since this is already using makepkg, I don't think telling makepkg to make a pacman package of the pacman package electron made will work, but I haven't tried. The rest of the recommended changes have been applied, thank you to all who helped me.ZorinArch commented on 2021-03-08 09:10 (UTC)
update line 15 to
source=(https://github.com/FreeTubeApp/FreeTube/archive/v$pkgver-beta.tar.gzmarcih commented on 2021-03-07 16:00 (UTC)
Again, FYI, freetube has moved to electron 12, making line 23 of the PKGBUILD obsolete - in fact: a) freetube hasn't used electron v11.1.0 since 0.10.0; b) the regex itself is written wrong, the comma should be after the double quotes.
I don't know what the reasoning was to removing the build dependency on electron and whether it is still necessary, but if you want to keep it removed then line 23 ought to be:
sed -i 's@"electron": "^12.0.0",@@g' "$srcdir/$_pkgname-$pkgver-beta/package.json"Also, question: since the build system can output what seems to be a pacman package directly (see "package-only-necessary.diff"), can we not somehow use that?
AndyRTR commented on 2021-03-07 12:00 (UTC)
New release builds well in a clean chroot on x86_64. Please add %U to .desktop file as suggested. I've confirmed this working to open links from Firefox using privacy redirect extension.
marcih commented on 2021-03-07 11:40 (UTC) (edited on 2021-03-07 15:27 (UTC) by marcih)
0.12.0-1 doesn't build for me on Manjaro aarch64:
Any ideas?
marcih commented on 2021-03-07 11:11 (UTC)
I appreciate the addition of ARM to supported architectures but please note that, in context of a PKGBUILD, "arm" is not a catch-all for all ARM arches, it defines specifically armv5; building natively on a PinePhone (aarch64) therefore still complains about unsupported architecture.
See also: https://wiki.archlinux.org/index.php/PKGBUILD#arch
marcih commented on 2021-03-07 11:03 (UTC) (edited on 2021-03-07 11:04 (UTC) by marcih)
FYI, in order to handle "freetube" URI schemes properly, the "Exec" entry should have a "%U" after the command, see desktop file from upstream deb pacakge:
Autodidaddy commented on 2021-03-06 16:36 (UTC)
Doesn't build;
npm ERR! semver.simplifyRange is not a function
malcolm commented on 2021-02-15 03:08 (UTC) (edited on 2021-02-15 03:08 (UTC) by malcolm)
The freetube.desktop file of the maintainer builds has the MimeType field, could you add it as well?
greektex commented on 2021-01-22 20:54 (UTC)
@picokan Yes, I can confirm this was an issue with the app itself, and it is resolved with the next release, 0.11.2 beta, as reported in this ticket:
https://github.com/FreeTubeApp/FreeTube/issues/948
picokan commented on 2021-01-18 12:03 (UTC) (edited on 2021-01-18 12:04 (UTC) by picokan)
I'm sorry, "run makepkg as you normally would" is incorrect, you need to use the -e flag to not re-extract the source code and overwrite your changes.
picokan commented on 2021-01-18 11:45 (UTC)
@greektex This is a bug on the developer side. For some reason his scripts had a hiccup and failed to mark this version as 0.11.1 in the package.json file. You can fix it manually by running makepkg -o, which will download only the source code and apply patches. Then go into the src directory and change the version in package.json to be 0.11.1 and run makepkg as you normally would.
greektex commented on 2021-01-17 16:44 (UTC)
I applied the recent update, but the app identifies itself as version v0.11.0 Beta in the "About" section and I get a notification on the starting page that I should update to v 0.11.1 Beta.
However, I would think that this is the version that I have installed?! Here is the output during makepkg:
je-vv commented on 2020-12-27 00:23 (UTC)
Thanks a lot @picokan !
picokan commented on 2020-12-26 16:42 (UTC)
I apologise for the recent inconvenience and frequently updating freetube and freetube-bin, but the way it was using the system electron before was poor and I thought the change was worth it. You should note that with this update the package size went from ~200MB to ~100MB and that it will now share the electron package with other programs like element-desktop.
je-vv commented on 2020-12-25 01:19 (UTC)
@picokan, nothing broke, thanks a lot !
picokan commented on 2020-12-24 19:07 (UTC)
I've added the modifications to use the system electron according to the tips I've been given. Please test and warn me if something broke.
je-vv commented on 2020-12-13 22:46 (UTC)
BTW, according to the answer on https://github.com/FreeTubeApp/FreeTube/issues/865, what could be tried is modifying "package.json" so that the electron version matches the system one. Haven't tried it yet, but sounds like something doable, :)
je-vv commented on 2020-12-13 00:26 (UTC)
Perhaps someone who knows can contribute get this package to use system electron, and as many system deps as possible, to prevent it downloading and building/using non system packaged sw... I have no clue how it can be done, but there's slack-electron and jitsi-desktop, which, as examples, use system electron. This would be just great. Thanks ! I made the question on https://github.com/FreeTubeApp/FreeTube/issues/865, but I doubt upstream would be interested on helping about this, :)
picokan commented on 2020-11-15 15:10 (UTC)
@rebal28 What extension in particular are you talking about? Right now, the only supported extension that I know of is Privacy Redirect. Support for the other Freetube redirect extension was probably dropped, as the developer was only supporting it because Freetube wasn't in Privacy Redirect until recently.
rebal28 commented on 2020-11-09 18:14 (UTC)
Are there any solution to the firefox/chromium redirect extension?
just adding
MimeType=x-scheme-handler/freetube;to the desktop file did not help.it still gives me an error
Unable to create io-slave. klauncher said: Unknown protocol 'freetube'.picokan commented on 2020-10-31 22:20 (UTC) (edited on 2020-10-31 22:21 (UTC) by picokan)
@satcom886 It's not nonsense. The developer of FreeTube made it this way, that's all there is to it. He could have it like you said, but I don't specifically know if that change would be easy or not.
@icewind That dependency is very temporary, only to have a hacky patch to make searches work better since the modules were disrupted by a recent Youtube update. It should not be needed very soon.
satcom886 commented on 2020-10-31 19:43 (UTC) (edited on 2020-10-31 19:44 (UTC) by satcom886)
I'm sorry if what I'm saying here is nonsense, I know almost nothing about JS and Electron.
Is it really necessary to download
electronwithnpm? Why not haveelectronas a dependency. It's already a package in Arch...icewind commented on 2020-10-23 13:35 (UTC)
requires git as makedepends (a git npm dependency is used)
alium commented on 2020-10-20 20:55 (UTC)
some feedback :-) https://paste.artixlinux.org/view/a12266f3
je-vv commented on 2020-10-03 21:29 (UTC) (edited on 2020-12-25 01:22 (UTC) by je-vv)
@logos, you can take a look at both PKGBUILs. The <...>-bin downloads a binary package, whereas this one downloads the tarball released source and builds the binaries from that source. Not so relevant to your question, at this point the <...>-bin AUR package is out of date, but nothing a PKGBUILD upgrade from the dev/maintainer doesn't solve...
logos commented on 2020-10-03 16:09 (UTC)
What's the difference between this and freetube-bin package?
picokan commented on 2020-10-03 08:51 (UTC)
My mistake, I copied a lot from the freetube-git package and I forgot to change that.
je-vv commented on 2020-10-03 02:09 (UTC)
Not that it bothers me, but why keeping git as a dependency, if this package thankfully uses the latest released tarball?