matthiasn/lotti

Tasks disappear immediately after creation in Flatpak version

Open

#2,585 opened on Jan 10, 2026

View on GitHub
 (14 comments) (0 reactions) (1 assignee)Dart (112 forks)github user discovery
help wanted

Repository metrics

Stars
 (1,121 stars)
PR merge metrics
 (PR metrics pending)

Description

Lotti tasks are not showing under tasks but are sucessfully being created as JSON objects in the DB. There show up in the log book for a limited amount of time as well. Search does not find them. None are marked as done or something similar. Settings are defaults. I also had issues with Lotti failing to open the keyring which I solve by adding org.freedesktop.secrets to session bus permissions.

Operating System: Bazzite 43(Fedora Atomic, both stable 43.20260101 and testing 43.20260105) KDE Plasma Version: 6.5.4 KDE Frameworks Version: 6.21.0 Qt Version: 6.10.1 Kernel Version: 6.17.7-ba22.fc43.x86_64 (64-bit) Graphics Platform: Wayland Lotti Version: 0.9.807

Steps to reproduce: Install Lotti from flathub run flatpak run com.matthaisn.lotti create a task navigate away from the task section or close and open the app

'''flatpak run com.matthiasn.lotti Fontconfig error: Cannot load default config file: No such file: (null)

** (com.matthiasn.lotti:2): WARNING **: 10:20:00.857: Could not load application icon from any file path, using theme fallback Fontconfig error: Cannot load default config file: No such file: (null) Gdk-Message: 10:20:00.919: Unable to load from the cursor theme package:media_kit_libs_linux registered.'''

Contributor guide

Research direction
Investigate why tasks created as JSON objects in the DB are not displayed in the UI. Trace the data flow from creation to list rendering, paying attention to Flatpak sandboxing and permissions (e.g., keyring, file system access). Check if the search failure is related.
Tech stack
dart
Domain
frontenddatabase
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitDart/Flutter
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75