Label updates hang the application

[shanlalit]

Label updates hang the application

[omenos]

This also occurs on label creation. Deletions do not seem to cause a problem, but creation and modification of labels freeze the interface.

The app itself is not completely hung, however. Keyboard shortcuts still work and other UI components are not impacted (a to add a task, m to collapse/expand the sidebar, ^+, to open preferences). Some shortcuts work after a popup/overlay window is activated; only the primary application interface has seized.

Desktop Information

• Fedora 40 Workstation
• GNOME 46
• Flatpak 1.15.8
• Planify 4.7.4

Flatpak Overrides

[Context]
sockets=!fallback-x11;!x11
filesystems=!home

Journal Log

May 20 11:27:45 systemd[2289]: Started app-gnome-io.github.alainm23.planify-10875.scope - Application launched by gnome-shell.
May 20 11:27:45 systemd[2289]: Started app-flatpak-io.github.alainm23.planify-10875.scope.
May 20 11:27:45 io.github.alain[10892]: objects_item_get_completed: assertion 'self != NULL' failed
May 20 11:27:45 gnome-shell[2548]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
May 20 11:27:46 io.github.alain[10892]: gtk_box_append: assertion 'GTK_IS_WIDGET (child)' failed
May 20 11:27:46 io.github.alain[10892]: gtk_stack_set_visible_child_name: assertion 'GTK_IS_STACK (stack)' failed
May 20 11:27:46 io.github.alain[10892]: gtk_stack_set_visible_child_name: assertion 'GTK_IS_STACK (stack)' failed
May 20 11:27:46 io.github.alain[10892]: gtk_stack_set_visible_child_name: assertion 'GTK_IS_STACK (stack)' failed
May 20 11:27:47 io.github.alainm23.planify.desktop[10892]: {"calendar_accounts":[],"calendars":[],"collaborator_states":[],"collaborators":[],"completed_info":[],"day_orders":{},"day_orders_timestamp":"1344642991.1","due_exceptions":[],"filters":[],"folders":[],"full_sync":false,"items":[],"labels":[],"live_notifications":[],"live_notifications_last_read_id":"0","notes":[],"project_notes":[],"projects":[],"reminders":[],"sections":[],"suggestions":[],"sync_token":"UkxPoDj7vZNb9H8B9F0LH0IgRTl1mQWVec26c__VXnjdnCoznJuKboegGhScC3eX2GFUYgw2GbT7ZHOaA2pFJjsImO6r4rewaykmZEnqElHbrg","temp_id_mapping":{},"view_options":[],"workspace_users":[],"workspaces":[]}
May 20 11:27:47 io.github.alainm23.planify.desktop[10892]: {"full_sync":true,"sync_token":"UkxPoDj7vZNb9H8B9F0LH0IgRTl1mQWVec26c__VXnjdnCoznJuKboegGhScC3eX2GFUYgw2GbT7ZHOaA2pFJjsImO6r4rewaykmZEnqElHbrg","temp_id_mapping":{}}
May 20 11:27:48 io.github.alainm23.planify.desktop[10892]: {"calendar_accounts":[],"calendars":[],"collaborator_states":[],"collaborators":[],"completed_info":[],"day_orders":{},"day_orders_timestamp":"1344642991.1","due_exceptions":[],"filters":[],"folders":[],"full_sync":false,"items":[],"labels":[],"live_notifications":[],"live_notifications_last_read_id":"0","notes":[],"project_notes":[],"projects":[],"reminders":[],"sections":[],"suggestions":[],"sync_token":"UkxPoDj7vZNb9H8B9F0LH0IgRTl1mQWVec26c__VXnjdnCoznJuKboegGhScC3eX2GFUYgw2GbT7ZHOaA2pFJjsImO6r4rewaykmZEnqElHbrg","temp_id_mapping":{},"view_options":[],"workspace_users":[],"workspaces":[]}
May 20 11:27:48 io.github.alainm23.planify.desktop[10892]: {"full_sync":true,"sync_token":"UkxPoDj7vZNb9H8B9F0LH0IgRTl1mQWVec26c__VXnjdnCoznJuKboegGhScC3eX2GFUYgw2GbT7ZHOaA2pFJjsImO6r4rewaykmZEnqElHbrg","temp_id_mapping":{}}

... Label edit submitted ...

May 20 11:28:15 gnome-shell[2548]: Window manager warning: last_focus_time (4646455) is greater than comparison timestamp (4666).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
May 20 11:28:15 gnome-shell[2548]: Window manager warning: last_user_time (4652485) is greater than comparison timestamp (4666).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
May 20 11:28:15 gnome-shell[2548]: Window manager warning: W50 appears to be one of the offending windows with a timestamp of 4589545.  Working around...
May 20 11:28:15 gnome-shell[2548]: Window manager warning: W156 appears to be one of the offending windows with a timestamp of 4652485.  Working around...
May 20 11:28:15 gnome-shell[2548]: Window manager warning: 0x4000004 appears to be one of the offending windows with a timestamp of 4569861.  Working around...
May 20 11:28:15 gnome-shell[2548]: Window manager warning: W134 appears to be one of the offending windows with a timestamp of 4634493.  Working around...

[omenos]

Quick hack, you can modify and add what you need directly via the sqlite db. Wouldn't recommend for safety reasons, but I can confirm it does work (just restart the app or quit it ahead of time).

$ sqlite3 [path-to-db]
sqlite> INSERT INTO Labels VALUES('<output of uuidgen>','<label_name>','<color>',<position_integer>,0,0,'local');

Colors can be found here.

If you need to modify, just use the correct SQL query for that 😅

sqlite> .schema Labels
CREATE TABLE Labels (
                id              TEXT PRIMARY KEY,
                name            TEXT,
                color           TEXT,
                item_order      INTEGER,
                is_deleted      INTEGER,
                is_favorite     INTEGER,
                backend_type    TEXT,
                CONSTRAINT unique_label UNIQUE (name)
            );

If you want to make sure your UUIDs don't potentially clash:

$ sqlite3 database.db .dump | grep -Eo '[a-z0-9]{8}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{4}-[a-z0-9]{12}'

Some UUIDs may be in md5 format (the ones created by Todoist were for me), but that's easy enough to rectify with the --sha1 and --md5 flags for uuidgen.