| Git Clone URL: | https://aur.archlinux.org/zapzap-git.git (read-only, click to copy) |
|---|---|
| Package Base: | zapzap-git |
| Description: | WhatsApp desktop application written in Pyqt6 + PyQt6-WebEngine |
| Upstream URL: | https://github.com/rafatosta/zapzap |
| Licenses: | GPL3 |
| Conflicts: | zapzap |
| Provides: | zapzap |
| Submitter: | bordam |
| Maintainer: | alllexx88 (AutoUpdateBot) |
| Last Packager: | AutoUpdateBot |
| Votes: | 1 |
| Popularity: | 0.000023 |
| First Submitted: | 2022-09-25 10:48 (UTC) |
| Last Updated: | 2026-05-17 09:26 (UTC) |
I just had some qt6 updates and even after a rebuild I am getting
GBM is not supported with the current configuration. Fallback to Vulkan rendering in Chromium.
Segmentation fault (core dumped) zapzap
Workround is
QT_QUICK_BACKEND=software /usr/bin/zapzap --disable-gpu
Since python has recently been upgraded to 3.13, you need to rebuild the package if you installed it last before the upgrade, e.g., with yay (thanks @marco.righi) you can:
yay -S zapzap-git --rebuildtree --noconfirm --rebuild --sudoloop
P.S. @gesh, sorry, have missed the notification. I wasn't being worried about the URL change, since it's the original author, AND the original URL before it was moved to an org repo.
A bit nervous at the URL change -- can't find any public reference to it. Moreover -- usually, these are from a private repo to an org repo. The only reference I could find is in f645c2a3f26cc80af45d11299432e9d1ced81bd8 in the new upstream, though there's been activity in the old upstream up until this April, so I'm suspicious. Also not helping matters is that the history has been rewritten -- you'd expect such a move to perhaps fork the history, but not rewrite it. Instead, checking with
root () { git rev-list --max-parents=0 "$1"; }
git range-diff $(root main)..main $(root new/main)..new/main \
| grep --only-matching '^...: ....... . ...: .......' \
| sed 's/.* \([^ ]\) .*/\1/' | sort | uniq -c
I see the histories are quite divergent. Indeed, I can only find 4 commits in common between the two -- and even then they've all been edited (180 more commits appear in the old upstream, and 872 in the new upstream). Moreover, it seems upstream changed authorship of some commits instead of just writing a .mailmap -- indeed, diffing git shortlog -s -n $branch | cut -f2 | sort, I see 12 authors in common, 14 only in the new upstream, and 2 only in the old upstream (11, 14, 2 if counting by emails).
All in all, a pretty suspicious-looking situation. I can see a charitable explanation -- perhaps the new repo used to be the main author's private repo, from which they'd send squashed histories to the main repo for a cleaner history? I don't know enough about the project's development history to be able to say, but it's enough not to make me trust it anymore without further contextualization.
@gesh thanks a lot, fixed.
Judging by other such files on my system, isn't the metainfo file supposed to be installed to /usr/share/metainfo, not /share/metainfo? This is the only package installing to /share on my system
A message from the developer:
Autostart will not work and there are some settings when running outside of flatpak that need to be removed. It won't take long to release the fix for that.
@musiclover Just like in zapzap, the zapzap-git package is supposed to require python-setuptools in makedepends, too.
Thanks in advance!
Pinned Comments
alllexx88 commented on 2024-12-24 09:09 (UTC)
Since python has recently been upgraded to 3.13, you need to rebuild the package if you installed it last before the upgrade, e.g., with
yay(thanks @marco.righi) you can:P.S. @gesh, sorry, have missed the notification. I wasn't being worried about the URL change, since it's the original author, AND the original URL before it was moved to an org repo.