Updated the System and now WeekToDo doesn't open. I'm using the .rpm package on the Fedora 39 pre-release build. Uninstalled and installed it again but it doesn't work and I'm afraid that I could lose my data.

I can open the web version but I don't know where to look for my saved stuff to sync up with.

System Details Report

---

Report details

• Date generated: 2023-10-06 19:14:23

Hardware Information:

• Hardware Model: HP HP Pavilion Gaming Laptop 16-a0xxx
• Memory: 8.0 GiB
• Processor: Intel® Core™ i5-10300H × 8
• Graphics: Intel® UHD Graphics (CML GT2)
• Graphics 1: NVIDIA GeForce GTX 1650 Ti
• Disk Capacity: 512.1 GB

Software Information:

• Firmware Version: F.20
• OS Name: Fedora Linux 39 (Workstation Edition Prerelease)
• OS Build: (null)
• OS Type: 64-bit
• GNOME Version: 45.0
• Windowing System: Wayland
• Kernel Version: Linux 6.5.5-300.fc39.x86_64

Screencast from 2023-10-06 19-02-35.webm

Update: For some reason it boots fine right clicking + "Use discrete graphics card" idk exactly what this option changed but at least I can use the app without crashing. So far no issues, but I did export my data just in case. I would really appreciate if there was an option to autosync with data existing on the system using the browser or a way to recover it if the app does not open altogether, like what happened to me.

In any case I hope this issue gives you enough info to prevent that from happening to other people, it was an stressful couple of days as I was relying a lot on this app to manage my tasks.

You have made a good piece of software! Hope you have a good day

Hi @JuchuDesign thanks for writing and for reporting this.

To be honest, I don't have a clear clue as to what could have happened there. I work with Ubuntu with gnome 43 and Wayland and here it works well although, but this compatibility across several systems becomes a problem for me in terms of compatibility and try the different scenarios.

In any case, I'm going to find out if electron changed anything related to graphical acceleration based on the workaround you used to solve the problem.

Regarding what you say about synchronization, yes, it is important to implement something like this or at least have a systematic save mechanism. I put this on my to-do list.

I'm sorry for any problems this may have caused. Best Regards.