Some apps not working after upgrade to Gnome 49

Hi there

Can I please have some advise with regards to the latest Gnome 49 update. Unfortunately a number of my apps (notably pCloud) are not working anymore. I understand that this is because Gnome 49 is now only supporting Weyland. I have tried to research options to get those apps running again under 49 but without finding a workable solution.

I read something about XWeyland - is that an option and how would I get this to work?

Alternatively, how can I go back to 48 and how to prevent my Garuda installation from upgrading to 49?

Any other options?

Thank you for your help.

Here is the output when starting pCloud from the cl:

> ./pcloud\(1\)_97b979aec321bdcf0247e9c5c60f4579
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
QSocketNotifier: Can only be used with threads started with QThread
Using TARGET_APPIMAGE /home/stephane/Applications/pcloud(1)_97b979aec321bdcf0247e9c5c60f4579
System:
  Kernel: 6.16.10-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.2.1 clocksource: hpet
    avail: acpi_pm parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=4ac36184-11e7-4536-9f5e-da586189d82d rw rootflags=subvol=@ quiet loglevel=3
  Desktop: GNOME v: 49.0 tk: GTK v: 3.24.51 wm: gnome-shell tools: gsd-screensaver-proxy dm: GDM
    v: 49.0.1 Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop Mobo: BESSTAR TECH model: UM700 v: V1.0 serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends v: AF5NV701.25 date: 12/15/2020
CPU:
  Info: model: AMD Ryzen 7 3750H with Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen/Zen+
    note: check gen: 1 level: v3 note: check built: 2019 process: GF 12nm family: 0x17 (23)
    model-id: 0x18 (24) stepping: 1 microcode: 0x8108102
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 4 threads: 8 tpc: 2 smt: enabled cache:
    L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 1532 min/max: 1400/2300 boost: enabled scaling: driver: acpi-cpufreq
    governor: schedutil cores: 1: 1532 2: 1532 3: 1532 4: 1532 5: 1532 6: 1532 7: 1532 8: 1532
    bogomips: 36732
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile
    Series] driver: amdgpu v: kernel arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie:
    gen: 3 speed: 8 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1,DP-2,DP-3 bus-ID: 05:00.0
    chip-ID: 1002:15d8 class-ID: 0300 temp: 50.0 C
  Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8 compositor: gnome-shell
    driver: X: loaded: amdgpu unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu display-ID: 0
  Monitor-1: HDMI-A-1 model: Acer KG271 G serial: <filter> built: 2021 res: 1920x1080 dpi: 82
    gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes: max: 1920x1080
    min: 720x400
  API: Vulkan v: 1.4.321 layers: 9 device: 0 type: integrated-gpu name: AMD Radeon Vega 10
    Graphics (RADV RAVEN) driver: mesa radv v: 25.2.4-arch1.1 device-ID: 1002:15d8 surfaces: N/A
    device: 1 type: cpu name: llvmpipe (LLVM 20.1.8 256 bits) driver: mesa llvmpipe
    v: 25.2.4-arch1.1 (LLVM 20.1.8) device-ID: 10005:0000 surfaces: N/A
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: vulkaninfo x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 05:00.1
    chip-ID: 1002:15de class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Audio Coprocessor driver: snd_pci_acp3x v: kernel
    alternate: snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x,
    snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh, snd_sof_amd_acp63,
    snd_sof_amd_acp70 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 05:00.5 chip-ID: 1022:15e2
    class-ID: 0480
  Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.16.10-zen1-1-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 1.4.8 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 02:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp2s0 state: down mac: <filter>
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  Device-3: Intel Wireless 7265 driver: iwlwifi v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    bus-ID: 04:00.0 chip-ID: 8086:095a class-ID: 0280
  IF: wlp4s0 state: up mac: <filter>
  IF-ID-1: eno1 state: down mac: <filter>
  IF-ID-2: proton0 state: unknown speed: N/A duplex: N/A mac: N/A
  IF-ID-3: pvpnksintrf0 state: unknown speed: N/A duplex: N/A mac: <filter>
  Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-2:2 chip-ID: 8087:0a2a class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.2 lmp-v: 8 status:
    discoverable: no pairing: no class-ID: 6c0104
Drives:
  Local Storage: total: 2.1 TiB used: 190.51 GiB (8.9%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: OM8PDP3256B-A01 size: 238.47 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: EDFK0S03 temp: 40.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Fanxiang model: S101Q 2TB MX size: 1.86 TiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 003 scheme: GPT
Partition:
  ID-1: / raw-size: 1.86 TiB size: 1.86 TiB (100.00%) used: 190.51 GiB (10.0%) fs: btrfs
    dev: /dev/sda2 maj-min: 8:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 632 KiB (0.2%) fs: vfat
    dev: /dev/sda1 maj-min: 8:1
  ID-3: /home raw-size: 1.86 TiB size: 1.86 TiB (100.00%) used: 190.51 GiB (10.0%) fs: btrfs
    dev: /dev/sda2 maj-min: 8:2
  ID-4: /var/log raw-size: 1.86 TiB size: 1.86 TiB (100.00%) used: 190.51 GiB (10.0%) fs: btrfs
    dev: /dev/sda2 maj-min: 8:2
  ID-5: /var/tmp raw-size: 1.86 TiB size: 1.86 TiB (100.00%) used: 190.51 GiB (10.0%) fs: btrfs
    dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 15.32 GiB used: 0 KiB (0.0%) priority: 100 comp: zstd
    avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 49.6 C mobo: N/A gpu: amdgpu temp: 49.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB note: est. available: 15.32 GiB used: 3.65 GiB (23.9%)
  Processes: 376 Power: uptime: 24m states: freeze,mem,disk suspend: deep avail: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 6.1 GiB
    services: gsd-power, power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical
    tool: systemctl
  Packages: pm: pacman pkgs: 2145 libs: 540 tools: octopi,paru,yay Compilers: clang: 20.1.8
    gcc: 15.2.1 Client: Unknown Client: electron inxi: 3.3.39
Garuda (2.11.1-1):
  System install date:     2025-02-22
  Garuda release:          240428
  Last full system update: 2025-10-03
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut garuda-hardware-profile-standard garuda-hardware-profile-standard-x11
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:            
--- System Health Check Report ---
23/24 checks run in 1.63 seconds ⌛
Powered by garuda-health 🦅

âś… System health check passed. No issues found.

Have you tried that?

4 Likes

This is possible using downgrade and IgnorePkg in pacman.conf, but it is strongly NOT advisable in the case of a DE. Garuda Linux is arch-based and therefore rolling release, which means that partial updates are generally not supported or recommended. Partial upgrade`s/updates should only be used for testing purposes and in exceptional cases - they are not intended as a permanent solution. With Gnome 48, this would mean that dependencies would be missing or the corresponding version would be incompatible during one of the next system updates, which would cause your system to break.

What other applications (besides pCloud)?

1 Like

Just using the following is not making any difference.

QT_QPA_PLATFORM=wayland

I did some more reading and came across this suggestion:

QT_QPA_PLATFORM="wayland;xcb"

This seems to work for my other apps formerly not wanting to start. Such as:

HiFile (file manager)

4kvideodownloaderplus

Unfortunately it is not working with pCloud, which is the most important app for me! Here is the shell output when trying to start pCloud:

> QT_QPA_PLATFORM="wayland;xcb" pcloud
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
QSocketNotifier: Can only be used with threads started with QThread
Using TARGET_APPIMAGE /opt/pcloud/pcloud-drive.AppImage

Okay, downgrading is then not an option. I really need to get pCloud working!

Please see the post I just wrote about adding xcb to the option.

Have you tried using the App Image version?

Yes, I have. Download the latest version - no success. Tried starting the Arch installed version - no success.

Maybe look for a gnome app that interacts with pcloud? like GitHub - hwittenborn/celeste: GUI file synchronization client that can sync with any cloud provider | S3Drive. I’m sure there are others.

2 Likes

What if you force the program to launch with x11?

QT_QPA_PLATFORM="xcb" XDG_SESSION_TYPE=x11 pcloud

Thanks TNE, I’ve tried that but unfortunately that’s not working either. Interestingly enough this command is executing without any error messages (but pCloud is not launching).

I wrote an email to the pCloud support but haven’t heard back yet (may never happen :frowning:

Are other x11 applications working?

This might be a bug that is reportable to xwayland.

I quickly tested it in a VM - Garuda Gnome (garuda-gnome-linux-zen-251002.iso) fully up to date. Installed pcloud-drive from the AUR and it launches OOTB (I can’t test it further due to lack of an account).

3 Likes

Hi @nepti , that is good news!

The not so good news is that I don’t know what’s wrong.

The system information in your screen shot is identical to mine (apart from CPU and GPU).

I wonder if there is something I have installed that causes the problem. I don’t tinker with the system and normally leave everything as is.

I only completely installed Garuda again a few weeks ago as it was broken after an update. I don’t really want to go through all this again.

I’m stuck.

You have obviously installed Gnome 49 fresh - whereas I have upgraded from 48 to 49. I wonder if there is some legacy stuff which makes problems.

Yep.

I tested exactly this scenario yesterday with an older Garuda Gnome ISO (garuda-gnome-linux-zen-250308.iso) to check whether pcloud still works after updating to Gnome 49 – and it works without any issues:

clean install w/o updates

after the full system update

And after a quick internet search, I couldn’t find anyone else who was having issues with pcloud and Gnome 49. Looks like the problem lies with your system.

2 Likes

Have you tried launching this application on a new user account?

That way we can isolate if the application is at fault or the system is at fault.

4 Likes

Hi there, I got a response from the pCloud support team. They suggested to remove AppImageLauncher which I have done now. This has solved the problem and pCloud is now launching and working without any errors. I can live without AppImageLauncher.

Thanks @TNE @nepti and the others for all your time, help and suggestions.

Kind regards

Stephane

5 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.