| Summary: | k4dirstat crashes under wayland | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Emmanuel Touzery <emmanuel.touzery> |
| Component: | qt5 | Assignee: | Helio Chissini de Castro <helio> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | fedora, helio, kryzhev |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-08 19:35:18 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Emmanuel Touzery
2016-11-28 07:11:47 UTC
Well. I haven't machine with wayland. Anyway, looks like for some reasons it calls gtk2 which lacks wayland support. At all. And looks like EVERY kf5 package linked with gtk2 as Qt5 is. That strange. I suppose I can't do anything here for now. maybe it tries to display the gtk2 file picker if it detects a gnome environment? That's correct. It does. And as Wayland is default for Gnome now k4dirstat fails to use X features and fall. The workaround could be starting it as following: GDK_BACKEND=x11 k4dirstat Or to force usage of qt file picker. qgnomeplatform package could help here (or not, I can't test this, sorry). Note that the same problem also affects qtcreator. The GDK_BACKEND=x11 trick helps for both applications. given that this happens with k4dirstat, qtcreator and also a custom-built Qt5 QML application of mine, I think this should be assigned to the "qt" component in general, not k4dirstat in particular. Hopefully the maintainers there can do something about this, it's quite a serious problem... It's a GTK bug not Qt I suppose. This bug is probably a duplicate of bug #1392605. I agree, closing as duplicate. *** This bug has been marked as a duplicate of bug 1392605 *** |