Arch Linux User Repository

Breaking Change in 6.0.30-2: Config File Moved

With the latest update (6.0.30-2), the user flags configuration file has been relocated for better consistency. This aligns with common Arch Linux packaging practices and TickTick’s existing config directory structure.

Please, you should move your config file:

mv -v ~/.config/ticktick-flags.conf ~/.config/ticktick/user-flags.conf

Thanks @OJFord for pointing this out.

Custom Flags Support for TickTick

I recently pushed an update to v2.0.0, introducing a helper script to launch TickTick with custom (Electron) flags. Previously, this wasn't possible, making it hard to enable Wayland support. Fortunately, TickTick now allows this.

How to configure it:

Create the flags file:

mkdir -p ~/.config/ticktick
touch ~/.config/ticktick/user-flags.conf

Add your Electron flags, one per line (comments are ignored):

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

Run TickTick

Please add noto-fonts-emoji package as a dependency as it enables showing icons.

Breaking Change in 6.0.30-2: Config File Moved

With the latest update (6.0.30-2), the user flags configuration file has been relocated for better consistency. This aligns with common Arch Linux packaging practices and TickTick’s existing config directory structure.

Please, you should move your config file:

mv -v ~/.config/ticktick-flags.conf ~/.config/ticktick/user-flags.conf

Thanks @OJFord for pointing this out.

Thanks for using XDG_CONFIG_HOME. Per the XDG base directory spec though, could you please nest the conf file inside a ticktick directory? e.g. $XDG_CONFIG_HOME/ticktick/flags.conf.

Custom Flags Support for TickTick

I recently pushed an update to v2.0.0, introducing a helper script to launch TickTick with custom (Electron) flags. Previously, this wasn't possible, making it hard to enable Wayland support. Fortunately, TickTick now allows this.

How to configure it:

Create the flags file:

mkdir -p ~/.config/ticktick
touch ~/.config/ticktick/user-flags.conf

Add your Electron flags, one per line (comments are ignored):

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

Run 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.