| Summary: | AppImage fails to start in Wayland session | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Roman Gilg <subdiff> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | kde, mail, meven29, notuxius, probono |
| Priority: | NOR | Keywords: | wayland-only |
| Version First Reported In: | 5.0.2 | ||
| Target Milestone: | --- | ||
| Platform: | Appimage | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Roman Gilg
2016-11-11 14:11:59 UTC
No, didn't. Don't know if I want to build the wayland stuff on centos 6, but I'll have a look. Is it true that we now need to bundle QtWayland with all Qt applications in order for them to launch on Wayland? Wouldn't that mean that all older applications refuse to run under Wayland? I cannot imagine that, do you have a pointer to documentation saying that? Wayland is a completely new graphics system. Nothing will run there unless the framework and/or application ports to that stack. For Qt, unless you ship the Wayland platform plugin, your application has no chance to run. KDevelop-5.2.3-x86_64.AppImage is launching ok in Wayland session with appimagelauncher 1.0alpha+git20180707.84edcfc-1
Distribution: Netrunner Rolling
Kernel: 4.18.0-1-MANJARO
Plasma: 5.13.3
Apps: 18.04.3
Qt: 5.11.1
Frameworks: 5.47.0
Wayland: 1.15.0
Graphics: Card-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel bus ID: 00:02.0
chip ID: 8086:0a16
Display: wayland server: X.Org 1.20.0 driver: intel unloaded: modesetting compositor: kwin_wayland
tty: N/A
OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 18.1.4 compat-v: 3.0 direct render: Yes
I would expect that uses XWayland, right? Possibly, but it'll launch. We've fixed things so that Qt will use X or wayland depending on both what sockets are available and what plugins are available. It'll always launch now. |