[GH-ISSUE #7410] [Bug] Font selector is unresponsive #3299

Open
opened 2026-03-23 21:29:05 +00:00 by mirror · 12 comments
Owner

Originally created by @almereyda on GitHub (Feb 22, 2025).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7410

Bug Description

The font selector can almost freeze the application upon initial toggle or scrolling through the list.

How to Reproduce

  1. Open settings
  2. Go to workspace settings
  3. Select another font
  4. See the application freeze without notice and the system get sluggish

Expected Behavior

Fonts are loaded lazily without blocking the application or system.

Operating System

Ubuntu + Flatpak

AppFlowy Version(s)

0.8.4

Screenshots

N/A

Additional Context

It is not obvious if this shows the system fonts or packaged fonts from the Flatpak.

This could very well be caused by a huge list of fonts.

Originally created by @almereyda on GitHub (Feb 22, 2025). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7410 ### Bug Description The font selector can almost freeze the application upon initial toggle or scrolling through the list. ### How to Reproduce 1. Open settings 2. Go to workspace settings 3. Select another font 4. See the application freeze without notice and the system get sluggish ### Expected Behavior Fonts are loaded lazily without blocking the application or system. ### Operating System Ubuntu + Flatpak ### AppFlowy Version(s) 0.8.4 ### Screenshots N/A ### Additional Context It is not obvious if this shows the system fonts or packaged fonts from the Flatpak. This could very well be caused by a huge list of fonts.
Author
Owner

@khorshuheng commented on GitHub (Feb 24, 2025):

Does this happens only on flatpak?

EDITED: we are able to replicate the sluggish performance on desktop app as well in Linux (MacOS version seems ok from initial testing), though the application is still responsive. That is probably due to difference in machine spec. Will find out how to improve this.

<!-- gh-comment-id:2677298516 --> @khorshuheng commented on GitHub (Feb 24, 2025): Does this happens only on flatpak? EDITED: we are able to replicate the sluggish performance on desktop app as well in Linux (MacOS version seems ok from initial testing), though the application is still responsive. That is probably due to difference in machine spec. Will find out how to improve this.
Author
Owner

@almereyda commented on GitHub (Feb 24, 2025):

I would have to test against other Desktop builds.

On Mon, 24 Feb 2025 at 03:09, Khor Shu Heng @.***>
wrote:

Does this happens only on flatpak?


Reply to this email directly, view it on GitHub
https://github.com/AppFlowy-IO/AppFlowy/issues/7410#issuecomment-2677298516,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMRV7CRYML5VE5AXWXQBVD2RJ5N7AVCNFSM6AAAAABXU5GCWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZXGI4TQNJRGY
.
You are receiving this because you authored the thread.Message ID:
@.***>
[image: khorshuheng]khorshuheng left a comment
(AppFlowy-IO/AppFlowy#7410)
https://github.com/AppFlowy-IO/AppFlowy/issues/7410#issuecomment-2677298516

Does this happens only on flatpak?


Reply to this email directly, view it on GitHub
https://github.com/AppFlowy-IO/AppFlowy/issues/7410#issuecomment-2677298516,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMRV7CRYML5VE5AXWXQBVD2RJ5N7AVCNFSM6AAAAABXU5GCWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZXGI4TQNJRGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:2679545032 --> @almereyda commented on GitHub (Feb 24, 2025): I would have to test against other Desktop builds. On Mon, 24 Feb 2025 at 03:09, Khor Shu Heng ***@***.***> wrote: > Does this happens only on flatpak? > > — > Reply to this email directly, view it on GitHub > <https://github.com/AppFlowy-IO/AppFlowy/issues/7410#issuecomment-2677298516>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAMRV7CRYML5VE5AXWXQBVD2RJ5N7AVCNFSM6AAAAABXU5GCWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZXGI4TQNJRGY> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > [image: khorshuheng]*khorshuheng* left a comment > (AppFlowy-IO/AppFlowy#7410) > <https://github.com/AppFlowy-IO/AppFlowy/issues/7410#issuecomment-2677298516> > > Does this happens only on flatpak? > > — > Reply to this email directly, view it on GitHub > <https://github.com/AppFlowy-IO/AppFlowy/issues/7410#issuecomment-2677298516>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAMRV7CRYML5VE5AXWXQBVD2RJ5N7AVCNFSM6AAAAABXU5GCWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZXGI4TQNJRGY> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Author
Owner

@aquaspy commented on GitHub (Mar 5, 2025):

@khorshuheng
It looks like it happens overall on Linux with flatpak, deb or AppImage. It started after 0.84. I can use 0.83 without any issues.

The issue continues to occur on 0.8.5

I can only use the web for now since the desktop version freezes all the time.

<!-- gh-comment-id:2701612643 --> @aquaspy commented on GitHub (Mar 5, 2025): @khorshuheng It looks like it happens overall on Linux with flatpak, deb or AppImage. It started after 0.84. I can use 0.83 without any issues. The issue continues to occur on 0.8.5 I can only use the web for now since the desktop version freezes all the time.
Author
Owner

@khorshuheng commented on GitHub (Mar 6, 2025):

@aquaspy While we were able to reproduce the issue with slow performance when choosing and scrolling font on Linux, the app should still be responsive under other situations, at least, not sluggish to the point of unusable. Can you perhaps take a short video to demonstrate the performance issue?

And does downgrading back to 0.8.3 makes the issue dissapear entirely? If so, what is the distro and desktop environment which you are using?

<!-- gh-comment-id:2702423111 --> @khorshuheng commented on GitHub (Mar 6, 2025): @aquaspy While we were able to reproduce the issue with slow performance when choosing and scrolling font on Linux, the app should still be responsive under other situations, at least, not sluggish to the point of unusable. Can you perhaps take a short video to demonstrate the performance issue? And does downgrading back to 0.8.3 makes the issue dissapear entirely? If so, what is the distro and desktop environment which you are using?
Author
Owner

@aquaspy commented on GitHub (Mar 6, 2025):

Here is the video showing it @khorshuheng

On current desktop, I am using a RX 6500 XT, Linux Mint Cinnamon 22.1 based on Ubuntu 24.04 and X11
https://github.com/user-attachments/assets/a2eef19c-4131-441b-8d2d-d0850525f741

<!-- gh-comment-id:2705097731 --> @aquaspy commented on GitHub (Mar 6, 2025): Here is the video showing it @khorshuheng On current desktop, I am using a RX 6500 XT, Linux Mint Cinnamon 22.1 based on Ubuntu 24.04 and X11 https://github.com/user-attachments/assets/a2eef19c-4131-441b-8d2d-d0850525f741
Author
Owner

@khorshuheng commented on GitHub (Mar 7, 2025):

Can you share the log files of the app, so that we can check if there is any anomaly? I will also see if I can reproduce this on cinnamon desktop environment.

<!-- gh-comment-id:2705238557 --> @khorshuheng commented on GitHub (Mar 7, 2025): Can you share the log files of the app, so that we can check if there is any anomaly? I will also see if I can reproduce this on cinnamon desktop environment.
Author
Owner

@khorshuheng commented on GitHub (Mar 7, 2025):

@aquaspy Can I create a new issue and track this in a new issue? From preliminary investigation, your text field freezing issue is a different problem compared to the font selector issue reported here. This seems suspiciously similar to https://github.com/flutter/flutter/issues/153560 , which only affect Linux Mint Cinnamon.

<!-- gh-comment-id:2705335135 --> @khorshuheng commented on GitHub (Mar 7, 2025): @aquaspy Can I create a new issue and track this in a new issue? From preliminary investigation, your text field freezing issue is a different problem compared to the font selector issue reported here. This seems suspiciously similar to https://github.com/flutter/flutter/issues/153560 , which only affect Linux Mint Cinnamon.
Author
Owner

@aquaspy commented on GitHub (Mar 7, 2025):

Hi @khorshuheng,z

Absolutely! Thanks so much for that. I was not expecting cinnamon to crash with flutter, but I bet that is the issue. In this case we need to wait a fix from flutter right?

  2025-03-07 10:15:20  INFO flowy_server::af_cloud::server: [websocket] state: Connecting
    at flowy-server/src/af_cloud/server.rs:307

{"msg":"[websocket] state: Connecting","time":"03-07 10:15:20","target":"flowy_server::af_cloud::server"}
{"msg":"🔵websocket start connecting","time":"03-07 10:15:20","target":"client_api::retry"}

(AppFlowy:41297): Gdk-CRITICAL **: 10:15:43.687: gdk_device_get_source: assertion 'GDK_IS_DEVICE (device)' failed

(AppFlowy:41297): Gdk-CRITICAL **: 10:15:43.687: gdk_device_get_source: assertion 'GDK_IS_DEVICE (device)' failed

(AppFlowy:41297): Gdk-CRITICAL **: 10:15:52.895: gdk_device_get_source: assertion 'GDK_IS_DEVICE (device)' failed

(AppFlowy:41297): Gdk-CRITICAL **: 10:15:52.963: gdk_device_get_source: assertion 'GDK_IS_DEVICE (device)' failed

(AppFlowy:41297): Gdk-CRITICAL **: 10:15:52.963: gdk_device_get_source: assertion 'GDK_IS_DEVICE (device)' failed

Looks like it got a little better with 0.86.

<!-- gh-comment-id:2706433099 --> @aquaspy commented on GitHub (Mar 7, 2025): Hi @khorshuheng,z Absolutely! Thanks so much for that. I was not expecting cinnamon to crash with flutter, but I bet that is the issue. In this case we need to wait a fix from flutter right? ``` 2025-03-07 10:15:20 INFO flowy_server::af_cloud::server: [websocket] state: Connecting at flowy-server/src/af_cloud/server.rs:307 {"msg":"[websocket] state: Connecting","time":"03-07 10:15:20","target":"flowy_server::af_cloud::server"} {"msg":"🔵websocket start connecting","time":"03-07 10:15:20","target":"client_api::retry"} (AppFlowy:41297): Gdk-CRITICAL **: 10:15:43.687: gdk_device_get_source: assertion 'GDK_IS_DEVICE (device)' failed (AppFlowy:41297): Gdk-CRITICAL **: 10:15:43.687: gdk_device_get_source: assertion 'GDK_IS_DEVICE (device)' failed (AppFlowy:41297): Gdk-CRITICAL **: 10:15:52.895: gdk_device_get_source: assertion 'GDK_IS_DEVICE (device)' failed (AppFlowy:41297): Gdk-CRITICAL **: 10:15:52.963: gdk_device_get_source: assertion 'GDK_IS_DEVICE (device)' failed (AppFlowy:41297): Gdk-CRITICAL **: 10:15:52.963: gdk_device_get_source: assertion 'GDK_IS_DEVICE (device)' failed ``` Looks like it got a little better with 0.86.
Author
Owner

@khorshuheng commented on GitHub (Mar 7, 2025):

There are workarounds which we can try, based on the GitHub issue which I shared.

<!-- gh-comment-id:2706435057 --> @khorshuheng commented on GitHub (Mar 7, 2025): There are workarounds which we can try, based on the GitHub issue which I shared.
Author
Owner

@aquaspy commented on GitHub (Mar 7, 2025):

Yup! Just confirmed that this one worked!
https://github.com/flutter/flutter/issues/153560#issuecomment-2503660633

the problem is sometimes solved by disabling the virtual keyboard in the Linux Mint accessibility settings

Perhaps we can add it to the FAQ here to help some other mint users around the world?

<!-- gh-comment-id:2706437046 --> @aquaspy commented on GitHub (Mar 7, 2025): Yup! Just confirmed that this one worked! https://github.com/flutter/flutter/issues/153560#issuecomment-2503660633 ``` the problem is sometimes solved by disabling the virtual keyboard in the Linux Mint accessibility settings ``` Perhaps we can add it to the FAQ here to help some other mint users around the world?
Author
Owner

@khorshuheng commented on GitHub (Mar 7, 2025):

There are also other work around that we can apply on our end. Removing accessibility would unfortunately, impact the users who need it. So it's best if we apply the workaround on our end, until flutter team fixed this issue.

<!-- gh-comment-id:2706449427 --> @khorshuheng commented on GitHub (Mar 7, 2025): There are also other work around that we can apply on our end. Removing accessibility would unfortunately, impact the users who need it. So it's best if we apply the workaround on our end, until flutter team fixed this issue.
Author
Owner

@aquaspy commented on GitHub (Mar 7, 2025):

Ah I see, you are right. Let me know if I can help with more tests.

<!-- gh-comment-id:2706454868 --> @aquaspy commented on GitHub (Mar 7, 2025): Ah I see, you are right. Let me know if I can help with more tests.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#3299
No description provided.