Package Details: franz 1:5.10.0-1

Git Clone URL: https://aur.archlinux.org/franz.git (read-only, click to copy)
Package Base: franz
Description: Free messaging app for services like WhatsApp, Slack, Messenger and many more.
Upstream URL: https://meetfranz.com
Licenses: Apache
Submitter: 314eter
Maintainer: ItachiSan
Last Packager: ItachiSan
Votes: 146
Popularity: 0.000113
First Submitted: 2017-10-26 11:34 (UTC)
Last Updated: 2023-09-11 20:46 (UTC)

Dependencies (5)

Required by (0)

Sources (3)

Pinned Comments

ItachiSan commented on 2019-10-07 08:26 (UTC) (edited on 2021-09-08 07:58 (UTC) by ItachiSan)

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 :)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 19 Next › Last »

ItachiSan commented on 2019-10-07 08:26 (UTC) (edited on 2021-09-08 07:58 (UTC) by ItachiSan)

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 :)

ItachiSan commented on 2019-10-07 08:18 (UTC)

@xored I tested it and it was working. As it uses native Node.js stuff, you have to rebuild it every time there is a Node.js / Electron update.

Actually, thanks for pointing this out, should do a pinned comment for this.

xored commented on 2019-10-06 15:33 (UTC)

As usual, broken again as on very single update :)

ItachiSan commented on 2019-08-24 09:04 (UTC)

Hi @dreieck

  1. That's impossible as many packages are not properly Arch-packaged, thus npm is the only way to install them.
  2. That is more reasonable; will do when I come back from my holidays.

dreieck commented on 2019-08-23 16:00 (UTC)

It seems that it downloads stuff in build(). This should not happen, every data needed to build the package should already be there during build(). Please download everything needed with the source-array or, as an exception if that is not possible, in prepare().

ItachiSan commented on 2019-08-12 08:02 (UTC)

Hi @everyone, Was on a business trip until Saturday. Will update the package ASAP.

plooff commented on 2019-07-12 14:00 (UTC)

Thanks everyone ! You're the best !

ItachiSan commented on 2019-07-11 13:12 (UTC)

Hey, @AG_Caesar thanks for the tip, will do it soon. @everyone sorry for the delay in updating this but life is quite busy recently!

AG_Caesar commented on 2019-07-10 12:30 (UTC)

@plooff Change all occurrences of electron to electron4 (remember franz.sh) and it will work again :) Just changed it in my ferdi fork bould and it works great

plooff commented on 2019-07-02 10:57 (UTC)

Does franz still works ? It stopped working since the package electron refers to the version 5 and electron version 4 is electron4.