Bug 372346 - AppImage fails to start in Wayland session
Summary: AppImage fails to start in Wayland session
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 5.0.2
Platform: Appimage Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords: wayland-only
Depends on:
Blocks:
 
Reported: 2016-11-11 14:11 UTC by Roman Gilg
Modified: 2020-04-07 21:29 UTC (History)
5 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 Roman Gilg 2016-11-11 14:11:59 UTC
At the moment the AppImage is not starting in Wayland session. Did you bundle QtWayland in the AppImage?
Comment 1 Sven Brauch 2016-11-11 20:02:23 UTC
No, didn't. Don't know if I want to build the wayland stuff on centos 6, but I'll have a look.
Comment 2 probono 2017-11-20 07:38:13 UTC
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?
Comment 3 Sven Brauch 2017-11-20 12:35:23 UTC
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.
Comment 4 Alexander Mentyu 2018-07-15 16:38:58 UTC
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
Comment 5 Sven Brauch 2019-10-17 10:43:29 UTC
I would expect that uses XWayland, right?
Comment 6 David Edmundson 2020-04-07 21:29:48 UTC
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.