Bug 496788 - Flatpak crashes at startup
Summary: Flatpak crashes at startup
Status: RESOLVED WORKSFORME
Alias: None
Product: NeoChat
Classification: Applications
Component: General (show other bugs)
Version: git master
Platform: Flatpak Linux
: NOR crash
Target Milestone: ---
Assignee: Tobias Fella
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-11-28 14:16 UTC by tuug
Modified: 2025-01-02 03:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tuug 2024-11-28 14:16:59 UTC
SUMMARY
The neochat flatpak refuses to run, either from desktop or from terminal.

STEPS TO REPRODUCE
1. Run `flatpak run org.kde.neochat`

OBSERVED RESULT
```
Gtk-Message: 09:16:10.524: Failed to load module "xapp-gtk3-module"
Qt: Session management error: Could not open network socket
QQmlApplicationEngine failed to load component
qrc:/qt/qml/org/kde/neochat/qml/Main.qml:33:22: Type WelcomePage unavailable
qrc:/qt/qml/org/kde/neochat/login/WelcomePage.qml: Type NeoChatSettingsView unavailable
qrc:/qt/qml/org/kde/neochat/settings/NeoChatSettingsView.qml:13:1: KirigamiSettings.ConfigurationView is not a type
```

EXPECTED RESULT
Application to launch

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 42
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Comment 1 Tobias Fella 2024-12-02 20:48:24 UTC
Is that the fedora flatpak or the flathub flatpak?

(run "flatpak info org.kde.neochat", and check the "Origin" row
Comment 2 tuug 2024-12-03 01:35:55 UTC
(In reply to Tobias Fella from comment #1)
> Is that the fedora flatpak or the flathub flatpak?
> 
> (run "flatpak info org.kde.neochat", and check the "Origin" row

No, I installed it from an individual nightly flatpak (https://cdn.kde.org/flatpak/neochat-nightly/)
Comment 3 Bug Janitor Service 2024-12-18 03:46:51 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2025-01-02 03:47:33 UTC
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.