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

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.

Any way of enabling native window decorations? I'm using Arch + Plasma 5.24 and I get nothing just like obsidian-native-window without running a command they provided in the comments.