FS#64488 - [kdeconnect] missing depency on qt5-wayland

Attached to Project: Community Packages
Opened by Nathan Wallace (nwallace) - Wednesday, 13 November 2019, 13:06 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 14 November 2019, 10:17 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Package cannot run when installed on a system without qt5-wayland.

Package version 1.3.5-3

Here's the systemctl status output for my kdeconnectd service that shows the failure:

```
● kdeconnectd.service - Daemon to connect your Android phone with your Linux desktop.
Loaded: loaded (/home/nathan/.config/systemd/user/kdeconnectd.service; linked; vendor preset: enabled)
Active: failed (Result: core-dump) since Wed 2019-11-13 06:46:52 CST; 1min 26s ago
Process: 5885 ExecStart=/usr/lib/kdeconnectd (code=dumped, signal=ABRT)
Main PID: 5885 (code=dumped, signal=ABRT)

Nov 13 06:46:52 professor systemd[3425]: Started Daemon to connect your Android phone with your Linux desktop..
Nov 13 06:46:52 professor kdeconnectd[5885]: qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
Nov 13 06:46:52 professor kdeconnectd[5885]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
Nov 13 06:46:52 professor systemd[3425]: kdeconnectd.service: Main process exited, code=dumped, status=6/ABRT
Nov 13 06:46:52 professor systemd[3425]: kdeconnectd.service: Failed with result 'core-dump'.
Nov 13 06:46:52 professor systemd-coredump[5895]: Process 5885 (kdeconnectd) of user 1000 dumped core.

Stack trace of thread 5885:
#0 0x00007ff4acb5cf25 raise (libc.so.6)
#1 0x00007ff4acb46897 abort (libc.so.6)
#2 0x00007ff4acf598f4 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5)
#3 0x00007ff4ad6384e5 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5)
#4 0x00007ff4ad638d81 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5)
#5 0x00007ff4ad1694e5 _ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5)
#6 0x00007ff4ad63ab30 _ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5)
#7 0x00007ff4adc6603a _ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5)
#8 0x000055ce6aec4166 n/a (kdeconnectd)
#9 0x00007ff4acb48153 __libc_start_main (libc.so.6)
#10 0x000055ce6aec471e _start (kdeconnectd)

```

After installing the package qt5-wayland, the service started normally and is running fine.

Steps to reproduce:
1. From a fresh Arch install, install a non-KDE wayland desktop (I'm using sway, though I believe GNOME would exhibit the bug as well)
2. Install kdeconnect
This task depends upon

Closed by  Antonio Rojas (arojas)
Thursday, 14 November 2019, 10:17 GMT
Reason for closing:  Fixed
Additional comments about closing:  Added optdepend for 5.14
Comment by Antonio Rojas (arojas) - Wednesday, 13 November 2019, 13:36 GMT
This is unrelated to kdeconnect. You need either qt5-wayland (or xwayland as a fallback) to run any Qt application in a pure wayland session. I don't think this is something that can be solved via dependencies, feel free to document it on the wiki.
Comment by Nathan Wallace (nwallace) - Wednesday, 13 November 2019, 21:48 GMT
Do you think either kwayland or qt5-base should have qt5-wayland as a dependency then? I wondered if maybe I should report the bug against one of those packages instead (kdeconnect depends on both of those). But maybe it's not appropriate, since wayland is just one display server option and the user might have X instead?
Comment by Antonio Rojas (arojas) - Thursday, 14 November 2019, 10:13 GMT
Not kwayland, that is only relevant for KDE applications and this affects all Qt ones. Best I can do is add an optional dependency to qt5-base.

Loading...