[Issue]: MegaSync Crash on ArchLinux KDE Plasma

# Issue - MegaSync Crash on ArchLinux KDE Plasma ### **Summary** Provide a brief summary of the issue or suggestion. Everytime I enter into my desktop environment, MegaSync crashes. It's been there for a couple of weeks (maybe 2-3 weeks). <img width="1256" height="652" alt="Image" src="https://github.com/user-attachments/assets/a25a4e18-00cc-41ff-b428-24ca5f94ddca" /> This is the details in the Crashed Processes Viewer: [megasync_crash.log](https://github.com/user-attachments/files/25826823/megasync_crash.log) --- ### **Environment Details** Provide details about the environment where the issue occurred. ``` -` taot@taot-t14 .o+` ------------- `ooo/ OS: Arch Linux x86_64 `+oooo: Host: 21AHCTO1WW (ThinkPad T14 Gen 3) `+oooooo: Kernel: Linux 6.19.6-arch1-1 -+oooooo+: Uptime: 3 mins `/:-:++oooo+: Packages: 1791 (pacman), 7 (flatpak) `/++++/+++++++: Shell: bash 5.3.9 `/++++++++++++++: Display (DELL P2222H): 1920x1080 in 22", 60 Hz [External] * `/+++ooooooooooooo/` Display (CMN143F): 1920x1200 @ 1.4x in 14", 60 Hz [Built-in] ./ooosssso++osssssso+` DE: KDE Plasma 6.6.2 .oossssso-````/ossssss+` WM: KWin (Wayland) -osssssso. :ssssssso. WM Theme: Breeze :osssssss/ osssso+++. Theme: Breeze (Classic) [Qt], Breeze [GTK2/3] /ossssssss/ +ssssooo/- Icons: breeze [Qt], breeze [GTK2/3/4] `/ossssso+/:- -:/+osssso+- Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4] `+sso+:-` `.-/+oso: Cursor: breeze (24px) `++:. `-/+/ Terminal: tmux 3.6a .` `/ CPU: 12th Gen Intel(R) Core(TM) i5-1240P (16) @ 4.40 GHz GPU 1: NVIDIA GeForce MX550 [Discrete] GPU 2: Intel Iris Xe Graphics @ 1.30 GHz [Integrated] Memory: 4.17 GiB / 23.17 GiB (18%) Swap: 0 B / 4.00 GiB (0%) Disk (/): 344.17 GiB / 475.94 GiB (72%) - btrfs Local IP (wlp0s20f3): [192.168.68.55/22](http://192.168.68.55/22) Battery (5B10W51865): 96% [AC Connected] Locale: en_US.UTF-8 ``` --- ### **Helpdesk Support** Have you already contacted our [support team](https://mega.io/contact)? If so, please provide the ticket ID to help us track it: Ticket ID: UEP-467-69578 --- ### **Additional Context** I asked OpenCode with the system information and error log. Here's the suggestions it gave me: ``` You’ve got a real issue, and it’s not RAM pressure. - The crash is in Qt’s XCB GLX integration path (libqxcb-glx-integration.so) while creating a QQuickWidget render context (QQuickRenderControl), exactly where your stack points. - In this codebase, MEGAsync explicitly forces itself off Wayland by unsetting XDG_SESSION_TYPE on Linux Wayland sessions (src/MEGASync/main.cpp:437, src/MEGASync/main.cpp:443), which pushes it into XCB/XWayland + GLX. - The app uses QQuickWidget in multiple startup UI paths (src/MEGASync/gui/qml/QmlWidgetWrapper.h:27, src/MEGASync/gui/qml/MegaQuickWidget.h:7), so it hits that GL integration early. - Your crash is recurrent, not one-off: older coredumps (e.g. PID 1514 on Feb 26) show the same QXcbNativeInterface::addHandler -> libqxcb-glx-integration.so failure chain. - So the likely root cause is: XCB GLX backend instability on your Wayland/KDE setup when MEGAsync forces X11 mode. Quick workaround (no code changes): - Launch/autostart MEGAsync with QT_XCB_GL_INTEGRATION=none (or xcb_egl) and optionally MEGA_LIBGL_ALWAYS_SOFTWARE=1. - Since your autostart comes from ~/.config/autostart/megasync.desktop, set Exec to: - Exec=env QT_XCB_GL_INTEGRATION=none MEGA_LIBGL_ALWAYS_SOFTWARE=1 megasync Recommended code fix in repo: - Keep current behavior, but when Wayland is detected and app still chooses XCB, set a safer default before QApplication creation: - QT_XCB_GL_INTEGRATION=none (recommended) or xcb_egl. - This change belongs in Linux startup env handling near src/MEGASync/main.cpp:437. If you want, I can prepare a patch now with a conservative default (QT_XCB_GL_INTEGRATION=none only when Wayland session is detected and user hasn’t explicitly set it). ``` I followed its quick workaround and set the `Exec` to this in `~/.config/autostart/megasync.desktop` ``` Exec=env QT_XCB_GL_INTEGRATION=none MEGA_LIBGL_ALWAYS_SOFTWARE=1 megasync ``` and seems it did solve the issue. I tried restarting my machine for a few times and didn't see that error again. While the workaround seems working, it might be better to fix it in a proper way. Please fix this or give suggestions. Thanks! --- > **Note:** Issues without enough details may be closed or take longer to address.