Skip to content
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.

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

Closes soon after opening (Wayland with Nvidia proprietary drivers) #226

Closed
Filip-Anicic opened this issue Aug 5, 2024 · 10 comments
Closed

Comments

@Filip-Anicic
Copy link

Few seconds after opening the application with my messages being loaded. The application closes without any message.
Is there a way to fix this as I was looking for a good WhatsApp client on Linux?

Linux
flatpack 5.3.7
Fedora 40 Workstation
Gnome 46 DE

@rafatosta
Copy link
Owner

Few seconds after opening the application with my messages being loaded. The application closes without any message. Is there a way to fix this as I was looking for a good WhatsApp client on Linux?

Linux flatpack 5.3.7 Fedora 40 Workstation Gnome 46 DE

Run via command line and check for errors, please

flatpak run com.rtosta.zapzap

@rafatosta
Copy link
Owner

I'm using Fedora Workstation too and I don't have a problem. I believe that the log of your execution can inform what is the problem with your machine

@Filip-Anicic
Copy link
Author

Filip-Anicic commented Aug 7, 2024

This is the output I get in the terminal

QPropertyAnimation: you're trying to animate the non-writable property width of your QObject
QDBusTrayIcon encountered a D-Bus error: QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name is not activatable")
The Wayland connection experienced a fatal error: Protocol error

@rafatosta
Copy link
Owner

This is the output I get in the terminal

QPropertyAnimation: you're trying to animate the non-writable property width of your QObject
QDBusTrayIcon encountered a D-Bus error: QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name is not activatable")
The Wayland connection experienced a fatal error: Protocol error

Do you have Nvidia?

Try switching to X11 via flatsel or using the copr version

@Filip-Anicic
Copy link
Author

Yes I have Nvidia proprietary drivers.
The suggestion to use Flatseal and disable Wayland windowing system, while keeping X11 windowing system and fallback seems to work.

Thanks

@Filip-Anicic
Copy link
Author

Should I keep the issue open since the Wayland bug is not fixed yet?

@Filip-Anicic Filip-Anicic changed the title Closes soon after opening Closes soon after opening (Wayland with Nvidia proprietary drivers) Aug 16, 2024
@rafatosta
Copy link
Owner

rafatosta commented Aug 16, 2024

Should I keep the issue open since the Wayland bug is not fixed yet?

Yes. I'm about to buy a new notebook with NVidia. Let's wait and see.

@sergiotca
Copy link

Hi guys, same issue here (Wayland).
I just wanted to add onto Filip's documentation with a bit longer log:

[sergiotca@fedora ~]$ flatpak run com.rtosta.zapzap
qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
QPropertyAnimation: you're trying to animate the non-writable property width of your QObject
QDBusTrayIcon encountered a D-Bus error: QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name is not activatable")
js: Error with Permissions-Policy header: Feature xr-spatial-tracking's parameters are ignored.
js: Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'attribution-reporting'.
js: Error with Permissions-Policy header: Unrecognized feature: 'bluetooth'.
js: Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'compute-pressure'.
js: Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'interest-cohort'.
js: Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'shared-storage'.
js: Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'shared-storage-select-url'.
QPropertyAnimation: you're trying to animate the non-writable property width of your QObject
The Wayland connection experienced a fatal error: Protocl error

There are no crashes if I run it on X11 though (flatpak nosocket=wayland run com.rtosta.zapzap).
So... Wayland issue, perhaps?

System:
-App Flatpak 5.3.7
-Fedora 40
-Gnome 46 + Wayland
-Nvidia Driver 560.35.03

@rafatosta
Copy link
Owner

Hi guys, same issue here (Wayland). I just wanted to add onto Filip's documentation with a bit longer log:

[sergiotca@fedora ~]$ flatpak run com.rtosta.zapzap
qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
QPropertyAnimation: you're trying to animate the non-writable property width of your QObject
QDBusTrayIcon encountered a D-Bus error: QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name is not activatable")
js: Error with Permissions-Policy header: Feature xr-spatial-tracking's parameters are ignored.
js: Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'attribution-reporting'.
js: Error with Permissions-Policy header: Unrecognized feature: 'bluetooth'.
js: Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'compute-pressure'.
js: Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'interest-cohort'.
js: Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'shared-storage'.
js: Error with Permissions-Policy header: Origin trial controlled feature not enabled: 'shared-storage-select-url'.
QPropertyAnimation: you're trying to animate the non-writable property width of your QObject
The Wayland connection experienced a fatal error: Protocl error

There are no crashes if I run it on X11 though (flatpak nosocket=wayland run com.rtosta.zapzap). So... Wayland issue, perhaps?

System: -App Flatpak 5.3.7 -Fedora 40 -Gnome 46 + Wayland -Nvidia Driver 560.35.03

Yes, it's a Wayland and Nvidia problem, unfortunately.

@rafatosta
Copy link
Owner

duplicate: Can't run on Wayland #215

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants