Arch Linux User Repository

If you have troubles, read this message!

Please go to the relevant section of this comment in order to make both your and my life easier :)

1. Errors when starting the app like: the chat area is all blue
2. (Obsolete) I get an error when upgrading packages

Now, to the resolutions!

1. The app opens but I got a blue screen and nothing more / The app refuses to start / ...

The package depends on Node.js native stuff which are compiled at build time, which makes it break on Electron updates.

With a PKGBUILD between 2020-11-15 till 2021-09-08, you should always have gad a correct matching between Electron and Franz versions.

After 2021-09-08, while the Electron packages follows just the official Arch package dependency, as it is based on not-rolling versions (AKA following a specific Electron branch) breakages are unlikely.

If you would like to help me on this, whenever you have problems starting it, do the following:

1. Open Franz
2. Franz is broken: maybe for a recent update?
3. Reinstall Franz from AUR; this will make it rebuild the native blobs
4. Re-open Franz
5. Franz should work fine; if so, it was a Node.js/Electron/else update problem

If the above steps help you, report the package as outdated here and write in the comment something like:

Electron update broke Franz

If you have some other issues, you should open the developer tools and give me its output, in addition to what is your environment, so I can figure out if it is a packaging issue (my job to fix) or an upstream/code issue (their job to fix); in the second case, I will open a bug request and mention it in a comment, so that you can track it.

2. (Obsolete) I cannot upgrade Electron

The following resolution is not valid since 2021-09-08, it is kept for historic purposes

This is intended; since the PKGBUILD for Franz 5.5.0-4, the package marks as dependency a version-locked Electron package in order to avoid issues with binary modules over upgrades.

In such scenario, you should, assuming _electron="electron" in the PKGBUILD (meaning the Electron used is bundled in the package electron):

1. Mark this package as out of date
2. Do you regular updates with: pacman -Syu --ignore electron

If you want however to upgrade the Electron package, do

1. Upgrade the electron package with pacman -S --assume-installed electron=FRANZ.REQUIRED.VERSION electron
2. Rebuild Franz if needed

Hope this was a good explanation, might get updates if I missed something :)

Same error as @confus and @abdulhakeem. My locale is en_US.UTF-8 and I'm using the original Node/npm provided by Arch, not shadowed by n/nvm/asdf.

Doesn't work, I get the same locale (C.UTF-8) error that confus posted. I also have python2 and git installed. Franz4-bin works fine but I'd really like to use the updated version... :'(

I also get this cnnot change locale (C.UTF-8)` nonsence. Complete log here: http://paste.ubuntu.com/26036541/ I have python2 and git installed. Also beta 14 is out.

Hi, as I already wrote in the old package repository (franz-bin) the packages git and python2 have to be added as makedepends to build this package in a clean chroot environment. (see https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot ) When these are missing the following errors occur: - for git [code] [1/4] Resolving packages... [2/4] Fetching packages... error Couldn't find the binary git info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. [/code] - for python [code] gyp info using node-gyp@3.6.2 gyp info using node@9.2.0 | linux | x64 gyp ERR! configure error gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable. gyp ERR! stack at PythonFinder.failNoPython (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:483:19) gyp ERR! stack at PythonFinder.<anonymous> (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:397:16) gyp ERR! stack at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:16) gyp ERR! stack at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29) gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16 gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:42:5 gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/mode.js:8:5 gyp ERR! stack at FSReqWrap.oncomplete (fs.js:166:21) gyp ERR! System Linux 4.13.12-1-ARCH gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /build/franz/src/franz-5.0.0-beta.13/node_modules/@paulcbetts/cld gyp ERR! node -v v9.2.0 gyp ERR! node-gyp -v v3.6.2 gyp ERR! not ok [/code]

I moved to this package from franz-bin and I had a problem with the locale as this package requires en_US.UTF-8, otherwise npm will fail. If someone else has this problem when moving to this package, just install en_US.UTF-8.

I added the gconf dependency. I don't think the other dependencies are really necessary. I will add you as co-maintainer.

Yes but currently the franz-bin package provides the same as this package plus the history of franz 4. So either we delete my package and you update this one (I added some depends which are needed), delete yours and rename mine or ask a TU to merge them. Don't you think? Just trying to avoid confusions for the users when they see 3 packages. I am fine with all options ;)

From https://wiki.archlinux.org/index.php/Arch_User_Repository#Rules_of_submission: "Submitting binaries should be avoided if the sources are available" Binary packages are useful if there are no sources available (e.g. franz4), but some people don't want to download and install binaries from untrusted sources. Since franz5 became open source, we can now download the sources and compile them locally.

Hi there, I am maintaining the original franz-bin package and wondering why this package is needed (We have currently 3 different packages for franz which might confuse users).

a compiled linux binery version (franz_5.0.0-beta.13_amd64.deb) is provided by developer. why not use it?