mirror of
https://github.com/AppFlowy-IO/AppFlowy.git
synced 2026-03-24 12:56:59 +00:00
[GH-ISSUE #7077] [Bug] Crashed in fedora 41, flatpak #3129
Labels
No labels
2024
2025
2026
acct mgmt
AI
automation
bug
calendar
ci
CJK
cloud
code-block
collaboration
copy-paste
database
data migration
data sync
deploy
desktop
develop
develop
documentation
duplicate
editor
editor-plugin
emoji
export
files
flutter-only
follow-up
formula
good first issue for devs
good first issue for experienced devs
grid
hacktoberfest
HACKTOBERFEST-ACCEPTED
help wanted
i18n
icons
images
importer
improvements
infra
install
integrations
IR
kanban board
login
look and joy
mentorship
mobile
mobile
needs design
new feature
new feature
non-coding
notes
notifications
onboarding
organization
P0+
permission
platform-linux
platform-mac
platform-windows
plugins
program
pull-request
Q1 25
Q1 26
Q2 24
Q2 25
Q3 24
Q3 25
Q4 24
Q4 25
react
regression
rust
rust
Rust-only
Rust-only
Rust-starter
Rust-starter
self-hosted
shortcuts
side panel
slash-menu
sync v2
table
tablet
task
tauri
templates
tests
themes
translation
v0.5.6
v0.5.8
v0.5.9
v0.6.0
v0.6.1
v0.6.4
v0.6.7
v0.6.8
v0.7.1
v0.7.4
v0.7.4
v0.7.5
v0.7.6
v0.7.7
v0.7.8
v0.8.0
v0.8.4
v0.8.5
v0.8.9
web
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AppFlowy-IO/AppFlowy#3129
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @zhaob1n on GitHub (Dec 28, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7077
Originally assigned to: @LucasXu0 on GitHub.
Bug Description
I installed appflowy from flathub. when I tried to open it, it showed a blackscreen and immediatly crashes.
How to Reproduce
launch the app
Expected Behavior
app launches successfully
Operating System
Fedora 41
AppFlowy Version(s)
0.7.8
Screenshots
Additional Context
flatpak run log
dmesg(multiple runs):
logs from problem reporting:
problem-reporting.tar.gz
@LucasXu0 commented on GitHub (Dec 30, 2024):
@xcpky are there any more logs after this line?
@zhaob1n commented on GitHub (Dec 30, 2024):
no, sometimes there are no logs at all
@zhaob1n commented on GitHub (Dec 31, 2024):
I found something interesting.
so xwayland works fine, but not wayland
@zhaob1n commented on GitHub (Dec 31, 2024):
No idea why, but after running appflowy in xwayland, i switched back to wayland, it works...
@LucasXu0 commented on GitHub (Dec 31, 2024):
Thanks for the hint. I assume that it's related to Wayland. I'll do some research to see if there's any configuration to use Wayland or XWayland based on the platform.
@zhaob1n commented on GitHub (Dec 31, 2024):
Typically appflowy supports wayland well, this is the first time I met this issue, when I installed it on a freshly installed fedora. Appflowy works well on my other machines running wayland, and now it works on this machine too.
Since wayland is always preferred over xwayland on wayland environment, and appflowy by default runs on wayland natively and works well, I don't think it needs any additional configuration. It just this issue happens and disappears without known reasons. and it's caused by segmentation fault,there should be other bugs.