8000 Randomly closes app on QT6/Wayland · Issue #2290 · doublecmd/doublecmd · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Randomly closes app on QT6/Wayland #2290

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
D33M0N opened this issue Apr 29, 2025 · 8 comments
Open

Randomly closes app on QT6/Wayland #2290

D33M0N opened this issue Apr 29, 2025 · 8 comments
Labels
bug Something isn't working

Comments

@D33M0N
Copy link
D33M0N commented Apr 29, 2025 •
edited
Loading

Version

Double Commander
Version: 1.1.23 gamma
Revision: 694
Commit: 15e166e
Build date: 2025/03/22
Lazarus: 3.8.0.0
FPC: 3.2.2
Platform: x86_64-Linux-qt6
OS version: Manjaro Linux

Widgetset library: Qt 6.9.0

Description

Swapped Manjaro doublecmd-qt5 (had 0 such issues) with doublecmd-qt6 package (technically a little bit delayed Arch linux package) and in less than 5 minutes it just closed itself.

apr   29 11:56:07 Zen kwin_wayland_wrapper[1838]: error in client communication (pid 2093616)
apr   29 11:56:07 Zen doublecmd[2093616]: xdg_surface#116: error 2: the surface already has a role assigned xdg_toplevel
apr   29 11:56:08 Zen systemd[1742]: app-doublecmd@64a3598e36fa4aef90964e5b67b666e3.service: Main process exited, code=exited, status=255/EXCEPTION
apr   29 11:56:08 Zen systemd[1742]: app-doublecmd@64a3598e36fa4aef90964e5b67b666e3.service: Failed with result 'exit-code'.
apr   29 11:56:08 Zen systemd[1742]: app-doublecmd@64a3598e36fa4aef90964e5b67b666e3.service: Consumed 14.382s CPU time, 536M memory peak.

and again...

apr   29 12:09:28 Zen kwin_wayland_wrapper[1838]: error in client communication (pid 2095091)
apr   29 12:09:28 Zen doublecmd[2095091]: Dexdg_surface#58: error 2: the surface already has a role assigned xdg_toplevel
apr   29 12:09:28 Zen systemd[1742]: app-doublecmd@e1ce3950433c45e0be153aed65364336.service: Main process exited, code=exited, status=255/EXCEPTION
apr   29 12:09:28 Zen systemd[1742]: app-doublecmd@e1ce3950433c45e0be153aed65364336.service: Failed with result 'exit-code'.
apr   29 12:09:28 Zen systemd[1742]: app-doublecmd@e1ce3950433c45e0be153aed65364336.service: Consumed 7.772s CPU time, 183.8M memory peak.
@D33M0N D33M0N added the bug Something isn't working label Apr 29, 2025
@D33M0N
Copy link
Author
D33M0N commented Apr 29, 2025

qt5 version works perfectly.
(Double Commander
Version: 1.1.23 gamma
Revision: 694
Commit: 15e166e
Build date: 2025/03/22
Lazarus: 3.8.0.0
FPC: 3.2.2
Platform: x86_64-Linux-qt5
OS version: Manjaro Linux

Widgetset library: Qt 5.15.16)

@pwn0r
Copy link
pwn0r commented Apr 29, 2025

finally someone actually reported this -- was thinking of making a report myself already.

i have the same problem on two different manjaro machines, both VM and real. I think the issue maybe related to the most recent gnome/qt6 updates?

Thing is that my version of doublecmd is more updated but the issue is still same.

Double Commander
Version: 1.1.24 gamma
Revision: 721
Commit: 5b42d86
Build date: 2025/04/23
Lazarus: 3.8.0.0
FPC: 3.2.2
Platform: x86_64-Linux-qt6
OS version: Manjaro Linux

Widgetset library: Qt 6.9.0

@alexx2000
Copy link
Contributor

Qt6 has a serious problems under Wayland. I am not recommend to use it. Qt5 is a best choice for Wayland at this time.

@ciros88
Copy link
ciros88 commented May 5, 2025

switched today from doublecmd-qt5 to doublecmq-qt6 (manjaro linux) and yeh, same issue

@ciros88
Copy link
ciros88 commented May 5, 2025 •
edited
Loading

seems this avoids the crashes:
export QT_QPA_PLATFORM=xcb; doublecmd

if you confirm this works, here's the workaround code:
githubuser0xFFFF/Qt-Advanced-Docking-System#714

@alexx2000
Copy link
Contributor
alexx2000 commented May 5, 2025 •
edited
Loading

seems this avoids the crashes:

Yes, of course. Because this is a Wayland only problem. With QT_QPA_PLATFORM=xcb DC starts using XWayland. But XWayland can have some other problems...

@ciros88
Copy link
ciros88 commented May 5, 2025 •
edited
Loading

Yeh XWayland currently seems a good way: my proposal is to set xcb at code level until wayland issues will be fixed, instead of being forced to install deprecated qt5 lib on a modern linux system

@D33M0N
Copy link
Author
D33M0N commented May 7, 2025

Yeh XWayland currently seems a good way: my proposal is to set xcb at code level until wayland issues will be fixed, instead of being forced to install deprecated qt5 lib on a modern linux system

I rather use QT5 version with wayland than anything with Xwayland. But I guess, for everyone their own...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@alexx2000 @D33M0N @pwn0r @ciros88
0