why is the icon so ultra low res?
Search Criteria
Package Details: cursor-bin 1.1.5-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/cursor-bin.git (read-only, click to copy) |
---|---|
Package Base: | cursor-bin |
Description: | Cursor App - AI-first coding environment |
Upstream URL: | https://www.cursor.com/ |
Licenses: | custom:proprietary |
Submitter: | g.schulz |
Maintainer: | g.schulz |
Last Packager: | g.schulz |
Votes: | 55 |
Popularity: | 7.96 |
First Submitted: | 2024-06-09 14:27 (UTC) |
Last Updated: | 2025-06-21 21:05 (UTC) |
Dependencies (2)
Required by (1)
Sources (4)
Latest Comments
« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 18 Next › Last »
devops69 commented on 2025-03-06 07:34 (UTC)
aspirogrammer commented on 2025-02-26 17:43 (UTC)
Can you mention the differences with the vanilla cursor-bin package to the description?
sentisso commented on 2025-02-20 17:02 (UTC) (edited on 2025-02-20 17:10 (UTC) by sentisso)
Checksum's failing for me again... pkg version 0.45.11-1, current cursor version is 0.45.14 updated checksum: e4c196262f133fed778d97fa60c314539b9863fdce053171b46a62aef823f192
g.schulz commented on 2025-02-19 23:24 (UTC)
For reference, here are the scripts responsible for updating the PKGBUILD: https://github.com/Gunther-Schulz/aur-cursor-bin-updater
g.schulz commented on 2025-02-19 11:04 (UTC) (edited on 2025-02-19 23:27 (UTC) by g.schulz)
For those wondering why I don't use https://downloader.cursor.sh/linux/appImage/x64, here is the explanation: Using that link directly does not allow me to download a specific version of the binary. Also cursor does a staggered release through their home page pushing new versions only to a subset of downloaders at first and you never know what you get. To verify for yourself that the PKGBUILD is using the proper source you can open the network tab in developer tools in your browser and download the file directly from cursor.com. There you will see that the actual download that you receive is for a specific build of the cursor binary directly from download.todesktop.com. Here is a screenshot to illustrate https://pasteboard.co/8QZOka26mK4R.png . Why curl does not show that, I do not know. Wget won't show it to me either. In addition, Homebrew for macos is using the same source as you can see here: https://github.com/Homebrew/homebrew-cask/blob/master/Casks/c/cursor.rb . Also to quote from https://www.cursor.com/security "We use ToDesktop for distributing our app and for doing auto-updates. They are trusted by several widely used apps, such as Linear and ClickUp.". I think this is sufficient evidence for the validity of the source of the binary.
othmane_m commented on 2025-02-17 12:34 (UTC) (edited on 2025-02-17 12:37 (UTC) by othmane_m)
Yes, same here: thanks @garlandKey for having pointed that out.
I'm hesitant about this PKGBUILD, as the $source of the image doesn't look immediately clear to me,
I ran curl to see if https://downloader.cursor.sh/linux/appImage/x64
is just a redirect to https://download.todesktop.com/230313mzl4w4u92/cursor-0.45.11-build-250207y6nbaw5qc-x86_64.AppImage
but instead it serves the file directly, and could be used as source.
curl -v https://downloader.cursor.sh/linux/appImage/x64
@g.schulz
Thank you very much for your work of packing this piece of software,
I wonder, why not using directly https://downloader.cursor.sh/linux/appImage/x64
as image source? To make it instanyly recognizable to everyone that it's a safe source?
garlandKey commented on 2025-02-08 00:47 (UTC) (edited on 2025-02-08 00:51 (UTC) by garlandKey)
I'm confused. Where is the AppImage
coming from? It seems as though cursor.com
has an API that serves the most recent download automatically from this route:
https://downloader.cursor.sh/linux/appImage/x64
However, this PKGBUILD
is getting it from:
https://download.todesktop.com/230313mzl4w4u92/cursor-0.45.11-build-250207y6nbaw5qc-x86_64.AppImage
it seems like that yes but in actuality it comes from todesktop.com which cursor uses as their release platform. And that is where we pull it from, versioned.
@g.schulz How did you figure this out?
Ataj commented on 2025-02-04 22:38 (UTC) (edited on 2025-02-05 00:46 (UTC) by Ataj)
I noticed that cursor-bin currently runs under XWayland on Wayland systems, causing performance issues and incorrect icons due to StartupWMClass being set to cursor-url-helper, which is meant for Wayland. I've fixed this by updating cursor-bin.sh to detect Wayland vs. X11 at runtime and properly launch the app:
#!/bin/bash
XDG_CONFIG_HOME=${XDG_CONFIG_HOME:-~/.config}
# Allow users to override command-line options
if [[ -f $XDG_CONFIG_HOME/cursor-flags.conf ]]; then
CURSOR_USER_FLAGS="$(sed 's/#.*//' $XDG_CONFIG_HOME/cursor-flags.conf | tr '\n' ' ')"
fi
# Detect X11, Wayland, or unknown session type at runtime
if [[ $XDG_SESSION_TYPE == "wayland" ]]; then
exec /opt/cursor-bin/cursor-bin.AppImage \
--ozone-platform=wayland \
--enable-features=UseOzonePlatform,WaylandExplicitSynchronization,WaylandOverlayDelegation,UseSkiaRenderer \
--use-gl=egl \
--disable-gpu-driver-bug-workarounds \
--no-sandbox "$@" $CURSOR_USER_FLAGS
elif [[ $XDG_SESSION_TYPE == "x11" ]]; then
exec /opt/cursor-bin/cursor-bin.AppImage --no-sandbox "$@" $CURSOR_USER_FLAGS
else
# Default to X11 if unknown
exec /opt/cursor-bin/cursor-bin.AppImage --no-sandbox "$@" $CURSOR_USER_FLAGS
fi
This ensures Wayland users get native Wayland performance & working icons in the dash. also added more flags to fix tearing issues and graphical bugs
Nexi commented on 2025-01-30 11:03 (UTC)
In pkgbuild, mantainer name and email is Your Name <your.email@example.com>
. It's probably a good idea to change that to actual nickname and email. Thanks!
Pinned Comments
g.schulz commented on 2025-05-17 08:01 (UTC) (edited on 2025-05-18 10:16 (UTC) by g.schulz)
For anyone who want's to contribute a PR, this is the repo: https://github.com/Gunther-Schulz/aur-cursor-bin-updater