search

FyraLabs-Graveyard / skiff-desktop

Skiff, now on a Linux Desktop near you!
GNU General Public License v3.0
33 stars 6 forks source link

[BUG] Fail to display window content #11

Open madonuko opened 8 months ago

madonuko commented 8 months ago

Description

Skiif Desktop when started on KDE Plasma (both Wayland and X11) shows a blank window: image

On the same computer, it runs fine on Budgie.

System information

App information

Skiff - Privacy-first end-to-end encrypted email

          ID: com.fyralabs.SkiffDesktop
         Ref: app/com.fyralabs.SkiffDesktop/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 0.1.7
     License: GPL-3.0-or-later
      Origin: flathub
  Collection: org.flathub.Stable
Installation: system
   Installed: 3.7 MB
     Runtime: org.gnome.Platform/x86_64/45
         Sdk: org.gnome.Sdk/x86_64/45

      Commit: af48c28c8b8ee08fcdcd44f2b1a03ac2ec280dfd99e4b4a35848e2f29850bb9d
      Parent: 1ea5f1c5465485f37958c0e93b56ff1e44a426e310b2c1bdc066500317b7d2ff
     Subject: fix: update commit sha (1b209aa4)
        Date: 2024-01-07 01:24:10 +0000

Logs

(com.fyralabs.SkiffDesktop:2): Gtk-CRITICAL **: 22:34:26.154: gtk_widget_get_first_child: assertion 'GTK_IS_WIDGET (widget)' failed

(com.fyralabs.SkiffDesktop:2): Gtk-CRITICAL **: 22:34:26.154: gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed

(com.fyralabs.SkiffDesktop:2): Gtk-CRITICAL **: 22:34:26.402: gtk_widget_get_first_child: assertion 'GTK_IS_WIDGET (widget)' failed

(com.fyralabs.SkiffDesktop:2): Gtk-CRITICAL **: 22:34:26.402: gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed flatpak-spawn: Invalid byte sequence in conversion input Try "flatpak-spawn --help" for more information.

ghost commented 8 months ago

I have the same exact behavior, however this behavior only happens to me on wayland.

Im running Arch Linux with KDE Plasma, and when i start a session on x11 on a fresh boot skiff desktop works fine and launches (both on flatpak and manual build), but if i do a fresh boot and launch into Wayland, it will not work and i get the behavior as stated above.

Edit : A temporary workaround at least on my end, is to set KDE plasma display settings for monitor to 100% scaling when in the Plasma Wayland session, and then application then launches when i relaunch skiff-desktop. However, upon closure and if i were to attempt to launch anything higher than 100%, it will refuse to launch as the above image shows as well.

madonuko commented 8 months ago

That's really interesting. This is my test results:

So it basically works on every single desktop environment / window manager other than KDE Plasma. My display scaling is set to 100% all the time. I cannot set it to be lower than 100%.

Update: I have manually built Skiff myself and it works, meaning the issue only exists for the Flatpak version on KDE Plasma for me.

ghost commented 8 months ago

I can confirm too, get the same thing, any other environment works ( hyprland , i3-wm ) all work but kde is being silly on my end as well. I'll try manually building and see if it works good on my end :)

lleyton commented 8 months ago

Hm, can you test the GNOME Web Flatpak on Plasma? It also uses webkitgtk.

madonuko commented 8 months ago

Can confirm GNOME Web just crashes with the same flatpak-spawn error, might be an issue with webkitgtk in flatpaks?

borisjulinuv7 commented 8 months ago

i confirm this happen to me to on Nobara KDE (modified) wayland if someone know a work around i would take it.

edit : the simple 100% ui scale work for me

ghost commented 8 months ago

RIP skiff :C everybody check your emails

lleyton commented 8 months ago

you gotta be fucking me

lleyton commented 8 months ago

well, I guess that also means, goodbye Skiff Desktop for Linux