Missing icon and app name in the dash of Gnome Shell

[Digitalone1]

Is there an existing issue for this?

• I have searched the existing issues.

What's the problem?

As shown in the screenshot. Usually this issue is resolved specifying StartupWMClass in the .desktop file. Tried it, but nothing changes.

Maybe an issue related to iced library. I don't know. Should be investigated.

How did you install the app?

downloaded one of the provided packages

Operating System

Linux

Additional context

https://archlinux.org/packages/extra/x86_64/sniffnet/

[Digitalone1]

Making some researches I found out these:

• Gnome wmclass is null in Wayland rust-windowing/glutin#1067
• Introduce WindowBuilderExt::with_app_id for wayland rust-windowing/winit#700
• https://developer.gnome.org/documentation/tutorials/application-id.html

TLDR: The app needs an id in Wayland. Maybe it's not set and this causes the issue? The question is whether iced has a way to set it.

[Digitalone1]

Maybe the id here, but I don't know if it's already specified.

[GyulyVGC]

Mm, it's not a problem related to iced.

The icon displays just fine in the Debian based and Red Hat based distros (see here the corresponding files: https://github.com/GyulyVGC/sniffnet/tree/main/resources/packaging/linux).

I didn't personally packages it for Arch Linux.
Maybe @orhun, the package maintainer, can tell you more about this, as I think the problem could reside in how the app was packaged for Arch.

[Digitalone1]

Did you test on Gnome Wayland?

[Digitalone1]

Look, I replaced the content of this desktop file (the custom Arch one uses the keyword key and different categories).

Even tried to reboot the system, but the icon is still not showing.

I don't think the package is built in a different way you normally do. You can see here: https://gitlab.archlinux.org/archlinux/packaging/packages/sniffnet/-/blob/main/PKGBUILD#L26-43

I don't know what this post install is doing: https://gitlab.archlinux.org/archlinux/packaging/packages/sniffnet/-/blob/main/sniffnet.install

setcap cap_net_raw,cap_net_admin=eip usr/bin/sniffnet

But I don't think it's related to the menu.

I can confirm, at least on Gnome Wayland 44, the dash can't see the name of the application and its icon.

[GyulyVGC]

Did you test on Gnome Wayland?

Nope

I don't know what this post install is doing: https://gitlab.archlinux.org/archlinux/packaging/packages/sniffnet/-/blob/main/sniffnet.install

setcap cap_net_raw,cap_net_admin=eip usr/bin/sniffnet

But I don't think it's related to the menu.

It has nothing to do with icons, that script just sets the capabilities to inspect a network adapter.

I can confirm, at least on Gnome Wayland 44, the dash can't see the name of the application and its icon.

I'm not able to try the app on Gnome Wayland right now, so I cannot troubleshoot it at the moment.
Luckily it's a minor usability issue, but if you discover something new please let me know.

[Digitalone1]

I'm not able to try the app on Gnome Wayland right now, so I cannot troubleshoot it at the moment. Luckily it's a minor usability issue, but if you discover something new please let me know.

As I pointed out, this issue could be resolved setting an app_id.

Unfortunately I'm not expert with Rust, otherwise I would have tried to test the library. Anyway, can you try to set an app id?

Should be the id property here of the Settings structure attached to the window instance: https://docs.rs/iced/latest/iced/settings/struct.Settings.html

Winit has this method to set it: https://github.com/elinorbgr/winit/blob/5643865387d805ae7557af2c491deafe11ce97fa/src/os/unix.rs#L229-L234

Should be something similar for iced.

[GyulyVGC]

Sure, I will set that field to "sniffnet".
I will ping you at the next release to know if it's enough to solve the issue.

[Digitalone1]

Sure, I will set that field to "sniffnet". I will ping you at the next release to know if it's enough to solve the issue.

Is there a way to test the application without installing the build files under /usr/? So I can test soon after you make the commit, without waiting for the next release.

Arch package is built with cargo build --frozen --release and it seems to build the executable under ``target/release/sniffnet`. Can you confirm? Sorry if I'm not an expert, the only builds I tested are for C++ apps.

[GyulyVGC]

Done.
Oh sure, if you have Rust installed you can clone the repo and build yourself with cargo build --release (I've never used the --frozen flag).
The executable will be in the directory you mentioned.
Then you can move that executable in usr/bin to test the behaviour.

[Digitalone1]

Nice. That was the cause of the issue. Resolved.

[GyulyVGC]

Wow, thank you so much for having let me know about that id field 🥇