Bug 497438 - Non-Native FileDialog Seg Fault when Importing Keys
Summary: Non-Native FileDialog Seg Fault when Importing Keys
Status: RESOLVED UPSTREAM
Alias: None
Product: NeoChat
Classification: Applications
Component: General (other bugs)
Version First Reported In: git master
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Tobias Fella
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-14 00:29 UTC by Timothy Arnold
Modified: 2024-12-14 17:08 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Timothy Arnold 2024-12-14 00:29:27 UTC
SUMMARY
When running NeoChat on a non-native QT platform (e.g. Cosmic) and attempting to import Encryption keys, you get a seg fault.
`qrc:/qt/qml/org/kde/neochat/settings/ImportKeysDialog.qml:14:1: QML ImportKeysDialog (parent or ancestor of FileDialog): No QQmlContext for QQuickPlatformFileDialog; can't create non-native FileDialog implementation`

You're, however, able to attach files to a message successfully and the file dialog pops up correctly. It's not clear what the difference in file selection dialogs are to me.

STEPS TO REPRODUCE
1. Build Git Master of Neochat in a container image (I used Fedora 41 image) with appropriate dependencies
2. Click on Settings -> Security -> Import Keys -> Back Up File

OBSERVED RESULT

You receive a seg fault when you attempt to open the file dialog to import the back up

EXPECTED RESULT

On non-native platforms, you should still be able to open the file dialog to import keys

SOFTWARE/OS VERSIONS
NeoChat: 25.03.70
Fedora Linux 41 (Toolbx Container Image) (Wayland)
libQuotient: 0.9.0 (built against 0.9.0)
KDE Frameworks: 6.8.0
Qt: Using 6.8.0 and built against 6.8.0
Build ABI: x86_64-little_endian-lp64
Kernel: linux 6.9.3-76060903-generic

ADDITIONAL INFORMATION
This is in the course of getting a development environment ready in a container
Comment 1 Joshua Goins 2024-12-14 17:00:32 UTC
This is fixed in Qt 6.8.1, reproduced locally.
Comment 2 Joshua Goins 2024-12-14 17:08:24 UTC
Oh, and one more thing: Fedora just released Qt 6.8.1 for Fedora so if you update it'll most likely be fixed for you too!