Search Criteria
Package Details: android-messages-desktop 5.4.2-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/android-messages-desktop.git (read-only, click to copy) |
|---|---|
| Package Base: | android-messages-desktop |
| Description: | Android Messages as a cross-platform desktop app |
| Upstream URL: | https://github.com/OrangeDrangon/android-messages-desktop |
| Keywords: | android |
| Licenses: | MIT |
| Submitter: | yochananmarqos |
| Maintainer: | yochananmarqos |
| Last Packager: | yochananmarqos |
| Votes: | 8 |
| Popularity: | 0.000082 |
| First Submitted: | 2018-07-15 23:46 (UTC) |
| Last Updated: | 2024-01-05 17:17 (UTC) |
Dependencies (3)
- electron20AUR (electron20-binAUR)
- git (git-gitAUR) (make)
- yarn (corepackerAUR, yarn-pnpm-corepackAUR, yarn-berryAUR) (make)
Latest Comments
1 2 3 Next › Last »
yochananmarqos commented on 2023-12-30 20:57 (UTC)
@uint2048_t: As far as I know that value is already the default. You can always copy the desktop file to userspace and edit the Exec line.
uint2048_t commented on 2023-12-30 20:47 (UTC) (edited on 2023-12-30 20:48 (UTC) by uint2048_t)
Consider adding these arguments to the .desktop file to enable Wayland support:
uint2048_t commented on 2023-09-10 02:34 (UTC) (edited on 2023-09-10 03:15 (UTC) by uint2048_t)
Any update @orangedrangon? This is a great package and don't want to see it get forgotten.
orangedrangon commented on 2023-07-01 18:25 (UTC)
I will attempt to bump dependencies upstream and make a release.
yochananmarqos commented on 2023-07-01 17:48 (UTC)
@digital_mystik: I've tried Electron 22, 23, 34 & 25. Unfortunately, 21 is still the latest working version. You'll need to use
electron21-binnow aselectron21was dropped from the Arch repos and was built withicu72.digital_mystik commented on 2023-07-01 17:29 (UTC)
howdy.. any chance of porting this to electron25? It will launch but I get a white screen with the toolbar for both 24 and 25. I thought it was a wayland issue but still exhibits the same behavior with X (at least on my end)
orangedrangon commented on 2020-06-10 20:15 (UTC)
Hello this is the person who forked and attempted to fix some of the bugs.
Addressing a few of the problems I am new to this and made the naive mistake of changing the location where the settings are saved resetting them to their defaults for anyone that installs the package. Sorry for any confusion that this causes but everything should work as before if you reconfigure your settings.
Again I am sorry about this. I did not realize the consequences or confusion this would cause.
Please open any issues you have with the software on the upstream git repo and I will do my best to resolve them.
pixel1138 commented on 2020-06-09 21:10 (UTC)
The newest 4.0.0 version fixed the error I was getting.
jylertones commented on 2020-06-09 15:25 (UTC)
@pixel1138 - I got the same thing initially. It seems like a bug, but it did go away when I retried.
1 2 3 Next › Last »