Arch Linux User Repository

I recently pushed an update to v2.0.0 which includes a new helper script to launch TickTick with the (Electron) flags you want. Previous versions, did not allow this, making it impossible to pass those that enable wayland support. It seems that from now the TickTick team has allowed this use.

How to configure it:

• Create a new file ~/.config/ticktick-flags.conf

• Add one flag per line. Comment lines will be ignored.

# enable wayland support
--enable-features=UseOzonePlatform
--ozone-platform=wayland

• Start TickTick

I recently pushed an update to v2.0.0 which includes a new helper script to launch TickTick with the (Electron) flags you want. Previous versions, did not allow this, making it impossible to pass those that enable wayland support. It seems that from now the TickTick team has allowed this use.

How to configure it:

• Create a new file ~/.config/ticktick-flags.conf

• Add one flag per line. Comment lines will be ignored.

# enable wayland support
--enable-features=UseOzonePlatform
--ozone-platform=wayland

• Start TickTick

Can confirm the fix as of 1.0.80-4, thank you for your efforts @Aerz, much appreciated!

@OJFord You're right. Ticktick changed it and the package should be updated.

I would like to make automated requests to https://ticktick.com/static/getApp/download?type=linux_deb_x64 in the future to keep it up to date by using some CI as @roscar commented, but it's still on my tasklist.

Next time, feel free to flag the package out-of-date.

How can we verify the new download URL? The upstream (webpage-driven) download is via https://d2atcrkye2ik4e.cloudfront.net/download/linux/linux_deb_x64/ticktick-1.0.80-amd64.deb, not (directly, visibly) the 'ticktick-download-linux' bucket.

Since it's mentioned below, I assume it is correct, but they just updated to put Cloudfront in front of it (but kept the bucket public). In that case both for verifiability and in no disfavour to upstream, might be worth updating to use the CDN URL?

Fixed. Sorry for the inconvenience.

The intention in the last upgrade was to keep the installation similar to the ticktick developer's package in the .deb file because I noticed that some programs like hardcode-tray ^1 expect those files to perform their tasks.

Previously, I attempted to create a more "integrated" version, so I removed some code including the symlink. Now it's restored.

Thank you for reporting it. :)

Same here – I upgraded to v1.0.80, and suddenly didn't have a ticktick executable anymore. A symlink into $PATH fixed the problem, but that's probably not intentional?

Did the launcher change location? I upgraded as of the latest release and it's disappeared from my dmenu, found it in /opt/TickTick/ticktick. It launches fine, but was surprised to discover this.

Hi Aerz, I'd be happy to help maintenance for this by making the updates automatic. Simplest way to do this is probably to check the normal linux download link as it redirects to the url for the most recent release, which you can find in the header:

curl --head "https://ticktick.com/down/getApp/download?type=linux_deb_x64"
HTTP/2 302 
date: Fri, 02 Jun 2023 04:35:27 GMT
location: https://ticktick-download-linux.s3.amazonaws.com/download/linux/linux_deb_x64/ticktick-1.0.70-amd64.deb

A simple CI on GitHub could run which periodically checks this for a new release and if there is one downloads the file, gets the hash, and updates the PKGBUILD.

Update for version 1.0.50:

@@ -1,7 +1,7 @@
 # Maintainer: Agustin Cisneros <agustincc@tutanota.com>

 pkgname=ticktick
-pkgver=1.0.40
+pkgver=1.0.50
 pkgrel=1
 pkgdesc='Official desktop application for Linux'
 arch=('x86_64')
@@ -11,7 +11,7 @@
 depends=('alsa-lib' 'gtk3' 'nss')
 source=("${pkgname}-${pkgver}.deb::https://appest-public.s3.amazonaws.com/download/linux/linux_deb_x64/${pkgname}-${pkgver}-amd64.deb"
         'LICENSE')
-sha256sums=('f5696d44bec38a6498a8cee068435cecea95ba88abebea62d8ac6c92025d0748'
+sha256sums=('0e9b47bd3406dd9af859904b573536c36d826c8e7b134813235907efec982af9'
             '2d866fcb749c30d931fa96cc1578869b3fa9fc61a5c5f30e0316ddb00abb5814')

 package() {

@ucelote I see the problem, but I think this should be reported to TickTick developers. I will create a ticket to them, but in the meantime you can get the similar result doing the following (with root privileges):

pacman -S nodejs npm
cd /opt/ticktick/resources
npx asar extract app.asar app.asar.d
sed -i '/init main window/{s/frame:!1/frame:1/g}' app.asar.d/bundler/index.js
rm app.asar    
npx asar pack app.asar.d app.asar

This steps are a dirty edit because the custom window controls are still there and edit the css will the next step to get rid of them, but it's not easy as we could do it in obsidian.