Package Details: beeper-latest-bin 1-1

Git Clone URL: https://aur.archlinux.org/beeper-latest-bin.git (read-only, click to copy)
Package Base: beeper-latest-bin
Description: metapackage - migrate to beeper-v4-bin
Upstream URL: None
Submitter: xiota
Maintainer: xiota (sundbp)
Last Packager: xiota
Votes: 11
Popularity: 0.58
First Submitted: 2023-07-28 06:12 (UTC)
Last Updated: 2025-05-02 20:34 (UTC)

Dependencies (1)

Required by (0)

Sources (0)

Pinned Comments

xiota commented on 2025-05-02 20:35 (UTC)

This package will be retired in favor of aur/beeper-v4-bin. It has been converted into a metapackage to assist users with migration before its eventual deletion.

Latest Comments

1 2 3 4 5 6 .. 8 Next › Last »

xiota commented on 2025-05-02 20:35 (UTC)

This package will be retired in favor of aur/beeper-v4-bin. It has been converted into a metapackage to assist users with migration before its eventual deletion.

xiota commented on 2025-03-26 12:01 (UTC)

@kromsam Here's a snapshot of 3.110.1-2. It should still work.

Before reporting issues upstream, test the AppImage directly. Here are upstream's instructions for reporting problems.

I can switch this package to vendored electron if someone confirms it works better than system electron.

kromsam commented on 2025-03-26 11:21 (UTC)

Where do I report bugs in the app? Currently it randomly crashes now and then. It would be great if there was still a v3 version of the app packaged, because I had no issues with that one.

mathix commented on 2025-03-02 11:17 (UTC)

if someone is interested by the v4 beta client -> https://aur.archlinux.org/packages/beeper-v4-bin

3bd commented on 2025-01-20 02:53 (UTC)

Thanks, xiota, beeper can now run with sh being non-bash. :)

xiota commented on 2025-01-19 21:31 (UTC)

Script has been synced with the one in extra/electron. Both scripts require bash.

3bd commented on 2025-01-18 21:50 (UTC)

Fix the script, because it is not a shell script, IT IS A BASH SCRIPT; IT CONTAINS BASHISM

here's a simpler script I made:

#!/bin/sh
: "${XDG_CONFIG_HOME:=$HOME/.config}"

_ELECTRON=/usr/bin/electron
_ASAR=/opt/beeper/resources/app.asar
_FLAGS_FILE=$XDG_CONFIG_HOME/beeper-flags.conf

if [ -r "$_FLAGS_FILE" ]; then
  _USER_FLAGS=$(cat <"$_FLAGS_FILE")
fi

if [ "$(id -u)" != 0 ] || [ "$ELECTRON_RUN_AS_NODE" ]; then
    exec ${_ELECTRON} ${_ASAR} $_USER_FLAGS "$@"
else
    exec ${_ELECTRON} ${_ASAR} --no-sandbox $_USER_FLAGS "$@"
fi

gdamms commented on 2024-07-13 10:06 (UTC)

@xiota "Unified Messenger" is nice! Yup, you could change the description as well :)

xiota commented on 2024-07-13 06:51 (UTC) (edited on 2024-07-13 06:52 (UTC) by xiota)

@gdamms The .desktop file has:

Comment=Beeper: Unified Messenger

Which would you prefer for generic name: "Chats", "Unified Messenger", "Messenger", ...?

I'm thinking about changing the description to something like, "A unified messaging application".