Drop-OSS/drop-app
1
0
Fork 0
mirror of https://github.com/Drop-OSS/drop-app.git synced 2026-07-21 00:45:21 -04:00
Code Issues 41 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #168] [BUG] Instant crash, Nobara Linux, Grey and Blank Window #88

New Issue
Closed
opened 2026-02-17 17:12:03 -05:00 by yindo · 11 comments
yindo commented 2026-02-17 17:12:03 -05:00
Owner
Copy Link
Copy Source

Originally created by @ArchEngel0 on GitHub (Nov 6, 2025).
Original GitHub issue: https://github.com/Drop-OSS/drop-app/issues/168

Describe the bug
Nobara 42 Gnome 48.5 Wayland Nvidia

Cannot run any of the Appimages or the RPM.
When launched it briefly creates the window, then closes.

When I attempted the Nvidia fix: env WEBKIT_DISABLE_DMABUF_RENDERER=1, no change.
When I attempted the libappindicator fix, no change.
When I attempted an older beta version found in someone else's related issue the window opens, and stays open, but remains grey/blank, with no window decorations.

So I attempted to build the app, the build process was fun, got to learn about pkgconfig and that kinda thing, and even after finally getting successful builds no success.

To Reproduce
Steps to reproduce the behavior:
1a. run appimage
1b. run installed rpm

Expected behavior
Not an instant crash, not a blank/grey window.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: Nobara 42 Gnome 48.5 Wayland Nvidia
  • App Version: v0.3.3

Additional context
Server install on unraid went great as far as I could tell, so that's neat.

Originally created by @ArchEngel0 on GitHub (Nov 6, 2025). Original GitHub issue: https://github.com/Drop-OSS/drop-app/issues/168 **Describe the bug** Nobara 42 Gnome 48.5 Wayland Nvidia Cannot run any of the Appimages or the RPM. When launched it briefly creates the window, then closes. When I attempted the Nvidia fix: env WEBKIT_DISABLE_DMABUF_RENDERER=1, no change. When I attempted the libappindicator fix, no change. When I attempted an older beta version found in someone else's related issue the window opens, and stays open, but remains grey/blank, with no window decorations. So I attempted to build the app, the build process was fun, got to learn about pkgconfig and that kinda thing, and even after finally getting successful builds no success. **To Reproduce** Steps to reproduce the behavior: 1a. run appimage 1b. run installed rpm **Expected behavior** Not an instant crash, not a blank/grey window. **Screenshots** If applicable, add screenshots to help explain your problem. **Desktop (please complete the following information):** - OS: Nobara 42 Gnome 48.5 Wayland Nvidia - App Version: [v0.3.3](https://github.com/Drop-OSS/drop-app/releases/tag/v0.3.3) **Additional context** Server install on unraid went great as far as I could tell, so that's neat.
yindo commented 2026-02-17 17:12:03 -05:00
Author
Owner
Copy Link
Copy Source

@Pacodastre commented on GitHub (Nov 6, 2025):

I am having the same issue. You can run the app with an environment variable to fix the issue:

WEBKIT_DISABLE_DMABUF_RENDERER=1 drop-app.

@Pacodastre commented on GitHub (Nov 6, 2025): I am having the same issue. You can run the app with an environment variable to fix the issue: `WEBKIT_DISABLE_DMABUF_RENDERER=1 drop-app`.
yindo commented 2026-02-17 17:12:03 -05:00
Author
Owner
Copy Link
Copy Source

@Sixdd6 commented on GitHub (Nov 13, 2025):

I tried adding the mentioned environment variable and the app still crashes immediately after opening for me. Using Nobara 42. I also tried the rpm package and it refused to install, the log location it gave me was also empty so I don't know what error it encountered.

@Sixdd6 commented on GitHub (Nov 13, 2025): I tried adding the mentioned environment variable and the app still crashes immediately after opening for me. Using Nobara 42. I also tried the rpm package and it refused to install, the log location it gave me was also empty so I don't know what error it encountered.
yindo commented 2026-02-17 17:12:03 -05:00
Author
Owner
Copy Link
Copy Source

@Pacodastre commented on GitHub (Nov 13, 2025):

I installed nobara in a virtual machine, and i was able to install drop-app and run it using the rpm package. Though I don't have a nvidia GPU on this machine, so I could not test your use case.

When you tried using the WEBKIT_DISABLE_DMABUF_RENDERER environment variable, was it using the app image or the rpm package? If you haven't, try using this environment variable when running drop-app installed with the rpm package.

@Pacodastre commented on GitHub (Nov 13, 2025): I installed nobara in a virtual machine, and i was able to install drop-app and run it using the rpm package. Though I don't have a nvidia GPU on this machine, so I could not test your use case. When you tried using the `WEBKIT_DISABLE_DMABUF_RENDERER` environment variable, was it using the app image or the rpm package? If you haven't, try using this environment variable when running drop-app installed with the rpm package.
yindo commented 2026-02-17 17:12:03 -05:00
Author
Owner
Copy Link
Copy Source

@Sixdd6 commented on GitHub (Nov 13, 2025):

Sorry I should have specified, I added the variable to my bashrc when I tested. If I'm correct that would have worked regardless of packaging.

@Sixdd6 commented on GitHub (Nov 13, 2025): Sorry I should have specified, I added the variable to my bashrc when I tested. If I'm correct that would have worked regardless of packaging.
yindo commented 2026-02-17 17:12:03 -05:00
Author
Owner
Copy Link
Copy Source

@Pacodastre commented on GitHub (Nov 13, 2025):

Did you source your bashrc after changing the file? What if you try to run it from the terminal with the env variable in front?

WEBKIT_DISABLE_DMABUF_RENDERER=1 drop-app

@Pacodastre commented on GitHub (Nov 13, 2025): Did you source your bashrc after changing the file? What if you try to run it from the terminal with the env variable in front? `WEBKIT_DISABLE_DMABUF_RENDERER=1 drop-app`
yindo commented 2026-02-17 17:12:03 -05:00
Author
Owner
Copy Link
Copy Source

@Sixdd6 commented on GitHub (Nov 13, 2025):

This is what I got when running from Terminal:

-> WEBKIT_DISABLE_DMABUF_RENDERER=1 drop-app |./Drop.Desktop.Client_0.3.3_amd64.appimage
bash: drop-app: command not found...
2025-11-13T22:47:38.791216581-06:00 | INFO | src/process/process_handlers.rs:36 - Some("umu-run")
2025-11-13T22:47:38.791926717-06:00 | INFO | src/lib.rs:350 - initialized drop client
panicked at /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/libappindicator-sys-0.9.0/src/lib.rs:41:5:
Failed to load ayatana-appindicator3 or appindicator3 dynamic library
libayatana-appindicator3.so.1: cannot open shared object file: No such file or directory
/lib64/libdbusmenu-glib.so.4: undefined symbol: g_once_init_leave_pointer
libayatana-appindicator3.so: cannot open shared object file: No such file or directory
libappindicator3.so: cannot open shared object file: No such file or directory
Aborted (core dumped)

I may not be using the variable correctly there since it complains about the command.

@Sixdd6 commented on GitHub (Nov 13, 2025): This is what I got when running from Terminal: ``` -> WEBKIT_DISABLE_DMABUF_RENDERER=1 drop-app |./Drop.Desktop.Client_0.3.3_amd64.appimage bash: drop-app: command not found... 2025-11-13T22:47:38.791216581-06:00 | INFO | src/process/process_handlers.rs:36 - Some("umu-run") 2025-11-13T22:47:38.791926717-06:00 | INFO | src/lib.rs:350 - initialized drop client panicked at /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/libappindicator-sys-0.9.0/src/lib.rs:41:5: Failed to load ayatana-appindicator3 or appindicator3 dynamic library libayatana-appindicator3.so.1: cannot open shared object file: No such file or directory /lib64/libdbusmenu-glib.so.4: undefined symbol: g_once_init_leave_pointer libayatana-appindicator3.so: cannot open shared object file: No such file or directory libappindicator3.so: cannot open shared object file: No such file or directory Aborted (core dumped) ``` I may not be using the variable correctly there since it complains about the command.
yindo commented 2026-02-17 17:12:03 -05:00
Author
Owner
Copy Link
Copy Source

@Pacodastre commented on GitHub (Nov 13, 2025):

ok so a few things here:

  • I was suggesting this command assuming the rpm package was installed. If you're using the appimage, try running it like this: WEBKIT_DISABLE_DMABUF_RENDERER=1 ./Drop.Desktop.Client_0.3.3_amd64.appimage
  • it seems you don't have the appindicator library installed. You can install it with: sudo dnf install libayatana-appindicator-gtk3
  • There could also be some missing dbus libraries.

This is what the output looks like for me. The app is running.

Image
@Pacodastre commented on GitHub (Nov 13, 2025): ok so a few things here: - I was suggesting this command assuming the rpm package was installed. If you're using the appimage, try running it like this: `WEBKIT_DISABLE_DMABUF_RENDERER=1 ./Drop.Desktop.Client_0.3.3_amd64.appimage` - it seems you don't have the appindicator library installed. You can install it with: `sudo dnf install libayatana-appindicator-gtk3` - There could also be some missing dbus libraries. This is what the output looks like for me. The app is running. <img width="1610" height="1024" alt="Image" src="https://github.com/user-attachments/assets/c32b2cf2-4013-403a-a2c3-cd4af8f54204" />
yindo commented 2026-02-17 17:12:03 -05:00
Author
Owner
Copy Link
Copy Source

@Sixdd6 commented on GitHub (Nov 14, 2025):

Ok, I installed the appindicator package and it gave this output when run as you showed:

WEBKIT_DISABLE_DMABUF_RENDERER=1 ./Drop.Desktop.Client_0.3.3_amd64.appimage
2025-11-13T23:11:00.887315576-06:00 | INFO | src/process/process_handlers.rs:36 - Some("umu-run")
2025-11-13T23:11:00.888113763-06:00 | INFO | src/lib.rs:350 - initialized drop client
panicked at /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/libappindicator-sys-0.9.0/src/lib.rs:41:5:
Failed to load ayatana-appindicator3 or appindicator3 dynamic library
/lib64/libayatana-ido3-0.4.so.0: undefined symbol: g_once_init_leave_pointer
/lib64/libdbusmenu-glib.so.4: undefined symbol: g_once_init_leave_pointer
libayatana-appindicator3.so: cannot open shared object file: No such file or directory
libappindicator3.so: cannot open shared object file: No such file or directory
Aborted (core dumped)
@Sixdd6 commented on GitHub (Nov 14, 2025): Ok, I installed the appindicator package and it gave this output when run as you showed: ``` WEBKIT_DISABLE_DMABUF_RENDERER=1 ./Drop.Desktop.Client_0.3.3_amd64.appimage 2025-11-13T23:11:00.887315576-06:00 | INFO | src/process/process_handlers.rs:36 - Some("umu-run") 2025-11-13T23:11:00.888113763-06:00 | INFO | src/lib.rs:350 - initialized drop client panicked at /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/libappindicator-sys-0.9.0/src/lib.rs:41:5: Failed to load ayatana-appindicator3 or appindicator3 dynamic library /lib64/libayatana-ido3-0.4.so.0: undefined symbol: g_once_init_leave_pointer /lib64/libdbusmenu-glib.so.4: undefined symbol: g_once_init_leave_pointer libayatana-appindicator3.so: cannot open shared object file: No such file or directory libappindicator3.so: cannot open shared object file: No such file or directory Aborted (core dumped) ```
yindo commented 2026-02-17 17:12:03 -05:00
Author
Owner
Copy Link
Copy Source

@Pacodastre commented on GitHub (Nov 14, 2025):

did the install command for libayatana-appindicator-gtk3 work? It still doesn't look like it installed properly. Can you post the output of the install command?

@Pacodastre commented on GitHub (Nov 14, 2025): did the install command for libayatana-appindicator-gtk3 work? It still doesn't look like it installed properly. Can you post the output of the install command?
yindo commented 2026-02-17 17:12:03 -05:00
Author
Owner
Copy Link
Copy Source

@Sixdd6 commented on GitHub (Nov 14, 2025):

So I found the part of the docs that related to the tray icon and when running the appimage with NO_TRAY_ICON=true the app runs fine. For anyone else that finds this issue just run the appimage like so:

NO_TRAY_ICON=true WEBKIT_DISABLE_DMABUF_RENDERER=1 ./Drop.Desktop.Client_0.3.3_amd64.appimage

If you aren't running an nVidia graphics driver you can probably ignore the webkit part, I haven't tried without it though so ymmv.

@Sixdd6 commented on GitHub (Nov 14, 2025): So I found the part of the docs that related to the tray icon and when running the appimage with NO_TRAY_ICON=true the app runs fine. For anyone else that finds this issue just run the appimage like so: ``` NO_TRAY_ICON=true WEBKIT_DISABLE_DMABUF_RENDERER=1 ./Drop.Desktop.Client_0.3.3_amd64.appimage ``` If you aren't running an nVidia graphics driver you can probably ignore the webkit part, I haven't tried without it though so ymmv.
yindo commented 2026-02-17 17:12:03 -05:00
Author
Owner
Copy Link
Copy Source

@ArchEngel0 commented on GitHub (Nov 14, 2025):

Great, thanks @Sixdd6 this works, I can't believe I didn't try both of those at the same time earlier on!
I attempted each individually, as well as successfully installing the appindicators, but sometimes its like this.

@ArchEngel0 commented on GitHub (Nov 14, 2025): Great, thanks @Sixdd6 this works, I can't believe I didn't try both of those at the same time earlier on! I attempted each individually, as well as successfully installing the appindicators, but sometimes its like this.
yindo changed title from [BUG] Instant crash, Nobara Linux, Grey and Blank Window to [GH-ISSUE #168] [BUG] Instant crash, Nobara Linux, Grey and Blank Window 2026-06-05 14:24:43 -04:00
yindo closed this issue 2026-06-05 14:24:43 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
duplicate
feature
needs-triage
pull-request
Mirrored from GitHub Pull Request
 support
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Drop-OSS/drop-app#88
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?