sudo chown root chrome-sandbox
chmod 4755 chrome-sandbox
Search Criteria
Package Details: whatsapp-nativefier 2.3000.1017392363-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/whatsapp-nativefier.git (read-only, click to copy) |
---|---|
Package Base: | whatsapp-nativefier |
Description: | WhatsApp desktop built with nativefier (electron) |
Upstream URL: | https://web.whatsapp.com |
Licenses: | custom |
Submitter: | frealgagu |
Maintainer: | frealgagu |
Last Packager: | frealgagu |
Votes: | 135 |
Popularity: | 1.17 |
First Submitted: | 2018-12-14 22:30 (UTC) |
Last Updated: | 2024-10-16 17:54 (UTC) |
Dependencies (7)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libxss
- nss (nss-hgAUR)
- imagemagick (imagemagick-gitAUR, imagemagick-full-gitAUR, imagemagick-fullAUR) (make)
- nodejs-nativefierAUR (make)
- unzip (unzip-natspecAUR, unzip-zstdAUR) (make)
- libindicator-gtk3 (optional)
Required by (5)
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 14 15 16 17 18 19 20 21 22 23 24 .. 26 Next › Last »
mcgll commented on 2019-09-30 16:55 (UTC)
Armag67 commented on 2019-09-30 11:43 (UTC) (edited on 2019-09-30 11:44 (UTC) by Armag67)
Hello,
With today upgrade, /opt/whatsapp-nativefier/resources/app/nativefier.json
change from "tray":false
(or "tray":true
) to "tray":"start-in-tray"
does not work anymore, Whatsapp always opens in window or in full screen, but not in systray only.
tuxitop commented on 2019-09-22 19:54 (UTC)
why are you installing the files with 755 permission. why should those files have execute permission?
nudl3r commented on 2019-09-17 13:23 (UTC)
It does not work anymore because whatsapp web shows a wrong chrome version error when launching whatsapp-nativefier.
Looks like the nativefier build command is outdated. People on GitHub got it working again by adding --clear-cache and using electron version 6.0.9 (-e).
@frealgagu could you please update the PKGBUILD script? Thanks a lot!
jemadux commented on 2019-08-28 10:00 (UTC)
whatsapp-nativefier [21539:0828/125831.858706:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/whatsapp-nativefier/chrome-sandbox is owned by root and has mode 4755. Παγίδα Trace/breakpoint (core dumped)
Raketenjoint commented on 2019-08-20 07:17 (UTC)
When I play voice recordings, I do not get any sound. A sink pops up in pavucontrol but it does not have any volume. Notification sounds are played properly in comparison.
frealgagu commented on 2019-08-04 02:11 (UTC)
@yoburtu Try to use makepkg directly and tell me what happens.
yoburtu commented on 2019-07-03 08:56 (UTC)
The package can't be created:
/tmp/yaourt-tmp-user/aur-whatsapp-nativefier/./PKGBUILD: line 44: 19177 Aborted (core dumped) convert "${srcdir}/${pkgname}.png" -resize "${_size}" "${pkgdir}/usr/share/icons/hicolor/${_size}/apps/${pkgname}.png" ==> ERROR: A failure occurred in package(). Aborting... ==> ERROR: Makepkg was unable to build whatsapp-nativefier. ==> Restart building whatsapp-nativefier ? [y/N]
Freso commented on 2019-05-28 19:34 (UTC)
Remember to bump $pkgrel
when you edit the PKGBUILD—in a way that changes the resulting package—without increasing $pkgver
…
gargakumar commented on 2019-05-26 20:16 (UTC) (edited on 2019-05-26 20:16 (UTC) by gargakumar)
Hi this package is causing issues with some docks apps like plank (icon not showing properly). Package whatsapp-nativefier.desktop reads StartupWMClass=whatsapp-nativefier however window class reported by wmctrl is "whats-app-nativefier-d52542". This apparently confuses plank. Changing the *.desktop file to StartupWMClass=whats-app-nativefier-d52542 fixes temporarily the issue... until next AUR update. Is there a way to properly fix this ? Thanks.
Pinned Comments
matejdro commented on 2023-10-06 04:51 (UTC)
Warning to all existing users: Nativefier is now unmaintained (https://github.com/nativefier/nativefier/issues/1577)
frealgagu commented on 2020-12-05 22:39 (UTC)
I maintain the latest built package at:
https://github.com/frealgagu/archlinux.whatsapp-nativefier/releases/
saulocastelo commented on 2020-03-29 10:46 (UTC)
Hey guys,
I created the original fix.
And now I share another way to use whatsapp web on nativefier. No code injection required.
Pressing ctrl+shift+i (on Linux) and the Devtools window will open. Then click on Application -> Service Workers And check the option Bypass for network.
Now press ctrl+r to reload. And ctrl+shift+i to close the Devtools.
Whenever you open your whatsapp the problem will occur, but since the Bypass for network option has already been enabled, you only need to press ctrl+shift+i (open devtools), ctrl+r (reload), ctrl+shift+i (close devtools)
@frealgagu, thanks for your work. This package was in my list as one of required apps to be installed after install Arch. I saw your last update ( document.querySelector("a[href='https://support.google.com/chrome/answer/95414']") ), NICE/GREAT/GOOD!
Another way to do the same in 2 lines: document.querySelector("a[href='https://support.google.com/chrome/answer/95414']") && navigator.serviceWorker.getRegistration().then(r => r.unregister() && document.location.reload());